Minor issues I'm having

[Mugz]

Hi all, I've just got the plug in up and running, sorta (version 2.6.0.29)

1)Camera. I'm having is that that I can move the camera via modo but how do I move it in the octane render window? Also, and maybe more confusing to me. The octane camera now seems to be completely uncoupled from the viewport? For instance in the standalone I drag sliders around like a mad man changing parameters and I see those changes take place REAL TIME. Now it's not until you move and release the slider that the update takes effect in the viewport??? This is awful, how can I fix this?

2) I have a gemstone on screen and instead of looking faceted it seems like octane is rounding all the facets so now the top of the stone looks like a cab (a marble cut in half).

[Mugz]

Anyone???

[face_off]

Hi

1)Camera. I'm having is that that I can move the camera via modo but how do I move it in the octane render window? Also, and maybe more confusing to me. The octane camera now seems to be completely uncoupled from the viewport? For instance in the standalone I drag sliders around like a mad man changing parameters and I see those changes take place REAL TIME. Now it's not until you move and release the slider that the update takes effect in the viewport??? This is awful, how can I fix this?

I not sure what you mean here....are you trying to move the camera with a slider? The camera is sync'd to the current Modo render camera - so select the "(Render Camera)" in the Modo viewport, and the Octane viewport will be sync'd to it.

2) I have a gemstone on screen and instead of looking faceted it seems like octane is rounding all the facets so now the top of the stone looks like a cab (a marble cut in half).

Turn smoothing off for gemstone material.

Paul

[Mugz]

Hi Paul

So what I mean about the camera is this. When I adjust the camera parameters with the octane viewport controls ie aperture, exposure, fstop etc. The effect does NOT happen real time and only takes effect once I release the slider?? In the standalone (and rhino) when you slide a slider the change is visible as you are making changes, inside modo this does not seem to be happening? Also and I'm having this issue in the standalone and all the plugins is that I have to change the aperture to zero just to get my object to show (working in mm) because otherwise my design is so blurred it's like it's not even there.

As for the gemstones not being faceted. I understand that's the smoothing option but I can't seem to find it to shut it off. I'm sure it's simply because I've not spent enough time in the plugin.

I just wish there were better videos for all these plugins, they all assume you have knowledge of the host software which isn't always the case. I for instance own modo and rhino but don't use them for modeling or rendering and am trying to adopt one or the other as a medium to get my rendering/animations done.

I'm used to working in programs like Bunkspeed where you can move, duplicate, animate etc etc all your geometry while having the file linked to the native file type so should the model change all that is required is a save and an update and it's done. This style of plug in is new to me and proving to be quite cumbersome.

No offence Paul I know you're working your butt off on these and I'm sure once I get more familiar it won't seem so foreign to me.

[face_off]

So what I mean about the camera is this. When I adjust the camera parameters with the octane viewport controls ie aperture, exposure, fstop etc. The effect does NOT happen real time and only takes effect once I release the slider?? In the standalone (and rhino) when you slide a slider the change is visible as you are making changes, inside modo this does not seem to be happening? Also and I'm having this issue in the standalone and all the plugins is that I have to change the aperture to zero just to get my object to show (working in mm) because otherwise my design is so blurred it's like it's not even there.

Most sliders in the plugin immediately update the corresponding Octane node pin value (material nodes for example), however some nodes (like the Camera, Post Processing, Imager and Environment) cause the original node to be deleted and then recreated - so this only happens once you release the mouse button. The reason for this is that re-creating these nodes requires the use of Modo API functions which are not available in the "slider move" Modo event. So the slider events get stored up until a Modo "idle" (ie. the user has released the mouse button) event, and then actioned. So this is really a Modo API limitation - sorry.

As for the gemstones not being faceted. I understand that's the smoothing option but I can't seem to find it to shut it off. I'm sure it's simply because I've not spent enough time in the plugin.

If there is no Octane Override for the gem, set the Smoothing % of the Modo material assigned to the gem to 0. Or even better - add an Octane Override for the gem material, and then select the (presumably specular) material node and untick Smooth.

I just wish there were better videos for all these plugins, they all assume you have knowledge of the host software which isn't always the case. I for instance own modo and rhino but don't use them for modeling or rendering and am trying to adopt one or the other as a medium to get my rendering/animations done.

Have you watched the Getting Started video at http://render.otoy.com/forum/viewtopic.php?f=34&t=42581. And read the manual at http://render.otoy.com/manuals/Modo/. I plan on doing more videos in the future, but putting these videos together is definitely not my strength. A good project for an "expert user"!

Paul

[funk]

Most sliders in the plugin immediately update the corresponding Octane node pin value (material nodes for example)

That doesnt appear to be working here. Updates only happen once I let go of the slider.

[face_off]

That doesnt appear to be working here. Updates only happen once I let go of the slider.

Yes are right Funk. I have found a potential (sneaky) coding workaround - which I have posted as release 2.14.0.44 in the TEST release thread.

Paul