![]() ![]() ![]() However, the UI system in Unity only allows me to anchor UI image size relative to the visible screen, which meant that the other images in the carousel that were off screen (since they were each nearly as wide as the screen for maximum visibility) cannot be scaled properly because they aren’t fully on the screen and the anchors can only be placed within screen space. My plan was to animate the images to slide off one side of the screen and the next image to slide on from the opposite side. ![]() Since my project was on mobile, I wanted to set up a stage select UI screen where the player could choose the stage they wanted by cycling through a carousel of stage images. The most recent example of this I’ve run into is also in Unity. I think the most frustrating thing is finding limitations in the engine that are working as intended, because they mean you can’t do anything else about it. Thankfully, I didn’t have that many UI animations overall so I only lost a few days worth of work, but it still sucked. I ended up having to redo all of my UI animations. The update did bring the plugin to my game, but also ended up breaking all of my UI animations because of a change in how their animation system worked. Recently I was working on a personal project (mobile puzzle game built in Unity to learn the engine) and I pulled down the updated version because they had incorporated TextMesh Pro into it and I wanted a better means of handling UI text in the project (Unity’s basic UI text system is not very good, which is why they bought the rights to TextMesh Pro). In the meantime, I was blocked and had to find other things to do. The other studio was apologetic and fixed the problem as quickly as they could, but such things take time to track down and fix. Nobody noticed what had happened until I found it because I was using the editor to make some UI changes and suddenly things started crashing. I just lost an entire week of dev time on my current project because a contractor studio working on some unrelated tools bugs were mucking around in the common code libraries for the tools and inadvertently broke the UI editor. Though this isn’t exactly the situation you describe, it’s close enough to warrant mentioning. They’re basically of the form “I wanted to do this, I realized it wouldn’t work because of (bug or engine limitation), I lost a bunch of work, it sucked.” Here, you’ll see what I mean. Sure, but these sorts of stories aren’t really very long or dramatic. For those who haven’t seen it, this is the video in question: ![]()
0 Comments
Leave a Reply. |