Separately, and I'm used to this getting swatted over to Deadline and ultimately my problem to solve is a problem on Linux.
Deadline sniffs out paths to convert from X:/ to /mnt to accommodate cross-platforms however fails to detect the Deep Image path - I don't know why, not sure how Octane presents paths or how Deadline needs to find those paths - it can detect/convert RGBTextures etc and all other Houdini paths I'm using (so it's already 99% Octane compatible) and only fails on this Deep Image.
As I mentioned, I'm used to these errors being left in the ether however, last time the Otoy Houdini developer was found guilty of making inconvenient changes and the community made him change the Octane behaviour back (lol!)
2024-03-28 12:13:35: 0: STDOUT: 12:13:35 INFOR: [save image] -------- Saving the EXR "/mnt/Projects/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: [Octane] 12:13:35 INFOR: [save image] -------- Saving the EXR "/mnt/Projects/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: 12:13:35 INFOR: [save image] -------- Saving the EXR deep image to the "X:/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1_Deep.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: [Octane] 12:13:35 INFOR: [save image] -------- Saving the EXR deep image to the "X:/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1_Deep.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: *** OCTANE API ERROR: can't open '/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1_Deep.0061.exr' for writing.
2024-03-28 12:13:35: 0: STDOUT: *** OCTANE API INFO: ERROR: failed to export the deep image file
OctaneRender 2023.1.2 for Houdini production (2023.1.2.1)
Moderator: juanjgon
- ricky_otoy
- Posts: 289
- Joined: Mon Jun 19, 2023 6:34 am
Hey there Renbry,
Sorry for the delay, we finished investigating the pathing issue from our side and unfortunately it does seem like this one is on Deadline's side.
If I may, I would suggest submitting a support ticket with AWS, hopefully they can get it resolved for you ASAP!
Sorry for the delay, we finished investigating the pathing issue from our side and unfortunately it does seem like this one is on Deadline's side.
If I may, I would suggest submitting a support ticket with AWS, hopefully they can get it resolved for you ASAP!
Hi Ricky,
Ok I'll chase that up with Deadline.
How about the first thing I posted re: the Image File Path Prefixes not doing the usual Houdini thing and letting us use expressions which are expanded automatically ?
viewtopic.php?f=102&t=83043#p432348
We'd love to reference Versions and such from other areas of Houdini however it seems that I have to have static Strings in there only. Am I missing something ?
Thanks!
Ok I'll chase that up with Deadline.
How about the first thing I posted re: the Image File Path Prefixes not doing the usual Houdini thing and letting us use expressions which are expanded automatically ?
viewtopic.php?f=102&t=83043#p432348
We'd love to reference Versions and such from other areas of Houdini however it seems that I have to have static Strings in there only. Am I missing something ?
Thanks!
- ricky_otoy
- Posts: 289
- Joined: Mon Jun 19, 2023 6:34 am
Hi, I was talking about that post too.Renbry wrote:Hi Ricky,
Ok I'll chase that up with Deadline.
How about the first thing I posted re: the Image File Path Prefixes not doing the usual Houdini thing and letting us use expressions which are expanded automatically ?
viewtopic.php?f=102&t=83043#p432348
We'd love to reference Versions and such from other areas of Houdini however it seems that I have to have static Strings in there only. Am I missing something ?
Thanks!