Ornatrix Maya: Redshift Proxies Ornatrix vs direct render creates tiny jitter/flicker fur. (maya)

Hello, We are generating redshift proxies as we are using ornatrix, for fur, with our characters. If we direct render it across numerous computers the fur is rock solid and doesn’t flicker but if we generate the Redshift proxy (on mulitple computers) and then render the it across multiple computers the fur flickers - just tiny little jitters. As the Redshift proxies is meant to be all the translation data stored to disk I would expect it to match a direct render without proxies. Any ideas? This has happened for at least the last 10 or so version of ornatrix/redshift. Cheers, Jeremy
2 June 2021 #29997
Jeordanis Figuereo	Hi Jeremy, Do you have Remember Roots Positions enabled in Hair from Guides? What happens if you export the proxy using a single machine? Jeordanis Figuereo (Product Designer. EPHERE Inc.) LinkedIn Discord
3 June 2021 #29998
Jeremy Howdin	Hello, We sure do. If Remember Roots Positions wasn't on a direct render would flicker/jitter too. If we proxy on one computer it doesn't flicker/jitter which is our current work around. My point is that it doesn't flicker/jitter on a direct render and RS proxy should be exactly the same (across multiple computers) but it isn't. I get if we have simulation on it needs to be on one computer but it shouldn't be for a non simulation hence a direct render on mulitple computers work. Any other ideas? Cheers, Jeremy
3 June 2021 #29999
Jeordanis Figuereo	Hi Jeremy, Once the proxy is exported Ox doesn't have any control on it. I'm investigating this issue but I'm not sure this is related to Ornatrix. Meanwhile is a good idea to ask on RS forums. I will get back to you soon. Jeordanis Figuereo (Product Designer. EPHERE Inc.) LinkedIn Discord
9 June 2021 #30013
Jeremy Howdin	Hello Jerodanis, I have reported the bug on the redshift forum. No luck yet on getting a resolve. I have just updated the report with some extra info/files that will hopefully assist in the resolution. This is a major problem with our pipeline as we can't be restricted to proxing on one computer as it's slow. Appreciate any help you can provide. https://www.redshift3d.com/forums/viewthread/38013/P15 Cheers
10 June 2021 #30018
Jeremy Howdin	Hello, Would great to get some help on this one as this will be a deciding factor to change hair solutions. It impacts our pipeline far too much. Here's the redshift thread. https://www.redshift3d.com/forums/viewthread/38013/P15 Cheers, Jeremy
10 June 2021 #30020
Jeordanis Figuereo	I asked a member of our team to participate on the thread. He will be there as soon as possible. Jeordanis Figuereo (Product Designer. EPHERE Inc.) LinkedIn Discord
10 June 2021 #30021
Jeremy Howdin	Great - Thank you.
19 June 2021 #30072
Jeremy Howdin	Hello, Updating what happed with the fur flicker. Confirming that when exporting ornatrix as rs proxy and rendering via mayaBatch producers the fur flicker. It’s when ornatrix has a “push away from surface” in the stack. This uses a collision with the meshes: https://ephere.com/plugins/autodesk/maya/ornatrix/docs/1/Push_Away_From_Surface.html mayaBatch when used with deadline keeps the scene open between rendering frames to save loading time. However this is where the issues is. For example when rendering frame 1 and then jumping to frame 20 causes the issue. So it’s not a redshift export rs proxy. I think it is a maya issue as it happens with other things as well. mayaCMD works perfectly but unfortunately the Deadline submitted forces the option to use mayaBatch when exporting rs proxy. Anyway thank you for your help and very happy I have isolated the issue. If you have any other work arounds that would help. Cheers, Jeremy

Posted by:		Jeremy Howdin
Data created:	2 June 2021