Community
Navisworks Forum
Welcome to Autodesk’s Navisworks Forums. Share your knowledge, ask questions, and explore popular Navisworks topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Object Appearance Resets When Reviewing Clash Results

12 REPLIES 12
SOLVED
Reply
Message 1 of 13
ryanzoldan
5326 Views, 12 Replies

Object Appearance Resets When Reviewing Clash Results

I have a "Home" view that has visibility of objects set that was originally set up and periodically updated using the Appearance Profiler. There are color changes as well as transparency changes. When I go into one of my clash batches, and select the results tab, all of the colors reset back to their original apperance (color and transparency). Is there a setting that controls this? I'd like for the colors/transparency to "stick" when I'm going through my clash results, turning on and off dimming of transparency.

 

Current workflow requires me to click on the clash batch, select the results tab, then click on my "Home" viewpoint to reset the colors. The problems comes when I exit the results tab or go to a different batch, all of the color/transperency reset.

 

I'm using Navisworks 2015, but tested this in 2016 with the same results

 

Hopefully there's a setting for this that I'm just not seeing.

 

Thanks,

 

Ryan Z.

12 REPLIES 12
Message 2 of 13
Lance.Coffey
in reply to: ryanzoldan

I tested this with one of the sample files, and I found that color and transparency overrides were maintained when reviewing clashes through the Clash Detective.

 

However, when writing the results to viewpoints (with preserve result highlighting), and using the Reset Appearance option, this would reset color and transparency overrides.

 

To work around this behavior, you can bake in your overrides by publishing to NWD.

 

When you open the published NWD the Reset Appearance option would no longer reset changes made before you published.



Lance Coffey

Technical Support Specialist
Message 3 of 13
Lance.Coffey
in reply to: ryanzoldan

Have you been able to try reproducing this behavior with one of the sample files?



Lance Coffey

Technical Support Specialist
Message 4 of 13
Anonymous
in reply to: Lance.Coffey

Lance et al,

 

I also periodically experience the same issue, it can be quite frustrating.  I do not use the Appearance Profiler (I will now) and find that NW'15 completely purges my custom materials out of the project when I switch to an older viewpoint.  It seems older NWCs override newer NWCs' materials, but not vice versa.  I have some questions about this:

 

 

- Is there a way to solidify Appearences without publishing?  A workaround that allows one to still work in the .nwf, short of changing the Revit file's  materials and reimporting as NWC

 

- Updating the old Viewpoint in an attempt to Update the materials does not work.  Do you know the process driving the material re-reference that occurs, which allows Viewpoints to make changes to model materials?

 

- Could the .xml data that can be exported from a Viewpoint be utilized here?

 

- Could it be the overwritten/purged material's image file location? i.e. something similar to 3ds' Project Folder structure

 

 

I use often NW for creating animations which makes this issue more common an occurence that I'd prefer. Using Navisworks 2015, Windows 7 Pro 64b,  NW'15 Service Pack 3.  Any help & tips greatly appreciated!

 

Thank you,

Paul

Message 5 of 13
ryanzoldan
in reply to: Lance.Coffey

Lance,

 

I finally got around to recording the process with one of the sample files and uploaded a screencast. The issue is still occurs for me. I created a test viewpoint with apperance overrides checkbox turned on, and then change color/transparency and update that saved viewpoint. Then I created a clash test and selected two arbitrary objects to clash against each other, selected the results tab and then the apperance overrides on the model went back to their original state (all grey). This also occurs when I save an NWD of the file. Even though the current view has the appearance overrides applied, the saved NWD reverts back to the original appearance. You can always click on the saved view and it goes back to the desired state, but it's a hassle when I am trying to review clashes.

 

Thanks,

 

Ryan

Message 6 of 13
masonblalack
in reply to: ryanzoldan

I was able to replicate the issue you are experiencing, not sure what's going on. 

 

I manage Appearance Overrides through Search Sets and the Appearance Profile and haven't run into any issues with appearances resetting using Clash Detection.  The Appearance Profile also makes it much easier to re-apply appearance settings when a model is updated.

 

I know it's not the answer you're looking for, but I always push the Appearance Profile over Manual Overrides on my users as it allows you to apply appearance overrides to new/updated model content with one click (see attachement).

 

 

Message 7 of 13
cgoin
in reply to: masonblalack

I have the same problem.. and it seems to be specifically with view points that were generated by the clash detective.

 

Also why is there a RESET APPEARANCE viewpoint created..

 

NO ONE wants that.. Its specifically a button that says "HERE SCREW UP ALL THE WORK THE DESIGNER DID " 

Message 8 of 13
kyle.spitznagel
in reply to: cgoin

Our office has experienced this bug since version 2015 (it's present in 2016 also). 

 

Fortunately, one of my colleagues and I stumbled on a solution this afternoon.

 

Here's the workaround:

 

1) Go through all your viewpoints and make sure that none of them has "Override Appearance" checked.

 

 Bad.PNGGood.PNG

2) Rerun the appearance profiler (don't skip this - rerun even if the colors look fine)

 

3) Save your .nwf

 

4) Now all saves, uses of the Clash Detective, etc, should keep your appearances as what you had overridden the colors to.

Message 9 of 13

If you need to get rid of all override apperances in a lot of Viewpoints, a workaround is to export all your viewpoints into an XML. Then delete all Viewpoints, than check your options -> Interface Viewpoint Defaults and set Override appearance OFF
and then import the viewpoints XML again. This should do step 1) in a quicker way.
Message 10 of 13

Thanks to both of you.. ! 

 

Now Autodesk needs to turn it OFF by default in 2017

Message 11 of 13
ryanzoldan
in reply to: CharlesGoin

I guess it's safe to assume for future projects, if you don't want this to occur during clash detection or on Save As of an NWD, you are required to run appearance profiler or override appearances prior to creating any viewpoints. I don't necessarily want to have the default for override appearance to be off because I typically create views that have color/transparency overrides.

 

What would be nice is to be able to reset the "default" or "home" view that it always reverts back to when running clash detection or saving nwd's without going through the process of exporting out the saved viewpoints, deleting the saved viewpoints, override the appearances, then re-import the views I want back in there. Seems like something that you should be able to change without going through that.

 

Oh well, those steps worked in order to get it to function properly while maintaining the colors/transparency that I wanted. Thanks!

Message 12 of 13

This is the perfect solution for colors getting messed up after running clash detective

Message 13 of 13

The fact that I have to reference this thread in 2024 is embarrassing...

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Rail Community


 

Autodesk Design & Make Report