Animation frames wont save on hdd

[portnicki]

Hey Paul,

I brought a small modo-Octane project from home to work (both modo 701 SP5).
the animation frames will render properly but they wont save on the harddrvie.

I've tried saving to different folders, tried changing the name prefix. Nothing helps.
I'll be happy to provide the scene file if u need it.

PS. the animation renders and saves fine back on the home computer.

[Greg]

I seem to remember an issue with spaces in the filename or folder....are you using under scores? worth a try.

[portnicki]

thx Greg but that's not it.
One of the very first things I tried was changing the output folder on the new machine, and also the file name prefix.
Did not help

When I started a completly new document and rendered a simple animation - the files saved appropriately.
So it must be something with this specific project

[face_off]

Make sure the "save to" folder exists - since I don't think Octane will create the folder if it does not. Also, make sure you have write access to that folder. And finally, after rendering the animation, check the Octane Log for any error messages.

Paul

[portnicki]

hej Paul.

the folder does exist. I'm admin on the system so I don't think it's permissions issue. I'll check the Octane log in a sec.
Would u be so kind to check out the scene if it works on your system?

[face_off]

Would u be so kind to check out the scene if it works on your system?

Sure - pls send it to paul at physicalc-software dot com.

Paul

[face_off]

Thanks for sending me the scene. It looks like the save format is invalid in the LXO. So go to Kernel->Animation and reselect the Save Format.

Paul

[portnicki]

Thanks for sending me the scene. It looks like the save format is invalid in the LXO. So go to Kernel->Animation and reselect the Save Format.

Paul

Thank you Paul. It works fine now.
But what the hell? I mean how did that get corrupt? I mean I would never ever think of re-selecting the file format. Is this a modo bug of some kind?

Nonetheless thanks for helping me out with this I'm glad I asked 'cause this would never occur to me.

[face_off]

But what the hell? I mean how did that get corrupt? I mean I would never ever think of re-selecting the file format. Is this a modo bug of some kind?

I'm not sure - when I traced through the code the Modo API was reporting an "invalid" value in the file format. I have never seen that before, and I don't have an explanation as to how it happened - sorry.

Paul