This is a very simple sample project to show the issue I am getting in my game. This happens on every iOS device I try. I did not see this issue on the Android devices I have tested on, but it might be there too.
This project just has two scenes, both with one button. The button will load up the other scene.
The first scene is “Portrait” mode scene (Only allows portrait mode and will force switch to portrait if the device is not in portrait mode)
The second scene is “Landscape” mode scene (This scene will allow for auto rotation but will not force rotation)
The issue is that when going back from the “landscape” scene to the “portrait” scene while still in landscape mode. The “Portrait” mode scene UI will be drawn the correct way that it should be. But the UI (Buttons) will not react to the correct positions.
Once you actually are able to press the button, and move to the next scene (back to “landscape”) if you rotate from “Portrait” to “Landscape” the screen gets cut in half and the app is broken.
This has been going on since RC1 and have not been able to find a solution.
I really don’t think that’s the issue. The entire screen gets cut in half including the 3d part. I don’t think this entire issue is happening from the ui portion of Unity
So are you saying that Unity doesn’t support non power of two images? Shouldn’t that be fixed regardless? Also. The sample project I attached here isn’t using anything besides a canvas scaler and two default buttons.
How could the power of two issue be tied to this too??
Im really starting to regret jumping into the 4.6 beta. I thought the new UI system was going to allow better flexibility but in the end, it is not really that much better over a custom UI system and it is painfully slow/glitchy due to the interaction with the gameobjects, I will probably have to revert everything I have done and recreate everything again from scratch. On top of that, I have to deal with issues that have apparently been fixed in the stable release.
Oh well, I will assume the consequences of my actions :S
Edit : I just noticed the release candidate 3 was released yesterday and probably include the fixes from the stable release… I guess I am out of luck
Yes according to what I read on the Unity site. This has been fixed and will be included in the following update of 4.61.
Just gotta hold out a bit longer.
Unfortunately for me I am having some Android issues but I don’t think it’s a bug. Just some weird device issues that don’t respond to my script like it should.