miversen33
-
Posts
9 -
Joined
-
Last visited
miversen33's Achievements
Watcher (1/12)
0
Reputation
-
I did test that after I uploaded my previous comment. My original load order would usually generate a lod that was around 20Gb. I haven't tested that build on this yet since that takes a while, but I have noticed that removing the `-t` flag and setting the temp/tmp environment variables instead did seem to "work". Though I am not completely sure if it properly utilized the "new" temporary location yet, I suppose I will find that out when I try my full load order this afternoon. In any case, it seems that I have a workaround which is great. Any idea what would cause that flag to throw this error? I don't mind (in my case) shifting my entire OS temp directory to another location but that seems like a rather large ask for most users, especially when xlodgen has the ability to utilize a temporary directory via command line flags. I am more than willing to use my machine as a test bed for figuring that out if you would like or if you cannot recreate the issue on your side.
-
I've finally figured it out! The `-t` flag is what is breaking things. If I remove the `-t` flag, it works just fine. I didn't add the `t` flag in my test on my other machine because I only had one drive in there, so it didn't even occur to me that that might be what is going on. lots of logs TES5VRLODGen_log (no flags).txt TES5VRLODGen_log (using t and o flag).txt TES5VRLODGen_log (using t flag on same drive).txt TES5VRLODGen_log (using t flag).txt TES5VRLODGen_log(using o flag).txt I don't know _why_ the `t` flag is breaking stuff, and I do need it if I am going to generate lods for my load order as my `C:` drive is much too small (it's a 128Gb ssd). Some notes about the setup here. `C:` is a 128Gb ssd connected over SATA `D:` is a 2Tb nvme `E:` is a 500Gb ssd connected over SATA `F:` is a 4Tb ssd connected over SATA Its a hodgepodge of drives lol. But they are _all_ SSDs so this isn't some weird shenaniganry with spinning disks. And I even tried using the same drive that xlodgen is on as temp. It failed in all cases.
-
So this is crazy. I completely wiped my pc. Like, deleted everything on the c drive, reinstalled windows 10, and literally started over from scratch. Below is my load order Paste.ee - Load Order Regenerated xlodgen (log: Paste.ee - Lodgen logs) xlodgen flags: `-tes5vr -o:"F:\LodGen\xLodGen" -t:"F:\tmp\xLODGen"` With all of this shenaniganery, I _still_ have that black lod in the distance. No errors reported in the xlodgen but still no dice. What on earth am I missing? It worked on a completely different machine but for some reason I can't get it working on the actual gaming PC I am using. I am so very confused
-
Well, I completely removed any trace of Skyrim VR from my machine (including all saves and temp data), reinstalled it fresh, and I am still seeing the errors I was seeing before after copying the functional settings from my other machine. At this point this has to be OS based. I don't know what or why, but nothing else makes any sense. I have already disabled the only AV I have (windows defender). Before I do something drastic like completely blowing away windows and starting fresh, is there anything else you recommend I look at? Most recent "failed" lodgen logs https://paste.ee/p/CHxwclOH
-
> You reported the error also happens while running xLODGen outside of MO2, which I take means it was started while MO2 was not running. In that case it is typically more like an OS issue - and whatever tools tie into file access/reading. This is correct. I am reasonably convinced the issue is os basd. Not 100% yet, still working through a few tests. I copied the flags I used and xLODGen settings I used over to the "new" pc so in theory everything should have been the same. The only difference is that I did use MO2 to run xlodgen on the new pc (though without the wabbajack). My flags are simply `-tes5vr -o:"F:\LodGen\xLodGen" -t:"F:\tmp\xLODGen"`. Nothing crazy. I am currently installing MO2 and going to reinstall skyrim vr altogether. I want to see if just starting fresh without the wabbajack and portable (provided) mo2 instance will let this go through. Maybe after I have figured that out we can work back up to figure out what is causing the error I am experiencing with my Load Order
-
So an interesting discovery. I happen to have a previously unused windows 10 machine with a GPU that is "capable" of running SSE VR. So I fired it up, wiped windows 10, installed SSE VR (and the bare minimum relevant tools), and xlodgen worked just fine. Here is the output https://paste.ee/p/HiGAJs5c Now, I am _not_ convinced it actually worked, as I see no mention of any of the `.dds` files it was complaining about before. But it certainly didn't fail and there are no black terrains in the distance now. I have not yet tried this on my main machine, so that is my next step. If it works, then indicates there is something wrong with the mo2 instance that is provided by the FUS wabbajack. Not exactly sure just yet, but progress
-
No dice. I do not have a third party antivirus software, just windows defender. I completely disabled windows defender and tried again but I am seeing the same things. I have tried several reboots and unfortunately its still the same result. On a whim, I tried just installing the mod raw into the Steam game folder (a manual installation) and running xlodgen _outside_ of Mo2. Still the same results. I genuinely don't know what I am missing here. Here are the logs from the run outside MO2 if that helps at all. Note, I have tried redownloading xlodgen as well as I thought maybe there was something chuffed with my version, but unfortunately I am seeing the same result. https://paste.ee/p/xjYBijLI
-
I was wondering if it was related to the vfs that mo2 create but from everything I see, mo2 is not having any issues supplying proper stuff for literally anything else (including the assets for landscapes when I browse the vfs) > Load the load order into xEdit, start the Asset Browser with CTRL+F3, enter dirt02.dds into the Filter field and if selecting it shows its header data in the lower status field and test if it can be opened opening by double click and saving it from the first mentioned container works. So this bit is weird. I was able to get the asset browser open, but nothing happened when I selected "dirt02.dds", all I see is this. That said, I was able to double click the asset and it opened with gimp and "looked" right (I have no idea what dirt02.dds _should_ look like but it looked like an asset of some kind). I opened both the one that was provided by the landscape mod _and_ the one that is provided by skyrim. I exported the one provided by the landscape mod overtop of itself as requested and re-ran xlodgen but alas, same result. post save of dirt02.dds lodgen logs It's probably worth calling out that _without_ my xlodgen output, skyrim displays lods "fine" (at least as fine as default skyrim displays a lod) so I do not believe its an issue with either the texture _or_ the vfs. Same location as before but without xlodgen output
-
Hello! I recently got back into skyrim via the wonderful FUS VR Wabbajack and I have since been tinkering with that modlist. One thing I have noticed is that no matter what I do, I _always_ see black terrain lods when using xlodgen while having any kind of landscape mod installed. I have followed the Step Modifications tutorial here, and really at this point any other tutorial that seems reasonably knowledgable about how to do xlodgen. I've tried this with Skyland and Fantasia. I know lodgen works as the FUS modlist _comes_ with a properly generated dyndolod and they are using Septentrional landscapes. However, when _I_ enable Septentrional Landscapes mod and try to generate a lod, its just black. I know I am doing something wrong but I just can't figure out what. For testing purposes (since I know for sure that Septentrional Landscapes works as it comes with a lod from FUS), I have been testing against that landscape. Below is my reduced load order And my modlist if that's useful Additionally, here are the various logs that are generated by xlodgen. https://paste.ee/p/hT2Urt9t My system information - AMD RX 7900 XTX - AMD Ryzen 7 7800X3D - 32GB DDR5 Ram My testing currently is to generate my terrain with xlodgen (following the settings from the tutorial above) for _only_ Tamriel. Once its complete, I load it into my load order, start a new save, exit whiterun and see the following I have reduced my testing all the way down to just this (I was previously generating the xlodgen, then the texgen, then the dyndolod but that would take upwards of an hour to fully complete, just to validate that its still not working). I have noticed that this error quite a bit in the logs `<Warning: Error loading texture textures\landscape\` which screams to me that something is wrong. But I don't know what as I have spot checked the various textures it says it can't find and I can see they are provided by whatever landscape mod I am using (checked via mo2. Here is an example, the last "missing" texture error > <Warning: Error loading texture Textures\Landscape\Rocks01.dds> exists in mo2 https://imgur.com/a/Sl7cdxc What am I missing here? Is there some configuration option I am missing? Some dependency I don't have? What am I doing wrong? Please let me know what else I can provide (or if I missed something)
