Thanks.

My specs:
i7-5820k @3.5GHz
2x GTX 980 SLI
16mb ddr4 ram
Also have the game stored on a 3TD HDD, not an SSD.
Correct me if I'm wrong, but didn't Fallout 3 have these things called Static Collections? It appeared, from reading the GECK article, that it's a form of runtime static batching, where statics are grouped into one 3D model, thus reducing the draw calls. That functionality was removed from New Vegas for one reason or another. Supposing that the static collections were treated as a single model, and not just a convenience thing that treated multiple game objects as a single one (NOT the same as combining 3D models!), that would offer potentially large reductions in draw calls.RoyBatty wrote: ↑Mon Mar 18, 2019 5:30 amI'm working on improving performance. It's heavy having two entire games and DLC, plus yes the object LOD is a tad heavier but shouldn't make much notice. I did test some areas like Point Lookout in Fallout 3 vanilla and the frame rate was pretty bad there too. My machine is no slouch, 1080ti+i4790k etc.
I just have to optimize the worldspaces, the lighting engine changes seem to be the most change or something else with how havok or rendering is handled in DC. In Vegas I maintain the stable framerate I get in vanilla. Fallout 3 is just more complex I think.
I imagine that with the capabilities of NVSE and JIP there's room for vanilla scripts to be made much more efficient. Hell, we have event handlers now.RoyBatty wrote: ↑Mon Mar 18, 2019 7:41 amNew Vegas still has and uses quite many static collections and you can create them in GECK, I have done so when working on optimizing Point Lookout. It requires more work than that though to remove unseen faces, merge the havok together and remove useless collision bodies, welding everything, fixing the normals and a lot of other work. Optimizing is time consuming and a lot of work to do correctly so it's low on my to do list, however I will get to it. Part of the problems are just badly optimized meshes in Fallout 3, which I address over time. There's endless things to fix/optimize in this game.
Thanks for the response Roy! Do you have any temporary suggestions in the mean time for improving performance? FPS is mostly bad when in larger fights such as during Operation Anchorage in the trenches, or in Big Town. I adore your work and thank you very much for any support that can be given.RoyBatty wrote: ↑Mon Mar 18, 2019 5:30 amI'm working on improving performance. It's heavy having two entire games and DLC, plus yes the object LOD is a tad heavier but shouldn't make much notice. I did test some areas like Point Lookout in Fallout 3 vanilla and the frame rate was pretty bad there too. My machine is no slouch, 1080ti+i4790k etc.
I just have to optimize the worldspaces, the lighting engine changes seem to be the most change or something else with how havok or rendering is handled in DC. In Vegas I maintain the stable framerate I get in vanilla. Fallout 3 is just more complex I think.