Octane Sketchup Exporter 1_00-03 Tweet

[TIG]

Here's v03.
The OBJ's MTL file's Kd values now include an adjustment **2.2 for "linear gamma correction".
Apparently all Sketchup exported format file's [OBJ, DAE etc] make their color conversions from "screen RGB" values by a simple division x/255, which it also expects in reverse when receiving the equivalent file format via its importer.
However, some apps - like Octane - expect "linear RGB" values with gamma correction [(x/255)**2.2] - so without this the unadjusted colors may look washed-out/muddy...
This algorithm update now makes the Exported OBJ/MTL files tailored to suit Octane's requirements for gamma correction.
This is in contrast to the native Pro OBJ Exporter that still makes unadjusted MTL Kd values etc...
This newest Exporter's MTL format file might also be suited for use in some other apps [Blender?], but note that reimporting such a file into Sketchup will result in the imported objects' colors appearing overly strong - e.g. an 'orange' when reimported will look noticeably 'redder'...

As usual...
Install it by extracting the contents of the ZIP into your Plugins folder, maintaining all helper files within their subfolders, as seen inside the ZIP, when appropriate.
Restart Sketchup to auto-load it.
Read the instructions provided...

[Interfaces]

TIG fantastic thank you, you're very good,
it works very well now.

I do not understand why not use octane numbers RGB 0, 255 in its interfaces.

Today it is not very functional

I often use the RAL CLASSIC, PANTONE ... Is it possible to add them.

THANKS

[abstrax]

TIG fantastic thank you, you're very good,
it works very well now.

I do not understand why not use octane numbers RGB 0, 255 in its interfaces.

Today it is not very functional

I often use the RAL CLASSIC, PANTONE ... Is it possible to add them.

THANKS

This is obviously something the exporter can't influence, since it's the UI of Octane defining how stuff is displayed in Octane. If you want to enter 0..255 numbers, just click on the color widget and use the color picker that opens.

Cheers,
Marcus

[Interfaces]

Sorry but your system is not functional, all other software uses the digit 0 -255

to get an exact color I have to gone through photoshop.
In my opinion I am not alone in this thought.

THANKS.

[Jaberwocky]

Cheers Tig

[TIG]

Many apps [like Sketchup] use RGB 0..255
Although you can also specify colors in several other ways.

OBJ/MTL format shows Kd as RGB values 0..1, as do other file formats like DAE, so these need to be derived from the RGB 0..255 system in the originating app.
Online guides and stuff I've found suggest that it's a simple conversion x/255 to get the 'float equivalents' 0..1.
Indeed, Sketchup's own OBJ exporter does this very thing; and its OBJ importer[s] assuming the equivalent when converting the values back into 0..255 system.

Some apps like Octane [and I suspect Blender etc] assume that the OBJ/MTL has 'linear' RGB values, rather than 'screen' values - something I find odd since the 'standard' OBJ way seems to use 'screen', so why isn't the adjustment to 'linear' made when importing into such apps? or at least available as an option 'flag', rather than this bald and poorly documented assumption - and 'assumption' is the mother of all ****ups as we all know too well.
Thus using the standard output from apps like Sketchup Pro's native OBJ exporter the colors will look washed-out or muddy in the OCS...
That said my latest Exporter update now converts the SKP's RGB vaues into the MTL's using (x/255)**2.2 which seems to adjust them to numbers that Octane likes and will displaysin the OCS visually matching the original 'screen' RSBs in the SKP... However, as was said earlier, the OBJ/MTL will then be 'wrong' [too saturated] when imported into other apps that justifiably might expect an unadulterated MTL encoding...

[clausgs]

HI TIG

First of all thanks for a nice work regarding this sketchup exporter and other great plugins you have made for sketchup.

I have started to do some heavy interior sence where the Tris count, in Octane, is over 300000. For Octane that is not a problem but for sketchup to export it with your plugin it takes about 15 min.
Is there any way to reduce this exporting to OBJ time. In my case the rendering takes about 5 to 10 min, and the exporting 15 min...

Hope there is some way to speed it up.

Brg.
Claus S

[TIG]

Do you really think that if I could make it faster that I would have not done so

It's exporter's timing is limited by Ruby's data-processing methods and the model's complexity.
If you look at the OBJ file size for this many entities you'll see it'll be enormous, so 15minutes seems reasonable to me - the rendering time isn't that much faster, especially if you keep refining the res etc !

If you can't find something else worthwhile to do for 15minutes... then may I suggest that buy SketchUp Pro, use it's built-in OBJexporter - it is a binary app and therefore runs somewhat faster, although the OBJ file size may be even bigger than mine!
Then manually create the OCS and add that OBJ node, or swap this new OBJ node for an exporter-made OBJ node in an exosting OCS - this way you keep the camera/sun etc... Or export the camera/shadow as OCMs [see another thread in this forum] and import that with your ProOBJ node...
However, all of these extra steps will undoubtedly eat up the time savings

I can't see how to make much of an impact on processing speed using raw-Ruby - this latest version is a few % faster because it handles shared vertex data differently, but I can't see much else that can readily be 'streamlined'...

[Force44]

Hi Tig!
Your exporter is too slow then sketchup exporter.
when we have more speed from you application ?

If compared 100 % Sketchup and 30 % octane sketchup exporter _00-03((((

[clausgs]

HI Tig

I do understand that more complex models will take longer time to export, I just try to find ways to speed things up if possible at all, maybe like what you described here.
Thanks
Claus S