11-17-2018, 04:41 PM
Long story short : Totally hunted at least the issue and quick workaround ... While not newbie proof as a solution, just not trusting on the OBJ exporter and selecting a bunch of meshes without joining, setting "selection only" is gonna make a proper group or object (even if marked the other setting for that!) that Wings can import without errors, as it wont. Or at least, not at this huge scene scale (maybe is unrelated).
I tested that meshes can be totally separated (several cubes in this test) , but if select them all, hit ctrl + j to join the objects (which in blender is not a boolean, meshes keep disconnected), be sure the now single object is also selected, export just the same ("selection-only"(non default) , and etc, pretty much defaults in that OBJ exporter) as I've done with the file causing the error, if ctrl+j joined, it will open without triggering the error message. Still, the problem of the massive memory or whatever prob yet happens later on (my other bug I reported today, http://wings3d.com/forum/showthread.php?tid=2712 ). [as mentioned, none of these bugs are stopping my work a single bit, just reporting]
So, I am attaching a zipped file, containing :
error.png --> the notification error it triggers if not ctrl + j in blender.
test.blend --> blender scene file which am using to provide these test files
scene.png --> settings needed in blender to actually "see" something, as if not, at that size the clipping (far and near scene clippings) wont let you see anything. (settings areas highlighted)
test.obj and test .mtl --> The exported obj file that triggers the error in Wings.
test_joined.obj and test_joined.mtl --> a file with ctrl+j applied to the meshes, so at least it will not trigger a error message window (the large scene wont be really something that can be handled, tho, as explained in the other report-thread ).
log_window.txt --> output in the Wings3d log Window, inside wings 3D UI, which I could select all + copy in one of the tests with this test scene.
wings_crash.dump ---> crash dump produced by this when not doing the ctrl + j objects join, and importing the obj in wings.
I tested that meshes can be totally separated (several cubes in this test) , but if select them all, hit ctrl + j to join the objects (which in blender is not a boolean, meshes keep disconnected), be sure the now single object is also selected, export just the same ("selection-only"(non default) , and etc, pretty much defaults in that OBJ exporter) as I've done with the file causing the error, if ctrl+j joined, it will open without triggering the error message. Still, the problem of the massive memory or whatever prob yet happens later on (my other bug I reported today, http://wings3d.com/forum/showthread.php?tid=2712 ). [as mentioned, none of these bugs are stopping my work a single bit, just reporting]
So, I am attaching a zipped file, containing :
error.png --> the notification error it triggers if not ctrl + j in blender.
test.blend --> blender scene file which am using to provide these test files
scene.png --> settings needed in blender to actually "see" something, as if not, at that size the clipping (far and near scene clippings) wont let you see anything. (settings areas highlighted)
test.obj and test .mtl --> The exported obj file that triggers the error in Wings.
test_joined.obj and test_joined.mtl --> a file with ctrl+j applied to the meshes, so at least it will not trigger a error message window (the large scene wont be really something that can be handled, tho, as explained in the other report-thread ).
log_window.txt --> output in the Wings3d log Window, inside wings 3D UI, which I could select all + copy in one of the tests with this test scene.
wings_crash.dump ---> crash dump produced by this when not doing the ctrl + j objects join, and importing the obj in wings.