Wings 3D Development Forum

Full Version: [duplicate|fixed] Ligtwave exporter error
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Bug reported by Hank in this post RE: W3D export to Blender

Ligtwave errors:


I was able to repeat the steps and get the same error.
Thanks for report it Hank.
Hi Micheus,

Just to make things clear: above print-screens are from 1.5.4 and for 2.1.5 I got:

[{lists,zip3,
[[<<0,57>>,
<<0,58>>,
<<0,59>>,
<<0,60>>,
<<0,61>>,
<<0,62>>,
<<0,63>>,
<<0,56>>],
[<<0,1>>,<<0,1>>,<<0,1>>,<<0,1>>,<<0,1>>,<<0,1>>,<<0,1>>,<<0,1>>],
[]],
[{file,"lists.erl"},{line,417}]},
{wpc_lwo,zip_lists_3,3,
[{file,"c:/Users/familjen/src/wings/plugins_src/import_export/wpc_lwo.erl"},
{line,245}]},
{wpc_lwo,'-make_vmad_uv2/2-fun-0-',2,
[{file,"c:/Users/familjen/src/wings/plugins_src/import_export/wpc_lwo.erl"},
{line,267}]},
{lists,map,2,[{file,"lists.erl"},{line,1239}]},
{lists,map,2,[{file,"lists.erl"},{line,1239}]},
{wpc_lwo,make_vmad_uv,1,
[{file,"c:/Users/familjen/src/wings/plugins_src/import_export/wpc_lwo.erl"},
{line,254}]},
{wpc_lwo,make_object,3,
[{file,"c:/Users/familjen/src/wings/plugins_src/import_export/wpc_lwo.erl"},
{line,96}]},
{wpc_lwo,'-make_objects_chunk/2-lc$^0/1-0-',2,
[{file,"c:/Users/familjen/src/wings/plugins_src/import_export/wpc_lwo.erl"},
{line,79}]},
{wpc_lwo,make_lwo,1,
[{file,"c:/Users/familjen/src/wings/plugins_src/import_export/wpc_lwo.erl"},
{line,69}]},
{wpc_lwo,export,2,
[{file,"c:/Users/familjen/src/wings/plugins_src/import_export/wpc_lwo.erl"},
{line,58}]},
{wings_export,export,4,
[{file,"c:/Users/familjen/src/wings/src/wings_export.erl"},
{line,35}]},
{wings_file,'-export_filename_1/2-fun-0-',3,[{file,[...]},{line,...}]},
{wings_develop,time_command,2,[{file,...},{...}]},
{wings_plugin,command,3,[{...}|...]},
{wings,raw_command_1,3,[...]},
{wings,raw_command,4,...},
{wings_wm,handle_event,...},
{wings_wm,...},
{...}|...]


BR, Hank
Hank, you tricked me. Undecided
I thought you already had applied the fixes I made available for 2.1.5.

It was reported and a fixed for this bug is available since May 2017.