"Display Color Components" only shows Wireframe

"Display Color Components" only shows Wireframe

marcelTC4LJ
Explorer Explorer
5,816 Views
76 Replies
Message 1 of 77

"Display Color Components" only shows Wireframe

marcelTC4LJ
Explorer
Explorer

I've selected the visual style "Shaded with Visible Edges Only". However, when I switch to "Display Color Components" my models are shown as a wireframe. It's not related to a specific file as I see this behaviour even for 3rd party step files. So it looks like I accidentaly activated an unwanted option.

0 Likes
Accepted solutions (1)
5,817 Views
76 Replies
Replies (76)
Message 21 of 77

Reno_Raines01
Enthusiast
Enthusiast

Some pictures below:

 

Picture 1 is with 'display component colors' toggled off.

Picture 1.png

Picture 2 is with 'display component colors' toggled on, as you can see  the bolts and the plate covers visible in picture 1 are wireframed. (Changing opacity as previously mentioned here in the thread has no effect on the wireframe parts).

Picture 2.png

0 Likes
Message 22 of 77

jim.fleser
Explorer
Explorer

Same issue here.  Over and over again.  So annoying...

0 Likes
Message 23 of 77

KellyDBW
Observer
Observer

Another vote for the same issue. When switching to coloured component view some faces are missing and only the shadows displayed. Looks a bit like wireframe view. On an Apple Silicone Mac. Started with the update to native. 

0 Likes
Message 24 of 77

ckp66253
Enthusiast
Enthusiast

I thought this was a M1 Mac problem but I just had the same thing happen on a Windows machine. Is it possible this has something to do with my "Preferences" setting?

0 Likes
Message 25 of 77

ckp66253
Enthusiast
Enthusiast

Crashed

0 Likes
Message 26 of 77

infoM8PWE
Contributor
Contributor

Same issue here... started a different thread about it...before another user made me aware of this one... https://forums.autodesk.com/t5/fusion-360-support/unwanted-and-random-mixed-visual-styles-in-the-sam...

 

Seems to have calmed down since I switched 'active component visibility' off in the settings.. 

 

 

 

0 Likes
Message 27 of 77

GRSnyder
Collaborator
Collaborator

I've been seeing this intermittently since, I think, October. I'm on a Mac Studio with an M1 Max and 32GB of memory. I'm currently using Sonoma 14.2.1. I'd like to add a few additional data points and clarify some previous claims.

 

I would imagine it's unlikely that this has anything to do with display performance options being throttled. I say this because of several specific pieces of evidence:

 

  • As mentioned by multiple people, the effect appears only in Display Component Colors mode. Switching that off instantly removes the effect. (Turning the switch on again brings the problem right back, however.) It's hard to imagine how solid pseudocolors would put any more stress on the display pipeline than normal view.

  • It is not related to the complexity of the model. It can happen with even the simplest of models, at any time. You might see the problem the moment you open your first model after starting Fusion 360. Or you might go for a whole day without seeing it at all.

  • It is not related to how long Fusion 360 has been open or how long the system has been up. You can reboot or restart Fusion 360 and see it immediately. Attempts to limit other applications' use of memory make no difference. It does not matter whether the system has free memory or has started to use the swap file.

  • The effect usually seems to happen on some bodies but not others. It's possible for the entire model to jump to wireframe, especially if the model is simple, but that's atypical. There's no apparent rhyme or reason to the selection of bodies that are affected. It doesn't happen preferentially to simple bodies or complex bodies. It doesn't happen to bodies that are  at a given distance from the camera plane.

  • No graphics setting appears to make any difference. I have systematically checked each one in an attempt to track down the issue.

 

A few additional points are worth making. First, it seems to happen in runs. As I mentioned, you might go a whole day without seeing the problem. But once it starts happening, it seems to be a constant annoyance for at least a day or two.

 

Second, it always happens in Display Component Colors mode, as described above. And usually, what you get is a display that's a mix of component-color-rendered bodies and wireframes with hidden lines drawn. But a couple of times, I've seen "normal" colors seeming to show up in Display Component Colors mode. For example:

 

Screenshot 2024-01-12 at 3.28.28 PM.png

 

This is a STEP file, which presumably has no pseudocolor information. This is absolutely, positively a capture with Display Component Colors turned ON, but clearly, the parts that are rendered correctly are being rendered as if they were in normal display mode.

 

Another point of note is that the problem seems to have "epochs." It doesn't randomize the rendering of bodies for each frame. When the problem occurs, you'll see a (potentially large) number of bodies drop out suddenly to wireframe. Those bodies then remain stable in that mode. You can orbit around the model and even work on it. Each body retains its own characteristic rendering style. There may be another batch of bodies that eventually drops to wireframe, but the wireframe-rendered bodies never seem to return to normal rendering.

 

It's a bit odd that no one from Autodesk has commented on this. @jeff_strater, is this on your radar?

0 Likes
Message 28 of 77

infoM8PWE
Contributor
Contributor
Well put! Very detailed description of my experience as well. Hope some tech people wake up now 🙂
Message 29 of 77

jim.fleser
Explorer
Explorer

GRSnyder's description of the problem is absolutely spot on and is in 100% alignment for my experience as well!  Thanks for taking the time to write it up so clearly.

Message 30 of 77

ckp66253
Enthusiast
Enthusiast

Does it seem like this happens less on the weekends? Possibly Autodesk resource issue?

0 Likes
Message 31 of 77

jeff_strater
Community Manager
Community Manager

Thanks, @GRSnyder - that is a very thorough description of the problem you are seeing.  I'm not certain whether anyone is looking into this or not.  The problem, I think, is that it is intermittent.  Intermittent  problems are VERY hard to diagnose and fix, as anyone who has ever had an intermittent car problem can attest.  If we could find a reliable way of reproducing this issue, then I'm sure it would get fixed.  I, personally, have never seen this issue, and I don't know of anyone internally that has, either.  Not at all saying the problem doesn't exist, I'm certain that it does.  But, until we can reproduce it, I'm afraid it is unlikely to get fixed.


Jeff Strater
Engineering Director
Message 32 of 77

ckp66253
Enthusiast
Enthusiast

Is anyone at Autodesk compiling a set of symptoms that those of us who are experiencing the problem have provided? If so, can you share those with us? Give us some hints as to how we can help you solve the problem. If you could re-create the problem what would you look for? Is there something we should be looking at when it happens? Should we be looking at the activity monitor? If so, what would we look for? 

0 Likes
Message 33 of 77

GRSnyder
Collaborator
Collaborator

@jeff_strater wrote: Thanks, @GRSnyder - that is a very thorough description of the problem you are seeing...The problem, I think, is that it is intermittent.  Intermittent  problems are VERY hard to diagnose and fix, as anyone who has ever had an intermittent car problem can attest.

Thanks for the update! I hear you for sure, @jeff_strater. That's the main reason I still hadn't reported the problem after living with it for a couple of months. But it's encouraging (so to speak 🙂) to hear that other people are experiencing the same issues.

 

I'll keep trying to develop a test case.

 

0 Likes
Message 34 of 77

trebor_madoverlord
Contributor
Contributor

I have a repeatable case! You can trigger the behavior by doing a repeated pattern of a feature that has a lot of repeats. If you just increase the number of repeats until you get the warning about too many, change to identical, then increase and decrease the number of repeats back and forth it'll eventually trigger.

 

Screencast of the behavior and fusion document attached. Even better (?), as I was going to save the .f3z file to post here, Fusion crashed as I was rolling back the timeline before the repeated pattern! The report ID is 742406648 so it may have some clues.

 

@jeff_strater gets his wish. 

Message 35 of 77

trebor_madoverlord
Contributor
Contributor

Potentially associated crash: 742407787

I went back in and completed the pattern without triggering the bug by first setting the type to Identical. I then saved the project. Fusion then crashed. Upon restart, I found that the project had been correctly saved.

0 Likes
Message 36 of 77

GRSnyder
Collaborator
Collaborator

@trebor_madoverlord wrote: I have a repeatable case! 

Strong work! I went to see if this worked for me, but the problem was already manifesting just from opening the file. 🙂 

 

I restarted Fusion 360 and was able to open the file without initially seeing the problem. But when I repeated your procedure, it dropped to wireframe before I even reached the "too many instances" warning.

 

In your video, the body eventually disappears completely, which is not something I've seen in connection with this issue. I just see wireframe rendering. I wonder if there might possibly be a second bug at work here.

0 Likes
Message 37 of 77

jeff_strater
Community Manager
Community Manager

@trebor_madoverlord - great that you found a repeatable case.  I have been trying your workflow on my machine, and have not yet managed to reproduce it, but I will keep trying.

 

One question:  In the video, it looks like the body disappears completely.  That is certainly bad behavior, but my understanding of this particular issue was that the body is there, but is displayed in wireframe only (no shaded surfaces).  Is that what others on this thread have seen?


Jeff Strater
Engineering Director
0 Likes
Message 38 of 77

trebor_madoverlord
Contributor
Contributor

I had my display settings on "Shaded", not "Shaded with Edges". My supposition is that it's the shading part that's going away, thus leaving only the edges -- but since I don't have edges on, there's "nothing to see here".

 

Message 39 of 77

jeff_strater
Community Manager
Community Manager

OK, that makes sense.  I did not notice that in the video, but that is a perfect explanation.  Thanks!


Jeff Strater
Engineering Director
0 Likes
Message 40 of 77

GRSnyder
Collaborator
Collaborator

@trebor_madoverlord wrote: I had my display settings on "Shaded", not "Shaded with Edges". My supposition is that it's the shading part that's going away, thus leaving only the edges -- but since I don't have edges on, there's "nothing to see here".

My normal rendering style is Shaded with Visible Edges Only, but when this issue kicks in, the affected bodies drop to Wireframe with Hidden Edges. So at least in my case, there seems to be something more specific going on than just losing the shading component.

 

(I suppose it's possible that the rendering pipeline for Shaded with Visible Edges Only draws all the edges first and then overdraws the shaded areas, overwriting the hidden lines. If that's how it works, then yes, I guess it does potentially make sense as a loss of the shading.)

0 Likes