I’m not sure if it’s a bug, just not supported or something else but while V-Ray renders some Enscape assets from it’s library it seems not to render custom assets I put in Enscapes library as well as external linked skp models which are placed in the scene using Enscape.
I’m not sure if there is a way to work around it or already an update in the making supporting both. I especially converted some models I needed to Enscape assets since I supposed Enscape > V-Ray should work pretty well.
V-Ray renders some Enscape assets from it’s library it seems not to render custom assets I put in Enscapes library as well as external linked skp models which are placed in the scene using Enscape
Custom Enscape assets should work without any limitations.
I can always provide you with a sample seen but I noticed this answer from you on a different thread
So I searched for the log file and I think it’s actually the same issue as Ted encountered especially if you look at the down right log file part of my screenshot.
The location of my custom assets is *E:\Documents\Enscape\custom assets* where **E:\Documents\** is actually the ‘My Documents’ folder but I don’t like it on C for backup reasons.
That custom asset directory you only set once, the first time when you create a custom asset in Enscape and the value is stored in CustomAssetEditorSettings.json located here C:\Users\<user name>\AppData\Local\Enscape. {"ProjectDirectory":"E:\\Documents\\Enscape\\custom assets","OutputDirectory":"E:\\Documents\\Enscape\\custom assets"}
Maybe V-Ray can just check for that specific OutputDirectory value in the Enscape file and a lot of it is solved (or I might think to straight forward )
I’m just testing/playing a bit and let me know if you still can use some example but I think it’s just a path-thing after digging some more.
Maybe V-Ray can just check for that specific OutputDirectory value in the Enscape file and a lot of it is solved (or I might think to straight forward )
We are doing that and that is what bothers me.
We were able to reproduce the missing custom assets scenario only once here in the office and it was with a beta version of Enscape.
After the colleague switched to the official Enscape version all was solved.
We are continuing to investigate…
Well that’s annoying. I tried some things to trick it a bit by not having the model/json in a separate folder and even creating zip + json and putting it at the place for the normal assets. Also copied some over to the maybe default C:/user/username/documents folder but all without luck.
If there’s something I can try to help you guys a bit let me know!
)