eebling Posted June 3, 2017 Share Posted June 3, 2017 So I have an odd problem I haven't been able to figure out yet. I have a Synology DS716+II NAS raid and using it as a shared drive so I can use HQueue to render jobs on other machines. That all works fine to render on the farm, however when I write alembic data to the NAS, I get an error everytime I try to read it back into Houdini or into maya. If I write the exact same alembic data to a local drive on my computer, then there are no read errors. And this seems to only happen with alembic and fbx data. I can write hip files and bgeo's all day to the network drive and everything reads fine, just alembic and fbx data that fails when trying to read it back from the Network drive. Does this make sense to anyone.? I would think if this was a firewall problem or permissions type thing, then no data should read or write to the NAS. The exact error I get when trying to read alembic data back into Houdini from the network drive is "Error evaluating alembic file". ANy help would be appreciated. Thanks E Quote Link to comment Share on other sites More sharing options...
eebling Posted June 3, 2017 Author Share Posted June 3, 2017 Well I was able to find some info about an environment variable named HOUDINI_ACCESS_METHOD and a suggestion in another thread about setting it to a value of 1 (0 by default). That did not fix the alembic or fbx load problems, but setting it to a value of 2 did. This is on a windows system. Can anyone shed some light as to why hip files and sim data and rendered images(exr's) would all read and write fine to the NAS drive with that variable set to a default of 0, but fbx and abc data was not able to read/write correctly.? Does Houdini somehow write those two file types out with different permissions or something.? Thanks for any info. E Quote Link to comment Share on other sites More sharing options...
Atom Posted June 4, 2017 Share Posted June 4, 2017 I know that you can't have a space in the file name, or Alembic read will fail. Maybe somewhere in your network path you have a space character? Quote Link to comment Share on other sites More sharing options...
eebling Posted June 4, 2017 Author Share Posted June 4, 2017 Thanks for the reply. There are no odd naming conventions happening, no spaces, usually use underscores or go with camelCase. Now all is working after changing the HOUDINI_ACCESS_METHOD to be equal to 2, but still unclear as to why other data like hip's and bgeo's worked before changing the variable. Quote Link to comment Share on other sites More sharing options...
octaviuz Posted June 23, 2018 Share Posted June 23, 2018 same here! i had a DS411, got a DS1817, load file...error!! very odd...will change the vairalbe you say see if that woks on my end...anyone has figured out how to fix this, maybe on the Synology NAS end? Quote Link to comment Share on other sites More sharing options...
grendizer Posted August 27, 2018 Share Posted August 27, 2018 (edited) Eebling God bless you for your post! I had the same problem and was pulling my hair. I thought I would never resolve it but thankfully I found your thread! My problem is exactly the same : working on the local D: drive, I imported FBX and Alembic files into my Houdini scene. I didn't have bgeo files. When I opened the file through the network drive N: FBX files appeared normally, but the Alembic files were invisible. Other thing I tested was to import the same Alembic file in a new scene and it failed. Then I followed your advice and all went well! Question : my NAS, on which I mapped the N drive, is also a Synology. Does it happen only with Synology hardware? Or perhaps it's because the NAS has a different login than Windows... Edited August 27, 2018 by grendizer Quote Link to comment Share on other sites More sharing options...
octaviuz Posted August 28, 2018 Share Posted August 28, 2018 I think it is due to a permission issue on the DSM end combined with alembic,,,not sure how to fix it other than the ACCESS METHOD Quote Link to comment Share on other sites More sharing options...
paranoidx Posted April 21, 2020 Share Posted April 21, 2020 lucky that I found this post. Last week Im ok with the network. Until today there is a computer reinstall on Windows 10, thing went wrong on .abc file, this post save me. Thank you. Quote Link to comment Share on other sites More sharing options...
grim0820 Posted March 2, 2021 Share Posted March 2, 2021 (edited) Thank you internet and all you kind people to post this here - I wasted 3 hours on this... HOUDINI_ACCESS_METHOD = 2 Now it is working! All the best!Now it is working! All the best! Edited March 2, 2021 by grim0820 Quote Link to comment Share on other sites More sharing options...
thePaul Posted September 19, 2021 Share Posted September 19, 2021 Thanks for this thread and the solution. Same problem here after switching from QNAP to SYNOLOGY's DS1621+ set HOUDINI_ACCESS_METHOD=2 in bat file works great. Quote Link to comment Share on other sites More sharing options...
90okm Posted September 7, 2022 Share Posted September 7, 2022 HOUDINI_ACCESS_METHOD=2 solves this problem only for houdini obviously....but under windows you will definitely have problems in some other cases... for example arnold won't work in batch mode when it is placed on mapped drive ... houdini would not be able to load packed alembics from synology NAS !! xsense can not export animation to drive mapped on synology ! shit (((( Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.