Camera movements very choppy since BH patch
Hi, I have a problem that started since the BH patch, that during Sims day time moving the camera, especially rotating it, or panning through the world becomes incredibly choppy, to a point that the ...
Forum Discussion
karoschmitz Thanks so much for the extra info. I've forwarded your thread both for the overall performance improvement (and the original problem) and concerning the error we've been seeing in macOS. I added TS4CommonRules to ConfigOverride and got around the error, and I separately tried deleting the include "Ts4CommonRules.sgr" line, which worked as well.
If you do narrow down the source of the issue to certain settings, I would love to hear about it. One thing to note is that in theory at least, you shouldn't have to change both RenderSimLODDistances and RenderSimTextureSizes, just one or the other. If all LOD values are the same (the latter), then it shouldn't matter at what distances the game switches between them (the former). However, if the problem is the calculations required to perform the switch, you could see a hit when editing only the latter values.
I did patch just now, and GraphicsRules.sgr didn't change, so the edits you've made are not part of the performance improvements called out in the patch notes.
Oh thank you so much for sharing, that's great to know!! What a pity about the patch though, I was really hoping the team might have already fixed the issue by chance, given we rarely get performance updates hehe.
Awesome, I'll put the test on my list to try skipping the change of the RenderSimLODDistances to see if this would make a difference. I assumed those 4 distance values are telling the game what camera distance thresholds are making the Sim render with their LOD0-3 meshes, and that the SimTextureSize maybe just applies to the actual textures that are applied to the meshes. But I'm only making assumptions from the little bit of CC creation that I have learned, will definitely test one without the other!
Ah nice that the include work-around worked! If you delete the include line in GraphicsRules I would assume the error goes away, as it doesnt try to find this file anymore, but it will then be missing all the Common graphic rules that the GraphicsRules file is expecting. I could imagine that this might cause unexpected graphic outcomes. An include, at least in other programming languages, usually tells a program to load and process the contents of the file as if it were part of the current file, and the GraphicsRules might be expecting those values. The safer option is probably to keep the include line intact and copy the original Ts4CommonRules.sgr together with the GraphicsRules file into the override folder, to make sure all expected values are still provided to the game. Unless the override folder doesn't replace previously loaded resources but only adds to them, then it wouldn't really matter :)
I'll give the game another spin with a partial edit of the file! Yesterday I used my Mac to update to the latest patch (while keeping my PC waiting for mod updates this week) but the M1 laptop is so slow that it is hard to even measure the performance, as it already only reaches 35-50 fps without even having Sims spawn into neighbourhoods yet. The whole experience there is stuttery all the time, hard to distinguish if it got any better with the patch.. That's why I bought the PC in the first place and loved the fluent movements and high fps there, and got incredibly sad when the camera on my PC started stuttering so much suddenly after the BH patch update.
Community Highlights
- EA_Cade11 months ago
Community Manager
