xLODGen - Terrain LOD beta 132 for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL, ENDERALSE

[sheson]

Bug report for you:

It appears that since moving from 33 to 34, the -o: command has changed a bit. Where previously a path like "D:\Modding Tools\xLODGen\Output\" would be fine, in the latest version this path results in "D:\Modding\" being created and used as the output. In other words, it seems to truncate the path at the first space.

 

Thanks for your time.

Make sure to put quotes around the path

 

-o:"D:\Modding Tools\xLODGen\Output\"

[mtreis86]

Make sure to put quotes around the path

 

-o:"D:\Modding Tools\xLODGen\Output\"

Yes these paths were quoted, still truncates.

Edited December 17, 2018 by mtreis86

[sheson]

Yes these paths were quoted, still truncates.

The code in xEdit that parses the command line hasn't been changed in ages. Everything still works as expected here in latest xLODGen or latest xEdit.

[Darth_mathias]

Bug report for you:

It appears that since moving from 33 to 34, the -o: command has changed a bit. Where previously a path like "D:\Modding Tools\xLODGen\Output\" would be fine, in the latest version this path results in "D:\Modding\" being created and used as the output. In other words, it seems to truncate the path at the first space.

 

Thanks for your time.

 

 

Make sure to put quotes around the path

 

-o:"D:\Modding Tools\xLODGen\Output\"

I have the same issue argument is -sse -o:"E:\Skyrim Special Edition Tools\xLODGen\SSELODGen_Output" But when I run v34 beta it creates a new Skyrim Folder in  E:\Skyrim the houses the textures and meshes generated from xLODGEN there instead.

 

This has recently started happening it behaved as expected on v33 Beta

[sheson]

I have the same issue argument is -sse -o:"E:\Skyrim Special Edition Tools\xLODGen\SSELODGen_Output" But when I run v34 beta it creates a new Skyrim Folder in  E:\Skyrim the houses the textures and meshes generated from xLODGEN there instead.

 

This has recently started happening it behaved as expected on v33 Beta

What are you using to start xLODGen?

[Darth_mathias]

I am running xLODGEN through Mod Organizer 2 the new Release canidate from there Discord Channel.

[sheson]

I am running xLODGEN through Mod Organizer 2

Which version?

 

Do a test through via a command prompt or a windows shortcut

Edited December 17, 2018 by sheson

[sheson]

I have no problem with xLODGen beta 0.34 and MO 2.16 RC1.

it also works using a command prompt or a Windows shortcut.

Both versions x86 or the x64.

 

I even download and used the archive from mega.

 

I tested on Windows 7.

 

Make sure to use the correct double quote " around the path

 

Check the MO mo_interface.log in its logs folder. This is what I get

 

[D] Spawning direct process < "C:/Skyrim/xLODGen/xLODGenx64.exe" , "-sse -o:\"c:\\The Output from xLODGen\"" , "C:/Skyrim/xLODGen" >
[D] Creating process hooked: < "\"C:\\Skyrim\\xLODGen\\xLODGenx64.exe\" -sse -o:\"c:\\The Output from xLODGen\"\u0000" >

Edited December 17, 2018 by sheson

[El_Rizzo]

Just wanted to report that I'm also getting the truncated output path with version 34 (x64) of xLODGen and MO2 version 2.1.6 (final build) and my MO interface log reports the correct argument, which is -fo4 -o:"F:\FO4 LODgen Output" :

 

 

21:36:21 [D] Spawning direct process < "J:/Tools Updates usw/Patches & Mods/Fallout 4/xLODgen/xLODGenx64.exe" , "-fo4 -o:F:\\FO4 LODgen Output" , "J:/Tools Updates usw/Patches & Mods/Fallout 4/xLODgen" >
21:36:21 [D] Creating process hooked: < "\"J:\\Tools Updates usw\\Patches & Mods\\Fallout 4\\xLODgen\\xLODGenx64.exe\" -fo4 -o:F:\\FO4 LODgen Output\u0000" >

 

The only difference I can see is that you tested on Windows 7 and I'm using Windows 10, could that be causing it?

[sheson]

Just wanted to report that I'm also getting the truncated output path with version 34 (x64) of xLODGen and MO2 version 2.1.6 (final build) and my MO interface log reports the correct argument, which is -fo4 -o:"F:\FO4 LODgen Output" :

 

 

The only difference I can see is that you tested on Windows 7 and I'm using Windows 10, could that be causing it?

Yes.

 

Edit: The log lines show that the path F:\FO4 LODgen Output is not surrounded by quotes. Compare to my log where there are escaped quotes \" around the path.

Edited December 21, 2018 by sheson

[El_Rizzo]

Huh, you are right, I've reported this to the dev team of MO2, one of whom could reproduce the issue the others and I have, an older version of xLODGen was using the correct output path, only 34 seems to have this issue since it requires to be run with admin privileges, unlike previous versions and that seems to be the reason things get wonky with MO2.

Edited December 21, 2018 by El_Rizzo

[sheson]

Huh, you are right, I've reported this to the dev team of MO2, one of whom could reproduce the issue the others and I have, but the weird thing is that on the same version of MO2, an older version of xLODGen was using the correct output path, only 34 seems to have this issue.

MO prints the log line before xLODGen is executed. I suppose it could have to do with MO being confused by file properties.

Create a windows shortcut with the arguments and execute that from MO instead. Or a batch file.

[El_Rizzo]

Alright, I've tried with a shortcut that gets executed in MO with the shortcut's target line looking like this: "J:\Tools Updates usw\Patches & Mods\Fallout 4\xLODgen\xLODGenx64.exe" -fo4 -o:"F:\FO4 LODgen Output\" and now the output goes straight into my overwrite folder, am I missing something or should this work and MO2 has another problem?

[sheson]

Alright, I've tried with a shortcut that gets executed in MO with the shortcut's target line looking like this: "J:\Tools Updates usw\Patches & Mods\Fallout 4\xLODgen\xLODGenx64.exe" -fo4 -o:"F:\FO4 LODgen Output\" and now the output goes straight into my overwrite folder, am I missing something or should this work and MO2 has another problem?

Look like MO does not like shortcuts. A *.bat with the line "c:\path\to\xLODGenx64.exe" -sse -o:"c:\path to output\" works as expected though.

 

Edit: I applied the xEdit 4.0.1 updates to xLODGen beta 0.35

Maybe the latest compile fixes whatever it is that confuses MO.

Edited December 22, 2018 by sheson

[Ashotep]

I've tried download xlodgen .34 and .35 and both times windows deletes the file because it has detected Win32/Cloxer.D!cl trojan.  Is this a false positive or something mega tried to insert?  I'm currently halfway through a Special Edition overhaul and your fantastic file is required.

 

I did some more searching and from what I'm seeing that a recent windows 10 update is triggering a false positive.  FYI.  I don't know if there is anything you can do about it.  Thanks again for your work.

Edited December 23, 2018 by Ashotep