Tranfering Octane scene between pc's v1.2

[Xipomus]

*** UPDATED FixOctanePaths file *** version 1.2 now. So redownload the zip and extract them and replace the old files. The CollectSceneOctane hasn't changed, but the FixOctanePaths has.

Changelog:
Changelog since 1.1 (release version on this forum)
Bugfix written the Octane_filename.pz3
Extra check for . so only extenstions get used (there was an issue with filenames with hdr in them for instance)
made a function of the repeating things (easier reading and adding or deleting filetypes to search for
more feedback for the user (log to show which paths have been found for which filetype or that nothing has been found)

Hopefully no more weird bugs. Tested with both Poser 2014 and Poser 2012, so should work without issues now in 9, 10, 2012 and 2014. Don't have Poser 8 so can't tell there.

==
With Poser you have the collectSceneinventory script that gets all the textures, camera's, lights ect for a poser scene and saves this in one output folder with a pz3 to point towards this.

It also copies the Addondata that Octane uses, unfortunately when you transfer it to 2nd pc, the model will be mostly blank qua textures, because it will look for the paths of the first's pc library.
The inventory script also ignores what textures you define for Octane (read Livedb), ies lights or Hdr's.

On small scenes, it's easy to edit the pz3 in the output folder and make it work, but bigger scenes take waay to much time.

To fix this, I build 2 scripts for a friend to gather all Octane textures, ies lights and hdr's and put them in the same output folder. The second is for the 2nd to correct the paths for Octane.

It's called collectSceneOctaneInv.pu and it's run from Poser after the collectSceneInventory script.
When you run it, it asks for the pz3 from the collectSceneInventory.

It reads that for the output folder and the textures that are in the Addondata, which are located in the %userprofile%\AppData\Roaming\Poser Pro\10 on mosts systems (win Vista and above).
Then copies those files to the outputfolder.

So all the scene data is now located in the output folder.
You transfer the output folder to the 2nd pc.

- Start Poser on the 2nd pc.
- Run the 2nd script called FixOctanePaths.py
- It asks for the pz3. Point it to the output folder you copied to this pc.
- It replaces all paths in the pz3 and saves it as Octane_filename.pz3. That way you still have the original.
- After that load the Octane_filename.pz3 and start Rendering.

Hopefully it's usefull for somebody.

ps. the code is still very quick and dirt. It can probably be done much better. But it works like this, so i'm not going to mess with it. Feel free to do so. But please post a modified version back so others can use it.

Cheers,

Xipomus

[face_off]

Thanks for the script! Very useful.

Another trick is to use the scene collector BEFORE rendering your scene in Octane - that way when the plugin converts all the materials - it will have the texturemap references from the collector folder rather than you runtime.

The next version of the plugin has a feature where when you load a scene, if it cannot locate a texturemap, you can specify a search directory (which could be the scene collector folder) and it will relink all the files from there.

Thanks again.

Paul

[Xipomus]

Paul,

Only problem with that trick, is you usually want to see the scene before transfering.. so you have to open octane on the orignal pc to see if everything works out.

But still a suggestion, but with this issue in mind.

Ciao

[Scott762]

UGH. I just discovered this problem as I re-installed from a legacy Poser runtime location to the modern User profile location.

I think I followed everything properly, but it didn't work. Of course, I don't have access to the first PC. It's the same PC, just a re-install.

The issue I see here is that it's copying all the data to another folder, so you'll use up a lot more data. I'd much rather fix the paths. Poser had no problems doing this.

[Xipomus]

Dunno which version of Octane you are using. But pz3's when you open them, ask for the new path. But for big scenes this can be a lot of work.

The script was developed at version 1.x, the auto correction paths wasn't there for octane then.

Character's saved with octane data in your library don't ask for changed paths, so that can be a problem.

So in conclusion, the scripts works for fixing a path to central folder. You can always change the code, instead of the central folder, you change it to the new Poser dir + lib, but if you change the way the runtime is filled compared to the original pz3, you best just edit it manually with notepad++

[Scott762]

Thanks Xipomus, I think I found it. I also used Notepad++, the file is huge I don't know how well regular Notepad would handle it.

My post:
viewtopic.php?f=45&t=52251