Unity 2019.3.3f1 crashes under Mac OSX Catalina and Mojave - unity3d

I'm trying to run a github repo that can found in here. with Unity 2019.3.3f1 . Which works fine on Windows10 but instantly crashes on Mac OS Mojave and Catalina. This is the first time that I've came across a Unity error like this, any ideas would really helpful :))
Error message: link

This error persists since Unity 2019.3.0 and is still there in the latest version (2019.3.13). So we are unable to upgrade and have to stick with Unity 2019.2.21. We will consider switching to the Unreal Engine for our next project.

Related

Shader graph connections not visible in Unity3D

About a week ago I opened shader graph in one of my projects when I noticed the connections between nodes are just gone (like shown in the image). The shader still works just fine as if the connections are there, but it's impossible to work with since they are not visible. Today I have noticed that the Visual effect graph also lacks the connections. The problem started on Unity 2021.3.6f1, then I upgraded to Unity 2022.1.22f1 and the problem remains. Even if I create a new project I still can not see any connections. I am working on Macbook pro 2017. Any help would be appreciated.
shader graph without connections
I tried restarting computer, reinstalling Unity Editor, downgrading to an older version of Unity Editor and creating a blank project but nothing fixed the problem.
I experienced this same issue in Unity 2021.3.11f1, and confirmed the bug in multiple projects that were previously fine (only one of which was recently changed).
What MacOS version are you running? My best guess is that MacOS Ventura 13.1 broke some versions of Unity, as upgrading from macOS Monterey was the biggest change to my system this week (2019 MacBook Pro 16").
The following steps appear to have resolved the issue for me (so far so good):
Reboot the computer (just to be sure)
Backup the project (I just created an archived duplicate)
Install Unity 2021.3.16f1 (the latest LTS release)
Delete the project library (in case there's something weird cached)
Open the project in the new version of Unity (which also regenerates the library)
I am now able to edit shader graphs again. Of note, deleting the library and regenerating in 2021.3.11f1 did not fix the issue. Only opening it and regenerating the library in 2021.3.16f1 worked for me.
I did not test leaving the old library intact while opening the project in the newest LTS version of Unity; it's possible regeneration isn't necessary, but it does seem like the safest bet. Especially if you didn't try removing the library before upgrading the project to Unity 20221.22f1 and you're still experiencing issues. You might try deleting the library to see if that resolves the issue now, without trying to downgrade to 2021.3.16f1?
There's a post over on the Unity Answers support site about this issue as well, but the login system appears to be broken (the irony!), so I can't respond there. https://answers.unity.com/questions/1927887/shader-graph-connections-not-visible.html

Mac M1 chip machine, Mac OS BigSur Version 11.5.1 having problem with eclipse app. Its not opening after restarting machine

I Installed eclipse on my new mac m1 chip machine, It was working fine until I restart my machine. After restart the machine, the eclipse app is not opening also no error is shown in the display..
I am trying to open the app in terminal I am getting the following error
rosetta error: /var/db/oah/223263137464320_223263137464320/27e2cf6e452a44ee1a3ccc20e0409d562f65d18f27dd9ff3ebd552b78e52a4e3/eclipse.aot: attachment of code signature supplement failed: 3 Trace/BPT trap: 5
the solution giving in this is to upgrade the OS, but I already upgraded to the new OS version.
I can't find a solution anywhere, even in Apple forum sites
I faced a similar issue today. In my case, I'm using Anypoint Studio, which is built on top of Eclipse 4.19. After updating the OS, it worked again.

Visual Studio Code on Mac Sierra 10.12.5

I am using a Mac OS Sierra 10.12.5 (16F73)- Macbook Pro touch pad. I have tried running Visual Studio Code to no avail. Nothing happens, no error message, nothing. It just won't start. I have read articles or using Mac Archive Utility to unzip the downloaded zip file, i still can't get it to run. Has anyone got a solution to this?
Many thanks!
I'm also using Mac OS 10.12.5 with a Macbook Pro and recently installed vscode.
Try to redownload the file or maybe restart your computer, you shouldn't have any problems with the installation.

Tango Unity Examples Not Building

I have been trying to build and run the tango unity example on my new tango device and it doesn't seem to be working. As soon as the app launched the app crashes on my device. It just says Unfortunetely, Unity Examples has stopped.
I also tried to run a simple app with Tango AR camera and got the same result.
I am running Unity 5.4.0f3 (64-bit) with Android Studio 2.1.2. I installed all the tools on the Surface Book (Windows 10) on 8/1/2016
As stated on the Tango developers group on G+, Tango SDK does not support Unity 5.4 yet, you need to download 5.3.
Hi Devs,
Unity released version 5.4 last week. As a result, Tango development is broken. The team is aware of the issue is currenlty working to address the issue this month. In the meantime, the only workaround is to stay on Unity 5.3.
Thank you for your patience everyone.
https://plus.google.com/+ProjectTango/posts/N9DEz2RKZSb

Unity 5.2 sudden VR crash

All of a sudden, I am getting a full blown crash whenever I run/play my project with the native VR support in Unity 5.2.0f3 and Oculus version 1.7 (SDK 0.6.0.1) which has never happened before, until today out of the blue. No change made to anything to do with VR or Oculus that might have triggered it, hence my confusion...
This is what I get on the log:
Unity Editor [version: Unity 5.2.0f3_e7947df39b5c]
OVRPlugin.dll caused an Access Violation (0xc0000005)
in module OVRPlugin.dll at 0033:eb9a3b9a.
My PC and GC:
- Windows 7
- Nvidia GTX980 Ti
Thanks in advance for your help,
I believe 5.2 requires SDK 0.7.0 for native VR support. Have you tried upgrading?
Got same error with Unity 5.3.3f1. Fixed it by changing Oculus Config Util settings as following:
Open Oculus Config Util App on windows.
Go to Tools->Service->Configure options.
Set the Debug HMD type to DK2.
might be help for new users.