You get an error while using some Windows method to copy the save directory?
The specific error is important.
It might be an error caused by trying to copy the save while Minecraft is using it, or it could be a hard disk error meaning the file is damaged due to a problem with your filesystem being corrupted or your hard disk being about to fail.
It all depends upon the error message.
Stack: [0x00000000024d0000,0x00000000025d0000], sp=0x00000000025ce1d0, free space=1016k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ntdll.dll+0x46655]
C [GDI32.dll+0x3aa1]
C [GDI32.dll+0x6caf]
C [D3DGear64.dll+0x108bba]
C [lwjgl64.dll+0x37d5]
C 0x0000000002a35b74
20:47:03 INFO]: Looking for orphaned versions to clean up...
[20:47:03 FATAL]: Fatal error launching game. Report this to http://bugs.mojang.com please!
java.io.FileNotFoundException: File 'C:\Users\hp\AppData\Roaming\.minecraft\assets\indexes\legacy.json' does not exist
at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:299) ~[launcher.jar:1.6.11]
at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1711) ~[launcher.jar:1.6.11]
at net.minecraft.launcher.Launcher.cleanupOrphanedAssets(Launcher.java:253) ~[launcher.jar:1.6.11]
at net.minecraft.launcher.Launcher.performCleanups(Launcher.java:495) ~[launcher.jar:1.6.11]
This message is alarming but meaningless in this context where it is happening with "performCleanups" in the stack trace. This is the cleaning step that happens after the game has exited, and unless you have ever launched a "legacy" version of minecraft before your launcher will not have downloaded the legacy.json file.
Just one of the many instances where a little effort on Mojang's part to clean up their code would make everyone's life simpler.
This is your problem, and not very informative.
[20:47:08 ERROR]: Game ended with bad state (exit code 1)
control keybindings (including mouse buttons) are configured in the options.txt file that is saved in each individual launcher profile.
Did it work and not work for saves that are in the same launcher profile?
Or did you change profiles when you changed saves which probably indicates you've changed the control key bindings in the profile that doesn't work as you expect).
thats a lot of messing about to get something that used to just pop up after it crashed. thanks anyway
edit: also, does it use much computer resources running in the back ground like that?
You had to set your old launcher to do that too. It's too bad Mojang didn't USE the existing launcher's configuration for the new launcher.
Probably doesn't use too much resources. The single biggest thing would potentially be memory if the new launcher is Java (I'm not running either the new launcher or the newer launcher. I'm still running the launcher that doesn't come with Java bundled in)
To be honest, I'm more concerned about the mechanism they are using, and when it changed. I've had the anti-banner thing active for years now, and with the arrival of the new launcher this is the first time it has caused a problem. So I'd like to know if this is something that changed with the new launcher.
It changed back in 2013. At the same time as, or shortly after, the launcher started supporting choosing which version of minecraft you wanted to run. At that point in time Mojang abstracted the resources to make it easier to share code and resource files. You want to run 1.2? The launcher knows you need these specific 150 different files and uses the ones you already have, and downloads any that are missing. If a new sound is added in 1.3, then you only need to download one new sound file to run 1.3 and reuse everything else you already have.
Generally speaking people tended to run into issues like this when they "uninstalled" minecraft or deleted the contents of .minecraft and therefore triggered a full redownload of resource files. Because I have 2 files in the /ad/ directory that were downloaded in 2013, 2 that were downloaded in 2014, and 4 that were downloaded in 2016. Of these only 3 are sound files, and 2 of those are the 2013 vintage files. The newest "ad" sound file is from 2016, MC 1.11 and is a llama sound. So generally speaking you'd be hard pressed to notice this problem as long as you hadn't enabled the adblocker before 2013
I haven't used the new launcher yet, but I got the impression that files are being stored somewhere different than before. The latest launcher may be downloading files that are already on your computer in the old locations.. and therefore acting the same as if you had deleted .minecraft.
0
http://windows.microsoft.com/en-US/windows7/Check-a-drive-for-errors
0
Make sure that the language you have selected in your minecraft options is actually supported in the version you are trying to run.
MC does not deal well with game settings that don't apply when you go backwards in versions.
0
You get an error while using some Windows method to copy the save directory?
The specific error is important.
It might be an error caused by trying to copy the save while Minecraft is using it, or it could be a hard disk error meaning the file is damaged due to a problem with your filesystem being corrupted or your hard disk being about to fail.
It all depends upon the error message.
0
Razer Synapse is known to cause this issue.
Probably in your logs you will see a log like "Picked up _JAVA_OPTIONS=256M"
This environment variable (if it exists) caps your heap size.
0
D3DGear is a game recording software package.
0
You saw that the fullscreen crash was triggered by D3DGear, right?
In any case, sometimes things work in a window or in fullscreen, but crash trying to do the switch.
1
You ran McLeaks or similar hacking software.
Now your computer config has been modified to not be able to talk to Mojang's login servers.
You have to delete these records from C:\Windows\System32\drivers\etc\hosts
(you'll need admin access to be able to edit that file)
2
This is not your problem:
This message is alarming but meaningless in this context where it is happening with "performCleanups" in the stack trace. This is the cleaning step that happens after the game has exited, and unless you have ever launched a "legacy" version of minecraft before your launcher will not have downloaded the legacy.json file.
Just one of the many instances where a little effort on Mojang's part to clean up their code would make everyone's life simpler.
This is your problem, and not very informative.
Post the game output log.
0
And if that doesn't help post the entire game output log that contains the NullPointerException.
The context that the error occurs in contains the clue as to what's wrong.
0
control keybindings (including mouse buttons) are configured in the options.txt file that is saved in each individual launcher profile.
Did it work and not work for saves that are in the same launcher profile?
Or did you change profiles when you changed saves which probably indicates you've changed the control key bindings in the profile that doesn't work as you expect).
0
WE DON'T CARE.
It's a problem with your modded client. Go talk to them about it.
Mojang no longer uses (i.e. pays for) S3 and any 3rd party client that tries to use S3 is BROKEN.
0
You need to do all the standard "clean up" windows things (and I don't mean use a registry cleaner).
All kinds of applications put stuff in %temp% that's what it is for! %temp% is for temporary stuff.
Not all applications clean up afterwards.
So right click on your C: drive and push the "Disk Cleanup" button.
Then when it shows you what will be cleaned you can hit OK.
You may want to also do the System files version of the cleanup since Windows Update can leave piles of cruft around too.
Files downloaded from the internet, cached web pages, all kind of junk files accumulate in the dusty corners of your teeny tiny SSD.
You have as much storage as an iPad mini and less storage than my phone's SD card.
0
You had to set your old launcher to do that too. It's too bad Mojang didn't USE the existing launcher's configuration for the new launcher.
Probably doesn't use too much resources. The single biggest thing would potentially be memory if the new launcher is Java (I'm not running either the new launcher or the newer launcher. I'm still running the launcher that doesn't come with Java bundled in)
0
If you had to right click on the old launcher and disable display scaling in the past then you'll need to do that again with the new launcher.
0
It changed back in 2013. At the same time as, or shortly after, the launcher started supporting choosing which version of minecraft you wanted to run. At that point in time Mojang abstracted the resources to make it easier to share code and resource files. You want to run 1.2? The launcher knows you need these specific 150 different files and uses the ones you already have, and downloads any that are missing. If a new sound is added in 1.3, then you only need to download one new sound file to run 1.3 and reuse everything else you already have.
Generally speaking people tended to run into issues like this when they "uninstalled" minecraft or deleted the contents of .minecraft and therefore triggered a full redownload of resource files. Because I have 2 files in the /ad/ directory that were downloaded in 2013, 2 that were downloaded in 2014, and 4 that were downloaded in 2016. Of these only 3 are sound files, and 2 of those are the 2013 vintage files. The newest "ad" sound file is from 2016, MC 1.11 and is a llama sound. So generally speaking you'd be hard pressed to notice this problem as long as you hadn't enabled the adblocker before 2013
I haven't used the new launcher yet, but I got the impression that files are being stored somewhere different than before. The latest launcher may be downloading files that are already on your computer in the old locations.. and therefore acting the same as if you had deleted .minecraft.