Unity 3d crashing on mac when I press "play" in the editor - unity3d

I downloaded Unity 3d on my macbook air and created a new project with a single 3d object (a plane).
When I press the "play" button (Triangle icon), unity hangs and crashes.
It happens no matter if I create a new project again and add a different 3d object (a sphere).
The only way my project doesnt crash when I press play is if it's a completely blank project with no 3d objects.
Interestingly I can build a mac build of a project and it runs okay (I can see the 3d objects, the plane or the sphere).
Can anyone offer any advice?
Edit: OS / X version 10.9

My version of OS/X was a little outdated.
Upgrading from 10.9 to 10.12.X fixed the problem (after a 4 GB download and 60 minute install)

Ok, i think i solved it. My project settings had metal editor support disabled. Enabling this option solved the crashing problem. I reproduced this issue with a freshly created project and just disabled the Metal editor support. I tried on a macbook pro 2018 (with dedicated graphics card) and could not reproduce the issue. This could be an Intel graphics driver related problem.

Related

How to fix the problem with white boxes instead of text in Unity Editor

I have come up with a problem in Unity Editor v. 2019.4.34f1 when I am not able to read the text in the editor windows. This problem occurred only in a few specific windows.
Screenshot
I was trying to restart Unity and MacOS, and also close/open window.
Change the Graphics driver target in Unity Preferences as shown in photo.
For me, the issue was across all unity versions. So, I figured out that either it was a font issue, or graphics issue. And I started playing around.
Changing Device to Use to internal driver fixed the issue for me.

My Unity Hub doesn't go past the loading screen on mac

I am trying to download the Unity Hub for a school project on my macbook. I have a macbook pro with macOS Montery version 12.6. Every time i try to download it, it seems to work during the entire download process, until i try to start the program. I click on the program in my launchpad and the window with the logo and the loading icon. Then it keeps stuck on that screen. I have added a screenshot of that window.
Please help :)
Screenshot loading screen
I could fix it by reinstalling it, but I needed to do a deeper uninstall to make it work.
You can follow this one to help you.

Unreal Engine 4.23 screen flicker

I have started to use Unreal Engine for hobby and learn c++. The problem is that the screen begins to flicker in UE while i'm works. If I run other programs or applications the screen don't flicker, only flickers in UE.
I updated the Intel drivers and Nvidia drivers (1050Ti) but the problem is still unsolved.
Thx.
Turning off anti-aliasing worked for me.
Setting AA off per Mesh
General Switch for project : Edit > Project Settings > Engine - Rendering :
Anti-aliasing mode
Have you tried to manage your graphic card in the NVIDIA Control Panel ?
I think that customize your settings for Unreal Engine can fix the problem, I had the same issue and it's working for me.
I don't even know why, but Unreal encounters some issues when he has to deal with different graphics cards in a same time.
So, you have to set manually the graphic card for use in order to avoid conflict and flickering.
Open your NVIDIA Control Panel
In the panel Manage 3D Setting, choose Program Setting.
In the part Select a program to customize : search for Unreal Engine editor(UE4Editor).
In the part Select the preferred graphic processor.....: choose High-Performance NVIDIA Processor
Click on apply, & that's all. Reopen Unreal Engine and see if it's working.
Here a screenshot of the settings that you should have.
Settings in Control Panel
Ok, so I have been having the same issue for the past month now and I have just recently fixed it. The way I did mine was I went under my Nvidia control panel and reset to defaults for the UE4Editor under program settings in 'Manage 3D Settings'. Hope this helps!
What solved this issue for me was unchecking Enable Window Animations under the Editor Preferences Window. Edit -> Editor Preferences -> User Interface
Yes thats right adding the program to run on nvidia high performance in the nvidia control panel solves this issue.
I have flicker on a Mac (Apple Silicon) in UE 4.27.2 on a second monitor, the main MacBook screen was fine. I had to turn off "Enable High DPI Support" in Preferences->General->Appearance->User Interface.
UE 5.1 doesn't have the same problem.

Vuforia and Unity : Unable to place mid-air objects or use ground plane

I'm trying to place an object in mid-air and detect ground planes. When I follow the steps in the documentation, it doesn't work and I have the following error when debugging with adb:
PositionalDeviceTracker has not been Initialized correctly, unable to create anchors
I tried on an iPad running iOS 11.2, Pixel XL running Android 8.1.0 and a OnePlus 3T on Android 8.0.0 (which is not supporting ground planes but should work with mid-air anchors)
I tried each on Unity 2017.3.0p4, 2017.3.0f3, 2017.3.1f1 and even 2018.1.0b7
None of the above combination had any of these two features working.
I also use the image target feature and this one works perfectly.
I once managed to detect ground planes a month ago and I haven't changed my Unity version since then. However I updated both my Android and iOS devices at least once since then.
Please could you let me know if I'm doing anything wrong or if there's a known issue about that?
Thanks

Why is the sample Unity ARcore scene not detecting planes?

I installed the arcore-preview.apk on my Samsung 8(SM-G950U). Then I installed the sample ARCore scene from Unity onto the S8. The app starts up fine , but does not draw any point clouds or blue guidelines displaying the planes. I also cannot place the little Andy bot onto a plane. All I get is the UI saying, "Searching For Surfaces". Any ideas? I'll be continuously tinkering until I find a solution.
The problem seemed to have been the version of Unity(2017.2.0b10) I was using. So I just went back to the Unity Beta Archives and downloaded 2017.2.0b9 and then downloaded Android Target Support specifically for 2017.2.0b9. All is now working correctly!
You need to get the beta version 0b9, it won't work on the current stable one