[Plugin] OBJexporter v3.0 20130131
-
PERHAPS USEFUL FOR 'FREE' USERS, WITHOUT THE OBJ-EXPORTER OPTION AVAILABLE.
TIG (c) 2010-2013
All Rights Reserved.
THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.OBJexporter.rb
Usage: menu File > 'OBJexporter...'
It Exports the Model in OBJ Format with an associated MTL file and a folder
of image-files [..._Textures] if appropriate.
By default the files use the SKP's name with spaces etc squeezed out.
By default the files and sub-folder are put into the SKP's folder.
A starting dialog allows you to give an alternative filename/folder.
You are asked if you want to make all Texture files PNG format?
By default everything in the SKP's active_entities, that's not Hidden and that's
on visible Layers will be Exported. If there is a Selection you are prompted to
export the 'Selection Only' [Yes] or 'Everything Active/Visible' [No].
By default the Units are in 'meters'.
By default All Exported Faces are Triangulated .
By default the Y & Z axes are swapped.
Note that 'distorted textures' are exported as new unique texture-files,
distorted to match and re-UVmapped, like the Pro-OBJexporter - any scaled
or rotated textures are UVmapped appropriately using the main texture-file.
Where possible shared-vertex data is reused ensuring correctly formed geometry.
This can mean that a SKP with 100,000 faces and potentially 300,000 vertices can
be 'compacted' to use perhaps 50,000 shared-vertices [but of course this depends
on the SKP's geometry, grouping etc]: this also reduces processing time [now
perhaps 60 seconds for this example], and when combined with optimized
numerical-entries, much smaller OBJ file sizes and faster processing in
3rd-party apps too.Donations:
By PayPal.com to info @ revitrev.org
###
Version:
1.0 20101216 First issue.
1.1 20110106 Image class method extensions only load if not already defined.
1.2 20110224 Distorted textures are now exported correctly, with their own
distorted 'unique texture' files [like the Pro-OBJexporter].
1.3 20110225 Glitch with some distorted textures 'flipping' addressed.
Materials and textures applied within and on to Groups or
Instances now properly defined and UV-mapped.
1.4 20110228 The new Filename now has spaces etc squeezed out.
Startup dialog added to allow Filename/Folder to be changed.
Glitches with reversals of some smoothed faces and materials
occasionally missing from complex faces now addressed.
General speed and Status-Bar progress-reporting improved.
1.5 20110323 Glitch with 'smoothed normals' addressed.
1.6 20110402 Option to export all Texture files in PNG format added.
1.7 20120118 Material images with no filetype now auto-revert to PNG.
Tolerance for deciding if 'distorted texture' relaxed.
1.8 20120214 Fixed issues with flipped-instance reversed face vertices.
1.9 20120215 Completely recoded. Issues with flipped-instance fully fixed.
2.0 20120217 Tolerance checks for deciding if 'distorted texture' improved.
2.1 20120220 Further work on avoiding the glitches with flipped-instances'
face-reversal/orientation/UVmapping.
2.2 20120220 Raw geometry hidden/off-layer merging during export resolved.
2.3 20120221 Typo corrected ;{
2.4 20120221 Recoded - speed ~v1.8, fixed flipped-instance face-reversal.
2.5 20120221 Recoded - resolves nested [flipped] transformation and
multiple-group-instances glitches etc.
2.6 20120222 Recoded for speed improvement ~5%. Flipped/rotated instances
transformations resolved for correct face orientation...
The MTL defaults now generally match the Pro exporter -
specularity=0.333, but ambience=color etc.
2.7 20121008 Alpha now set as d= and Tr= for cross-platform compatibility.
Coords' d.p. increased for accuracy. Option to Export Selection
Only, if there is a selection. Active_entities exported, allowing
just the contents of a group/component being edited to be exported;
or the whole model if the context is model.entities.
2.8 20130127 D.P. accuracy is not now applied to 'whole numbers'; -0 becomes 0;
any shared-vertex entries are now 'reused'.
2.9 20130130 Merging of shared vertices is now optional, as it slows processing
for larger models.
3.0 20130131 Improved shared-vertex merging algorithm is now slightly faster
than a non-merging version, so the option not to merge has been
removed. Notes updated.Download the latest version of the RBZ archive for this Plugin from the SketchUcation PluginStore...
http://sketchucation.com/pluginstore?pln=OBJexporter
Or get/install the SketchUcation Plugin Store dialogand thereafter you'll be able to AutoInstall all of your Plugins within SketchUp itself, without having to even download an RBZ at all.
http://sketchucation.com/pluginstore?pauthor=sketchucation -
That's awesome TIG! Thanks,
Chris
-
Thanks TIG, much appreciated
-
oh nice
you've done it again!
will there be an option to export as is? (I model in Quads...)edit : ignore me.. it does
-
Thank you TIG
-
Works fine for export to Blender 2.55 !
-
Thanks, TIG!
-
This exports materials as well? So I don't have to use FBX? Cool!
Thank you TIG!
I'll try and post you a donation, but I have to wait until after Xmas, because I'm still awaiting payment from a couple of people).
-
Thanks, TIG!
-
@unknownuser said:
Works fine for export to Blender 2.55 !
hey pilou, could you get the materials into 2.55?
-
I am new to Sketchup. I currently am trying the free Sketchup 8 on MacOS 10.6. I can read in an object into Sketchup, and run the OBJexporter from the plugin menu, but the message I keep getting is :
Writing textures failed!
Exporting Component: A
Exporting Component: B
etc.
Nothing to export
Exporting geometry to: /Users/eags/Desktop/Untitled.obj
Done.The .obj file has content, but cannot be read by Vue or Cheetah3D.
Am I missing something?
-
Have you saved the SKP before exporting?
Try exploding the imported 'group' and re-export as obj and see what happens...
Have you tried exporting a very simple box with some textured materials applied to it.
Then reimporting the obj... -
I will render my SU-Model in DAZ-Studio (http://www.daz3d.com) so I need my model as OBJ and I'm very happy to find these plugin. But after the import (.obj and .mtl) in DAZ (or I tested it also in MeshLab) not all textures are correctly. The wrong textures a not the biggest problem, I can fix it in DAZ, but a lot of skins are declared as "Default material" but there are not default. So I can't adjust them separately. Is where anything I can do to fix it?
-
@user2012 said:
I will render my SU-Model in DAZ-Studio (http://www.daz3d.com) so I need my model as OBJ and I'm very happy to find these plugin. But after the import (.obj and .mtl) in DAZ (or I tested it also in MeshLab) not all textures are correctly. The wrong textures a not the biggest problem, I can fix it in DAZ, but a lot of skins are declared as "Default material" but there are not default. So I can't adjust them separately. Is where anything I can do to fix it?
Remember to apply textured-materials to faces rather than components/groups.
Textures with 'skewed' UV-mapping will no be correct - make these materials unique before you export.
If you are opening a file based on an earlier obj your application might remember old settings - try afresh...
I suspect this as the main problem... IF you have faces showing with 'default-material' when they aren't in the SKP then I suspect that you have modeled [or have imported others' objects] with some of the faces 'reversed'.
To check this switch you View to Monochrome mode with a Style where the back-face material is very different to the front - say blue v. white. You might then find that you have applied textures to the back of some faces and the front face is indeed still in the 'default-material'. ALL back faces always export as having the 'default-material' since an OBJ by default only shows front faces with applied materials...
It is not the fault of the exporter, or the application importing the file - rather the modeler has simply made the SKP wrong and both other tools are showing the result...
There are several tools like my 'FixReversedFaceMaterials' that help you sort out this kind of messy modeling......
-
Thanks for the answer
– just these moment I found the same idea in the help …http://sketchup.google.com/support/bin/answer.py?hlrm=de&answer=36260
A plain has a front and a back side, no problem in SU. But on the export only the front side will be exported – so I have to use the monochrome-view to find all ‘back-side’ plains in my model an change them into a front-side. Easy but takes a long time …
-
@user2012 said:
Thanks for the answer
– just these moment I found the same idea in the help …http://sketchup.google.com/support/bin/answer.py?hlrm=de&answer=36260
A plain has a front and a back side, no problem in SU. But on the export only the front side will be exported – so I have to use the monochrome-view to find all ‘back-side’ plains in my model an change them into a front-side. Easy but takes a long time …
Look at this http://forums.sketchucation.com/viewtopic.php?p=264134#p264134 ............
-
Thanks!!!! Very good advice - the plugin is very helpfully. The German translation of the menutext in the plugin is horrible - but it works
-
@user2012 said:
Thanks!!!! Very good advice - the plugin is very helpfully. The German translation of the menu-text in the plugin is horrible - but it works
The ...DE.lingvo file is easily edited - the supplied lingvo files are not the definitive translations - some locales don't even get one! - they are for you to adjust/correct/improve - please do so and post you improved version for other German locale users too...
It is 'free' so do your bit to improve it...
-
@tig said:
The ...DE.lingvo file is easily edited - the supplied lingvo files are not the definitive translations - some locales don't even get one! - they are for you to adjust/correct/improve - please do so and post you improved version for other German locale users too...
It is 'free' so do your bit to improve it...So here is my version of the FixReversedFaceMaterialsDE.lingvo. I hope it will help other German users ("Viel Spass damit!"). Perhaps it's better posted or linked to the FixReversedFaceMaterial topic?
-
@user2012 said:
@tig said:
The ...DE.lingvo file is easily edited - the supplied lingvo files are not the definitive translations - some locales don't even get one! - they are for you to adjust/correct/improve - please do so and post you improved version for other German locale users too...
It is 'free' so do your bit to improve it...So here is my version of the FixReversedFaceMaterialsDE.lingvo. I hope it will help other German users ("Viel Spass damit!"). Perhaps it's better posted or linked to the FixReversedFaceMaterial topic?
I add it there and also include it in any future updates...
Advertisement