Repository navigation
Reference images for terrain editing
- Add PNG, JPEG or WebP maps as non-destructive tracing guides in Tile editing, including Mini and Manual terrains.
- Adjust guide opacity, visibility, scale and X/Z position while keeping terrain heights unchanged.
- Reference pixels and settings are embedded in local and portable .ptrterrain projects.
- Guides are excluded from terrain exports, screenshots, project previews and non-editing world modes.
- Fixes the Mini reference-image toolbar/render path and Vite startup.
Downloads
- Windows x64 portable application: extract the ZIP and run ProceduralTerrains.exe.
- npm:
npm install procedural-terrains@2.0.5 three@~0.185.1. - GitHub Packages:
@zyfou/procedural-terrains@2.0.5. - Blender 0.4.1 and Unity 0.4.0-alpha.2 archives are unchanged. Unity Editor 6000.3 execution was not tested.
Validation
994 frontend tests and 18 API tests pass. Application/runtime builds, TypeScript and installed-package checks pass. Native GPU checks cover reference orientation, transparency, opacity, visibility, transforms, mode isolation, portable roundtrip and terrain editing. Mini UI import and local persistence pass without JavaScript/console errors. Windows executable/interface version, startup, native save and reopen pass.
All six release assets are uploaded and SHA256 verified. Public npm latest is 2.0.5 with signed provenance. A fresh public-registry consumer installed/imported the package, built and rendered an exported project; its production dependency audit reports 0 vulnerabilities.
Forced Vite dependency optimization reaches the 2.0.5 landing page without errors. Production deployment succeeded: https://github.com/ZyFou/ProceduralTerrains/actions/runs/40490978723 . The served application bundle is 2.0.5 and matches the deployed server files; eight read-only API scenarios pass. The public browser smoke test from the Windows QA host is blocked by network/TLS resets; local production-build and native desktop checks passed.
Existing runtime limitation
The standalone runtime raw-heightmap source retains half-float precision (for example 8,850 m samples as 8,848 m), unchanged from 2.0.4.