Hi Chaps
Hip attached.
If I parent geometry to a null, and then run a DOP particle sim inside that geo, then a strange thing happens; I can't view the scene properly through an animated camera whilst inside the DOP network.
If I dive up one level and view the DOP network, or import the fields into the same geometry context - the positional relationship between a camera object and the geometry is fine. But once inside the DOP network, it shifts……and cannot view the sim in context of the camera.
Even if i select ‘Use Object Transform’ on the POP Object, which has no effect.
Well, if anyone can check out my hip - give me any pointers - that would be most appreciated. I'd liek to run an entire SIM in one geo obj node - not across multiple Obj's
Many Thanks..
Transformation issue with DOP Network inside geo
2711 5 0- Neil78
- Member
- 272 posts
- Joined: July 2010
- Offline
- anon_user_37409885
- Member
- 4189 posts
- Joined: June 2012
- Offline
- Neil78
- Member
- 272 posts
- Joined: July 2010
- Offline
- Neil78
- Member
- 272 posts
- Joined: July 2010
- Offline
- anon_user_37409885
- Member
- 4189 posts
- Joined: June 2012
- Offline
Does pinning the viewport where it's working properly work for you? You can then dive into the ‘/obj/NEW_EMBERS_SIM/SIM’ and be viewing through the camera.
When you dive into the Dop network its losing the null-parent translation-offset, you can that it's jumping back to 0,0,0 by viewing the simulation afar.
When you dive into the Dop network its losing the null-parent translation-offset, you can that it's jumping back to 0,0,0 by viewing the simulation afar.
- Neil78
- Member
- 272 posts
- Joined: July 2010
- Offline
Cheers MartybNz - yeah pinning 1 step up is the only option…annoyingly.
Thanks for taking a look.
It seems DOPs network in a geometry context loses that parent translation offset. So to view everything in context correctly, including DOP's guides etc, you need a seperate DOP object….. can't find way round it.
What a larf. :mrgreen:
Thanks for taking a look.
It seems DOPs network in a geometry context loses that parent translation offset. So to view everything in context correctly, including DOP's guides etc, you need a seperate DOP object….. can't find way round it.
What a larf. :mrgreen:
-
- Quick Links