[7.1.0.27] textures not mapping correctly in cloud

[ctjanney]

I just read the release notes for 7.1.0.30, and it looks like this may be fixed, so forgive me…

DL 7.1.0.27
Google cloud
linux

path mapping is working for scene files and render output, since scenes are being picked up from their cloud directories, and renders are going to their cloud directories just fine, but texture files and other external assets (alembic files, etc.) are still being read from the local file system and dragged, kicking and screaming, to the clouds (there’s a visual for ya).

I’ll test the new build in the morning, and I hope this is fixed, but wanted to make note of it.

Thank you,

-ctj

[Coulter]

I spoke to Ryan about this. Here is his response:

Typically, all assets that a Maya scene uses are in the Maya project folder, which is something that Deadline passes to Maya at render time (after the path mapping has taken place). However, it’s possible for scenes to reference assets outside of the project folder, in which case path mapping must be done on the asset paths in the scene file.

We do support this, but ONLY for scene files saved to the .ma format (which are ASCII format). We cannot support this for .mb scenes, which are binary format.

Would this explain the behavior you are seeing?

[ctjanney]

Ah, and that’s why it works fine for the nuke scripts, because they are ascii.