03-26-2020, 12:19 PM
It's a strange behaviour and it looks like something happen only in your PC settings since it's not a general problem. I have no problem like this running many versions of Wings3D at Windows 10.
The "opens an empty erlang emulator" really means you are not getting the initial information like this?
Some other informations you may provided us:
1) Did you tried to disable your anti-virus - to run again the installer (at least). Some antivirus uses to report the installer as a threat (a false positive).
Usually we need to install it as Administrator and in this case also force the Microsoft DLLs to be installed would make some difference.
2) Did you install the 32bits or 64bits? Could you try to install the another version you didn't install yet?
3) Do you get wings_crash.dump file on the desktop?
4) Is there a Erlang crash dump file at "F:\Program Files\wings3d_2.2.5\bin\erl_crash.dump"?
5) Is there any crash report from Windows? Do you can find something like this "C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_erl.exe_..." (that is the folder were we can find them - at least in Win7)?
Quote:Running with --debug opens an empty erlang emulator instance.It looks like you already tried everything we alread suggested in the past related to this loading fail.
Reinstalling Wings 3D changes nothing.
Reinstalling microsoft's DLLs changes nothing.
Running as admin changes nothing.
Running from command prompt displays no errors and changes nothing.
The "opens an empty erlang emulator" really means you are not getting the initial information like this?
Code:
Erlang/OTP 19 [erts-8.1] [64-bit] [smp:4:4] [async-threads:10]
Eshell V8.1 (abort with ^G)
Some other informations you may provided us:
1) Did you tried to disable your anti-virus - to run again the installer (at least). Some antivirus uses to report the installer as a threat (a false positive).
Usually we need to install it as Administrator and in this case also force the Microsoft DLLs to be installed would make some difference.
2) Did you install the 32bits or 64bits? Could you try to install the another version you didn't install yet?
3) Do you get wings_crash.dump file on the desktop?
4) Is there a Erlang crash dump file at "F:\Program Files\wings3d_2.2.5\bin\erl_crash.dump"?
5) Is there any crash report from Windows? Do you can find something like this "C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_erl.exe_..." (that is the folder were we can find them - at least in Win7)?