You can see weatherid in interiors in statistics of the mod. Depending from it every location looks different, obviously.Is the worldspaceid the same thing as the strings that I posted in my code example? Also, I'm not sure why someone would want to mix the weatherID with the worldspaceId. Does weather affect interiors? Even if it does in some dungeons where you can see outside, I would still rather have interior customization than proper interior weathers. Just my humble opinion of course.
keithinhanoi
ReduceSystemMemoryUsage is my memory manager.When you say "memory manager" are you talking about:
1. Your ENBoost dynamic memory allocation features using enbhost.exe (enabled with speedhack=true & ReduceSystemMemoryUsage=true in enblocal.ini)
....or...
2. Your alternative video memory manager (enabled with DisableDriverMemoryManager=true in enblocal.ini)
Tuoni
This parameter do not modify size of memory blocks, it just defragment memory.
Aleksandr
Well, you right. But i got a lot of reports with skse alpa, similar to previous regarding my own bugs. Also i have issues with ECE, it not work when executing "showracemenu" with ExpandSystemMemoryX64=true and SKSE alpha. Maybe it's incompatible with SKSE and require update, don't know.Before people spend ages doing something that might be a complete waste of time, how many people are actually reporting problems with ESMx64 and SKSE 1.7A? Is it just that one guy in this thread? Because if so, then it's that guy who should be doing the testing.
It was false by default. And what? Doesn't matter, the same as users do set memory size 16384 and other bullshit.Boris had no need to remove it at all, having an off switch anyone can use ( false setting )
pangallosr
Good find. But DisableDriverMemoryManager depends from videocard model/vendor and OS.
keithinhanoi
No, it's different. I'm handling only part of the video memory management, in most cases driver developers know better way how to allocate resources (but amd driver developers are awful, check out papers about decompiling drivers), compared to 10 years old directx9. If DisableDriverMemoryManager=true, dx9 handling part of resource allocations and it use for that not very nice obsolette functions.Changing DisableDriverMemoryManager to false means you're now using your video card driver's memory manager, instead of the video memory manager that Boris made.
Madpaddy
Anyone else have this?I also found another strange thing, don't know if anybody else has it, but if UseProceduralCorrection= is set to true my game will load fine to the start screen but will crash if loading or starting a new game.
To all
I can't restore ExpandSystemMemoryX64, this is not my bug, but the other code which is incompatible. The game itself, skse plugins or something else - i don't know, this is hard to find. Seems one of classic bugs when LAA enabled for software which not designed for it. If you want this to be back, do the tests which mods produce issue, ask authors to fix, then it will be done, i'll restore it.
Btw, ExpandSystemMemoryX64 do not affect stuttering and performance (at least to be noticable in game), if it do, something is very wrong. The difference is just how memory blocks aligned and where. With crappy game memory management it do the trick by splitting different memory allocation functions to not produce heavy fragmentation when they are used together (fragmentation of RAM is not the same as HDD, read articles).
