Difference between revisions of "Launcher"
From Exilent
| Line 10: | Line 10: | ||
== Parameters == | == Parameters == | ||
* '''Max heap size''': controls the max memory used by the client. Setting it too low can cause lag/crash. | * '''Max heap size''': controls the max memory used by the client. Setting it too low can cause lag/crash. | ||
| − | ** Recommended: 1024MB | + | ** Recommended: 1024MB. |
* '''DirectDraw''': controls the hardware acceleration. | * '''DirectDraw''': controls the hardware acceleration. | ||
** Recommended: true for Nvidia/AMD video cards, false for Intel integrated video cards. | ** Recommended: true for Nvidia/AMD video cards, false for Intel integrated video cards. | ||
Revision as of 11:46, 20 August 2018
The client starts up with a separate application that is responsible to keep the client file and its dependancies updated. Besides that it also sets the JVM parameters for the client.
Log
The log of the current client session is visible here.
See also: Logging
Parameters
- Max heap size: controls the max memory used by the client. Setting it too low can cause lag/crash.
- Recommended: 1024MB.
- DirectDraw: controls the hardware acceleration.
- Recommended: true for Nvidia/AMD video cards, false for Intel integrated video cards.
- If you have performance issues try changing this.
- Prefer IPv4: uses ipv4 protocol over ipv6 which is not supported by all computers yet.
- Recommended: true.
Tools
- Open client folder: helps you locate the client files
- Reset resource files: resolves resource related problems
- Reset client settings: resolves settings related problems
