VComrade Posted January 5, 2021 Share Posted January 5, 2021 That means to delete any other files than Occlusion.espOh now I get it, theres bunch of files left over after all those lod generations. Thanks! Link to comment Share on other sites More sharing options...
Stefan Posted January 8, 2021 Share Posted January 8, 2021 If you find the time, do the same with the latest version again and have an eye at what part (check the message log) it starts waiting. Then check if there are LODGen or TexConv processes running in the background.Doing it now, sorry for the delay. I am using the latest beta, 66, as a note, it still says beta 64 in the bar: https://prnt.sc/wixcxoWill let you know how it goes. Link to comment Share on other sites More sharing options...
Stefan Posted January 8, 2021 Share Posted January 8, 2021 (edited) Dead, within 10 minutes. Runtime error, no generating process running, secondary or primary. https://prnt.sc/wixsxb Beta 64 works fine. I use the settings from Step SSE guide, here, if you forget: https://prnt.sc/wixu82 EDIT: Looking for that error, it seems it's trojan related? Probably it doesn't apply here. I run Nod32 Internet Security. Beta 64 works fine, and I have never got the Runtime error on anything else. EDIT2: I am doing a NOD32 scan and F-secure one as we speak, but it can't be a trojan. I restore Windows from a clean ghost kept on an external HDD I keep in a box, I don't visit random websites, I don't install random software, etc. EDIT3: F-secure scanning done, it says my PC is clean. Eset will say the same probably. Edited January 8, 2021 by Stefan Link to comment Share on other sites More sharing options...
sheson Posted January 8, 2021 Author Share Posted January 8, 2021 it still says beta 64 in the bar: https://prnt.sc/wixcxo It says x64, always has. Link to comment Share on other sites More sharing options...
sheson Posted January 8, 2021 Author Share Posted January 8, 2021 Dead, within 10 minutes. Runtime error, no generating process running, secondary or primary. https://prnt.sc/wixsxb Beta 64 works fine. I use the settings from Step SSE guide, here, if you forget: https://prnt.sc/wixu82 EDIT: Looking for that error, it seems it's trojan related? Probably it doesn't apply here. I run Nod32 Internet Security. Beta 64 works fine, and I have never got the Runtime error on anything else. EDIT2: I am doing a NOD32 scan and F-secure one as we speak, but it can't be a trojan. I restore Windows from a clean ghost kept on an external HDD I keep in a box, I don't visit random websites, I don't install random software, etc. EDIT3: F-secure scanning done, it says my PC is clean. Eset will say the same probably.Post or pastebin the log Link to comment Share on other sites More sharing options...
Stefan Posted January 8, 2021 Share Posted January 8, 2021 (edited) It says x64, always has.Lol, I missed an X, little moron that I am. Post or pastebin the logI started it again, on beta 66, the second try worked flawlessly, here is the full log. Eset said the PC is clean too. WHich isn't necessarily true.https://www.dropbox.com/s/06d49enrha4ng85/xlodgen%20v66.zip?dl=0 Edited January 8, 2021 by Stefan Link to comment Share on other sites More sharing options...
sheson Posted January 8, 2021 Author Share Posted January 8, 2021 (edited) Lol, I missed an X, little moron that I am. I started it again, on beta 66, the second try worked flawlessly, here is the full log. Eset said the PC is clean too. WHich isn't necessarily true.https://www.dropbox.com/s/06d49enrha4ng85/xlodgen%20v66.zip?dl=0The error was probably caused by a race condition I fixed in beta 67 Edited January 8, 2021 by sheson Link to comment Share on other sites More sharing options...
Stefan Posted January 8, 2021 Share Posted January 8, 2021 The error was probably caused by a race condition I fixed in beta 67You are the man. Cheers. Link to comment Share on other sites More sharing options...
Bladehawke Posted January 14, 2021 Share Posted January 14, 2021 (edited) I've looked and can't find an answer to this, so I apologize if this has come up before. I'm trying to generate terrain LOD for FNV after installing the NMC texture pack (just so the terrain looks the right colors from a distance). I've installed all the optionals I can find with regard to FNVLODGen and NMC. But my log is full of stuff like: [00:39] Building terrain LOD meshes elapsed time: 00:27 [00:39] [WastelandNV] Building terrain LOD textures [-64,-64] to [63,95] 16/8 [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-40.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-44.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-64.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-60.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-48.y-60.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-44.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-64.y-48.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-64.y-60.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-40.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-64.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-60.y-60.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-60.y-60.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-64.y-60.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-64.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-40.y-56.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-40.y-56.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-60.y-44.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-56.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-40.y-40.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-48.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-56.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-60.y-44.dds [00:41] Error opening -flist file D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_1_1.txt [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-40.y-40.dds [00:41] Error: Executing Texconv failure 00000001: "G:\Modding\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -aw 256 -sepalpha -f DXT5 -bc d -o "g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals" -flist "D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_1_1.txt" [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-56.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-48.y-56.dds [00:41] Error opening -flist file D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_2_1.txt [00:41] Error: Executing Texconv failure 00000001: "G:\Modding\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -aw 256 -sepalpha -f DXT5 -bc d -o "g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals" -flist "D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_2_1.txt" [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-36.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-36.y-64.dds xLODGen is being called from inside MO2 with the arguments -fnv -o:"G:\Modding\xLODGenOutput" The outpud directory is NOT an inside the MO2 profile structure. I followed the guide in the first post, but for the life of me I can't figure this one out. I am using Beta 67 Edited January 14, 2021 by Bladehawke Link to comment Share on other sites More sharing options...
sheson Posted January 15, 2021 Author Share Posted January 15, 2021 I've looked and can't find an answer to this, so I apologize if this has come up before. I'm trying to generate terrain LOD for FNV after installing the NMC texture pack (just so the terrain looks the right colors from a distance). I've installed all the optionals I can find with regard to FNVLODGen and NMC. But my log is full of stuff like: [00:39] Building terrain LOD meshes elapsed time: 00:27 [00:39] [WastelandNV] Building terrain LOD textures [-64,-64] to [63,95] 16/8 [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-40.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-44.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-64.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-60.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-48.y-60.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-44.y-64.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-64.y-48.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-64.y-60.dds [00:40] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-40.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-64.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-60.y-60.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-60.y-60.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-64.y-60.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-64.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-40.y-56.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-40.y-56.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-60.y-44.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-56.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-40.y-40.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-48.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-56.y-48.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-60.y-44.dds [00:41] Error opening -flist file D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_1_1.txt [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-40.y-40.dds [00:41] Error: Executing Texconv failure 00000001: "G:\Modding\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -aw 256 -sepalpha -f DXT5 -bc d -o "g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals" -flist "D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_1_1.txt" [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-56.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-48.y-56.dds [00:41] Error opening -flist file D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_2_1.txt [00:41] Error: Executing Texconv failure 00000001: "G:\Modding\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -aw 256 -sepalpha -f DXT5 -bc d -o "g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals" -flist "D:\Users\Xander\AppData\Local\Temp\FNVEdit\Texconv_WastelandNV_2_1.txt" [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-48.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-36.y-64.dds [00:41] g:\modding\xlodgenoutput\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-36.y-64.dds xLODGen is being called from inside MO2 with the arguments -fnv -o:"G:\Modding\xLODGenOutput" The outpud directory is NOT an inside the MO2 profile structure. I followed the guide in the first post, but for the life of me I can't figure this one out. I am using Beta 67See if adding an exception to antivirus for LODGenx64.exe, Texconvx64.exe makes a difference. Link to comment Share on other sites More sharing options...
Bladehawke Posted January 15, 2021 Share Posted January 15, 2021 Okay, tried that, even put an exclusion on the temp folder subdirectory. Then I tried disabling the AV's real-time protection. No change in the console output. Link to comment Share on other sites More sharing options...
sheson Posted January 15, 2021 Author Share Posted January 15, 2021 Okay, tried that, even put an exclusion on the temp folder subdirectory. Then I tried disabling the AV's real-time protection. No change in the console output.Beta 68 should fix that. Link to comment Share on other sites More sharing options...
Bladehawke Posted January 15, 2021 Share Posted January 15, 2021 Beta 68 should fix that.Whatever you did worked. Thanks a ton :) Link to comment Share on other sites More sharing options...
sheson Posted January 21, 2021 Author Share Posted January 21, 2021 Left: vanilla terrain LOD Right: extended terrain LOD generated with [TES|SSE]-Terrain-Tamriel-Extend.esm Link to comment Share on other sites More sharing options...
mrshadoo Posted January 24, 2021 Share Posted January 24, 2021 Hello sheson, I just want to confirm something .. ! I've been using version 66 and the generated files in total was 9 gigs and with the latest version 69 I get only 900 MB ! is that normal ? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now