Changes between Initial Version and Version 1 of AdvancedSettings


Ignore:
Timestamp:
04/12/18 17:23:09 (6 years ago)
Author:
admin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AdvancedSettings

    v1 v1  
     1= Advanced Settings =
     2
     3You can set a few advanced settings by editing the `worldpainter.vmoptions` or `vmoptions.txt` file. This page describes what they are.
     4
     5'''Note that these are completely unsupported! ''' If you use them and they cause problems, don't ask about it here or on the official forum thread!
     6
     7Check the MoreMemory page for details on how to edit the `worldpainter.vmoptions` or `vmoptions.txt` file. It contains one setting per line. Check whether the setting is already there before adding a new line and if so, edit the existing line.
     8
     9'''Option:''' -Dorg.pepsoft.worldpainter.threads=''threads''
     10
     11Where ''threads'' is an integer number describing the number of parallel threads to use when exporting or merging a world. This will override the default, which is based on the number of CPU cores and the amount of memory available. Note that if you set this too high !WorldPainter may run out of memory when trying to export or merge a world. You could experiment with setting this ''lower'' than the default if you have many CPU cores, which may actually improve performance in some circumstances.
     12
     13Note that you can see how many threads !WorldPainter is using to export or merge the world (along with the number of cores and available memory) in the log file (`logfile0.txt` in the !WorldPainter configuration directory, see below).
     14
     15'''Option:''' -Dorg.pepsoft.worldpainter.debugLogging=true
     16
     17This will enable logging debug information to the log file (`logfile0.txt` in the !WorldPainter configuration directory, which is `%APPDATA%\WorldPainter` on Windows, `~/Library/Application Support/WorldPainter` on Mac OS X or `~/.worldpainter` on Linux/UNIX). Note that the amount of logging is so great that it may actually affect the performance of the application!
     18
     19If you replace `true` with `extra`, trace logging will be enabled, which will dump exponentially more debug information in the log file. This will cause even more performance degradation and disk usage, so use it sporadically and don't forget to turn it off again!
     20
     21'''Option:''' -Dorg.pepsoft.worldpainter.disableTabletSupport=true
     22
     23This will disable tablet support and enable legacy mouse support. Use this if the default tablet support is not working or causing problems, for instance when running !WorldPainter inside an emulator.
     24
     25'''Option:''' -Dorg.pepsoft.worldpainter.noSnowOn=''blockId''[,''blockId'' ...]
     26
     27The value should be a comma-delimited list of numeric block IDs (no data values can be specified), which will be added to the list of blocks on which the Frost layer will not deposit snow.
     28
     29'''Option:''' -Dorg.pepsoft.worldpainter.enforceBlockRules=false
     30
     31This will cause !WorldPainter ''not'' to post process the exported map to enforce Minecraft rules about where blocks may be placed. '''Warning:''' it is very easy to cause Minecraft to hang by having large amounts of blocks in the map which are illegally placed and which Minecraft will try to remove, causing a chain reaction of block updates! If you use this setting it is your own responsibility to make sure no blocks are placed where Minecraft would not allow them!
     32
     33'''Option:''' -Dorg.pepsoft.worldpainter.supportSand=false
     34
     35This will cause !WorldPainter ''not'' to turn unsupported or floating sand blocks into sandstone. Only applies when block rules are enforced (see above).