temp directory

[macchiorlatti]

If I open C:/documents/octane/temp/textures I find 1095 .png files (!), can I delete them or I have to preserve them for the next generations?
thank you

os: Windows 8.1

[fuzzybro]

Hi macchiorlatti,

UPD
Don't delete the files if you have important sketchup projects that are configured for octane.

The purpose of this folder is to store textures that are created when Octane Material is being applied to some Sketchup surface, so Sketchup can use it to sync display between Octane viewport and Sketchup viewport and textures from Sketchup materials (SU materials are stores in zip-like files so I need to stored then on a disk to be able to pass it to Octane).

I'll optimize the storage in the next build.

Hope that helps.

[resmas]

Hi macchiorlatti,

UPD
Don't delete the files if you have important sketchup projects that are configured for octane.

The purpose of this folder is to store textures that are created when Octane Material is being applied to some Sketchup surface, so Sketchup can use it to sync display between Octane viewport and Sketchup viewport and textures from Sketchup materials (SU materials are stores in zip-like files so I need to stored then on a disk to be able to pass it to Octane).

I'll optimize the storage in the next build.

Hope that helps.

Hello Fuzzy

In my opinion, if possible, this textures should be saved in the same directory of the project. This way would be easyer to organize our files. Because my documents/octane/temp folder is getting HUUUGEEEE has most of my projects are WIP and SU keep hadding lots of new files.

Is it possible to link the temp textures folder to the directory of the project?



Cheers
Resmas

[fuzzybro]

Hi resmas,

Yea, this makes sense but requires quite a lot of work to implement.
I'll add it to the roadmap.

Cheers,
F

[resmas]

Hi resmas,

Yea, this makes sense but requires quite a lot of work to implement.
I'll add it to the roadmap.

Cheers,
F

Thanks mate. We only ask for hard stuff...much as been done.

Many many thanks.

Cheers
Resmas

[Seekerfinder]

Hello Fuzzy

In my opinion, if possible, this textures should be saved in the same directory of the project. This way would be easyer to organize our files. Because my documents/octane/temp folder is getting HUUUGEEEE has most of my projects are WIP and SU keep hadding lots of new files.?

I'm with Resmas on this.

In relation to materials, here is another suggestion. Face_off gave us the option to associate an Octane LiveDB material *permanently* with Revit system materials. This is great because you quickly learn what 'common red brick' or 'earth' looks like both in Revit and the Octane plugin. From my experience working this way in Revit, I could see the benefits of this workflow in SU. We would need to set up only once a 'base set' of materials associated with the standard SketchUp palette. Then we could add & associate new materials as we progress. Another example of this would be lighting - a certain base colour (typically yellow in my case), represents a blackbody emitter. Need a light in Octane? Simply paint the SU mesh with that colour. Tweak. Done.

Also, I am frankly not quite sure where we are with 'local DB' implimentation, but is referencing a localDB material set as opposed to duplicating materials an option at all? I don't know if Octane allows material node referencing in that way at all and for moving SU files around this could be a problem so it's just a thought I guess but I like to hear if it has any merit.

Best,
Seeker

[fuzzybro]

permanent LiveDB still might be tricky and screw-up material sync which is still has some issues.

LocalDB is Octane Standalone feature only, there is no SDK methods to use it.

[Seekerfinder]

permanent LiveDB still might be tricky and screw-up material sync which is still has some issues.

LocalDB is Octane Standalone feature only, there is no SDK methods to use it.

Ok, but the material files associated with a project still reside on the user's local file structure. So what about the suggestion to 'permanently' link SU materials to Octane ones? This should be possible, no?

Seeker

[fuzzybro]

Hey Seeker,

Not sure, need more details. What's your goal?
If this is for portability between systems then I would rather implement feature to "pack project" which will place all scene data in a folder and reassign all paths according to it.

Al for LiveDB.. LiveDB material is a some sort of definition of a material, not material itself. When you apply material to SU geometry the material has to be changed (texture transformation node, etc) so it no longer corresponds to LiveDB material but it does use the same textures as LiveDB one. LiveDB material textures are downloaded to user folder and stored there. But yeah, I need to know what are you trying to do.

Cheers,
Bro

[Seekerfinder]

Hey Seeker,

Not sure, need more details. What's your goal?
If this is for portability between systems then I would rather implement feature to "pack project" which will place all scene data in a folder and reassign all paths according to it.

Al for LiveDB.. LiveDB material is a some sort of definition of a material, not material itself. When you apply material to SU geometry the material has to be changed (texture transformation node, etc) so it no longer corresponds to LiveDB material but it does use the same textures as LiveDB one. LiveDB material textures are downloaded to user folder and stored there. But yeah, I need to know what are you trying to do.

Cheers,
Bro

I guess it's just like I posted earlier:

In relation to materials, here is another suggestion. Face_off gave us the option to associate an Octane LiveDB material *permanently* with Revit system materials. This is great because you quickly learn what 'common red brick' or 'earth' looks like both in Revit and the Octane plugin. From my experience working this way in Revit, I could see the benefits of this workflow in SU. We would need to set up only once a 'base set' of materials associated with the standard SketchUp palette. Then we could add & associate new materials as we progress. Another example of this would be lighting - a certain base colour (typically yellow in my case), represents a blackbody emitter. Need a light in Octane? Simply paint the SU mesh with that colour. Tweak. Done.

It's just a thought but I SU has been shipping with pretty much the same materials for a long time. So I thought that if we could tell the plugin that a certain SketchUp material should *always* be a certain Octane material in the plug-in (set up once by each user to suit their own needs), it would save a heck of a lot of time setting up materials for every project. For archviz our workflow is repetitive to some degree and I'd like to know SketchUp's 'Translucent_Glass_Gray' will always be my preferred specular material for the plugin etc.....

Make sense? I'd like to hear the thoughts of others on this but, like I said, it works really well in the Revit plugin.

Seeker