This mod does not affect precombine/previsibine eventhough some static objects have been replaced. Two versions are available: 1) Replacer of objects not PreCombined by the game. This casts some interesting search and loot mechanics by itself, since not all raider bodies can be activated, used as a container. 2) Replacer and adder. The latter adds a rescaled (+0.01) raider body on top of the default raider body. This version affects ALL raider bodies in game world.
gedward1 technically possible, if i would replace the bodies with real NPC bodies and alter the ragdoll data to mimic the original static objects. then you would be able to replace the clothes OR in case of a settlement decoration trip you would likely make a "statue" out of the bodies similar in function to the armor and clothing dolls which are available by default. for now thats to much work to be worthwhile.
Maybe you could use Base Object Swapper to replace the bodies? That might make compatibility easier to work out, seeing as how users might have other mods that modify the same cells that you're mod modifies.
I'm definitely going to do that on my end for myself later, regardless. Really cool mod!
I hear about Base Object Swapper but for now i will stick to my current technique. Since its not just fire and forget. Alot of the bodies are PreCombined which i had to purge in the first place. Now you only see those few bodies left which are not precombined. If i would use a script and i suppose thats what Base Object Swapper is all about i would find myself of replacing Non- and PreCombined objects which i would have to check manually in the end to avoid conflicts. Correct me if im wrong.
Afaik, stacking multiple mods that modify CELL and WRLD records is not a problem. The main record is overwritten, but the data there is irrelevant as long as it is only about objects within the cell.
Example:
> Cell
> Block 0
> Sub-Block 6
> 000C9D24 MassStateHouse01 - "Main Record"
> Temporary
Same logic applies to Worldspace (WRLD).
The data in Temporary is relevant, sometimes Persistent. But the main record can show conflicts. Most of the time its just a PreVis and/or PreCombined Timestamp conflict of Vanilla and DLC. Which you need to patch of course. Everything else depends on the mods, sound files, locations reference etc.
For the raider corpse replacer its just about Temporary. Afaik these edits should hardly force problems if you dont get wild with your load order.
Oh, alright. You say that you had to purge the bodies that were precombined, and that you haven't broken precombines to the other commentor, but wouldn't disabling or deleting them cause the precombines to break? Unless I just don't understand what you meant by "purged". Maybe I'm just misunderstanding.
Also, with Base Object Swapper you can just swap the original static base object with the new container base object, and it'll replace all of the old statics that aren't part of any precombines. Precombined objects however won't be replaced automatically, but maybe it would if you removed their corresponding precombined object entries.
Also, with Base Object Swapper you can just swap the original static base object with the new container base object, and it'll replace all of the old statics that aren't part of any precombines. Precombined objects however won't be replaced automatically.
That sounds pretty clever. It would kill the fun factor for me though, when digging through the game files. You can always find something new. Be it CK or FO4Edit. I will come back to BOS when i have the time.
You locked my comment so I can't reply but I would appreciate a yes or no instead of just showing me what I already read. I haven't made a precombine/previsibine before, so I don't know what "are not marked [Placed Object]." means, but based on your file saying it affects CELL and WRLD records, I was thinking it might interfere with precombines/previsibines.
Again a clear yes or no would be helpful for me, as well as anyone else coming here looking for the same info. Appreciate it in advance.
EDIT: I'm more specifically asking if this would interfere with PRP, or similar mods.
Okay cool thanks. Didn't mean to be hostile at all if I came off that way, just wanted to get a clear answer. Really like the idea of the mod, and it would have been really unfortunate if it did break precombines/previsibines.
PRP should alter the cell worldspace main records. Im not sure if they precombine certain static object more or less in this regard. If those overrides in my mod are precombined by PRP then well my mod will probably not work if you load it before PRP. If you load my mod after PRP it will affect PRP.
But all of this are speculations. You should check it yourself in FO4Edit. It takes only a few minutes to browse.
Yw. The problem with Fo4 is, its extremly L2 and more likely L3 cache sensitive since it loads so much objects in real time. Even today it can wear certain hardware down.
Afaik, PRP, precombines/previs itself will avoid that since the engine will lower rendering in real time since well the objects are precombined. The problem with Boston is the amount of objects thrown around to render.
From my understanding if your hardware has enough L2/L3 cache which is affected based on your total number of mods and of course what those mods do, you can lean back at some point ...
That was back in the DDR3 era.. with DDR4 it stopped scaling around DDR4 3000 MHz on my 8700K from DDR4 3000 which I run now vs 3666 MHz there is zero FPS difference. still dips to the same lows. It did scale quite well with memory back in the day but memory bandwidth on modern systems is high enough that its back to being thread limited. Going from 5 GHz on my 8700K down to 4.6 now had a bigger impact than the ram. So yeah it scales with a memory to a certain point but not so much now. Latency can have an impact as well as L3 cache in fact L3 cache is likely the biggest factor anything that doesn't fit into cache will get pushed to the system memory so Ryzen X3D chips will likely have bigger gains. But the biggest benefit is if you use a Core Affinity app and set the game to just run on set cores with no HT. tends to smooth things out and stops the game from swapping between so many cores on which its single thread bound anyway. So while it will distribute load the 1 important thread is the main culprit. If you can't scale clock speed then scaling bandwidth helps but suffice to say the game is still a buggy mess on ancient code.
As it is with the 7950X3D with same settings etc vs a 7950X with higher clocks but same memory the extra cache shows a 20-30% improvement in performance. Game wants to nom nom on more L3 cache to keep the CPU thread properly fed with data. Faster memory helps but will never compensate for that.
Thank you that was all very informative. Also as far as I can tell this mod doesn't affect PRP at all. So that's good to see. That quote may weigh heavily into my next CPU upgrade though if I'm being honest.
28 comments
1) Replacer of objects not PreCombined by the game. This casts some interesting search and loot mechanics by itself, since not all raider bodies can be activated, used as a container.
2) Replacer and adder. The latter adds a rescaled (+0.01) raider body on top of the default raider body. This version affects ALL raider bodies in game world.
I'm definitely going to do that on my end for myself later, regardless. Really cool mod!
Afaik, stacking multiple mods that modify CELL and WRLD records is not a problem. The main record is overwritten, but the data there is irrelevant as long as it is only about objects within the cell.
Example:
Same logic applies to Worldspace (WRLD).
The data in Temporary is relevant, sometimes Persistent. But the main record can show conflicts. Most of the time its just a PreVis and/or PreCombined Timestamp conflict of Vanilla and DLC. Which you need to patch of course. Everything else depends on the mods, sound files, locations reference etc.
For the raider corpse replacer its just about Temporary. Afaik these edits should hardly force problems if you dont get wild with your load order.
That sounds pretty clever. It would kill the fun factor for me though, when digging through the game files. You can always find something new. Be it CK or FO4Edit. I will come back to BOS when i have the time.
I haven't made a precombine/previsibine before, so I don't know what "are not marked [Placed Object]." means, but based on your file saying it affects CELL and WRLD records, I was thinking it might interfere with precombines/previsibines.
Again a clear yes or no would be helpful for me, as well as anyone else coming here looking for the same info. Appreciate it in advance.
EDIT: I'm more specifically asking if this would interfere with PRP, or similar mods.
No it does not affect precombine/previsibine.
Really like the idea of the mod, and it would have been really unfortunate if it did break precombines/previsibines.
But all of this are speculations. You should check it yourself in FO4Edit. It takes only a few minutes to browse.
Afaik, PRP, precombines/previs itself will avoid that since the engine will lower rendering in real time since well the objects are precombined. The problem with Boston is the amount of objects thrown around to render.
From my understanding if your hardware has enough L2/L3 cache which is affected based on your total number of mods and of course what those mods do, you can lean back at some point ...
That quote may weigh heavily into my next CPU upgrade though if I'm being honest.
Afaik, BETH goes for AMD for Starfield. Might not be a coincidence with the L3 Cache ...