FAQ - Revision history

Spork at 02:36, 18 March 2018

2018-03-18T02:36:48Z

Spork at 02:36, 18 March 2018

2018-03-18T02:36:18Z

Spork: /* Scaling Problem with 4K screens */

2018-03-18T02:35:41Z

Scaling Problem with 4K screens

Spork at 02:29, 18 March 2018

2018-03-18T02:29:04Z

Spork: Created page with " === Frequently Asked Questions about MekWars === == Java 9 == Java 9 moved some of the functionality of XML out of the J2SE module and into the J2EE module, which is not load..."

2018-03-17T16:45:47Z

Created page with " === Frequently Asked Questions about MekWars === == Java 9 == Java 9 moved some of the functionality of XML out of the J2SE module and into the J2EE module, which is not load..."

New page

=== Frequently Asked Questions about MekWars ===
== Java 9 ==
Java 9 moved some of the functionality of XML out of the J2SE module and into the J2EE module, which is not loaded by default in the JRE. This results in the client erroring out with the following message in megameklog.txt:

:ClassNotFoundException: javax.xml.bind.JAXBException

You can fix this by adding the following to your java command:

:--add-modules java.se.ee

← Older revision		Revision as of 02:36, 18 March 2018
Line 1:		Line 1:
−
−	~~= Frequently Asked Questions about MekWars =~~
	== Java 9 ==		== Java 9 ==
	Java 9 moved some of the functionality of XML out of the J2SE module and into the J2EE module, which is not loaded by default in the JRE. This results in the client erroring out with the following message in megameklog.txt:		Java 9 moved some of the functionality of XML out of the J2SE module and into the J2EE module, which is not loaded by default in the JRE. This results in the client erroring out with the following message in megameklog.txt:

@@ Line 1: / Line 1: @@
-=== Frequently Asked Questions about MekWars ===
+= Frequently Asked Questions about MekWars =
 == Java 9 ==
 Java 9 moved some of the functionality of XML out of the J2SE module and into the J2EE module, which is not loaded by default in the JRE.  This results in the client erroring out with the following message in megameklog.txt:
@@ Line 14: / Line 14: @@
 Swing declares itself as self-scaling, but that is not actually the case, so when you view the MekWars client on a 4K screen, you see something similar to the image attached. There are a couple possible fixes:
-= Update to Java 9 =
+=== Update to Java 9 ===
 But see the above FAQ entry re: Java 9 and the J2EE modules
-= Set the High DPI Scaling option =
+=== Set the High DPI Scaling option ===
 # Find java.exe you installed.

@@ Line 10: / Line 10: @@
 :--add-modules java.se.ee
-== Scaling Problem with 4K screens ==
+== Scaling Problem with 4K screens in Java 8 ==
-Swing declares itself as self-scaling, but that is not actually the case, so when you view the MekWars client on a 4K screen, you see something similar to this:
+[[File:4kScalingProblem.png|thumb]]
-[[File:4kScalingProblem.png]]
+Swing declares itself as self-scaling, but that is not actually the case, so when you view the MekWars client on a 4K screen, you see something similar to the image attached. There are a couple possible fixes:

← Older revision		Revision as of 02:29, 18 March 2018
Line 9:		Line 9:

	:--add-modules java.se.ee		:--add-modules java.se.ee
		+
		+	== Scaling Problem with 4K screens ==
		+	Swing declares itself as self-scaling, but that is not actually the case, so when you view the MekWars client on a 4K screen, you see something similar to this:
		+	[[File:4kScalingProblem.png]]