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!
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
I'm using Unreal 4.26.0 and I finally got it to launch to my Oculus Quest 2. However, it doesn't always launch the latest version.
So, I might make a change, build the project, then launch the app on the Quest via Launch => Quest 2.
Eventually, it starts running on the headset, but often it doesn't have the latest changes. If I shutdown Unreal, then restart it, it does get the latest version.
How do I consistently have it launch the latest version of the app? Is there some formula for getting it to properly copy over during launch? Thanks in advance.
I did find the solution... just in case someone else has this same problem:
I did not have all the environment variables set correctly for Android/Java. I had to make sure all these were set:
JAVA_HOME
ANDROID_HOME
ANDROID_TOOLS
ANDROID_PLATFORM_TOOLS
ANDROID_NDK_HOME
So, after making sure each of those were specified, I also had to put each into my $PATH.
I should also note that I'm using Unreal 4.26, Android SDK 10, and Android NDK 22.0.7026061. These aren't exactly what the directions call for, but the directions are a bit old. These are (mostly) the newest versions as of this writing.
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...
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.
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.