From Unity 2023 to Unity 6, many weird issues and worse user experience in many topics

[OrsonFavrel]

Morning! First, let me thank you for your detailed feedback. It’s always very valuable to get them so that we can push VFX Graph further. I will answer the best as I can and with as much transparency as possible, putting some context whenever it makes sense.

@SrtoRubfish

But, there are a lot of things that are just worse now, starting by the lack of render order (At least, usable one)
On the VisualEffect dedicated output custom shader, you had the option to set a Sorting Order.

Since 6 doesn’t include this anymore, the only way I’ve found to set a custom render order per shader is this, the SortKey (If it doesnt do that, the descriptions are extremely confusing).

I am not sure why you are not seeing this Sorting Priority, as I can see it on my end. I’m guessing it’s a bug. If so please, don’t hesitate to fill a bug so that we can tackle it. This Sorting Priority allows you to enforce the Sort order between Output within the same VFX Graph. Another method is to use the Output Render Order (in the Inspector setting when selecting the VFX Asset in the Project) to easily manipulate the output list order.

Sorting transparency is often tricky, here are two post where you might find useful information about sorting and VFX Graph.
Post A
Post B

@SrtoRubfish

The change from a single “ParticleMesh” output that you could add a shader graph instead of the base one, to a “ParticleShaderMesh” without a toggle or a button to change from one to another, is just odd.

To give some context here, this change occurred to reduce some internal complexity and potential data loss while switching the Render Pipeline. This is part of an incremental improvements plan. To make it simple, we know that this is a regression on UX standpoint, but these foundation changes were needed, and this UX regression will be addressed in future released.

@SrtoRubfish

it makes sense to wanting to swap from one to the other, something not doable anymore. Seems like an odd change just for a worse result. I would ask at list for a toggle or an equivalent for those, instead of two indvidual outputs. (Found the convert output, makes flow easier, stills more messy than previous versions, but could be worse)

I’m not sure why the Right-Click→ Convert Output isn’t a viable solution. This allows you to convert your Output from Quad Unlit to Lit to Strip to Shader Graph Output pretty easily. And your Output Blocks as the Output settings that can are preserved. Now, don’t get me wrong, as said upper it’s an UX regression, but now that the foundations are better, we hope to mitigate this issue and improve the idea of Output composition instead of inheritance.

@SrtoRubfish

Removing the quick search access to some nodes, right now to search for a “multiply over lifetime” you need to access from a “set size over lifetime” and then select the subnode, or change it once it’s instantiated. The submenus are really nice, but missing a nice feature from previous versions is just weird.

So, to provide some context here, a lot of the Node Search and Blackboard UX changes and improvements have been made with several things in mind:

• Reduce interface clutter and overwhelming feeling for new users.
• Provide Better Browsing/ Search experience.
• Keep the Power user workflow

To reduce visual clutter and help the new users, we’ve put all the “Main variant” in the main panel, and moved the other variants to the details panels.
This details panel can be opened at any moment and its state is kept for the session.

All blocks with variants have an icon that lets you easily open the detail panel, although you can also open it with the dedicated icon in the top.

The Node search has also been re-ordered in a hierarchical tree view, instead of drawers. So, overall, the browsing experience should be way faster (less click to reach the wanted block) than before as the average folder depth is 2 while it used to be 4.

Now, most advanced users use the Search function, and VFX Graph always featured an approach that exposed to the users, most, if not all variants (Block with composed settings).
For new users, the feedback has always been that the number of results were scary and overwhelming.
To mitigate this, we decided that, by default, only the Main Variants (which were chosen for each block based on how often they were used.) will be displayed in the main panel and for “basic search”.

Now, VFX Graph users can still have the previous experience:

Toggling the Sub-Variant Visibility button, allows you to expose all variants in the search, just like before. The state of these buttons is kept between sessions.

You can also temporarily toggle all variant search by starting your search with a “+” as stated by the tooltip. This can be useful, to only get full search when needed.

@SrtoRubfish

This last feedback also applies to things like position shapes, I like that they are now unified under the same node (Shape: Sphere) From the menu, unless you find it first, there is no way you know you can change that later.

We’ve introduced some new visual elements → Pills/Tags, that should give some hints to know the Variant/settings part of a block. In the future, we want to implement Interactive Tag/pills on the Blocks themselves. This would allow the user to change the Composition mode, and settings directly by clicking the Tag/pills and without going into the inspector. This will help with setting discoverability, and also save space on each block.

I hope, this can shed some lights on why we’ve made those changes. So, from what I’m understanding from your feedback related to Node Search, enabling the Sub-variant toggle should give you the previous search experience. To get the previous browse experience, you can keep the details panel open. Both of those options are saved between session.

@SrtoRubfish

due to the “VFXGraph doesn’t save unless you save it, or close the effect” will be nice to have some kind of autosave feature that you could recover in case of a crash, something that happens pretty often in 2023-6.

An auto-save feature could be pretty useful. Sadly, it’s currently not planned for U6 Cycle but could be considered for later.

@SrtoRubfish

All the systems won’t open with the “updated” system for output, so you need to manually fix them one by one. Plus fixing blendings, ZW, sorting (if I could, but it’s broken), etc.

I’m truly sorry to hear that, as it shouldn’t happen. I would encourage you to fill a bug so that we can repro as this seems like a High user pain issue that should be resolved as swiftly as we can.

@SrtoRubfish

I fill this could be improved a lot if you want games with over thousand of effects being ported to any future version. (I work on one of those and that’s impossible to even consider)

While we are trying to provide the best possible upgrade solution, I would just like to highlight the fact that a Library of thousand of effect might not be the ideal configuration with VFX Graph. A thousand of different VFX assets means that none can be batched together thanks to the instancing features, which would be bad for performances. Furthermore, Built-time will clearly suffer from the size of such a library.
On of VFX Graph strength is to allow you to create a versatile VFX assets that can be parametrized and made unique by tweaking instanced properties.

To finish, I would like to thank you gain for taking the time to make this long feedback, and please keep them coming. I wish you a sunny day.