what importer?
does it not have an exporter…
john
The native importers / exporters are what they are. Which is why there are many import and export plugins.
Well, I have a custom importer plugin for what I need that I wrote… However, in the case I am working with right now, it is not a factor… The workflow I described earlier was to answer someone’s question about “where i got the precision from” in the general case… For now, I built a very very (very) simple model in SKP directly, then applied a rotation to it, and then exported it to OBJ. So in this case, its all internal to SKP. The rotation that I did was not a cardinal angle, so the rotated vertex positions are not nice round numbers… In this case, when I exported to OBJ and saw only three digits of precision, its what led to my question…
Well that’s all fine, but if the precision exists internally, it seems like the SKP development team could pretty easily update the code to have it written out when exporting to OBJ… Or at least make it an option… I mean in C++ its literally a call to “setprecision(12)” or something like that. Of course, I’m not a member of the SKP development team, so maybe there’s some reason that this is harder than I’m thinking, but TIG demonstrated that the precision exists, its just not being written to the OBJ file.
Doh!
I just realized that my old OBJexporter has greater precision !
[numbers are in " but units are set in header] e.g.
vn 0.686281746817 -0.727335798641 0
Here’s a link to download it:
When its RBZ is installed it appears in the File menu and because it’s old it’s not signed - but will work in v2020 with Extension Manager > Extension Loading Policy set to Unrestricted…
If you don’t have a membership, you can get a free one at SketchUcation - as you might desire…
1 Like
Ha! I didn’t even realize that was yours, but I had downloaded it earlier in the day… It does seem to work better, but doesn’t look like it includes the entity name on the "g " line of the OBJ… May not be a deal breaker, but it was the first thing I noticed when I ran a quick test earlier in the day… I’ll keep playing with it… Thanks!
Sure, and I’ve been waiting 12 years for some of the features I’ve logged requests for.
Point is, if you need it now, … use a plugin or write one.
My OBJ output seems to add a name etc: 
For an un-nested face inside the model’s entities:
g model_name-SKP-Default_Material
For an unnamed group:
g model_name-GRP-2000-Default_Material
For a named group:
g model_name-GRP-XXX-2000-Default_Material
For a component:
g model_name-COM-Component_1-1843-Default_Material
The naming convention for ‘g’ is:
model’s name [replacing any # with an _ etc]
-SKP/GRP/COM [container type]
-Container-name [if any, again replacing any # with an _ etc]
-ID number of container [if any]
-Face’s material [again replacing any # with an _ etc]
Whoops, you’re absolutely right - I just overlooked the group names since they were embedded in a larger string… That looks like it might work for what I need!
Just wondering - will it always put out triangle faces (3 verts only)? That is the behavior I’d prefer, so if so, that’s great - just didn’t know if I needed to worry about times it would spit out quads or more arbitrary faces?
It should always triangulate faces…