Question Scene View - Overdraw mode accurate?

The Unlit Particle Shader doesn't, according to the Overdraw mode of the Scene View, generate any overdraw upon itself. In other words, 100 particles all overlapping from a single system using this shader, do their somewhat correct additive blending, but don't show up as having been creating Overdraw.

Conversely, the older Legacy Particles Additive Shader used in the same manner does indicate in the Overdraw made as having each particle being an overdraw on each it overlaps with.

Is this accurate? If so, what's so special about the Unlit Particle Shader that it can do Additive blending without creating overdraw?

 

This problem/bug/issue is throughout all version between 2018 and now. Have checked.

Do you happen to know which is the most performant shader for additive blending of particles with Shuriken?

 

Why do I need to create a bug report for something so obviously wrong? Anyone can check it, anytime, in any version.

 

These all sound like Unity management problems, not me problems.

I strongly suggest you and all other proactive, customer and user focused staff get together and lobby your management to create budgets for logical, sensible and considered processes to care for customer and user experiences. Someone needs to point to the thousands of issues that aren't specifically bugs, but are more general, to prioritise and fix both these general issues and consider all low hanging fruit problems and possible improvements, and all manner of performance, optimisations, glitches and user experience annoyances.

We, the users, are not able to generate any momentum within Unity management, and it certainly seems as though there's practices and processes in place to ensure that that's the case.

 

While it's true that posts may get washed away over time, the forum is still an extremely valuable tool for discovering potential bugs and suggestions. Users are inclined to present whatever information they can and, if needed, you can place burdens on them to provide even more testing for free.

The main issue with asking users themselves to go a step further and directly submit bug reports are:

1. Users can only present what they know. Their understandings, ability to explain, and standards for what is important are all vastly different. There's no consistency or reliability. If I can't tell whether I've found a bug, a misuse, or a gap in my knowledge, I can't really submit it.
   
2. Training every single user to know how to effectively submit bugs is far less efficient than training a few super-users or devs to distill the more important parts (in the context of forum posts).
   
3. Anyone who uses the forums has encountered dead-end issues tracing back nearly a decade through necroed threads, creating a strong disincentive to bother submitting anything.

There's plenty more nuance to it, and having reasons for or against doesn't override the top-level priorities Unity has decided on or whether the submission process requires one flow over another. It is what it is.

 

Further to this "bug", ANY object that uses a material using the Particle Standard Unlit shader shows no geometry when in "Shaded Wireframe" mode of the Scene View.

interestingly, from the Gizmos dropdown menu, this does not impact the Selection Outline, that still works, but from the same menu, "Selection Wire" does not work.

Scene View Wireframe mode does not exhibit this problem. It shows all the wireframes.

But does also affect "render selection wireframe", which can be set via shortcuts.

Interestingly, there's still no default shortcut for editing shortcut keys.

Nor a delete option immediately within the shortcuts panels for each shortcut. Like the "x" that's used in all text entry boxes to clear there contents. That'd be nice. Probably needs a bug report to be considered, though.