PegasusKoga Posted August 27 Posted August 27 5 hours ago, sheson said: The BSA shipping with the mod has the Oblivion version instead of the FO3/FNV version. This test version of LODGenx64.exe should be able to properly read the NIFs from the BSA regardless. https://mega.nz/file/dcQg3IyC#o7F67rZVraQTcwIsZzbRYc00g90Lj0NrnqKxerCAhG0. Simply replace the file in the Edit Scripts folders. Typically there is no reason for a mod to include unmodified vanilla LOD models again. That is a mistake often seen from beginner mod authors. If using the mod, make sure it does not overwrite LOD models from any potential mods including improved LOD models. Next time you run into a problem with xLODGen, just report the issue and upload the logs and then follow the troubleshooting suggestions I write/quote and report their results to save time. Thank you so much, i'll make good use of it. Especially since i cried victory too soon, my LOD is still broken. But at least i now know i need to take a closer look at my other New Land mods so this time it shouldn't take nearly a week to find the offending mod.
sheson Posted August 27 Author Posted August 27 2 hours ago, PegasusKoga said: Thank you so much, i'll make good use of it. Especially since i cried victory too soon, my LOD is still broken. But at least i now know i need to take a closer look at my other New Land mods so this time it shouldn't take nearly a week to find the offending mod. Report the actual issue properly. Define what "LOD is still broken" means. Post a screenshot of the LOD and the close up full model with it being clicked in console so it shows the reference form ID. Upload the log.
ExoticRPGs Posted 5 hours ago Posted 5 hours ago The latest version of xLODGen always searches for a "FalloutNV_Epic" folder that doesn't even exist. I don't have Epic Games installed, so I don't know why it's doing this. I've tried reinstalling it, I can't use older versions of it or mods won't function, so I'm stuck. Any help would be appreciated, thanks. I've provided an image: https://i.ibb.co/jkd0fMR8/****inghelpme.png
sheson Posted 3 hours ago Author Posted 3 hours ago 1 hour ago, ExoticRPGs said: The latest version of xLODGen always searches for a "FalloutNV_Epic" folder that doesn't even exist. I don't have Epic Games installed, so I don't know why it's doing this. I've tried reinstalling it, I can't use older versions of it or mods won't function, so I'm stuck. Any help would be appreciated, thanks. I've provided an image: https://i.ibb.co/jkd0fMR8/****inghelpme.png Moved to the xLODGen thread. Read the first post, especially the part about the command line arguments. Also read the readmes included in the download archive. Upload the log text or copy and paste text instead of posting a screenshot. The only way that xEdit and its LODGen tool mode is using such an INI path is either with the -m or -i command line arguments or because EOSSDK-Win32-Shipping.dll exists in the data folder. EOSSDK-Win32-Shipping.dll is installed with EPIC games. https://tes5edit.github.io/docs/2-overview.html#CommandLineSwitches
ExoticRPGs Posted 2 hours ago Posted 2 hours ago Ok so it was that cursed EOSSDK-Win32-Shipping.dll that was causing it; I just removed it and LOD Generation is working like normal. I have the Steam version of FNV so not sure why this happened. But thank you Sheson for your help.
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