ItemView Editor Breaking bug since update

[drizztdourden08]

I'll be honest and say I have no idea how this can happen. I have upgraded from 1.2 --> 1.3 and suddely, every itemView aren't selectable like they should be.

The dropdown contain all my itemView just fine but I can't select them no matter what I try. I reinstalled the whole plugin, restarted unity more than once but it's a no go.

Here's the behavior itself.

NVIDIA_Share_ou90GUvtxA.mp4

[adgray1]

So far we haven't been able to reproduce this behavior, so a few follow up questions to better understand your setup and when it's not working:

1. Which Unity version are you using?
2. Did you happen to update the project to a newer (or older) version of Unity recently as well?
3. Are any errors or messages appearing in the console when you select an ItemVisuals type from the dropdown?
4. Does the issue occur in the Nova sample scenes and prefabs? e.g. Nova/Sample/UIControls/UIControls.unity and Nova/Sample/UIControls/Prefabs/Style_Simple/Button_Simple.prefab

One additional, general thing worth trying (if you haven't done so already) would be deleting the contents of your project's Library folder. If Unity has some corrupted/bad cached state, closing Unity alone won't always resolve it. Deleting the contents of Library is a heavier hammer, though unfortunately it'll take a bit longer to reopen the project the first time after doing so (because Unity will reimport and recache a bunch of stuff that was deleted) as well as reset your build platform to Standalone - still worth trying, but just want you to be aware of those side effects. And be sure to close Unity before deleting the contents of Library.

[drizztdourden08]

1- last lts 2022 2f-1
2- no same as before
3- no error
4- same in both

I did reimport all twice to no avail. I have not deeted the library folder but I though it was the same.

the setting for the project are like a default one for now but I’ll check for standalone just in case.

any way to downgrade to test 1.2 again?

[adgray1]

Deleting the Library folder isn't the same as reimporting, so it's still worth trying.

As far as downgrading to 1.2, are you using any kind of version control (e.g. git) in your project? Reverting to a snapshot (i.e. commit) taken before you updated the version of Nova would be the simplest way to switch back.

[drizztdourden08]

So after trying for over an hour to find more hint as to why it does that, I am still clueless.

• New project, install Nova, same unity version, works just fine
• Deleting Library didn't change anything
• I have refactored some things (Separating the project in multiple assemblies mostly) in the last week (and so can't revert to earlier version for now) but don't see why it would change anything. Also, this works with separate assemblies in the new project. so not that.
• cloned my last repo push to another folder and opened it... and it doesn't work either there. I'm pretty sure it was before.
• copying the nova folder (1.2) to the new one, doesn't give me anything different.
• already assigned itemVisual looks fine and I can see the public field on them like normal
• I can't assign new one is the issue
• Some of the prefabs are still assigned something in their itemVisual, and can't change them. some are stuck on unassigned, and one of them I can change as if everything was solved...

here's a video of all those cases:

NVIDIA_Share_YPynSt1IeJ.mp4

So yeah. at this point, I have no clue how that could be possible. especially since it does work in a new project. Was there any change to ItemView or ItemVisual done that could have broke something where if I have anything in the project that has ItemView on them, it will break all of it for... some reason?

Thanks for the help.

[drizztdourden08]

I've tried copying the only working one for fun, and the copy also end up not working...

• I've tried to delete literally every itemView I had in the project, except this one
• copy the component to another one, and it is still stuck
• deleting the component and re-adding to this working one, and it still works, and still not on any other one
• after messing around for a while, I saw that I had one left sitting in a scene, deleted that as well....

... and everything started working again.

So I don't know how Nova is built but you do. I'm pretty sure there is something somewhere that caches these ItemView components and maybe assign them some id or something. and these ids got messed up during the update. That's the only reason I can think of why deleting all of them and starting from scratch would resolved the issue.

Of course, this is far from an ideal solution and this means updating Nova is a risk that even going back to an older version somehow didn't fix it. Anyway, this is weird. Maybe having some function that we can trigger to clean some things up and try to fix what might have been broken during an update would be a nice add. That's for you guys to figure though as I have no idea how it is under the hood.

Anyway, thanks for the hint and trying to help. Hope this can lead to some kind of fix or improvement to avoid this in the future.

[adgray1]

Glad you managed to unblock yourself and get back to a functional state!

For some context on what you're suggesting could be going on, the only quasi-relevant caching Nova technically does here is to populate the ItemVisuals type-selection dropdown, but that's just through Unity's TypeCache API. And even that will only cache the list of ItemVisual-derived types, not any serialized instances, and won't persist across Unity restarts. Beyond that, there's nothing caching/tracking ItemViews or ItemVisuals or assigning them IDs anywhere.

So our best guess at the moment is some serialized state (either a scene or prefab with an ItemView in it) was causing something to become corrupted on import, which would at least explain the results of all your various tests (thank you for trying all those out and reporting back!) and why removing all the ItemViews eventually fixed it. But we still need to understand what was corrupted and where in order to know how to avoid it in the future.

Since we're unable to replicate the issue thus far, unfortunately we can only speculate. If you're able and willing to share your project or a subset of it which reproduces the bug, either by attaching it to this thread (without Nova included) or via email [email protected] we'd really appreciate that and will gladly investigate further!