Anytime I start the Unity application on my MacBook Pro the console ends up expanding, till it has finished loading, preventing me from accessing any other application till I minimise or close it. How can I prevent this from happening, so that the console doesn't expand fullscreen when launching Unity?
Related
I'm using 2020.3.15f2 at my project. Not regularly, but sometimes game freezes visually on mobile phone. I mean that moment is always on the scene even you change to different scene. You can click everywhere, also ads are coming too. There is no sign of error on profiler or XCode.
I've tried canvas with screen space camera, and I'm just rendering a changing text with a camera. It still doesn't change. So rendering is not the main problem here I guess. I did'nt find any release notes about it. Do you know what is the issue or what is the version with fix to that problem?
I have built an android game and published it. It works fine in Unity editor and Blue Stack emulator, and also works fine in jelly bean 4.1 on a real device.
The problem is that in Android Nougat and Marshmallow the game starts normally, the main menu appears and menus work normally. But whenever the user opens the first level, the game enters something like a paused state - the player does not move, controls do not work and even the traffic is stopped (it is a racing game). However, the pause menu can be opened using back button works fine and the user can use it normally.
This problem do not appear in Jelly Bean.
I am using unity 5.6.2f1 personal (64bit).
using google admob and iap.
I have android sdk build tool 27.0.3
NOTE1: I confirmed that Start() function runs fine on start of scene. but update() function do not run. all update functions of all scripts are stopped. i am not changing scaled time at all.
NOTE2: It only happens on android marshmallow and higher.Everything works fine on lower devices.
This is an issue that happens to me just sometimes, most of the times the emulator works ok.
screenshot of the problem with the emulator
The thing is, that the emulator starts but it can not be maximized. It doesn't matter if you click on its "window" from the Tasklist at the bottom or you try to force it to maximize/make it go to the front from the Task-manager; it just doesn't react to it.
In the little window that appears when you have the mouse over the task (see screenshot), you can even watch the emulator starting and waiting for the interaction with the clock and so on, but it is not accessible.
Any ideas?!
I had the same issue after forcing the emulator to close during debugging.
To fix the problem, try changing the screen resolution of the virtual device under Edit in the AVD manager and then launch the virtual device.
This fixed the issue for me and I was able to revert to the original resolution without any problems.
I'am programming one kiosk app using GTK+Ubuntu 10.10. All works ok when I run the app manually but If I setup it up as a Startup Application on Gnome, it does not become fullscreen. I'am using gtk_window_fullscreen() function to tell it to resize as a fullscreen window. When Gnome starts, it launch the app with its default size without resizing.
Calling gtk_window_fullscreen() a second time, some seconds after being launched, doesn't work.
If I move the mouse pointer over the window once opened, it resizes automatically to a fullscreen status.
Any idea how to get a fullscreen on startup?
Regards
Fullscreen is handled by the window manager, so you may need to make sure your program is launched after the window manager has started.
My app works fine when launching from XCode, and it starts back up from a saved state fine, but the problem is when I open the multitasking tray and manually close the app. After closing the app this way, when the app reopens it doesn't start from the loading screen, it starts from the screen it was at when it was closed, but it is frozen and pushing the home button from this state causes springboard to crash.
My first thought was that the app was taking too long to open, so in the applicationDidFinishLaunching function I load data in a new thread (I have also tried performSelectorInBackground and performSelector after delay) and this works fine except for the strange problem described above.
Also, nothing is written to the device log and no crash report is created.
Any help with this would be greatly appreciated, Thanks.
Is the Xcode debugger still attached when you shut down the app? That would cause the behavior you're seeing when you terminate the app from the task bar.