VComrade Posted January 4, 2021 Posted January 4, 2021 (edited) Hello, every time I generate new occlusion data, and press X when the generation is complete I get the following warning messages:Is this supposed to happen?Also, is it necessary to regenerate object and trees LoD with DyndoLoD after regenerating terrain LoD with XLoDGen? Thanks in advance Edited January 4, 2021 by VComrade
sheson Posted January 4, 2021 Author Posted January 4, 2021 Hello, every time I generate new occlusion data, and press X when the generation is complete I get the following warning messages: Is this supposed to happen? Also, is it necessary to regenerate object and trees LoD with DyndoLoD after regenerating terrain LoD with XLoDGen? Thanks in advancehttps://forum.step-project.com/topic/15375-xlodgen-rename-delete-error/
VComrade Posted January 4, 2021 Posted January 4, 2021 https://forum.step-project.com/topic/15375-xlodgen-rename-delete-error/Oh okay thanks, so it should not mess up anything?
VComrade Posted January 4, 2021 Posted January 4, 2021 https://forum.step-project.com/topic/15375-xlodgen-rename-delete-error/Can you answer my second question? "Also, is it necessary to regenerate object and trees LoD with DyndoLoD after regenerating terrain LoD with XLoDGen?"
sheson Posted January 4, 2021 Author Posted January 4, 2021 Oh okay thanks, so it should not mess up anything? Discard everything that is not Occlusion. Each LOD type works independent of each other. If there were a requirement to do anything it would be part of the instructions in the manual. Also see the chapter "Updating" in the DynDOLOD manual.
VComrade Posted January 4, 2021 Posted January 4, 2021 (edited) Discard everything that is not Occlusion. Each LOD type works independent of each other. If there were a requirement to do anything it would be part of the instructions in the manual. Also see the chapter "Updating" in the DynDOLOD manual.How do I discard it? I can only press "ok". Edited January 4, 2021 by VComrade
sheson Posted January 5, 2021 Author Posted January 5, 2021 How do I discard it? I can only press "ok".That means to delete any other files than Occlusion.esp
VComrade Posted January 5, 2021 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!
Stefan Posted January 8, 2021 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.
Stefan Posted January 8, 2021 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
sheson Posted January 8, 2021 Author Posted January 8, 2021 it still says beta 64 in the bar: https://prnt.sc/wixcxo It says x64, always has.
sheson Posted January 8, 2021 Author 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
Stefan Posted January 8, 2021 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
sheson Posted January 8, 2021 Author 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
Stefan Posted January 8, 2021 Posted January 8, 2021 The error was probably caused by a race condition I fixed in beta 67You are the man. Cheers.
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