Skip to content

Deploying

tobspr edited this page Apr 23, 2016 · 3 revisions

Deploying the pipeline

There are certain things you want to do before deploying your game with the render pipeline.

Removing the debugger

If you deploy your game, you most likely don't want to display the debugger overlay provided by the pipeline. You can disable this in config/pipeline.yaml by changing the variable display_debugger to false.

Notice: When the debugger is disabled, most of the hotkeys cannot be used anymore, and you can't change time of day or plugin settings dynamically anymore. This option is really just provided for releasing your game.

Creating a minified pipeline distribution

The pipeline comes with some files which are necessary for development, but not required in a distribution. Run toolkit/rp_distributor/main.py to generate a stripped-down version of the render pipeline.

A stripped down distribution of the pipeline is only about 30 MB, in contrast to several hundred megabytes of a devlopment version.

Notice: Do not use the distributed version for development. All development tools and features are removed from the distributed build. This is really just for distributing.

Adjusting the Panda3D configuration

There is a section in config/panda3d-config.prc named Production under which you should comment all settings in, and comment out the settings in the Development section. This ensures you are getting the optimal settings for distribution.