Re: Pointlocators out of sync
+1000 to what Vladimir said. Cached locations always loose contexts and does not resolve correctly, giving you red nodes all over the icetree. On the other hand, from my experience reinterpreting locations also crashes frequently. So, keep incremental backups! =) 2013/6/26 Gustavo Eggert Boehs gustav...@gmail.com Thanks Vladimir, your approach is solid :D Just what I needed to keep me sane! 2013/6/26 Vladimir Jankijevic vladi...@elefantstudios.ch that's a no go. I think the simplest way is to have a non-deforming and a deforming mesh in your scene. first take the ref from the non-deforming and then reinterpret the location on the deforming. this can be built really easily with a switch. I never managed to cache locations safely. Softimage behaves really weird concerning location interpretation. Cheers Vladimir On Wed, Jun 26, 2013 at 6:13 PM, Gustavo Eggert Boehs gustav...@gmail.com wrote: Hi guys, I am adding fur to a character and having a hard time with pointlocator consistency across ref models. I have a scene where I do my combing and am outputing a model that loads a combing cache. I intended to cache the strandspositions, the initial pointposition and normal, and a pointlocator to get the current position and normal on the surface to deform the strands acordingly. Sadly I get quite an incosistent behaviour with this locators across models. Simply cant get ref models to cooperate, and even regular models easily loose sync. This is the message I get: # WARNING : 3000 - Caching : PointLocator data gb_kH_EmmitLocation was generated from a different geometry. Cachefile is out of sync. I am pretty sure the mesh is exactly the same. Is my workflow not ideal? How are you guys performing such task? Best regards, -- Gustavo E Boehs http://www.gustavoeb.com.br/blog -- --- Vladimir Jankijevic Technical Direction Elefant Studios AG Lessingstrasse 15 CH-8002 Zürich +41 44 500 48 20 www.elefantstudios.ch --- -- Gustavo E Boehs http://www.gustavoeb.com.br/blog
Pointlocators out of sync
Hi guys, I am adding fur to a character and having a hard time with pointlocator consistency across ref models. I have a scene where I do my combing and am outputing a model that loads a combing cache. I intended to cache the strandspositions, the initial pointposition and normal, and a pointlocator to get the current position and normal on the surface to deform the strands acordingly. Sadly I get quite an incosistent behaviour with this locators across models. Simply cant get ref models to cooperate, and even regular models easily loose sync. This is the message I get: # WARNING : 3000 - Caching : PointLocator data gb_kH_EmmitLocation was generated from a different geometry. Cachefile is out of sync. I am pretty sure the mesh is exactly the same. Is my workflow not ideal? How are you guys performing such task? Best regards, -- Gustavo E Boehs http://www.gustavoeb.com.br/blog
Re: Pointlocators out of sync
that's a no go. I think the simplest way is to have a non-deforming and a deforming mesh in your scene. first take the ref from the non-deforming and then reinterpret the location on the deforming. this can be built really easily with a switch. I never managed to cache locations safely. Softimage behaves really weird concerning location interpretation. Cheers Vladimir On Wed, Jun 26, 2013 at 6:13 PM, Gustavo Eggert Boehs gustav...@gmail.comwrote: Hi guys, I am adding fur to a character and having a hard time with pointlocator consistency across ref models. I have a scene where I do my combing and am outputing a model that loads a combing cache. I intended to cache the strandspositions, the initial pointposition and normal, and a pointlocator to get the current position and normal on the surface to deform the strands acordingly. Sadly I get quite an incosistent behaviour with this locators across models. Simply cant get ref models to cooperate, and even regular models easily loose sync. This is the message I get: # WARNING : 3000 - Caching : PointLocator data gb_kH_EmmitLocation was generated from a different geometry. Cachefile is out of sync. I am pretty sure the mesh is exactly the same. Is my workflow not ideal? How are you guys performing such task? Best regards, -- Gustavo E Boehs http://www.gustavoeb.com.br/blog -- --- Vladimir Jankijevic Technical Direction Elefant Studios AG Lessingstrasse 15 CH-8002 Zürich +41 44 500 48 20 www.elefantstudios.ch ---
Re: Pointlocators out of sync
Thanks Vladimir, your approach is solid :D Just what I needed to keep me sane! 2013/6/26 Vladimir Jankijevic vladi...@elefantstudios.ch that's a no go. I think the simplest way is to have a non-deforming and a deforming mesh in your scene. first take the ref from the non-deforming and then reinterpret the location on the deforming. this can be built really easily with a switch. I never managed to cache locations safely. Softimage behaves really weird concerning location interpretation. Cheers Vladimir On Wed, Jun 26, 2013 at 6:13 PM, Gustavo Eggert Boehs gustav...@gmail.com wrote: Hi guys, I am adding fur to a character and having a hard time with pointlocator consistency across ref models. I have a scene where I do my combing and am outputing a model that loads a combing cache. I intended to cache the strandspositions, the initial pointposition and normal, and a pointlocator to get the current position and normal on the surface to deform the strands acordingly. Sadly I get quite an incosistent behaviour with this locators across models. Simply cant get ref models to cooperate, and even regular models easily loose sync. This is the message I get: # WARNING : 3000 - Caching : PointLocator data gb_kH_EmmitLocation was generated from a different geometry. Cachefile is out of sync. I am pretty sure the mesh is exactly the same. Is my workflow not ideal? How are you guys performing such task? Best regards, -- Gustavo E Boehs http://www.gustavoeb.com.br/blog -- --- Vladimir Jankijevic Technical Direction Elefant Studios AG Lessingstrasse 15 CH-8002 Zürich +41 44 500 48 20 www.elefantstudios.ch --- -- Gustavo E Boehs http://www.gustavoeb.com.br/blog
