Octane Sketchup Exporter - Full 1022-07 Tweet

[TIG]

Here's version 1022-07

Octane_1022-07.zip

(513.98 KiB) Downloaded 349 times

An attempt at using a Project-Path containing special-characters/accents is now better flagged.
Special-characters in Project-Path are now allowed on MAC [Unicode], BUT although special-characters could now work on PC, they can cause failure in the 'Octane-Render' itself - as it seems to convert Unicode to ANSI when reading from the command-line in cmd or vbs ?... So on PC they are still not allowed - stick to A-Za-z0-9_- + <spaces> for PC project-paths. On PC and MAC project-names should consist of A-Za-z0-9_- [NO <spaces>].
On a PC the ".cmd" files are now written to "C:\Temp\" and auto-deleted.
Problem with v8/Win7 unsaved model.path resolved.

Note: To delete a flaky model's corrupted ‘Octane’ attribute_dictionary values you can paste
ad=Sketchup.active_model.attribute_dictionary("Octane");ad.each{|k,v|ad.delete_key(k)}
into the Ruby Console. It defaults all of the 'Octane Render Exporter' dialog-settings, for that model.

I hope this resolves issues a few of you have with recent versions and the new SUp v8.

Feedback please

[DigitalDouble]

Hi Tig.

With the new version, The dialog box does pop up now, great job !

However, when clicking on the render button It doesn't fire up Octane.

I noticed that it was able to creates the "untitled.obj" and "untitled.mtl" files and the textures directory but does not fire up Octane.
NO *.ocs and cmd files are created.

BTW, The skp file name is not untitled.skp but rather test.skp - isn't it supposed to use the skp file name ?
YOu can see in the dialog box that it doesn't really pick up the project name, but uses always "untitled"




Uploaded with ImageShack.us

[DigitalDouble]

Edit:

I re-read your post and noticed that the .cmd is now written to C:\temp.

I never had this directory so I created one !
That seems to fix it !

So the only outstanding issue I can see right now is the project name - hard-coded to untitled instead of using the actual project name.

[TIG]

Glad it works...

I never though of anyone not having the standard C:\Temp\ folder

I'll have to add something in the next update to make it if it's not there ! Or revert to the project-folder ? OR better use the User's ENV["TEMP"] folder...

The project-name will take any new value you type in.
Note: if it's a copy of an earlier SKP that you had named 'untitled', that you had run the tool on, then it will have remembered the project-name value from that, even if the SKP now has a new name - the dialog's values exist across sessions saved with the SKP - a copy of the SKP remembers those values too. The next time you reopen the SKP and run the tool the dialog will show the last saved project-name...

Try making a new SKP file, saving it with a new-name and then running the tool - it should then start the dialog with the project-name matching the SKP-name - subject to adjustments for spaces and non-standard characters...

[DigitalDouble]

Tig,

Yes, you were right.
There is no issue with the project name ...

So, all seems to work perfect on my end now...

Thank you for all the hard work and the speedy turn-around !!!

[TIG]

That's great

See the next version... 1022-08...
It even traps for user not having a C:\Temp\ folder !