05-21-2016, 04:12 PM
Humm, not good. Hard to find the problem.
Are you sure the vcredist is the one shipped with Wings3d installer? You can force it be installed, in case the check mark is unchecked.
Is there any change that white box appear for a time enough to take a printscreen (the whole screen) and maybe we could see anything written on it?
Did you installed Wings3d in the default path (c:\program files)? If so, could use run Wings3d as administrator?
An Erlang crash also creates a dump file, but it is written under the same path of the executable and in this case only if Wings3d is ran as Administrator rights. It must create a file named erl_crash.dump (in a place like C:\Program Files\wings3d_2.0.4).
Are you sure the vcredist is the one shipped with Wings3d installer? You can force it be installed, in case the check mark is unchecked.
Is there any change that white box appear for a time enough to take a printscreen (the whole screen) and maybe we could see anything written on it?
Did you installed Wings3d in the default path (c:\program files)? If so, could use run Wings3d as administrator?
An Erlang crash also creates a dump file, but it is written under the same path of the executable and in this case only if Wings3d is ran as Administrator rights. It must create a file named erl_crash.dump (in a place like C:\Program Files\wings3d_2.0.4).