What makes you say that? Was a bug report created back in February this year? Maybe it was actioned and resolved? Maybe the above was part of some issue with Burst that was actioned? Plenty of time is spent on the forums asking question after question chasing root causes but not all can be, even if they are discovered in the first place.
If the above is something that is easily repeated and affects more than an individual then Iâd be very surprised if a bug wasnât reported and therefore fixed.
This is why bug reports are important. Posts on Discussions are not a bug report and cannot be actioned or tracked.
You are entitled to your opinion but also, saying âUnityâ doesnât care as if itâs a single thing rather than many developers across lots of feature areas in teams, youâre essentially saying that none care about their specific area which is both wrong and pretty insulting to be honest.
The 2D team has some of the lowest bug counts with turn-around time extremely low for fixes. I can tell you quite confidently that we do care about the quality of the product.
Likely happened due to a version mismatch or invalid skinning data. Usually resolved with package update or re-import. Since Burst has limited exception support, it just reports an error even though we do handle it internally.
Kindly please ensure to submit a bug report or a repro project when reporting a bug. This really helps analyzing the issue and if a bug report is submitted helps track the issue easily for all.
What makes me say that is how 11 months had passed without a peep from anyone from Unity. Did the original poster submit a bug report? I donât know. But I did after I experienced a similar bug and saw that nobody from Unity even bothered to address the original posting.
Trust me, I submit bug reports all the time. Iâm starting to feel like a bother to the Unity team from all the bug reports I submit. What annoys me most is how probably 75% of the bug reports are closed either because itâs deemed âby designâ or âwonât fixâ because not a lot of people have reported it, or because the team canât reproduce a bug on demand. If people from Unity could watch over my shoulder as I do a normal day of work, youâd see TONs of errors happening, some of which Iâve reported, some of which Iâve just grown to ignore or work around. What scares me most is how me and others like me are getting so used to Unity bugs being a regular thing that we just treat it as normal now. So yeah, it feels like Unity doesnât care most of the time.
By the way, regarding the original post. I donât know if itâs the same issue, but discovered that if you are animating a skinned sprite, changing the active flag of a GameObject via animation will throw all kinds of errors. Perhaps your animations were doing that? Yes, I submitted a bug report about that, with a project reproducing the issue.
Our support system isnât based on ensuring we see every single post about an issue. Itâs based upon bug reports or the worse-case, devs stumbling across posts. If you want to correlate responses on Discussions to your viewpoint then feel free but itâs not a valid metric.
You may feel that way but do you have the same experience with 2D bugs or 2D animation because itâs here that you chose to make the statement âUnity doesnât care, apparentlyâ?
This is more constructive for everyone.
If you have an active bug report then Iâd be curious to know what the incident number is and its status.
Despite you thinking bugs are ignored and/or closed without consideration, I can at least assure you that this isnât the case for the 2D team. Most of the team like me are on leave for Xmas yet weâre here on the forums.
I am happy to see some passion in your response. Itâs something thatâs typically lacking in general from Unityâs responses. Please remember that most people like me donât see individuals working on specific issues. We see âUnityâ as a whole. That doesnât mean you specifically donât care. It means all the way from the CEO down to the middle management. People that make the big decisions and brag publicly about how stable the latest release is without actually knowing what itâs really like. I apologize to you and the team directly working on the product, since you probably donât have much choice on what to focus your efforts on.
To be fair, I havenât used a lot of the 2D features of Unity. But in my defense, the first time I used the sprite skinning feature, I ran into multiple bugs. The first time. Then when googling for answers (because thatâs the first thing I do before submitting a bug report), a similar problem goes unnoticed for 11 months. Thatâs not a good impression.
By the way, I also had problems with the IKManager2D component. One thing that drives me crazy more than anything with Unity is when I click the ? button for a built-in component and get a broken link. Lack of easily accessible documentation is a huge problem, which is why it always leads to googling and finding forums posts like this.
I am looking at the list of bugs we have for 2D animation, and it seems that there is no report described in the original post in this thread. It would be great to have it reported so that we can repro the issue and fix it if the bug persists.
As my colleague MelvMay said, we track bug records, but not necessarily forum discussions.
As MelvMay mentioned, could you share the incident number if youâve filed it ?
Iâve scanned our 2D Animation bug list and couldnât find anything that appears to match this issue at a glance.
Could you let us know which Unity Editor version and 2D Animation package version youâre using? Iâve just tested this on my end and confirmed that the â?â button is pointing to a valid link.
To clarify, the original post wasnât mine, but I commented that MAYBE itâs the same issue that I ran into, which is the one I reported in the link in my previous reply.
First of all, thank you for taking the time to provide the information and report it the issue with the Bug Reporter!
However, when Iâve accessed the attached project the Animation directory seems to be omitted (only the .meta file exist). Hence I am not able to follow your provided reproduction steps.
That being said, I have attempted to create my own simplistic deformed sprite animations with sub-sprites being activated/deactivated during the animation clip in 6000.3.0a2 (2D Animation 13.0.2) as mentioned.
I start to encounter errors such as âSystem.IndexOutOfRangeException: Index -1 is out of range of â38ââ when entering Playmode when I have two distinct animated sprites with activation/deactivating in the same scene, but it seems different from the original posterâs issue. Is this what you are experiencing Gillissie?
If you are able to provide the reproduction steps in creating the animation assets required, or able to provide these animation assets to reproduce the issue youâve faced, that will be most useful.
In the meantime, Iâll be continuing to gather more information on the issue I have encountered.
It sounds like youâve already reproduced the bug. As I mentioned above, I donât know if the original postâs bug was the exact same thing, but maybe it was. Thereâs not a lot of extra info in the orignal post.
I donât know why there would be missing assets in the submitted project though. I just submitted it through the bug reporter and included the project as it does by default. However, I did submit two different bugs, with varying versions of that same project. I assumed the bug report would link to the version of the project that existing at the time of the bug report, but maybe youâre getting it confused with the other bug report.
Hereâs a screenshot of the project as it exists right now on my computer.
@DavidTeo Iâve zipped and attached the full project here. All you have to do is play the game, then click the button in the top left to start the animation and watch the errors happen.
Also by the way, this is the other bug I reported thatâs related to this project, but probably doesnât have the animations included in the attached project. I wonder if theyâre getting confused.
@Gillissie
Thank you for the very prompt response and providing the repro project here.
I have downloaded the project you have attached here, and indeed the Animation assets is there and able to reproduce it by going into play mode and hitting the UI button at the corner.
Iâll be communicating to the team about this bug and this should be fixed.
Regarding about this bug, when I have accessed the project with 6000.3.2f1 and tried to follow the provided reproduction steps, I am not able to observe the appearances of errors when accessing the Skinning Editor on the sprite.
Are there any other required information that can help us to reproduce and investigate into this issue?
Hello. I encountered exactly the same issue when upgrading from Unity 6 to 6.3. I admit that I didnât read all the messages in the thread very carefully, focusing mainly on the solution itself, but I would like to note just in case that in Unity 6 (6000.0.36f1) I did not encounter any such problems in the same project.
I will closely follow the search for a solution. Thank you for your work.
