I installed forge 1.10 and then it failed to launch, and it says that I am trying to play an unsupported version of the game and it's no longer supported
Here is the crash log-
---- Minecraft Crash Report -------- Minecraft Crash Report ----
WARNING: coremods are present:Contact their authors BEFORE contacting forge
// Don't be sad, have a hug! <3
Time: 11/10/18 1:11 PMDescription: Initializing game
java.lang.NoSuchFieldError: ofAaLevel at Config.initDisplay(Config.java:199) at net.minecraft.client.renderer.OpenGlHelper.func_77474_a(OpenGlHelper.java:114) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:431) at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:351) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- Head --Thread: Client threadStacktrace: at Config.initDisplay(Config.java:199) at net.minecraft.client.renderer.OpenGlHelper.func_77474_a(OpenGlHelper.java:114) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:431)
-- Initialization --Details:Stacktrace: at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:351) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
-- System Details --Details: Minecraft Version: 1.10 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 980102496 bytes (934 MB) / 1308622848 bytes (1248 MB) up to 2147483648 bytes (2048 MB) JVM Flags: 8 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 FML: Loaded coremods (and transformers): Launched Version: 1.10-forge1.10-12.18.0.2000-1.10.0 LWJGL: 2.9.4 OpenGL: Intel(R) HD Graphics GL version 4.0.0 - Build 10.18.10.4653, Intel GL Caps: Using VBOs: Yes Is Modded: Definitely; Client brand changed to 'fml,forge' Type: Client (map_client.txt) Resource Packs: faithful64pack-v1.4.0.zip (incompatible) Current Language: ~~ERROR~~ NullPointerException: null Profiler Position: N/A (disabled) CPU: <unknown>
-Vanilla Launcher or third party like MultiMC or Twitch?
-Modlist please, a big thing here due to 1.10.2 over 1.10 or 1.9.4 compatability, world gen mods I find are awkward for these versions with my experiences at least with mods loading more so than actual world gen problems. Just ore and otherwise acknowledgement and so on for loading them is more my thoughts behind it.
-Forge version is 2000, have you tried 1999 at all, I don't think it makes too much difference but just for the sake of testing and since its a Beta Forge you never know what might come up at times. Even though it would be more a mods need of consider over Forge. Just considering all options here that's all.
Glad I made a 1.10 modpack for other reasons and its coming in hand for another reason besides my 2 own (video documenting of mods from this period because why not as well as past mod version enjoyment for mods that died at 1.10 or are exclusive to 1.10 that I still prefer to play from time to time).
I considered my older setup of my .Minecraft in Vanilla first so if I had to compare to 2018 instance creations or MultiMC5 for 2018 creations over 2016/2017 I'll be using that to work things out here or otherwise start a new .Minecraft Vanilla instance just to test 2018 if I had to find out why your instance is crashing from a 2018 creation over a 2016/2017 creation of the profile.
Otherwise from my past 1.10 instance to see it work in a modded environment due to what Forge .jars I had on me more so that being 1999 and 2000 of 1.10 jars which by the looks of the crash shows you have 2000, which I jumped back and forth between 1999 and 2000 at times when making my own 1.10 instance functional now and have stuck with 1999 and no idea why I did afterward since its worked for me and more been a mods thing compared to Forge. I don't think 2000 would have issues but I'm just saying maybe could have.
I believe and I'm using the Vanilla Launcher at least for this not MultiMC5 and playing a working small modpack besides the obvious of it being a beta Forge of course with limited 1.10 mods that moved to 1.10.2 by this point or lack of 1.10 with 'compatibility of both apparently' and what comes with it at times with certain mods or the game being annoying with its beta experiences but never enough that it crashes and I can't get it 100% working much which are my assumptions here.
If you are using MultiMC5 or something I have an instance that is newer and not like my 1.10 from the Vanilla Launcher working period, but haven't 100% tested it yet but now I have a chance to and am glad I made it just encase. But I'd assume you are using Vanilla so I'll base my experiences as well as what I assume yours are on that for now unless you state your using another launcher of some kind.
Can you show a mod list please, maybe that might help since I had to sort mods out to make sure I got mine working but I did so more for other reasons besides just my small modpack being a thing I was into (Videos documenting the mods more so) but either way. I do think particular support for mods or elements from mods is needed to be determined here so a mod list will help out a lot here.
I feel that certain world gen elements from mods can be awkward sometimes and hold the game back so I usually am particular with those. Even 1.9.4 mods or those that are for 1.10.2 even over 1.10 or 1.10.1 (which obviously 1.10. is even more lacklustre unless you have a 1.10.1 forge since they don't have them on the Forge site anymore, even 1.11.1 even or 1.12.1, it makes sense why but still, I don't need 1.8.8 but can still get Forge for it so go figure).
Never encountered a problem with 1.10 not completely working to result a crash though. At least from my assumptions. And it shouldn't likely be a java version issue since 1.10 was 2016/2017 (counting vanilla and mods focuses, not the 2018 focus of other new mods for it) so its not too bad unlike 1.6.4 or 1.7.10 being outdated. Hmm.
I installed forge 1.10 and then it failed to launch, and it says that I am trying to play an unsupported version of the game and it's no longer supported
Here is the crash log-
---- Minecraft Crash Report -------- Minecraft Crash Report ----
WARNING: coremods are present:Contact their authors BEFORE contacting forge
// Don't be sad, have a hug! <3
Time: 11/10/18 1:11 PMDescription: Initializing game
java.lang.NoSuchFieldError: ofAaLevel at Config.initDisplay(Config.java:199) at net.minecraft.client.renderer.OpenGlHelper.func_77474_a(OpenGlHelper.java:114) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:431) at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:351) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- Head --Thread: Client threadStacktrace: at Config.initDisplay(Config.java:199) at net.minecraft.client.renderer.OpenGlHelper.func_77474_a(OpenGlHelper.java:114) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:431)
-- Initialization --Details:Stacktrace: at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:351) at net.minecraft.client.main.Main.main(SourceFile:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at net.minecraft.launchwrapper.Launch.launch(Launch.java:135) at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
-- System Details --Details: Minecraft Version: 1.10 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 980102496 bytes (934 MB) / 1308622848 bytes (1248 MB) up to 2147483648 bytes (2048 MB) JVM Flags: 8 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 FML: Loaded coremods (and transformers): Launched Version: 1.10-forge1.10-12.18.0.2000-1.10.0 LWJGL: 2.9.4 OpenGL: Intel(R) HD Graphics GL version 4.0.0 - Build 10.18.10.4653, Intel GL Caps: Using VBOs: Yes Is Modded: Definitely; Client brand changed to 'fml,forge' Type: Client (map_client.txt) Resource Packs: faithful64pack-v1.4.0.zip (incompatible) Current Language: ~~ERROR~~ NullPointerException: null Profiler Position: N/A (disabled) CPU: <unknown>
First things first:
-Vanilla Launcher or third party like MultiMC or Twitch?
-Modlist please, a big thing here due to 1.10.2 over 1.10 or 1.9.4 compatability, world gen mods I find are awkward for these versions with my experiences at least with mods loading more so than actual world gen problems. Just ore and otherwise acknowledgement and so on for loading them is more my thoughts behind it.
-Forge version is 2000, have you tried 1999 at all, I don't think it makes too much difference but just for the sake of testing and since its a Beta Forge you never know what might come up at times. Even though it would be more a mods need of consider over Forge. Just considering all options here that's all.
Glad I made a 1.10 modpack for other reasons and its coming in hand for another reason besides my 2 own (video documenting of mods from this period because why not as well as past mod version enjoyment for mods that died at 1.10 or are exclusive to 1.10 that I still prefer to play from time to time).
I considered my older setup of my .Minecraft in Vanilla first so if I had to compare to 2018 instance creations or MultiMC5 for 2018 creations over 2016/2017 I'll be using that to work things out here or otherwise start a new .Minecraft Vanilla instance just to test 2018 if I had to find out why your instance is crashing from a 2018 creation over a 2016/2017 creation of the profile.
Otherwise from my past 1.10 instance to see it work in a modded environment due to what Forge .jars I had on me more so that being 1999 and 2000 of 1.10 jars which by the looks of the crash shows you have 2000, which I jumped back and forth between 1999 and 2000 at times when making my own 1.10 instance functional now and have stuck with 1999 and no idea why I did afterward since its worked for me and more been a mods thing compared to Forge. I don't think 2000 would have issues but I'm just saying maybe could have.
I believe and I'm using the Vanilla Launcher at least for this not MultiMC5 and playing a working small modpack besides the obvious of it being a beta Forge of course with limited 1.10 mods that moved to 1.10.2 by this point or lack of 1.10 with 'compatibility of both apparently' and what comes with it at times with certain mods or the game being annoying with its beta experiences but never enough that it crashes and I can't get it 100% working much which are my assumptions here.
If you are using MultiMC5 or something I have an instance that is newer and not like my 1.10 from the Vanilla Launcher working period, but haven't 100% tested it yet but now I have a chance to and am glad I made it just encase. But I'd assume you are using Vanilla so I'll base my experiences as well as what I assume yours are on that for now unless you state your using another launcher of some kind.
Can you show a mod list please, maybe that might help since I had to sort mods out to make sure I got mine working but I did so more for other reasons besides just my small modpack being a thing I was into (Videos documenting the mods more so) but either way. I do think particular support for mods or elements from mods is needed to be determined here so a mod list will help out a lot here.
I feel that certain world gen elements from mods can be awkward sometimes and hold the game back so I usually am particular with those. Even 1.9.4 mods or those that are for 1.10.2 even over 1.10 or 1.10.1 (which obviously 1.10. is even more lacklustre unless you have a 1.10.1 forge since they don't have them on the Forge site anymore, even 1.11.1 even or 1.12.1, it makes sense why but still, I don't need 1.8.8 but can still get Forge for it so go figure).
Never encountered a problem with 1.10 not completely working to result a crash though. At least from my assumptions. And it shouldn't likely be a java version issue since 1.10 was 2016/2017 (counting vanilla and mods focuses, not the 2018 focus of other new mods for it) so its not too bad unlike 1.6.4 or 1.7.10 being outdated. Hmm.
Niche Community Content Finder, Youtuber, Modpack/Map Maker, Duck
Forum Thread Maintainer for APortingCore, Liteloader Download HUB, Asphodel Meadows, Fabric Project, Legacy Fabric/Cursed Fabric, Power API, Rift/Fabric/Forge 1.13 to 1.17.
Wikis I Maintain: https://modwiki.miraheze.org/wiki/User:SuntannedDuck2