Nexus Modding > Modding Tools

Issue running Nexus' model / texture converter

(1/7) > >>

Arparso:
A while ago I did a fresh Windows 10 install and since then I can't run Nexus' model / texture converter. As soon as I try to start it, it displays an application error dialog and tells me, that the application could not be started (also giving the error code 0xc0000142).

Does that sound familiar to anyone? I remember having trouble starting the converter back on Windows 7 as well, but I don't remember the actual error message and how I eventually got it to run.

Without the converter, I cannot bring in new assets or make changes to old ones... kind of kills Nexus modding for me :(

The Old Dragon:
Hi Arparso,

I'm in exactly the same spot. I can't get either the game or the converter to run in Windows 10, yet I can create and run mod missions without any problems  ???

In event viewer, it seems to indicate that the ntdll.dll file is faulty. Here's the entry if it helps...


--- Quote ---Faulting application name: converter.exe, version: 0.0.0.0, time stamp: 0x2a425e19
Faulting module name: ntdll.dll, version: 10.0.10240.16430, time stamp: 0x55c599e1
Exception code: 0xc0000005
Fault offset: 0x00055635
Faulting process ID: 0x1ec4
Faulting application start time: 0x01d11c0959f6ee8d
Faulting application path: B:\Program Files (x86)\Nexus - The Jupiter Incident\mod_tools\converter.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 2ae397bf-199f-4f2b-84b7-1b52648b5765
Faulting package full name:
Faulting package-relative application ID:
--- End quote ---

Update: 16/11/2015
Went back to Windows 8.1 over the weekend and now Nexus (the actual game) runs - Hurrah.
Unfortunately, the converter still will not. Now the event viewer is pointing the finger at the 'lwolib.dll' and saying it's faulty. Tried replacing it with a different one but no joy.

At this rate, I'm thinking of finding an older machine to run the converter. Didn't have any luck with a VM.

The Old Dragon:
Hi Arparso,

Quick update. I copied the mod_tools folder from my laptop (windows 8) where the converter doesn't work and took it into work. The pc's there are all windows 7 and the converter works perfect. So it's got to be the differences between the two OS's causing the problem.

Arparso:
Yeah, but what exactly is missing or different in Win10, that the converter just keeps crashing? :(

I mean, I could just run an older OS in a VM, but that seems like overkill just to get that one tool to run... and I'd need another OS license.

fleenots:
Hi
Has anyone manage to find a workround for this problem?
Thanks

Navigation

[0] Message Index

[#] Next page