OTOY Forums

There seems to be a same issues of checking, when you move an instance (only when create a multiples instances) :
1) load a character and put hair (put it as child under character), wardrobe (put it as child under character)
2) make an instance of the character (with hair and wardrobe). Render OK. move it : render OK
3) make multiple instances of the same character (using Create/New Node Instances), move one of these instances, and render : Oh hair and wardrobe don't move with the character.
4) Need to rebuild the scene to render correctly.

I have changed the way mesh changes are detected in the new release of the plugin. Could you pls check if that addresses the above problem, and if not, let me know.

Paul

face_off wrote:

There seems to be a same issues of checking, when you move an instance (only when create a multiples instances) :
1) load a character and put hair (put it as child under character), wardrobe (put it as child under character)
2) make an instance of the character (with hair and wardrobe). Render OK. move it : render OK
3) make multiple instances of the same character (using Create/New Node Instances), move one of these instances, and render : Oh hair and wardrobe don't move with the character.
4) Need to rebuild the scene to render correctly.

I have changed the way mesh changes are detected in the new release of the plugin. Could you pls check if that addresses the above problem, and if not, let me know.

Paul

Thanks for fixing this so quickly. Do we download the new release from the first post in this thread or from our accounts?

Hi Paul,

I don't know if the one on the fisrt post is the lastest one (2.25.0.16), but it doesn"t fix my issue of moving instances without rebuild complete scene.

itou31 wrote:Hi Paul,

I don't know if the one on the fisrt post is the lastest one (2.25.0.16), but it doesn"t fix my issue of moving instances without rebuild complete scene.

Me neither. Checking the OctaneLive tab in the plugin, R2.25.0.16 was released on 21 March 16 so it can't be the latest release. Checked my account and all new builds are released here first.

I don't know if the one on the fisrt post is the lastest one (2.25.0.16), but it doesn"t fix my issue of moving instances without rebuild complete scene.

Sorry - I wasn't clear with that. It's in the latest TEST build (3.0.12.20). This quite a substantial change to the plugin, so it's not a change I would put through to the 2.25 STABLE release until users have indicated the TEST version is working well for them.

Paul

face_off wrote:

I don't know if the one on the fisrt post is the lastest one (2.25.0.16), but it doesn"t fix my issue of moving instances without rebuild complete scene.

Sorry - I wasn't clear with that. It's in the latest TEST build (3.0.12.20). This quite a substantial change to the plugin, so it's not a change I would put through to the 2.25 STABLE release until users have indicated the TEST version is working well for them.

Paul

How do I test this if I'm still using v2? I haven't upgraded to v3 yet because it's a test version and I need to be able to render animation reliably. Can I install v3 over v2 and then revert back to v2? The project I'm working on where I encountered the problem with the d-formers not updating uses v2 of the plugin. Will it also be compatible with v3?

How do I test this if I'm still using v2? I haven't upgraded to v3 yet because it's a test version and I need to be able to render animation reliably. Can I install v3 over v2 and then revert back to v2? The project I'm working on where I encountered the problem with the d-formers not updating uses v2 of the plugin. Will it also be compatible with v3?

If you temporarily upgrade to version 3.0 of the plugin, save the .duf files as a different name, so your Octane 2 save info is not overwritten. That way, if you need to come back to Octane 2.25 you just re-install that version of the plugin and can re-open those scenes without the risk of the Octane 3 data in the .duf file causing issues.

Paul

Hi Paul,

Ok, just test with the 3.0.12.20.
Not fixed (for me on instances moving). I need to rebuild the scene if I move an instance. if I move the original, all is OK. So same as previous version.

I'm sorry that the v3 update hasn't solved your problem itou31. It seems to work really well for my scene with animated d-formers. In fact it's shaved about 30 seconds off render times for each frame. v2 took 117 seconds to render a frame (without updating the d-formers) while v3 takes 47 seconds to render the same frame with d-formers updating correctly. I'm impressed!

My only concern is whether v3 is developed enough to completely render my animation? It seems to render each frame correctly but is it missing some features I'm not aware of? I'd like to begin a 60 hour animation render so it's pretty crucial v3 is up to that.

There seems to be a same issues of checking, when you move an instance (only when create a multiples instances) :
1) load a character and put hair (put it as child under character), wardrobe (put it as child under character)
2) make an instance of the character (with hair and wardrobe). Render OK. move it : render OK
3) make multiple instances of the same character (using Create/New Node Instances), move one of these instances, and render : Oh hair and wardrobe don't move with the character.
4) Need to rebuild the scene to render correctly.

I can reproduce this issue on the latest build. It is a plugin plugin bug, but proving to be very hard to fix. I will see what can be done...

Paul