[osuire]

As for now, they just don't seem to be exported to the .mxs file...

Cheers,

--
Olivier

[osuire]

Oh, ok, read the previous topic.

But Jeremy, why not *communicate* with McNeel on that one ?
I mean, there is probably very little to do to make this work ?

The Rhino plug-in is by far the one that has the most posts in this newsgroup so it suggests that most Maxwell customers use Rhino.
I think it justifies the existence of the V5 WIP plug-in, but since the plug-in itself is a WIP, shouldn't it be updated from time to time to follow the latest V5 evolutions ?
I know you don't want to waste your time Jeremy, and I have thoroughly read your little disclaimer, but then, when are you going to finish the plug-in ?
When V5 ships ?
It goes against the whole "Work in progress" philosophy if you want my opinion.

Or is there some huge changes comming up in Maxwell that justify the status quo ?
I can't remember such a long period of stillness on the Maxwell front...

Cheers,

--
Olivier

[JDHill]

Olivier, it is not even worth trying to track changes as quickly as they occur in the WIP process, and due to its being a WIP process, it is most often ill-advised even to attempt to do so. Extrusions are a prime example of this; I cannot even estimate how many places in the plugin code would need to be modified to make it aware of them. On the other hand, depending on how McNeel finalizes how they operate, it may be that no changes are required at all.

The plugin is not a WIP in the same way as Rhino V5 is; it is a Rhino V4 plugin, built against the Rhino V4 SDK. The only reason it works in V5 is because of the priority McNeel puts on compatibility for plugins -- that is to say, because Rhino V5 is able to load Rhino V4 plugins. I don't ask McNeel alot of V5-specific questions, because this is not a V5-specific plugin.

So far, I have implemented interactive preview in two of my four plugins, and Rhino is one of those two. There is absolutely no way I could justify pouring effort into Rhino V5-specific code when two plugins remain to have interactive preview implemented. Even if that were not the case, I still would not consider doing so until Rhino V5 had at least officially entered its beta phase.

[osuire]

Ok, Ok,... and what if solving this extrusion object issue was just a matter of making a phone call and changing one line of code ?
Isn't it worth the try ?

Just askin'

--
Olivier

[JDHill]

When I wrote 'it may be that no changes are required', I should've written it as 'nearly no changes', because there is really no logical way for it to actually require no changes. And even one line of code here means splitting the project and building V5-specific plugins, with V5-specific installers, etc., etc. It can make no sense for me to ask McNeel V5-specific questions until I am using the V5 SDK.

For the time being, I would just recommend that you run the UseExtrusions command and set the default for extrude operations to produce Polysurfaces.

[osuire]

Ok.
By the look on your face, I can tell I'd better shut up if I don't want to get a shot of that laser blaster.


Cheers,

--
Olivier

[JDHill]

It's not a personal thing, Olivier -- if you want to see what I'm talking about, just hop up to the Cinema plugin forum where a guy is yelling at me for not implementing Fire in the Cinema plugin yet. Then tell him that you want me to work on Rhino V5 stuff.

Cheers.

[Aji Enrico]

It's not a personal thing, Olivier -- if you want to see what I'm talking about, just hop up to the Cinema plugin forum where a guy is yelling at me for not implementing Fire in the Cinema plugin yet. Then tell him that you want me to work on Rhino V5 stuff.

Cheers.

I'm quite sure that the yelling cinema guy is just trying to motivate you and express his love for maxwell... in a different way