Zedwimer

Success! The initial in-game & CK "visual" tests check out: So far, everything looks good. But now I'll test out everything else you mentioned (navmeshes, activators, trigger boxes, etc.) and I'll let you know how those go as well. Thank you so much sheson!

Thank you sheson! I'll give it a test today and let you know the outcome.

Thanks, I looked through it before but I'll check it out again in case I missed anything. One thing I didn't mention (but was implied) is that I'm creating an entirely new worldspace and not using the Commonwealth or any other DLC worldspaces. Also at this stage I haven't placed ANY objects/trees/etc. in the worldspace, I'm dealing with raw terrain only. Not sure if that helps or not.

I have a very strange problem that I have troubleshooted to the best of my own amateur ability with very limited success. Hopefully someone here may know what is causing this or can help track the solution down. To start with, I used TESAnnwyn to convert a DEM into an ESP for Fallout 4. The terrain cells load in the game and in the CK without issue, so my next step was to generate an initial batch of distant terrain LODs. The CK takes forever and tends to crash before it finishes the job, so when I found xLODGen recently, I installed it (version 97) and gave it a try. I'm still a relative newb to a lot of this, but I read through all the documentation and feel confident I was doing it right. I generated some terrain LODs and placed them into the proper subfolders in the Data folder... but when I loaded up the game or the CK, only the 16x and 32x LODs appeared, the 4x and 8x LODs don't show up. I tried re-running xLODGen several times, adjusting various settings, but nothing changed; the 4x & 8x LODs were "invisible" in-game and in the CK. They show up as generated in the logfile and all the 4x & 8x .BTR files have data in them (they're not all 0K). Eventually I got the idea to load some of them up in Nifskope... and that's where I made a breakthrough of sorts. All of my 4x and 8x LODs are missing their Z data. Every vertex has a "Z inf" coordinate and if I click into the Z coordinate, it converts it to "Z 1000000.0000". It is like this for ALL of the 4x and 8x LODs I sampled (I couldn't test all of them, but I did sample them randomly), while all of my 16x and 32x LODs have normal Z coordinate data. I did a search and couldn't find this issue elsewhere here in the forums or anywhere else on the Web. I don't know if this is an issue with xLODGen, with my ESP, or some fateful combination of the two. I am attaching my logfile here for reference, but I can also upload screenshots of what I'm describing above and/or I can make my ESP available if either would help. Or if there's anything you want me to try or more info you want me to give, please let me know. FO4LODGen_log.txt