CRITICAL: Enscape cannot read Texture mapping on VisualARQ objects

Quote from rheinason

Subject is pretty self explanatory

This is a pretty critical feature, is this related to Enscape or to VisualARQ?

If this object has been imported/created with the VisualARQ plugin, then the corresponding texture mapping might not (yet) translate into Enscape as seen in Rhino. You can gladly send in the project so that I can also forward this file to our developers!

In this case, if possible, I'd recommend making use of our Rhino material editor, again, if this would be an option for you only.

Quote from rheinason

Using the SketchUp Material Editor in Rhino? And how would that help with the Texture Mapping? I've gotten a response from the VisualARQ developers who are claiming some of the blame.

Pardon! There has been a misunderstanding from my side, I meant that you could make use of the material editor in Rhino instead, as this may already be helpful with what you're trying to achieve. I've adjusted my last response accordingly.

rheinason - if the VisualARQ models are using textures like UV's that UV information can only be edited in the Rhino Material Editor, as we do not offer that level of control in the Enscape Material Editor, and we simply take the information from Rhino, if Rhino provides that.

So, you may, for example, have to edit or reapply the textures in Rhino before Enscape can read the textures correctly.

Do you know what kind of texture mapping VisualARQ is using?

It seems that the mapping used by VisualARQ does also not translate to Octane, which appears to be an issue within Rhino, and in that regard it would be something you need to approach the Rhino team about.

rheinason - Would you be able to pass the project to me? I'll PM you with a link you can use. Thanks.

Hello!
I'm also using VisualArq (great plugin!) Got the same UV issue here...

However, even the exploded slab has incorrect UVs in Enscape.

Had this issue in a non-VisualArq project recently, too. The UVs did not update immediately. I can't tell when or how they finally did, sorry!

Thanks for looking into this!

Best regards

Eugen

Hi Tupaia! Would you please be so kind as to send the project where this is occuring to support@enscape3d.com? Then we can take a closer look. Thanks!

Sorry, have been a bit occupied otherwise... here's the scene and a screenshot.

All 3 objects have a planar UV map applied, fit to the object.

Best regards

Eugen

Hi Tupaia , sorry for the late reply. Without having the VisualArq plugin installed, I've seen some improvements in the way the texture is handled when converting the material to an Enscape material. (Select "Enscape" in the Type dropdown menu in the Rhino Material Editor.)

Can you please check if that helps resolving the issue?

Hello Kaj!

Installed latest, here's a screenshot.

Not much difference.

... and here's a screenshot with a normal bitmap texture instead of a 2D-checker:

As you can see, the 'pure' VisualArq slab won't show it's texture, no matter what.

And may I be so bold as to suggest something:

Why don't you and the VisualArq developers get in direct contact? You are super helpful and dedicated guys on both sides.

Going through us users as 'middlemen' just slows things down maybe. From my side, this is a show stopping bug, so I hope it gets fixed soon.

Sincere thanks!

Quote

And may I be so bold as to suggest something:

Why don't you and the VisualArq developers get in direct contact? You are super helpful and dedicated guys on both sides.

Going through us users as 'middlemen' just slows things down maybe. From my side, this is a show stopping bug, so I hope it gets fixed soon.

Sincere thanks!

I could not agree more

Hi everyone.

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:

1. 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.
2. 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.

Regards,

Enric

enric , Thank you so much for this valuable insight! At all, I hope exploding the objects will be a feasible workaround until the issue can be fixed. Let me know in case there's any additional questions!

Hello!
Just wanted to ask if there's any progress here.

Still having the problem that I have to explode the VisualArq objects to get correct UVs. That's the workaround for now, but yeah.

Thanks so much!