2026-03-16T00:14:38 Little bit of an odd specific case thing I ran into earlier today – I've taken to using Niri (the wayland scrolling tiled window manager) over the past week or so, and when I come out of OpenMW (eg. to check the UESP) it loses its fullscreen-ness, and reverts to a standard Niri tiled window. Going into settings and switching to windowed then back to fullscreen fixes it (until i go out again). I haven't run into 2026-03-16T00:14:38 this issue with other fullscreen games, they handle being in the scrolling environment fine (so far). 2026-03-16T16:12:11 <.arrean> Been looking through the server for references to background physicss thread Why no more than 3? Won't it be dependent on the specifc cpu? 2026-03-16T16:15:15 If you search for intern Hemaris posted a good explanation the other day. 2026-03-16T16:15:39 The gist is that sometimes it takes more work to delegate work effectively than it would just to do it yourself. 2026-03-16T16:16:48 <.arrean> That's fair, but 3 reads as oddly specific to me. I'll try and find that explanation 2026-03-16T16:18:26 <.arrean> Right, I see it - normal scheduling/threading stuff. I'm more interested in how the specific number 3 was arrived for this specific use case 2026-03-16T16:24:27 You try different numbers and see which number works best. 2026-03-16T16:28:58 <.arrean> Right, and that would depend on cpu 2026-03-16T16:29:02 <.arrean> and other variables 2026-03-16T16:29:33 <.hemaris> i tried finding the past discussion i was remembering, and it turns out to have been about preload num threads 2026-03-16T16:29:41 <.arrean> I'll take that was just a genereal guideline 2026-03-16T16:30:13 <.arrean> Ah, so it was not even about this var specifically :D 2026-03-16T16:30:32 <.arrean> I guess 3 works too. On my rig at least 3-4 are best anything over seems to be detrimental 2026-03-16T16:31:28 <.hemaris> the marginal benefit drops to zero as soon as physics is no longer the bottleneck on your frame times 2026-03-16T16:32:10 <.arrean> Ye, so -> slower gpu, no sense in maxing out physics thread, cause you're limited elsewhere 2026-03-16T18:28:46 Anyone have any idea why the merge plugins would not recognize one particular file path? It happened with both delta and tes3merge lmao 2026-03-16T18:37:06 Hi! I searched around but didn't see mention of this - I've got openmw running with no mods yet. Enabled controller menu and if I click on the side of the inventory as if to resize it, it crashes the game. Is this known or a way to prevent it ? Not a big deal but probably could cause a lot of accidental crashes 2026-03-16T18:42:27 Crashes are always a problem with OpenMW, and should always be reported through the issue tracker like the popup says. 2026-03-16T18:44:12 This specific one is fixed in dev builds 2026-03-16T18:50:50 no idea what pop up you mean and figured this one was addressed somewhere since it's readily apparent 2026-03-16T18:50:55 thanks 2026-03-16T18:51:20 are those safe to use ? or I should just avoid clicking the menu 2026-03-16T18:52:12 Safe-ish? 2026-03-16T18:52:20 anyone know what these errors could be referencing? [18:46:43.216 W] ReadDDSFile warning: Vertical flip was skipped. Image dimensions have to be multiple of 4. [18:46:43.717 I] BulletNifLoader: RootCollisionNode is not attached to the root node in meshes/rr/_gg/rp_gg_statindor.nif. Treating it as a NiNode. [18:46:43.731 I] BulletNifLoader: RootCollisionNode is not attached to the root node in 2026-03-16T18:52:20 meshes/rr/_gg/rp_gg_statredoran.nif. Treating it as a NiNode. [18:46:43.908 W] Warning:: Compressed osg::Image not a power of two, cannot apply to texture. [18:46:44.465 I] NiTextureEffect missing source texture in meshes/x/terrain_rock_ma_09.nif 2026-03-16T18:52:27 Generally, it's sensible to use dev builds unless you're more scared of regressions than going through the tedium of dodging known bugs. 2026-03-16T18:52:40 It is very apparent but it actually took a while to address 2026-03-16T18:52:49 No errors in that snippet, just warnings. 2026-03-16T18:52:58 happy to use them, im an experienced modder/game dev, where they at though 2026-03-16T18:53:07 At the downloads page 2026-03-16T18:53:14 If you're not the mod creator, generally you don't need to care about those warnings. 2026-03-16T18:53:36 ok, no problem. Can I safely ignore them? 2026-03-16T18:54:29 last q, I know y'all probably hate MO2 but I am a diehard fan soooo, can someone confirm that you can build the list in MO, use the export plugin, and then run the openmw exe from MO2 (not the launcher) and all should work properly with that setup ? 2026-03-16T18:54:53 yes 2026-03-16T18:54:56 thanks for making this, I get to be 13 again woo 2026-03-16T19:07:20 how do I fix the issue where transparent objects look invisible with VAIO clouds and sky rendering enabled. I have transparent postprocess active but it still looks off 2026-03-16T19:10:13 that's the near part, you don't :todd: 2026-03-16T19:11:10 dayum 2026-03-16T19:11:27 but the rendered sky looks so nice 2026-03-16T19:11:34 😭 2026-03-16T19:11:47 unfortunately nothing that you can do to fix this on your side 2026-03-16T19:12:11 except beg the author to make the fog not a postprocess shader 2026-03-16T19:13:25 its not even the fog its everything else lol 2026-03-16T19:13:37 like spells and just spotted the ghostgate fence looking weird 2026-03-16T19:14:26 yes, anything with depth writes disabled will look broken 2026-03-16T19:15:50 ok makes sense, any recommendations for something I could use as an alternative to the rendered sky and clouds? 2026-03-16T21:17:33 You shouldn't be launching OpenMW from MO2. Use MO2, use the export plugin, and then launch through the launcher 2026-03-16T21:41:44 I get frequent freezes and crashes in a very sparse load order (only the one lua mod I am making). Is there a good place to share my crash and freeze .dmp files, and the openMW log? 2026-03-16T21:41:53 There's no reason to use launcher. 2026-03-16T21:42:38 Maybe you can register Steam to know MW is playing that way, but other than that there's no reason. 2026-03-16T21:46:08 I meant OpenMW launcher 2026-03-16T21:46:17 See previous post 2026-03-16T21:47:59 I meant that too, you don't need that. 2026-03-16T22:47:26 <.arrean> issue tracker. 2026-03-16T22:48:13 <.arrean> Devs generally hold to "any crash or freeze is an openmw issue and should be reported on the tracker" so go for it 2026-03-16T22:52:29 Thanks!