Autodesk Viewer Missing surface

[syman2000]

Hi there, I am testing the Autodesk viewer. I upload a DWF file created from Revit and this is the result I am getting. It is missing surface. I've included the DWF file to see if your software engineer can resolved the issue. Thanks.

[Viveka_CD]

Hi @syman2000

I'll take a look at your file and let you know for an update.

Can you let me know the version of Revit you used to create the file?

Thanks,

[syman2000]

This was created in Revit 2017. I do notice this happens a lot with adaptive surface. One side will show up with material while another side shows up as transparent. Unfortunately within revit, you cannot define which side you want the material to show up.

show up missingmaterial shows up on the inside

[Viveka_CD]

Hi @syman2000

car part missingThe problem is that the 'body adaptive part' has multiple layers, can try putting them separately (front and back). I'll also test it in Revit to see if we can group them.

Regards,

[Viveka_CD]

Hi @syman2000

I see what you are a saying.

Can you share the native Revit file and a journal recording the steps to test and reproduce this issue on our end?

I'll test this separately with other adaptive components.

Regards,

[syman2000]

The issue is the Autodesk viewer is built with positive and negative side in mind. From what see and play around, to keep the refresh rate acceptable, getting rid of the negative side helps the engine runs faster. Unfortunately within revit, you cannot define which side is positive or negative. Hopefully your engineer team can add a feature in Autodesk viewer to show both material surface instead of one.

[Viveka_CD]

Hi @syman2000

We will have to test this out in different models to confirm.

Meanwhile, can you send across your files and diagnostic data to cross check? I can send you a private upload folder.

Looking forward to hearing from you.

Regards,

[Viveka_CD]

Hi @syman2000

I'm looking at the Autodesk viewer settings - and checking if resetting any helps resolve your issue -

Autodesk viewer settings

Regards,

[Viveka_CD]

@syman2000 Also, can you confirm if you are on the latest build for Revit 2017 ?

You should be able to install the updates from your desktop app.

I will test both in Revit 2017 and Revit 2019

Regards,

[syman2000]

I send you the file thru private message. Please take a look. I don't think it is Revit issue. I am using the latest Revit patch. Also I did try uploading RVT file to the online viewer and result is the same as DWF.

[Viveka_CD]

Hi @syman2000

Thanks for confirming that you are on the latest build!

I got your file. I have tested this with a conceptual model and I get the same results. Currently, a QA Web services manager is looking at your file for further diagnosis.

I will update once I hear back and if I need more information from your end. We may need a journal file, but I'll let you know.

Regards,

[Viveka_CD]

Hi @syman2000

As an update, a quick fix for the online viewer is being looked at.

Also, can you let us know if the model was natively created in Revit or imported as a block from another software or addin?

Do send us your journal file when you have a chance. the model appears fine in viewers - truview and design review so, with the normals flipped in the online viewer, the materials appear transparent when viewing. Using explode control shows that the material is applied on only one side.

I look forward to hearing from you and thanks for reporting this!

Regards,

[syman2000]

The model was built natively within Revit. No addin. I will include the journal tonight.

[Viveka_CD]

Great. Thanks for sharing the journal @syman2000

I checked the materials in Revit  2017 & 2019. There are applied correctly.

See image below; Design Review has an option for making the adaptive surface transparent or solid, but the online viewer has no transparent/solid option and only visibility on/off (which has more or less the same results of missing parts). 

I'll update once I hear back from the Web services manager.

Regards,

[Viveka_CD]

Hi @syman2000

I wanted to share an update on the testing done so far:

On loading the model into ACAD or 3ds Max, the same problem can be seen. Here, 3ds Max shows the normals in blue which highlights the fact that the surfaces in the source model are inconsistent. This can be mitigated with 2-sided materials, but the best solution would be to unify the normals in the model itself.

See image below:

normals in the model

Regards,

[Viveka_CD · Accepted solution]

@syman2000

One of the engineers suggested the below workaround, for now, please try and let me know if you have any questions.

(Open A360 online viewer, launch model and right click on page > click inspect - it will open the console)

In the browser development console, enter the following:
NOP_VIEWER.impl.matman().forEach(function(mtl) { mtl.side = THREE.DoubleSide;})

Browser dev console

Click inside the viewer and you should be able to see all the surfaces.

What the syntax fix does is that it forced to change the double-sided geometry to shows ALL materials to double-sided, which was set to false before (i.e allows only one-sided materials)

"double sided geometry": {
"value": false
},

Please try and I look forward to hearing from you!

Please select the Accept as Solution button if my post solves your issue or answers your question. Likes welcome!

 Regards,

[syman2000]

Thanks for the workaround. I test it on chrome & firefox, both works. Once I close the chrome browser, I have to re-enter the code. It can be annoying for the user who aren't computer savvy.

[Viveka_CD]

Hi @syman2000

Thanks for responding!

Glad to hear this works for you. For now, this is a temporary fix.I'll pass on your feedback of re-entering the code every time and post here when I have an update.

I'm waiting for further feedback from the Revit team for any other feedback in double-sided materials on adaptive surfaces.

Thanks,

Regards,

[Viveka_CD]

Hi @syman2000

I've marked post 16/18 as the solution until we have any further update on this one. This will help the community seeking solutions to similar issues.

Regards,

[Anonymous]

Hello, I am having the same issue, and the code line you provided does not fix it, any permanent solution to this? thank you!