07-25-2019, 12:18 AM
(This post was last modified: 07-25-2019, 12:19 AM by robertfreitag.)
Hello, Tyson!
Thanks again for doing all the stuff you are doing!
I've come across multiple issues with caching and would like to know if you are aware of it.
1.)
When I Input a relative path after I previously have chosen a path via the "..." button, it will cache into the wrong directory.
So If I chose "C:\temp\cache\tycache\file.tyc" via the "..." button and then after that change the string in the edit field to a relative
path like ".\cache\mycache.tyc", then it will cache into the wrong directory, but I do not understand the exact behavior in my case it
was suddenly saving it to "C:\temp\cache\cache\tycache\cache\mycache.tyc - but I don't know why exactly.
When I delete the cache node, then create a new one, then input the relative path directly, it works fine.
2.)
I render all my projects with V-Ray Standalone. Having said that, the usual goal for rendering is to "outsource" as much animated geo
as possible into Standalones supported caching formats like abc and vrmesh so that V-Ray does not dump all this info as text into the
vrscene files on export, resulting in huge vrscene files.
Now I'm sure that V-Ray standalone does currently not have a plugin that can interpret Tyflow caches directly and I'm sure it's very
low prio on the to-do list if it is on there at all.
So, I've tried the different export methods from tyflow (Vrmesh and alembic) and came over multiple issues:
Alembic: I export an alembic file via "export particles" node, then I import that abc file via the VrayProxy loader,
the normals are usually flipped and the material IDs are gone, and it looks like the velocities are not exported correctly.
Vrmesh:
In my test, the vrmesh export was doing nothing, not creating a file, just popping up the message box "Vray Proxy export complete!"
3)
After these tests I thought I could just use the "regular" vrmesh exporter or the "regular" alembic exporter on a TyCache object.
The problems are:
Alembic:
It does not export animation at all and does not export material IDs properly when I load the abc via VrayProxy
Vrmesh:
Vertex animation looked okay! It also export the material IDs correctly but apparently velocities are not exported to the vrmesh file.
When I import it via VrayProxy, it does not show motion blur. (the shell feature in the "tearing" section is off).
Additional info:
If I use the vrmesh exporter on the tyflow object (not the tycache object) it the velocities are actually
exported correctly as well as the material IDs and pretty much everything else.
Sorry for the long text but I wanted to include as much info as possible, attached to this thread you will find the scene I used for doing these tests.
Again, thanks for doing all this.
-Robert
Thanks again for doing all the stuff you are doing!
I've come across multiple issues with caching and would like to know if you are aware of it.
1.)
When I Input a relative path after I previously have chosen a path via the "..." button, it will cache into the wrong directory.
So If I chose "C:\temp\cache\tycache\file.tyc" via the "..." button and then after that change the string in the edit field to a relative
path like ".\cache\mycache.tyc", then it will cache into the wrong directory, but I do not understand the exact behavior in my case it
was suddenly saving it to "C:\temp\cache\cache\tycache\cache\mycache.tyc - but I don't know why exactly.
When I delete the cache node, then create a new one, then input the relative path directly, it works fine.
2.)
I render all my projects with V-Ray Standalone. Having said that, the usual goal for rendering is to "outsource" as much animated geo
as possible into Standalones supported caching formats like abc and vrmesh so that V-Ray does not dump all this info as text into the
vrscene files on export, resulting in huge vrscene files.
Now I'm sure that V-Ray standalone does currently not have a plugin that can interpret Tyflow caches directly and I'm sure it's very
low prio on the to-do list if it is on there at all.
So, I've tried the different export methods from tyflow (Vrmesh and alembic) and came over multiple issues:
Alembic: I export an alembic file via "export particles" node, then I import that abc file via the VrayProxy loader,
the normals are usually flipped and the material IDs are gone, and it looks like the velocities are not exported correctly.
Vrmesh:
In my test, the vrmesh export was doing nothing, not creating a file, just popping up the message box "Vray Proxy export complete!"
3)
After these tests I thought I could just use the "regular" vrmesh exporter or the "regular" alembic exporter on a TyCache object.
The problems are:
Alembic:
It does not export animation at all and does not export material IDs properly when I load the abc via VrayProxy
Vrmesh:
Vertex animation looked okay! It also export the material IDs correctly but apparently velocities are not exported to the vrmesh file.
When I import it via VrayProxy, it does not show motion blur. (the shell feature in the "tearing" section is off).
Additional info:
If I use the vrmesh exporter on the tyflow object (not the tycache object) it the velocities are actually
exported correctly as well as the material IDs and pretty much everything else.
Sorry for the long text but I wanted to include as much info as possible, attached to this thread you will find the scene I used for doing these tests.
Again, thanks for doing all this.
-Robert