System IO 'Invalid Access' when using LOD Generation tool.

Questions about Wine on Linux
Locked
lodgenerator
Newbie
Newbie
Posts: 1
Joined: Wed Jul 12, 2023 2:52 pm

System IO 'Invalid Access' when using LOD Generation tool.

Post by lodgenerator »

Let me try to explain my situation as brief and concise as possible.

I am using a LOD Generation program for the mainline Bethesda games, in this case, Fallout: New Vegas. The program's log outputs the following when generating Object and Terrain LOD. 'Objects LOD' can be replaced with 'Terrain LOD meshes' for the latter:

Code: Select all

[00:22] Unhandled Exception: System.IO.IOException: Invalid access.
[00:22]    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
[00:22]    at System.IO.__Error.WinIOError()
[00:22]    at System.Console.set_Title(String value)
[00:22]    at LODGeneratorCMD.Program.Main(String[] args) in C:\project\LODGen\LODGeneratorCMD\Program.cs:line 848  [00:22] [WastelandNV] Objects LOD generation error: LODGen process error, exit code E0434352 
My prefix has both vcrun2019 and dotnet48 installed, as per the requirements for the program. I've contacted the author of the program, to quote:

https://stepmodifications.org/forum/top ... ent=272396
System.IO.IOException: Invalid access

From the first post:
Do not generate into any game, any mod manager folders or special Windows folder like Program Files x86, Users, Desktop, Documents, Downloads etc.

From the Readme.txt:
Do not generate into any game or any mod manager folders that are part (direct or indirect) of the virtual file system. Install the output as a mod.

Make sure OS, antivr is not preventing access either.

Insufficient memory to continue the execution of the program. System.OutOfMemoryException

Use the x64 version.
Previously, I attempted to generate the LOD meshes into an ext4 drive (Z:/), where it'd count as a 'mod' for my Mod Organizer 2 install. I tried again, but opted to install it into the prefix (C:/), yielding the same error as before. I also used the x64 version of tool, and again, the same exception happened. If I recall correctly from the FAQ, WINE 'runs' programs as a Windows administrator, so technically 'Invalid Access' shouldn't happen to begin with.

So I am currently stumped. Why would this 'Invalid Access' exception occur, and would it be possible to prevent this from happening? Perhaps I'm missing something here, I haven't tried running the program as 'sudo' yet, as I am away from my main desktop, maybe that could be the solution? Any help is appreciated, thank you in advance.
Locked