lostinwhere

Glad I could help.

There have been changes to the BA2 archives in the game. If your StarfieldCustom.ini or any other .ini file has an Archive section with old entries, you'll get this problem. My StarfieldCustom.ini only has these two lines: bInvalidateOlderFiles=1, and sResourceDataDirsFinal=. I started getting the same distant LOD issues after the 1.13.61 update. It was being caused by a mods .ini file that contained the usual long list of BA2 archives. The problem was, the list was outdated and contained a couple of BA2 archives that Bethesda removed and didn't have one or two new ones. The Starfield.ini file that's in your root directory should have the correct list under the Archive section. I believe the Starfield.ini is generated by the game itself and contains the correct list and nothing else.

No idea what's going wrong with your game. I do know that when I upgraded, there were three files that did not install correctly. The files were libxess.dll, steam_api64.dll, and one other. I had to do the verify the integrity of my game files thing to get those installed correctly.

Your StarfieldCustom.ini is located here: C:\Users\username\Documents\my games\Starfield. Also note that this file is something you have to create on your own. If you're new to modding Starfield, take a look at this video to get you going:

Yes

The StarUI series of mods have been updated, definitely not all other UI mods. The one that caused my issue, Scanner Encumbrance Display hasn't been updated since September of 2023. Edit: The original Scanner Encumbrance Display with Time mod by YoddleBerry, has been taken over and updated by PunishD and is now called Scanner Encumbrance Display with Time Updated. He just updated it today to compatible with 1.14.70 Shattered Space.

When you say "not able to interact", do you mean that when you try to open a door for instance, you can no longer do that? If so, do you have any UI, "user Interface" mods installed. Adding the lines bInvalidateOlderFiles=1 sResourceDataDirsFinal= to your StarfieldCustom.ini wont cause any issues in itself and is actually one of the first steps in setting up your game to load loose files for modding. What was discovered with the last update, was that certain UI mods like Star UI Inventory, Enhanced Healthbar, Scanner Uncumbrance Display and other UI mods were causing the activate key to go dead. Some of these mods have been updated, some may not have.

I've been using the over powered version since it came out. It's still working for me. I just tried it at Akila. I was able to shoot those floating Baleen Rotifer's out of the sky when they were so far away that they were just little specks in the distance.

Have you tried console commands like disable or mark for delete? Or does the thing just respawn every time you land?

The current version of the game is 1.13.6 not 1.12.36. It's also going to update in a few days when Shattered Space comes out. What version are you running and what source are you getting these from?

Yup, as soon as I started playing this game, I saw the similarities. Unfortunately, it was a short lived series that never expanded into a franchise.

Yeah, but the problem is that mod that he's referencing still has install instructions advising the use of the sTestFile method of activating the plugin. I've seen other new modders run into problems recently due to following old, outdated install instructions.

Do not use sTestFile entries in your Starfield Custom.ini file. Any mod that is recommending the sTestFile method for activating their mod is using outdated information. Do not use .esp plugins in the game. That mod has an updated .esm file that is now compatible with the game. For reference on what plugins are compatible with the game:

https://aka.ms/vs/17/release/vc_redist.x64.exe That's the link to the latest Microsoft Visual C++ Redistributable.

When you start the game, go into Settings, then Bindings. Scroll to the very bottom where you have your Vehicle bindings. See what's set for POV, Zoom In and Zoom Out. If none of them are working, re-assign new bindings and try again.