I made a stackoveflow account just to post about this since it's been bothering me for 3 days time (tinkering after work so not much time every day). And this is my first post so please be forgiving if I break a few rules :)
My problem is that after I have installed and configured everything and I have followed the official guide I get these errors thrown by VS
I have researched as much as I can and still nothing. Things I have tried:
Reinstalling VS
Reinsatlling and manually installing the Windows 10 SDK
Adding all the sdk folders to the Path Env. Variable
Rebuilding the project
Building a new project
Changing the version of the UWP
Has anyone else had this issue or know a way to fix it? I really want to start developing for MR after doing a ~10 page documentation on why its the most promising technology...
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
when I try installing build tools using sdkmanager on window using this command below
C:\all-things-flutter\flutter-installation\android\cmdline-tools\bin>sdkmanager.bat "build-tools;30.0.0" --sdk_root=../
I keep getting this error
Warning: IO exception while downloading manifest
please this is not a duplicate question, cus I didn't find the answer I needed.
this has been bugging me for days so how can I get it right
So since I could not get an answer after 8 months, I have decided to share how I did it and other kinds of solutions people have suggested but not from here.
How i did it
I downloaded android studio (even tho i was not going to use it), then i use android studio to download the recommended SDK i will need, after that i added the SDK folder path to my system variable, that way i can continue the flutter installation and run flutter doctor, which did ditect my SDK path.
Other people Suggesttion
From my research online, I saw people saying that you need a much slower internet connection because if your internet connection is faster, it will skip some downloads, which can cause the SDK to not work well.
but my response to that is "yer good luck with that".
I've been developing blazor wasm apps in vscode for the past few months without incident. All of a sudden, I can't debug via F5 any longer. I'm literally starting with a brand new app (dotnet new blazorwasm) and when I hit F5 I get the following error:
I've uninstalled/reinstalled vscode, chrome, updated .net core 5, tried Edge put things into my launch and launchsettings.json that have helped others and plenty of other things things that I can't recall. Even created a new account on my computer to eliminate possible plugins or settings, same problem.
One thing that does work is that I can debug the old way where I would run Chrome from the command line: open /Applications/Google\ Chrome.app --args --remote-debugging-port=9222
Then you can hit Cmd+Shift+D in Chrome to start debugging within Chrome. This is a stop gap, but I'd really like to figure out how/why this just stopped working.
I created repo that reproduces it on my machine.
I'm not finding a lot of ways to gather diagnostic details that might help me determine the cause, so would appreciate any tips that would help me solve this.
Using latest chrome and vscode, even tried the insider build. No luck. I'm not sure what I did or how to fix it. Any help is greatly appreciated!
This is todo with omnisharp update. I get the same. You can downgrade omnisharp as a test and it will work again. I am investigating.
I will start a project at the beginning of 2019 (January or February). Maybe a bit later.
Will it be better to start with the current version (3.9) , or should I start with version 4 which is currently on Beta but may be released soon. depending on the Ionic team life-cycle development. Any advise ideas are welcome
Any info about their roadmap?
I know it's not the best location to ask ... But I think that some people are wondering the same question!
revision
Thanks in advance
No, it is not. I recently upgraded my project from 3.19 to 4 and I regret doing so. I knew I might have this problem. I proceeded anyway as my cli would not desist from troubling to ugrade to the latest version.
First, I had problem with platforms, especially android platform. Later, I could not build. Then it started giving me all sorts of incomprehensible gradle errors.
I did all I could, I removed plaforms folder, added again, removed node_modules, run npm install again. Nope nothing worked.
Now I am going back to my earlier version.
So in my opinion, don't use it for production.
I am currently working with multiple Ionic 4 projects, I would have to say that the documentation is not the best for this version. There are still bugs here and there and some package issues (e.g. ionic-native packages) but seems to be in the right direction. It is a personal decision which one to use based on your project.
I personally prefer to go with Ionic 4 since the angular adaptation makes it easier for me to work around.
I have tried the beta version and also updated one of my projects from version 3 to version 4 and got a lot of errors. I think we have to wait for the actual release.
I have installed latest version of unity(5.6.0f3) from https://store.unity.com. Every time i try to launch the unity I get unity bug reporter window popped up.I am not able to create a new project or use unity. I uninstalled latest version and installed unity 5.3.5f1 version. But still I am facing the same problem.
Maybe memory problem in your pc, try to end task of anything running even google chrome (because it takes a lot of memory) and then run Unity as administrator.
It can be also that your windows is 32 bits and you wanna run Unity3d 64 bits.
I hope this helped you ;)
I also faced the problem like this.
In my case this bug reporter appeared when I tried to open the "unity-3d-simplefps-master" project downloaded from GitHub.
So I renamed the source folder name and I just avoided this bug reporter.
Best wishes!