09-16-2022, 09:37 PM
Sorry for the delay. It's hard to think about what to do for something like this;
Also, even you didn't used previous version of Wings3D, please check if the preferences.txt file was created during the first fail. Look at this folder: C:\Users\<your user name>\AppData\Roaming\Wings3D
Another thing that maybe you would try to do is to force the MSV runtime library that came with the installer to be installed/modified. The installer will let this option unchecked if it is already installed, but in the past doing this process helped other user to run Wings3D.
And, as a last option that came out my mind now it would be try to run Wings3D in compatibility mode. Maybe you can try Windows 7.
Quote:Starting Wings using Erlang gives basically the same results; Wings opens for just a moment, then both Wings and Erlang close. I can see that some text appears on Erlang once Wings opens, but due to how quickly it closes, ...Please try this: still by starting werl.exe, but before run the wingstart(), use menu File->Open Logfile... to get the file erlshell.log created somewhere you define. It's possible it record the text before the total crash.
Also, even you didn't used previous version of Wings3D, please check if the preferences.txt file was created during the first fail. Look at this folder: C:\Users\<your user name>\AppData\Roaming\Wings3D
Another thing that maybe you would try to do is to force the MSV runtime library that came with the installer to be installed/modified. The installer will let this option unchecked if it is already installed, but in the past doing this process helped other user to run Wings3D.
And, as a last option that came out my mind now it would be try to run Wings3D in compatibility mode. Maybe you can try Windows 7.