Please post bug reports for the 1.1 development release in this thread.
Wings 1.1 bug reports
| Author | Comment | ||
|---|---|---|---|
 bjorng |
Wings 1.1 bug reports |
Lead | |
|
(05/17/09 06:38:09) |
|
||
|
wasamonkey |
|||
|
(05/17/09 13:21:43) |
Dump written 2009-5-17_16-16
Version: 1.1 Window: geom Reason: {badrecord,st} Stack trace: [{wings,command,2}, {wings,raw_command,3}, {wings_wm,handle_event,3}, {wings_wm,send_event,2}, {wings_wm,do_dispatch,2}, {wings_wm,get_and_dispatch,0}, {wings,init,1}] pressed "a" after calling the connect command from the rmb menu had to close wings by closing erlang window was unable to recreate the crash, hopefully the dump will shed some light on it
Last Edited By: wasamonkey
05/17/09 13:25:08.
Edited 1 times.
|
||
|
bjorng |
|||
|
(05/17/09 18:45:37) |
wasamonkey wrote: Thanks! I was able to repeat it. The crash is caused by using Aim on highlighted elements. |
||
|
plec |
1.1 is not running | ||
|
(05/18/09 13:22:39) |
Dump written 2009-5-18_16-21
Version: 0.99.54a Window: "<Unknown Window Name>" Reason: {terminated,[{io,put_chars,[<0.37.0>,unicode,"Trying OpenGL modes\n"]}, {wings_init,try_video_modes,2}, {wings_init,init,0}, {wings,init,1}]} Short stack trace: [{ets,lookup_element,3},{wings_lang,str,2},{wings,halt_loop,1}] Long stack trace: [{ets,lookup_element,[wings_lang,{wings,halt_loop,2},2]}, {wings_lang,str,2}, {wings,halt_loop,1}] I am under xp64 |
||
|
bjorng |
|||
|
(05/18/09 13:30:30) |
The crash dump is from 0.99.54a. Does Wings 1.0 work on your computer? Is there an Erlang program still running and are there any messages there (you will
probably have to scroll up)?
|
||
|
plec |
|||
|
(05/18/09 13:56:02) |
bjorng,
I have multiple versions. I have installed v1.1 and when I run the exe that is what I am getting unfortunately. Maybe the installer fails to make 1.1 as default wings. I will try installing on another computer and see if it runs ok Here is the one from erlang window Erlang R13B (erts-5.7.1) [rq:1] [async-threads: 
Eshell V5.7.1 (abort with ^G) Reading preferences from: e:/Documents and Settings/masaustu/Application Data/Wings3D/Preferences.txt 1> =ERROR REPORT==== 18-May-2009::16:53:54 === Error in process <0.37.0> with exit value: {{case_clause,{{state,#Ref<0.0.0.417>,<0.24.0>,80,24,100,1,{[],[]},[],[],0,undefined,false},{error,{request,{put_chars,unicode,<<20 bytes>>}}}}},[{wings_console,server_loop,1}]} |
||
|
bjorng |
|||
|
(05/18/09 23:58:17) |
plec wrote: Multiple versions are always OK as long as they are installed in separate directories. Installing a new version on top of an old version in the same directory usually works, but it will waste disk space, so that is not recommended. Installing Wings 1.1 on top of Wings 0.99.54a does not work. The reason is the "a" in the version. The Erlang code loader will always load the highest version of an application it finds, but that only works for version numbers that only contains numbers separated by dots. (Note to self: Don't use version numbers ending with "a" again.) So what happened in your case that you were try to run to run Wings 0.99.54a in a newer version of Erlang/OTP (R13B) than it was originally released with and that does not work. |
||
|
GetaVe |
|||
|
(05/21/09 05:54:00) |
I guess this isn't necessarily a bug per se but when using the 'Force Axis-Aligned Ortho' option, and subsequently viewing in the x/y/z axis,
shouldn't the ortho icon be selected to represent that fact?
|
||
|
Fonte Boa |
|||
|
(05/21/09 15:52:33) |
Tweaking with Masking on,
..................................................
Stack trace:
Size Size in words for this undo state.
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
Size Cost Command Change
..............................................
|
||
|
optigon |
|||
|
(05/22/09 21:14:14) |
Thanks for the report Fonte Boa
|
||
|
pauljs75 |
|||
|
(05/22/09 22:44:14) |
Using Face mode|Select|Similar normals over multiple objects causes a crash.
Here's the crash.dump:
Dump written 2009-5-23_1-32
Version: 1.1 Window: geom Reason: function_clause Short stack trace: [{e3d_vec,dot,2}, {wings_sel_cmd,any_matching_normal,3}, {wings_sel_cmd,check_face_normals,5}, {wings_sel_cmd,norm_search,5}, {wings_sel_cmd,'-oriented_faces/2-fun-4-',4}, {wings_sel,fold_1,4}, {wings_sel_cmd,oriented_faces,2}, {wings,raw_command,3}] Long stack trace: [{e3d_vec,dot, [{6, {9, {24, {5,{3,nil,nil},{7,nil,{20,nil,nil}}}, {32,{28,nil,nil},{36,nil,{40,nil,nil}}}}}}, {-0.999999999997737,2.1142515232106607e-6,2.3633593446776196e-7}]}, {wings_sel_cmd,any_matching_normal,3}, {wings_sel_cmd,check_face_normals,5}, {wings_sel_cmd,norm_search,5}, {wings_sel_cmd,'-oriented_faces/2-fun-4-',4}, {wings_sel,fold_1,4}, {wings_sel_cmd,oriented_faces,2}, {wings,raw_command,3}] |
||
|
bjorng |
|||
|
(05/23/09 04:37:00) |
Thanks! This is a bug in 1.0 too, so it will be corrected in both 1.0.1 and the next development release.
|
||
