curve piping does not work
curve piping does not work
Pretty sure this is related once again to Enscape's choice of RDK
we tried to switch to the API introduced in Rhino 6, which is the preferred way if you ask McNeel. With this implementation we get edge softening works, decals and better material IDs without any code from our side. We really want to make the switch ourselves.
Unfortunately there are serious shortcomings regarding live updates when editing blocks. You can see the same problems when using Cycles (switch to Cycles, edit blocks, end editing, see how Cycles renderer gets out of sync). In our opinion it's better to have a synchronous rendering, even if this means to miss out on a few other features. You can try it out for yourself and give feedback. How serious are these sync problems in your opinion?
McNeel is aware of the bugs in the API, probably it's not as easy to fix as it might seem. I'm not aware of any ETA for the bugfixes.
Which is a two year old issue. There's been some movement, like this:
This is Enric Marquès, one of the lead developers of VisualARQ.
VisualARQ seems to have problems with real-time renders, like Enscape, Octane, V-Ray Interactive, and even Rhino Raytraced display mode. AFAIK, there are two issues:
- Wrong materials: VisualARQ objects contains several meshes, with different UV mappings and materials. Rhino SDK allows plug-ins to query the object meshes, with its correct UV texture coordinates applied, but materials for each mesh cannot be queried, so all meshes will be rendered using the object render material. Then, Rhino provides another SDK, called RDK (Render Development Kit), to query not only the meshes (with their UV mapping) but also the materials for each mesh. I guess that some of the real-time renders do not use RDK.
- Wrong texture coordinates: The second reason is that VisualARQ objects are Rhino blocks (with asteroids). If a plug-in sees a VisualARQ object as a simple block, it will just render the objects that are inside the block. As VisualARQ objects share geometry between several instances (for example, two columns with the same profile, will use the same block definition), objects inside the block do not have correct UV texture coordinates. Only the meshes provided but the VisualARQ object (the column) have correct UV mapping. Renders should get meshes for the VisualARQ object using RDK, and if RDK is providing meshes for the block, then do not try to render the block contents.
If you explode all VisualARQ objects before updating the model in Enscape, it should be rendered correctly.
I've already talked to Enscape regarding this issue. They told me there is a bug in Rhino that is the reason of the issues between VisualARQ and Enscape. It seems McNeel will fix this issue in Rhino 7.
We're open to make changes in VisualARQ if those changes will fix the issues between Enscape and VisualARQ.
rheinason - just to update you, as the developer, even though on leave, answered my request for an update.
He said that McNeal won't fix the issue that we reported until the next major Rhino release. So in this regard we are waiting on McNeal. The developer will follow this up once they are back from leave, and we will then update you again as to the status. Thanks for your patience.
And we're past Rhino 7 and there's no real update.
As a workaround you can use ExtractPipedCurve, that should show up in Enscape
Hey Enric - thank's for your idea! a new command for my mind.