Maps editing workflow

From PSwiki
Revision as of 22:04, 24 May 2022 by Talad (talk | contribs) (Created page with " === Notes === * BuiltData files are storing: ** lightmap textures (created by Build Lighting only) ** volumetric light probes / samples (created by Build Lighting only) * umap files are storing: ** navigation paths (created by Build Paths) === Map creation flow === You should never upload BuiltData file in SVN. Those will be regenerated when we create the shipping release. If you want to test locally the full game including lights then you need to: * Load all the le...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Notes

  • BuiltData files are storing:
    • lightmap textures (created by Build Lighting only)
    • volumetric light probes / samples (created by Build Lighting only)
  • umap files are storing:
    • navigation paths (created by Build Paths)

Map creation flow

You should never upload BuiltData file in SVN. Those will be regenerated when we create the shipping release.

If you want to test locally the full game including lights then you need to:

  • Load all the levels and Build Lighting only, this gives the best result on map borders, but I think you can avoid it

OR

  • Load Persistent Level + one or more maps you want relit, and Build Lighting only. In this case the single maps will be ok, but the borders between maps will not


If you want to test locally the full game including NPC movement then you need to:

Retrieved from "https://planeshift.top-ix.org//pswiki/index.php?title=Maps_editing_workflow&oldid=24434"