View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002077 | NoesisGUI | Unity3D | public | 2021-08-09 09:59 | 2021-09-03 19:40 |
Reporter | asusralis | Assigned To | sfernandez | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 3.1.0 | ||||
Target Version | 3.1.1 | Fixed in Version | 3.1.1 | ||
Summary | 0002077: Woes updating to 3.1 | ||||
Description | After this point, almost *any* action I do in Unity will make Noesis reimport all xaml assets. Clearing or scrolling the unity console, playing the game, or restarting Unity will reimport all my xaml assets. Just about everything I do will cause all of these assets to reimport. Is there something I'm missing? Also, can I please be told a way to disable Unity asking to update to the new input system? Updating to this would break many plugins I'm using. If I understand correctly, this new system only impacts Noesis' support for gamepads, which I will not support. I really can't have this message appear every time I open Unity. | ||||
Steps To Reproduce | 1): Close Unity, delete NoesisGUI and all Noesis .asset files. 2): Add Noesis 3.1 package. 3): Unity crashes (attached crash). Open up Unity. 3): Click no to use the new input system. 3): Go to Noesis settings, add key/pass, reference my Resources xaml dictionary. | ||||
Tags | No tags attached. | ||||
Platform | Any | ||||
Regarding the new input system, setting in to "Both" should stop Unity asking about it. | |
I see, thanks for the info! I will try that. For the other issue I'm having, would it be easier if you try to recreate it in my project as well? | |
Yes, we will reproduce this using your project. Thank you | |
I have the same problem. I'm on Unity 2020.3.2 and 2020.3.15. It's basically impossible to work like asusralis is explaining. It happens for basically every interaction you do inside Unity. |
|
The problem appeared when the Application Resources contained references to user controls. That scenario was invalidating the application resources all the time and triggering a reimport of all xamls again. We fixed this situation for the next release coming next week. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2021-08-09 09:59 | asusralis | New Issue | |
2021-08-09 09:59 | asusralis | File Added: Crash_2021-08-09_075051504.rar | |
2021-08-09 11:22 | sfernandez | Assigned To | => sfernandez |
2021-08-09 11:22 | sfernandez | Status | new => assigned |
2021-08-09 11:22 | sfernandez | Product Version | => 3.1.0 |
2021-08-09 11:22 | sfernandez | Target Version | => 3.1.1 |
2021-08-09 11:24 | asusralis | Description Updated | |
2021-08-09 15:38 | jsantos | Note Added: 0007356 | |
2021-08-11 08:12 | asusralis | Note Added: 0007359 | |
2021-08-11 12:13 | jsantos | Note Added: 0007360 | |
2021-08-12 18:33 | Tiddan | Note Added: 0007363 | |
2021-08-31 22:17 | jsantos | Relationship added | related to 0002099 |
2021-09-03 19:38 | sfernandez | Status | assigned => resolved |
2021-09-03 19:38 | sfernandez | Resolution | open => fixed |
2021-09-03 19:38 | sfernandez | Fixed in Version | => 3.1.1 |
2021-09-03 19:40 | sfernandez | Note Added: 0007406 |