ILOG CPLEX Optimization Studio not working on MacOS - eclipse

I tried to use ILOG CPLEX Optimization Studio on my MacBook. The installation worked fine, but after startup the application is literally unusable.
I created a empty Project, when I click any file I get a java.lang.NullPointerException. In the preferences, when I try to access any page I just get a error that the current page has wrong values.
Any Idea how to fix that. My colleague has exactly the same problems. I have currently installed 12.10, but already tried with 12.9 which shows the same errors.
Edit: Tried it on macOS Catalina and Big Sur with the same behaviour

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

How can I investigate extensions problems with Visual Studio for Code?

When I click the Extensions I get nothing on one of my computers. I have checked the marketplace is not down. I have tried to delete the app and download a new version. Nothing helps. So are there any ways I can investigate this further? Quite frustrating to not been able to install extensions...
I'm on a Mac with Catalina 10.14.6 and I have VS for Code 1.41.1. I launched the Console app and see some messages from Electron(which I suspect is some part of VS for Code since it is mentioned in the about window) but none really makes sense.

Weaver failure: unable to locate assemblies (no matching project) for: Temp/Assembly-CSharp.dll

I opened Unity for the first time in a while today and I'm unable to create new scripts of any type. Both the normal and right click menus are missing the option:
Adding a script through the inspector creates a file, but yields these errors:
Although the file is created, it does not appear in either the project browser, or inspector panels.
Googling various parts of these errors actually gets a lot of posts, but almost all of them come down to "restart Unity", which isn't doing anything.
All of this is reproducible for me on a fresh project file. I've tried restarting Unity and my computer, as well as reinstalling Unity from scratch. I've also double checked that I have .NET installed properly (reinstalled, and dotnet command works in terminal).
Unity: 5.4.5p5
Mac OS 10.13.3
This is a bug present in versions between Unity 5.1 and 5.4. It has been fixed in Unity 5.5.0 and an update to 5.5.0 and above should fix it.
If updating to Unity 5.5.0 which has the fix did not fix it then it's better to upgrade Unity to the latest version which is currently Unity 2017.4 at the time of posting this answer. This version should be able to get ride of that error.

Visual Studio Code Won't Run on Mac 10.8.5

I just downloaded a fresh copy of VSCode-darwin.zip from https://code.visualstudio.com/, upzipped, dragged to my Applications directory, and tried to run it. After the initial "Verifying Visual Studio App" window ran, the dock icon bounced a few times then vanished and the app didn't load. Subsequent attempts yielded the same result. Anyone else experience this? Any known conflicts or dependencies for 10.8.5?
VS Code does not support Mac OS X 10.8 and below. We have a dependency to Electron and updated recently which caused this.

Windows Phone SDK 7.1 Emulator Complete Re-boot Error

I thank you all for reading this lengthy question. It's really important and I will appreciate it if you can assist me :)
The problem -------
I am have been using the Windows 7.1 SDK for about two months now. The emulator has worked without any problem so far. However, today, it began displaying this error (The saved state (Name of File).dess is corrupt. Please delete the corrupted saved state file and then retry). I had not made any significant changes to my project code, or moved any files. I had just added some Visual State animations for a button.
As it suggested, I went ahead to delete the file. I then started debugging again. However, the emulator now opened and displayed the message (Windows Phone Emulator is doing a complete OS reboot). This message was displayed for a very long time. I closed the emulator and project. Since then, I have been unable to use the emulator. I am able to code normally in Visual Studio, but I cannot test my application.
What I have tried ------
I read up on this issue and found many others who faced the same emulator issue. Following their suggestions, I have run one repair of the Windows Phone SDK 7.1. I have also tried uninstalling and then re-installing the SDK 7.1 once.
System Specifications -----
I am using Visual Studio Express 2010 for Windows Phone (Windows 7 64 bit)
I have downloaded the Windows Phone SDK 7.1 from this link: http://go.microsoft.com/fwlink/?LinkId=258412
I have read that this issue might be because of some hardware incompatibility. However, I think my machine is compatible with the emulator. Here is some information.
DirectX Version: DirectX 11
8GB RAM
Driver Model: WDM 1.1
Additional Information:
I have read that installing the 'January Update' might fix this issue. I tried downloading the update from this link: http://www.microsoft.com/enus/download/details.aspx?id=23854
However, the installer said that the update is not compatible with the product/version of the product I am using.
Usually the Repair function of the WP7.1 SDK is enough to fix all the issues. It runs the generation of the saved state of the emulator again.
Please try to delete files in %ProgramData%\Microsoft\XDE folder first (make sure you backup them somewhere else.), then run the emulator. If the emulator runs with a message "Windows Phone Emulator is doing a complete OS boot," let it boot. It takes some time though. This way you will know that the emulator actually can run on your computer. This won't generate a new saved state image, but the emulator should at least load.
Next, try installing WP7.1.1 SDK update from http://www.microsoft.com/en-us/download/details.aspx?id=29233. This update also installs additional 256MB emulator image besides the original 512MB image. It also generates emulator's saved states in the process, potentially fixing the issue.
If everything fails, then try these instructions to fix the saved state of the emulator:
Uninstall WP7.1 SDK
Manually delete these folders:
%ProgramData%\Microsoft\XDE
%LocalAppData%\Microsoft\XDE
Install WP7.1 SDK again.
Install WP7.1.1 SDK update: http://www.microsoft.com/en-us/download/details.aspx?id=29233.
Edit:
Btw, have you tried to reboot your computer? Once this fixed the issue for me.
Alright, I managed to solve this problem.
I reinstalled Windows and downloaded the SDK 7.1 again. The emulator works fine now!
#Paulos, thanks for helping!
I had the same problem for a long time. Try this:
Start up Visual Studio 2010, but before you start debugging, click on the tabs of all the open pages so that all the xaml pages and code behind pages can load.
I noticed it when I opened Visual Studio, but the first open page was a code behind page and not an xaml page, so when I first clicked on the tab of a xaml page, of course, it took some time to load the xaml page into the editor. However, when that and one or more open xaml pages were also loaded, the emulator started without the error message.