Having updated to MacOS Sierra (10.12), gfxCardStatus is now a dependency, so I cannot switch to the integrated graphics option. How do I fix this?
This is a known issue. Fortunately steveschow has a branch that solves this for 2011 or later Macs, and another branch that solves it for 2010 Macs.
Related
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
While migrating from a old 2015 Macbook Pro to a new 2019 Macbook Pro, how do I copy IDEs like Eclipse with all the configuration intact?
I have several applications like Eclipse, Microsoft Remote Desktop, Keychains, Terminals with profiles.
Is there a way to get everything running in new Macbook Pro exactly as it was (in the older one) without sweating much?
I asked this question. At the moment, it looks like the easiest way is to clone the old Mac drive and restore it in new Mac. I have not yet tried it.
From MAC to MAC, The best solution is to use Migration Assistant for Mac .
Have a good day
I've just updated my MacOs into MacOs High Sierra and then Scilab 6.0.0 doesn't work anymore, by unmatching with the system version. How can I fix this problem or does it exist an intermediary software or alias (like anaconda) to use scilab on mac?
Thanks
I have same problem. From what I've read Scilab 6 is not compatible with Sierra. Scilab version 5.2.2 can be made to run under Sierra and there are instructions online to do this. I haven't tried it yet so can't vouch for it.
Last week I successfully update my MacBook to High Sierra, the new OS of Apple...
I decided to also update my developer studio. I upgraded from 10 to 11. No problem so far.
I was starting to develop in version 11, when I needed a menu item. For instance Project > Clean...
ALL those menu items in the top level window menu of developer studio are greyed out... My conclusion was that version 11 is not compatible with the high sierra.
I switched back to 10... DAMN! Same issue. Installed 10 and 11, with and without the current workspace. Same issue!
I guess it is due to the fact that it is due to high sierra. I cannot revert my mac, so using developer studio at this moment on my MacBook is very problematic.
Who else?
#Jboss developers: when will this be fixed? Or how do I have to create a bug report? The menu in developer studio to report a bug is disabled...
Looked on google but no one has reported this so far... or Google hasn't picked it up yet ;)
We are aware of the problem, and this may land in the next update release
I upgraded my system to OS X El Capitan beta 3 and installed JDK 8 downloaded from Oracle. However, other applications that use JDK is run correctly, only Eclipse Mars stuck on the logo. I checked that stats of Eclipse process. It showed that Eclipse process is sleeping.
Is there any methods to make Eclipse run correctly? Thanks for any helpful answer.
This has been reported to Eclipse as high priority bug 472259. Currently there is no solution.
This is mentioned in release notes for OS X El Capitan DP3 [1]
Some versions of Eclipse may hang during use.
See [2] Apple Dev Forums for workaround by reverting back to DP2
[1] https://developer.apple.com/library/prerelease/mac/releasenotes/General/rn-osx-10.11/
[2] https://forums.developer.apple.com/thread/8776
This bug its already resolved in Beta 4.
According to reports on https://forums.developer.apple.com/thread/8776#30240 the 4th beta release (public beta 2) fixes the problem. I'm having the same issue but I'm not able to upgrade and test it myself since I'm away from my backup drive for the next few days and I'm not upgrading without that restore point. I'll try to update this with more info once I've tried the upgrade myself.
Update: Just upgraded and Eclipse loads without any problems.
there is a makefile that you can use on project to compile and fix this problem.
https://github.com/mnott/javamake