the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Question Invisible Meshes and stretched/corrupted objects

markraza

New Member
Messages
7
Hi all,

I had a pretty heavy load order, but decided to give SS a shot finally and had ALOT of issues with invisible meshes and stretching/corrupted objects.

To troubleshoot:

1. I had NMM uninstall ALL mods and then I did a completely fresh install of FO4 with all DLC. (deleted Applog fallout4 folder, Documents and settings, and the fallout4 folder from steam).

2. Next I installed F4SE (for version .163) and did a test load to get the .ini built and the gfx settings saved.

3. Then I used NMM .71.0 to install only MCM(1.39), Hud-Framework (1.0f), WorkshopFramework (1.1.9) sim-settlements 3-1 (4.2) and conqueror (4.2).

4. To test, I started a new game and chose the defaults and let conqueror prebuild the settlements before exiting the vault.

Upon exiting, I went straight to Abernathy farm and the same various fences and walls were still invisible. The collision was there like before, but the mesh was invisible.

I used MCM to create a holotape and initiated a city rebuild. This resulted in different invisible meshes and ALOT of stretching/corruption.

It seems like it's mostly the walls and wire fences and an occasional post (the most southern that has a power conduit on it). I then retested with first the .ini IMemoryMax edits from the SS wiki and then again with Enboost (memory set to 16384) added in. The results are unchanged.

System Specs:

6700K
32GB RAM
2x 980Ti (SLI)
N.2 SSD

v-sync enabled. (VRAM usage in Abernathy: 4GB out of an available 6GB/card.)

Any help ANYONE can provide would be greatly appreciated.
 
Thanks, MrCjohn

I lowered my Enblocal to 8192 and restarted and refreshed the city plan. Unfortunately, the problem persists.

I also, downloaded and manually installed the 4.2.1 files for both the sim settlements 3-1 and conqueror after uninstalling and deleting the 4.2 files. This resulted in no improvements.

I did manage to track down these older posts where the user appeared to have the same issues:

(can't share links - user account too new)

It appears this user was also using graphics cards with SLI. They fixed it by enabling Vsync, which I already have enabled.

Another user stated they were using SLI without issues, though. I'm at a real loss, here.
 
Thanks, MrCjohn

I lowered my Enblocal to 8192 and restarted and refreshed the city plan. Unfortunately, the problem persists.

I also, downloaded and manually installed the 4.2.1 files for both the sim settlements 3-1 and conqueror after uninstalling and deleting the 4.2 files. This resulted in no improvements.

I did manage to track down these older posts where the user appeared to have the same issues:

(can't share links - user account too new)

It appears this user was also using graphics cards with SLI. They fixed it by enabling Vsync, which I already have enabled.

Another user stated they were using SLI without issues, though. I'm at a real loss, here.

Turn of your SLI … another user turned it off and fixed their issue.
John
 
UPDATE: disabling SLI completely fixes the issue for me.

But, this actually has a pretty noticeable impact on my frame rate. Is there ANYONE running SLI with Sim settlements (Nvidia) without issue? If so, can you share which SLI profile you're using and possible which application mode you're using?

I guess the real question here is:

"Is Sim Settlements compatible with SLI?"
 
FINAL UPDATE: Setting SLI Configuration to "Single GPU" is the fix.

Using the DDU utility, I fully removed my Nvidia drivers and settings and registry entries from my and PC and re-installed with version 26.21.14.4187. Then I set power management to "Prefer Maximum Performance".

I then tested with the following SLI configurations and here are my final results:

1. "Nvidia Recommended" 40 FPS, Invisible Meshes
2. "Force Alternate Frame Rendering 1" 11 FPS, No issues with meshes
3. "Force Alternate Frame Randering 2" 35 FPS, No issues with meshes
4. "Single GPU SLI" 40 FPS, No issues with meshes

So, going forward, I will be using option 4 above. It should be noted that "Single GPU" is not the same as SLI Disabled. It just means that the processing is handled on one GPU at a time instead of slitting between the 2. In this configuration, card 2 is still sharing the load - in more of an overflow style - instead of balancing the load between the 2.

@kinggath, this may be useful information to add to the troubleshooting sections of the website in case other SLI users run into the same issue.
 
I would assume this is related to Static Collection objects, as those are the only thing we're making heavy use of that most mods don't.

Very bizarre that SLI would have anything to do with those - but we've noticed that hardware combinations can be pretty important to the success or failure of people's Fallout 4 experiences. This is actually the number one reason I'd like to see Bethesda move to Unity or Unreal.
 
Top