-
Bug
-
Resolution: Fixed
-
2.0.806 (Windows), 2.0.995 (Windows), 2.0.996 (Mac OS), 2.0.1003 (Windows), 2.0.1004 (Mac OS), 2.1.1351 (Windows) / 2.1.1350 (Mac OS) / 2.1.1349 (Linux), 2.1.2480-2.1.2482, 2.1.2494-2.1.2496
-
None
-
None
-
Windows 8.1 x64
launcher says it's: 2.0.832
installed Java versions:
(in C:/Program Files...):
jdk1.7.0_13
jdk1.8.0_31
jdk1.8.0_40
jre1.8.0_31
jre1.8.0_40
jre1.8.0_65
jre1.7.0_60
(in C:\Program Files(x86)...):
jre1.8.0_31
jre1.8.0_65
jre1.7.0_60
(in Minecraft Install dir (D:\Program Files(x86)\Minecraft)):
jre1.8.0_25
Windows System Environment Path variable includes: (in order)
C:\ProgramData\Oracle\Java\javapath (links to jre1.8.0_65 64bit)
C:\Program Files\Java\jre7\bin (jre1.7.0_60 64bit)
so by default jre1.8.0_65 64bit is used.Windows 8.1 x64 launcher says it's: 2.0.832 installed Java versions: (in C:/Program Files...): jdk1.7.0_13 jdk1.8.0_31 jdk1.8.0_40 jre1.8.0_31 jre1.8.0_40 jre1.8.0_65 jre1.7.0_60 (in C:\Program Files(x86)...): jre1.8.0_31 jre1.8.0_65 jre1.7.0_60 (in Minecraft Install dir (D:\Program Files(x86)\Minecraft)): jre1.8.0_25 Windows System Environment Path variable includes: (in order) C:\ProgramData\Oracle\Java\javapath (links to jre1.8.0_65 64bit) C:\Program Files\Java\jre7\bin (jre1.7.0_60 64bit) so by default jre1.8.0_65 64bit is used.
-
Confirmed
After the Java Executable option is filled out, turning it off (to make it default to the bundled executable) is ineffective and the game is still launched with the custom executable.
I've found it easy to demonstrate the issue by turning on the option, setting the field to an invalid path, then turning it off and attempting to launch the game.
I think the option to turn off the custom executable should either reset the field or keep the custom path but use the bundled path thus allowing the user to re-enable the feature using the previously set custom java-executable.
- is duplicated by
-
- Resolved