[Plugin] OBJexporter v3.0 20130131

Judith

Thanks for your answer TIG. I tested with the model and if the conversion does take long though. The problem I commented in the previous post I came up with a model downloaded earlier. I attached so that you can try. In that case, does not convert google sketchup and reports with an error message. In ruby console the message (sketchup :: group deprecated method).

In my final year project of computer science,run google sketchup from a program created by me. With some models perform well the conversion (a. Obj), but appears white screen error.. To what can this be? I need to check whether the execution was successful and that message makes the result may not be correct because the conversion has been performed and the error message has gone.

Thank you so much!

Catedral.rar

TIG

I looked at your latest Catedral SKP and see that there are several reversed faces, and single plane parts where the back face will not render properly as the back faces are not UVmapped, even if the renderer/importer used applied the front color to the back.
View it in Monochrome mode with the reversed faces in the Style set contracting as this example. CatedralREVD[MONOCHROME].PNG My FixReversedFaceMaterials tool helps you 'flip' such faces whilst keeping the UVmapping of any textures on the now-front face to match...

Don't get too hung up about the 'error' - actually it's a 'warning' and the process completes fine - make_unique should never be needed on a group BUT it is needed so the API's warning is just wrong - it has been like that for years !

You refer to the 'white screen error' - this is NOT an error - when SketchUp does intensive processing [can even occur with it's native tools!] it becomes 'unresponsive' and it 'whites-out' BUT it is still processing - as the Task Manager will show... If you ask SketchUp to process millions of facets, materials etc you must expect it to take a while to finish. My OBJexporter is written in Ruby which is hardly an efficient tool. The Pro equivalent OBJexporter is a binary app that executes faster, but still takes a long time to finish. The latest version of my OBJexporter lets you export a selection so this could be much quicker when testing SKP for export to OBJ...

If you want to check that the OBJexport has finished - within the SKP using Ruby you can check to see that the active tool has changed to 'Select' ? Otherwise from the outside you need to see that SketchUp has stopped using any significant amount of processing memory etc...

sicksickisck

smoothing groups ??!! export

TIG

@sicksickisck said:

smoothing groups ??!! export
Cryptic.
It does create 'smooth surface' normal maps, if the object's faces are themselves 'smoothed'.
However, hidden lines keep sharp change of plane.
Most rendering apps know how to use/display such 'smoothed surfaces'...
In what app are you using the OBJ file?
Does that app have 'settings'?
Can you post a small example zipped SKP/OBJ/MTL/Textures set etc showing what you think is the issue...

Note that importing any OBJ back into SketchUp will ignore the facets 'smoothing' - unlike most 3rd-party renderings apps etc...

It works for me...

sujunwei

very brilliant job.
Is it possible to export obj file with all faces grouped based on their materials. for instance, all faces with color-0 are placed together, and then another color, and ...
something like
g pb-GRP-2609-Color_000
usemtl Color_000
v...
vn ...
vt...
f...

g pb-GRP-2670-Color_000
usemtl Color_000
v...
vn ...
vt...
f...

#//all other faces with Color_000 ...
#then another color, color_001 for instance, and all the faces with color _001 are placed together

g pb-GRP-2639-Color_001
usemtl Color_001
v...
vn ...
vt...
f...

#//other colors ...

That can be useful for some applications, for instance, using snappyHexMesh in OpenFOAM for general CFD(computational fluid dynamics) applications.
There should not be too much job it think, but it will facultate a large group of openfoam users. Would it be possible for you to add such a functionality in your next release? Thank you very much.
Best Regards, Junwei

tulacong

thank TIG....very goog

MidgeUre

Thank you very much.

T_Osborn

Is it inevitable, technically speaking, that SU geometry Group and Component associations are lost when exporting to an OBJ file? What I tried to do was open a SU model (interior room scene) in Blender so as to try and work with Blender's rendering features. Discreet objects within the SU outliner--entertainment center cabinet, wall(s), floor, mouldings, plantation shutters--were no longer discreet objects in Blender's outliner. In Blender's outliner there was only a very long list of 'meshes'. The model/scene itself displayed properly in Blender's viewport. If I placed the cursor over what had been the 'cabinet' in SU, then clicked to select, only a single mesh among the many comprising the cabinet would be selected. There was no practical way to determine which among the hundreds of meshes in the outliner were those that comprised the cabinet exclusively, and so I could not select it individually so as to make material assignments (color, sheen, and all that).

TIG

Much as with the Pro OBJ Exporter the geometry [mesh] is broken down by 'loose/group/component/image' and then within each of those subdivided 'by material'. So if you have a box-component with a different colored 'lid', then the component's mesh is inside a single 'container' [named after the original object], and its two meshes are made with their respective materials. Nested objects' container naming reflects those containers...

T_Osborn

@tig said:

Much as with the Pro OBJ Exporter the geometry [mesh] is broken down by 'loose/group/component/image' and then within each of those subdivided 'by material'....

OK, I can see something of this now in Blender's outliner. After expanding the size of the outliner window, I do see that each mesh is identified as part of a component or group, or with the component name ('crown moulding') and material name. I just needed more screen space to reveal all of the text. I'm embarrassed, but Blender's interface is difficult for a modeling noob after a little time spent in SU.

I think I can more effectively combine the relevant meshes into the singular objects they were meant to be, but it still will be tedious.

andybot

@t_osborn said:

@tig said:

Much as with the Pro OBJ Exporter the geometry [mesh] is broken down by 'loose/group/component/image' and then within each of those subdivided 'by material'....

OK, I can see something of this now in Blender's outliner. After expanding the size of the outliner window, I do see that each mesh is identified as part of a component or group, or with the component name ('crown moulding') and material name. I just needed more screen space to reveal all of the text. I'm embarrassed, but Blender's interface is difficult for a modeling noob after a little time spent in SU.

I think I can more effectively combine the relevant meshes into the singular objects they were meant to be, but it still will be tedious.

That's correct, the OBJ exporter organizes the model by material, so everything with a material, even if it's in different components or groups will come in as one "mesh" into Blender. If you want your component and group heirarchy to be maintained, the best way is to use the 3DS exporter that's available in the pro SU version.

Andy

Lana

God bless you . Thank you.

bomastudio

TIG: thank you for all the plugin you share with all of us!!!!

A question: this plugin (well, OBJ format) can export cameras positions?
Thanx.

TIG

No, OBJ format is for geometry only [faces] and their associated materials/textures.
Some formats like DXF include data on the camera.
There are some tools in the API to get a scene's view camera data, but after that it depends on the program into which you want to import that data, on how it can be suitably structured...
What did you have in mind ?

bomastudio

Well I need to bypass the Octane exporter (as I use Ubuntu/Lubuntu+wine+SkecthUp) and the webdialogs doesn't work no more (with SU6 webdialog worked....). So exporting in OBJ format I can solve model+texture troubles, but I need to export also the scenes (cameras).

TIG

So this is an Octane based query... only peripheral to Sketchup.
There are already two tools available on the Octane Sketchup forum for licensed users.
You need 'OctaneOCMbatchExporter.rb' - the tools allow you to batch-export your scenes' cameras and suns/shadows settings into Octane OCM files, which can then be loaded and used as 'nodes' in the matching OCS file, that you have made from the SKP exporter via OBJ/MTL files etc.
That forum's thread is named "Batch Cameras / Suns OCM Exporter v1.0"

bomastudio

TIG, you are definitively the best source of info about SU!!!! thanx, how would I do without you?

eubz

nice. i love this exporter.

sceptile

says the file can amage my computer?

TIG

@sceptile said:

says the file can amage my computer?
Let us assume you mean 'damage'...
Who, what where, when, why and how ?
Yours might win this week's prize for the most useless error report / query...