Reverse way a Plugin can take

[8Eggar8]

Not touting Maxwell, it is significantly pricier, but an interesting way to overcome the interaction & manipulability hang up a 'solely' rendering engine may have.

(Recent Post in Rhino's Newsgroup)

news://news.mcneel.com:119/4cd44829$[email protected]

[SamPage]

Not touting Maxwell, it is significantly pricier, but an interesting way to overcome the interaction & manipulability hang up a 'solely' rendering engine may have.

(Recent Post in Rhino's Newsgroup)

news://news.mcneel.com:119/4cd44829$[email protected]

I saw this as well, and would love to have something similar for Octane, but unfortunately this is not possible with the current tools given to us plug-in developers. The way it works now, we (the plug-in maker) just create an obj and an mtl file, then we start Octane by passing it a few command line options (stuff like what file open, what mesh node to link, camera / target position, that kind of thing), once Octane starts, we have no way to communicate with it, so Rhino has no idea with Octane is doing and vise versa. It was in fact this simplicity which led me to think "hmm, making a little script to do this wouldn't be so hard."

I know that this type of back and forth (well, perhaps not as "live" as the Maxwell video, but at least better than having to close and restart Octane every time) has been wished for by other plug-in developers, but no word as to how possible this would be.

Sam

[8Eggar8]

Yep, that's how it seemed to me as well. Not an issue with the 'plugin - facilitator' (you) but more with the product development team Relating to the outside app's RDK or, as in Maxwell's case, coming out with their own (Preview) interface with in the outside app.

Thank you Sam