Noah Petherbridge
93623e4e8a
Especially to further optimize memory for large levels, Levels and
Doodads can now read and write to a ZIP file format on disk with
chunks in external files within the zip.
Existing doodads and levels can still load as normal, and will be
converted into ZIP files on the next save:
* The Chunker.ChunkMap which used to hold ALL chunks in the main json/gz
file, now becomes the cache of "hot chunks" loaded from ZIP. If there is
a ZIP file, chunks not accessed recently are flushed from the ChunkMap
to save on memory.
* During save, the ChunkMap is flushed to ZIP along with any non-loaded
chunks from a previous zipfile. So legacy levels "just work" when
saving, and levels loaded FROM Zip will manage their ChunkMap hot
memory more carefully.
Memory savings observed on "Azulian Tag - Forest.level":
* Before: 1716 MB was loaded from the old level format into RAM along
with a slow load screen.
* After: only 243 MB memory was used by the game and it loaded with
a VERY FAST load screen.
Updates to the F3 Debug Overlay:
* "Chunks: 20 in 45 out 20 cached" shows the count of chunks inside the
viewport (having bitmaps and textures loaded) vs. chunks outside which
have their textures freed (but data kept), and the number of chunks
currently hot cached in the ChunkMap.
The `doodad` tool has new commands to "touch" your existing levels
and doodads, to upgrade them to the new format (or you can simply
open and re-save them in-game):
doodad edit-level --touch ./example.level
doodad edit-doodad --touch ./example.doodad
The output from that and `doodad show` should say "File format: zipfile"
in the headers section.
To do:
* File attachments should also go in as ZIP files, e.g. wallpapers
|
||
|---|---|---|
| .. | ||
| boolprops.go | ||
| cheats.go | ||
| debug.go | ||
| feature_flags.go | ||
| flag_free.go | ||
| flag_paid.go | ||
| fonts.go | ||
| numbers.go | ||
| README.md | ||
| runtime.go | ||
| shell.go | ||
| theme.go | ||
| workarounds.go | ||
balance
Constants and settings for the Doodle app.
Environment Variables
Some runtime settings can be configured in the environment. Here they are with their default values.
Most colors work with alpha channels; just provide an 8 hex character code,
like #FF00FF99 for 153 ($99) on the alpha channel.
- Application Windw Size (ints):
DOODLE_W=1024DOODLE_H=768
- Shell settings:
D_SHELL_BG=#001428C8: shell background color.D_SHELL_FG=#0099FF: shell text color.D_SHELL_PC=#FFFFFF: shell prompt color.D_SHELL_LN=8: shell history line count (how tall the shell is in lines)D_SHELL_FS=16: font size for both the shell and on-screen flashed messages.
- Debug Colors and Hitboxes (default invisible=off):
DOODLE_DEBUG_ALL=false: turn on all debug colors and hitboxes to their default colors and settings.DEBUG_CHUNK_COLOR=#FFFFFF: background color when caching a chunk to bitmap. Helps visualize where the chunks and caching are happening.DEBUG_CANVAS_BORDER: draw a border color around every uix.Canvas widget. This effectively draws the bounds of every Doodad drawn on top of a level or inside a button and the bounds of the level space itself.DEBUG_CANVAS_LABEL=false: draw a label in the corner of every Canvas with details about the Canvas.
- Tuning constants (may not be available in production builds):
D_SCROLL_SPEED=8: Canvas scroll speed when using the keyboard arrows in the Editor Mode, in pixels per tick.D_DOODAD_SIZE=100: Default size when creating a new Doodad.
Development booleans for unit tests (set to any non-empty value):
T_WALLPAPER_PNGfor pkg/wallpaper to output PNG images.