Extrudeface, thanks for the information and files.
In regards to the test.obj file we can experience a real bug when importing that file. Thanks for report that.
[EDIT] I took a look in the current code and the problem was already fixed. it will be available soon in the next release.
As for the scale/view issue, you have the option to scale down the objects during the importing process. By using the file you provided me (test_joined.obj) a value equal or less than 0.001 was the value that Wings3D started to handle the object properly - be able to select elements. Something we may need to find a solution.
Because of the need to put the camera too far from the origin, it's "mandatory" to hide the Ground Plane before you start to work on this scene. That is causing the system overload when you try to frame the scene as reported in your thread Memory problem (freezes system) when framing a selected OBJ of a huge scale 2.17,2.15.
In order to be able to see this enormous scene you have to adjust the viewer clip, which you can do in View->Camera Settings and changing the Far Clipping Plane parameter from 10000.0 to a value like 1000000.0. The Near Clipping Plane may need to be increased proportionally in order to avoid strange artifacts on screen.
That should allow you to properly frame your scene.
In regards to the test.obj file we can experience a real bug when importing that file. Thanks for report that.
[EDIT] I took a look in the current code and the problem was already fixed. it will be available soon in the next release.
As for the scale/view issue, you have the option to scale down the objects during the importing process. By using the file you provided me (test_joined.obj) a value equal or less than 0.001 was the value that Wings3D started to handle the object properly - be able to select elements. Something we may need to find a solution.
Because of the need to put the camera too far from the origin, it's "mandatory" to hide the Ground Plane before you start to work on this scene. That is causing the system overload when you try to frame the scene as reported in your thread Memory problem (freezes system) when framing a selected OBJ of a huge scale 2.17,2.15.
In order to be able to see this enormous scene you have to adjust the viewer clip, which you can do in View->Camera Settings and changing the Far Clipping Plane parameter from 10000.0 to a value like 1000000.0. The Near Clipping Plane may need to be increased proportionally in order to avoid strange artifacts on screen.
That should allow you to properly frame your scene.