Corrupt orbx file when saved as a package.

[MB]

Has anyone encountered this:

Saving a scene as a package writes a corrupt orbx file that subsequently cannot be opened.
It appears that it is all of the image files that get corrupted, so when subsequently opening the orbx file any image texture based materials will not load. if you unpack the package, all of the image file types in the 'assets' folder (jpg, tiff, png) will not open in an image editor.

Does anyone have a fix for this or know what causes it to happen. Not positive but I think it only happens when overwriting a package that has been previously saved.

thx

[Zay]

Which Octane version are you using?

You can try this. Unpack the .orbx. Close Octane. Do your image editing. Open the unpacked .ocs and make the changes and then pack it again.

[pegot]

Yes I have had a few instances where my ORBX files were corrupted though I think my issue may be slightly different.

My problem occurred on ORBX files exported from Octane Blender after a night of rendering in Stand Alone. When I checked the job in the morning the rendering completed successfully but after saving the file (to ensure my changes in SA to the ORBX were kept) and upon trying to reopen the saved ORBX, Octane could no longer find paths to the internal assets. See attached screen shot.

The assets are still in the ORBX file though as file size does not change and, in fact, all the assets could be unpacked and later manually re-linked.

This issue occurred at least 4 or 5 times for me and always when I was rendering an ORBEX from my file server. Don’t know if that, and the fact that the computer goes to sleep after some time of inactivity after the render completes, has anything to do with it.

If devs want to take a look at my ORBX file PM me.

[john_otoy]

Saving a scene as a package writes a corrupt orbx file that subsequently cannot be opened.

Hi MB. I think you may have already submitted your corrupted orbx to support? Would it be possible to get a zipped copy of the original scene and its files, so we can try running an export here?
Please PM me, or reply to support if you've already contacted them.

Yes I have had a few instances where my ORBX files were corrupted though I think my issue may be slightly different.

Hi pegot. I have PMed you.

[abstrax]

It's the first time I hear of those problems. I had a look at the ORBX from pegot and it consists mostly of 0s. What is interesting though is that in both cases, the OCS file inside the package is intact while all assets are corrupted. The assets are still there and seem to have the correct sizes, but only contain garbage. Not sure what to make of it.