Can I lower uGridsToLoad from 5 to 3?

[FrancisRossi]

What happens if I lower this setting in .ini file? The game brokes or something? Anyone tried it?

[SpeedFreak1972]

Not sure I guess nothing however most of us want increase the ugrids not decrease so I'm not certain also spawning points may be affected.

[loverevolutionary]

Why would you? Doing so will mean only nine cells are fully loaded at a time, rather than twenty five. Nothing further away than the very next cell will ever be loaded, your sniping distance will be cut in half because enemies further away won't be loaded. If it works, it will probably dramatically increase your framed rate, but break your game in six dozen different ways.

[Jackal]

thats the 1 setting you should never change, ever. it will break your game and your saves

[Drua]

grid change is a bit dangerous, savegames can be damaged and other issues, the engine can be instable in the worst case, backup savegames and ini files and try it

[Dominic]

Originally posted by Jackal:

thats the 1 setting you should never change, ever. it will break your game and your saves

I have ugrids set to 7 for over 200 hours. I guess my PC will catch fire and my OS will strangle me in my sleep now?

[SpeedFreak1972]

Originally posted by Jackal:

thats the 1 setting you should never change, ever. it will break your game and your saves

Nope I played for more 2k hours with ugrids 7 in skyrim and all saves survived. However if you increase it don't push it.

[FrancisRossi]

I want to do this because when the game loads new areas, the fps stutter a lot... And is annoying. I tried it and I get better fps.

[You Kissed a Boy and Liked It]

Old thread, but for those interested: I use 7 uGrids with little to no discernible CTD issues. Trying "9" did work... but then started to crash after a while -- eventually getting to a point where it crashed 10 seconds after re-loading. (*Noticed it ran okay at night, but daybreak brought with it CTD's -- methinks because it renders more [visible] objects in the day, than at night time). It also incorporated some frame rate drops in open areas surrounded by cities.

The uGrids parameter loads the active areas of the map -- i.e., the "sphere of interaction". So, in effect, "high" settings (9+) will let you snipe enemies that you can barely discern the type of, from long distances (*provided you have an applicable "increased projectile range" mod enabled). Lower settings mean that (i) stuff does not load in as far from the player and (ii) even loaded stuff may not be interactive (e.g., cannot be killed).

It's actually the most important function for immersion, IMO: as stuff being non-interactive breaks immersion, while stuff happening all over the map, imbues a sense of a living, breathing world.

The GTA games always let me down in this respect: anything beyond a couple of blocks around the player was non-interactive. Thus, the likes of sniper rifles were only a novelty and a video game-y way of avoiding direct confrontations (as distinct from a realistic tool of disposal).

Most players likely don't even notice such things, as they just run into close combat for mish mash mauling orgies. But, the "sphere of interaction" always concerned me, as far back as GTA: Vice City, so FO4's uGrid function really piqued my interest.

Hopefully future game engines are robust enough to incorporate worlds that are big enough to go to the bounds of player viewing distances, thereby presenting a faultless level of immersion (with respect to world size / interactivity).

[K i r k H 4 2 0]

I've been using uGridsToLoad=9 for months and i'd say that the majority of any CTDs that my game experiences are most often related to the workshop. Someone experiencing more crashes at day than at night, I would suspect your Godrays settings might need tweaking or turned off. Increasing the uGrids setting is raising the cutoff point at which surrounding objects will load based on their proximity to the player character. If raising this number is causing crashes, it'd be logical to consider that maybe the crash is caused by something else but now you're just loading that area when you are not even walking close to it yet.

I've read some say that you can't reduce this number once it's been increased and a new gamesave has been made. I tested this, changed my uGrids from 9 down to 7 and there were no noticeable affects, saves loaded up right away. I'm not saying that YOU should do it, I'm just saying that my GPU didn't burst into flames.

Using MSI Afterburner's overlay to watch my GPU's VRAM filling up during the loading screens, there isn't actually a noticeable difference in MB. There's probably a point of diminishing returns as far as pushing uGrids up to 9. Are the returns worth the issues it can cause such as scripted events triggering early?

[Draekus2]

Originally posted by K i r k H 4 2 0:

I've been using uGridsToLoad=9 for months and i'd say that the majority of any CTDs that my game experiences are most often related to the workshop. Someone experiencing more crashes at day than at night, I would suspect your Godrays settings might need tweaking or turned off. Increasing the uGrids setting is raising the cutoff point at which surrounding objects will load based on their proximity to the player character. If raising this number is causing crashes, it'd be logical to consider that maybe the crash is caused by something else but now you're just loading that area when you are not even walking close to it yet.

I've read some say that you can't reduce this number once it's been increased and a new gamesave has been made. I tested this, changed my uGrids from 9 down to 7 and there were no noticeable affects, saves loaded up right away. I'm not saying that YOU should do it, I'm just saying that my GPU didn't burst into flames.

Using MSI Afterburner's overlay to watch my GPU's VRAM filling up during the loading screens, there isn't actually a noticeable difference in MB. There's probably a point of diminishing returns as far as pushing uGrids up to 9. Are the returns worth the issues it can cause such as scripted events triggering early?

you know this thread is 8 years old, right ?

[UsernameTaken666]

lmfao. at least the person who raised this from the dead got more comments. sigh.
clearly their input was valuable enough to necro it. /S /S