If I build Wings and launch it with w1 it'll close every time, but the erlang console is also visible so I wonder if something is happening there.. would that save an error log somewhere? how could I start the exe with the console visible?
something to with this addition maybe?
http://www.wings3d.com/forum/showthread.php?tid=2681
I understood that. I was not testing in the console. I was patching a file with some printouts. No success.
using the Linux command on Windows 10 also gets the hang
erl -pa C:/wingsdev/src/wings/ebin -run wings_start start_halt ${1+"$@"}
Nothing in the console sadly.
Thanks for the tip.
The simple
erl -pa C:/wingsdev/src/wings/ebin -run wings_start start_halt helped to reproduce the problem on Windows 7.
As I could to track it's something beyond Wings3D code because every piece of code ran until the last command when it hangs.
It's something for
dgud evaluation - it's far away from Erlang knowledge.
Thank's!
I will follow up the tread.
Since we should have a delay for the new release be available, due the current circumstances (caused by COVID-19), I'm making available the file
wings_frame.beam to be replaced in your current Wings3D v2.2.5 install.
That should put an end in the headache caused by this bug.
p.s. You cannot use the
File->Install Plug-in and Patches option to update this one - it must be
replaced by hand. Check the
Patches/Fixes for Wings3D and check for v2.2.5.