Hi Robert,
1) Until now I haven't officially supported relative paths specifically....could you elaborate on the behavior you'd expect? Is the relative path you type in something you expect to be saved to the output filename box? Or just a shorthand way of navigating in the file save window? For example, if I navigate to "c:\tyflow\export\files\" and then type my save location as "..\thefile.vrmesh", once the save file dialog closes the path that appears should be "c:\tyflow\export\thefile.vrmesh", correct? Sorry, I just don't work with relative paths very often...
2) My alembic exporter doesn't directly support velocity export (yet)....that's further down the todo list once I develop a unified velocity system for tyFlow for all the different interfaces I support (max has no internal idea of 'vertex velocity' prior to version 2019, so it's a nightmare trying to pass the data around to every renderer and export format). For non-changing topology most renderers should be able to interpret geometry even without those velocity values, but I see you're doing lots of cloth tearing so that I imagine that's the issue...
As for normal flippage and matIDs missing...make sure your proxy loader is set to display full geometry and not preview geometry. I get the visual artifacts you described when in preview mode but not in full mode, when I preview Alembic exports from tyFlow in a VRay Proxy object within max. Also make sure you're using the latest build since matID export support was only added in v0.16041.
As for vrmesh not exporting anything...I did some testing and it seems like the issue is that the export method I'm using now gets mad when there are unescaped special characters in the path (like if your path is "c:\files\test" it interprets the "\t" as a tab), so that will be fixed in the next build. In my current test once I fixed that, your file exported from the Export Particles exporter to a .vrmesh file just fine....and in your write-up above you have lots of "\t"s, so I'm guessing that was the problem.
3) I can't speak for Max's built-in Alembic exporter because unfortunately Max's current Alembic implementation has a bunch of bugs and limitations (it doesn't correctly support matIDs on changing topology, for one)
The vrmesh exporter having all the correct data makes sense, since ChaosGroup is good at writing working code
1) Until now I haven't officially supported relative paths specifically....could you elaborate on the behavior you'd expect? Is the relative path you type in something you expect to be saved to the output filename box? Or just a shorthand way of navigating in the file save window? For example, if I navigate to "c:\tyflow\export\files\" and then type my save location as "..\thefile.vrmesh", once the save file dialog closes the path that appears should be "c:\tyflow\export\thefile.vrmesh", correct? Sorry, I just don't work with relative paths very often...
2) My alembic exporter doesn't directly support velocity export (yet)....that's further down the todo list once I develop a unified velocity system for tyFlow for all the different interfaces I support (max has no internal idea of 'vertex velocity' prior to version 2019, so it's a nightmare trying to pass the data around to every renderer and export format). For non-changing topology most renderers should be able to interpret geometry even without those velocity values, but I see you're doing lots of cloth tearing so that I imagine that's the issue...
As for normal flippage and matIDs missing...make sure your proxy loader is set to display full geometry and not preview geometry. I get the visual artifacts you described when in preview mode but not in full mode, when I preview Alembic exports from tyFlow in a VRay Proxy object within max. Also make sure you're using the latest build since matID export support was only added in v0.16041.
As for vrmesh not exporting anything...I did some testing and it seems like the issue is that the export method I'm using now gets mad when there are unescaped special characters in the path (like if your path is "c:\files\test" it interprets the "\t" as a tab), so that will be fixed in the next build. In my current test once I fixed that, your file exported from the Export Particles exporter to a .vrmesh file just fine....and in your write-up above you have lots of "\t"s, so I'm guessing that was the problem.
3) I can't speak for Max's built-in Alembic exporter because unfortunately Max's current Alembic implementation has a bunch of bugs and limitations (it doesn't correctly support matIDs on changing topology, for one)
The vrmesh exporter having all the correct data makes sense, since ChaosGroup is good at writing working code