Difference between revisions of "Launcher"
From Exilent
| Line 16: | Line 16: | ||
** 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. | ||
** If you have performance issues try changing this. | ** If you have performance issues try changing this. | ||
| − | |||
| − | |||
== Tools == | == Tools == | ||
| − | * '''Open client folder''': helps you locate the | + | * '''Open client folder''': helps you locate where the files of Exilent are stored |
| − | + | * '''Reset client settings''': sets all Exilent settings to default | |
| − | * '''Reset client settings''': | ||
Revision as of 08:32, 29 September 2018
Exilent starts up with a separate application called the launcher.
The launcher is responsible for keeping the client file and its dependencies updated and setting the JVM parameters.
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.
Tools
- Open client folder: helps you locate where the files of Exilent are stored
- Reset client settings: sets all Exilent settings to default
