Set Up a New City Scene

01The one-step version

1. Open the scene.
2. Tools → BoneCracker Games → CCDS → Create Scene Managers → Gameplay (or Main Menu).

That creates a CCDS_SceneManager, sets its levelType, and builds every manager that scene type requires. Run it again at any time — it reuses what already exists instead of duplicating it, and reactivates a manager that had been disabled.

Figure 01Open full size ↗

This is what a configured gameplay scene looks like: the CCDS managers, the mission markers nested under CCDS_MarkerManager, and the RCCP_SceneManager / RTC_SceneManager / RTC_TrafficSpawner objects that the vehicle and traffic systems need.

02What gets created

CCDS_SceneManager is the scene's root reference holder. Its levelType decides the manager set.

Gameplay scenes

Main menu scenes

Note what is not in the main menu set: no gameplay manager, no mission managers, no minimap. A main menu scene that has them was built as a gameplay scene by mistake.

03Register the scene

Add it to File → Build Profiles → Scene List. The index matters:

• CCDS_Settings.mainMenuSceneIndex (default 0) points at your main menu.
• CCDS_Settings.defaultSelectedSceneIndex (default 1) is the gameplay scene a new player starts in.
• The player's chosen scene is saved and read back by CCDS.GetScene() / CCDS.SetScene().

Adding a gameplay scene without updating those defaults gives new players a scene index that does not exist.

04Register network bindings

The same gameplay scene can run single-player without Photon PUN2 and multiplayer with the optional integration. Network authoring lives in CCDS_NetworkBinding components, so keep those components when working without the SDK.

For a scene containing bindings:

1. Save the scene and make it active, outside Play Mode and Prefab Mode.
2. Open Tools → BoneCracker Games → CCDS → Multiplayer Setup.
3. Click Register Active Scene and Assign IDs.
4. Save the scene changes when ready.

Registration records the scene in the CCDS scene ID policy, assigns IDs to placed bindings, and adds an active CCDS_NetworkSceneBootstrap if the scene has bindings and no bootstrap. The bootstrap prepares runtime views before their consumers initialize. Keep exactly one bootstrap in each scene containing authored bindings.

In registered scenes, the editor also assigns IDs after placing or duplicating bindings. It preserves existing valid unique IDs and replaces missing, duplicate or out-of-range IDs. These edits support Undo and mark the scene dirty; they do not save it automatically. Prefab assets keep sceneId = 0. Do not apply a placed instance's scene ID back to its prefab.

Under Advanced: several scenes in one room, Select Scene ID Policy opens Assets/CCDS/Editor/Networking/Data/CCDS_NetworkSceneIdSettings.asset. If multiple scenes will coexist in one room, their bindings need distinct IDs across that scene combination; the policy's matching nonempty roomSet identifies that relationship. Registration alone does not partition IDs between those scenes.

05Scene requirements

Beyond the managers, a gameplay scene needs:

Re-bake the NavMesh whenever you change the city geometry. Nothing warns you that it went stale; the AI simply stops moving.

06Layers

With CCDS_Settings.enableAutoLayerManagement enabled (the default), CCDS creates and assigns these automatically:

Put your city's drivable geometry on CCDS_Map — that is the layer the minimap and raycasting use.

Turning auto layer management off means assigning all six by hand, on every object, forever. Leave it on unless you have a specific conflict.

07Traffic

Traffic comes from RTC. Drag RTC_TrafficSpawner.prefab from the RTC package into the scene and lay out its waypoints along your roads.

Density is player-facing: CCDS.GetTrafficDensity() / CCDS.SetTrafficDensity() range 0–2 with 1 meaning 100%, and CCDS_Settings.defaultTrafficDensity sets the starting value.

Two runtime controls exist for gameplay moments:

CCDS.DisableTrafficForAWhile();        // temporary, e.g. during a race
CCDS.ToggleTrafficPermanently(false);  // until turned back on

In multiplayer, the master client owns traffic. The spawner instantiates over the network and non-master clients receive it. Do not spawn traffic locally on a client.

08Validate

Tools → BoneCracker Games → CCDS → Open Validation Panel.

It checks the scene against CCDS_SceneManager.CheckMisconfigurations() and every component implementing ICCDS_CheckEditorError, and reports specific missing references — for example "Missing 'Spawn Point' on CCDS_MainMenuManager!" or "Missing UI Text 'Money Text' on MainMenu Manager!".

Run it before every build. It catches the broken-reference class of bug that otherwise only shows up at runtime.

09Common problems

10Next

• Create a Mission
• Multiplayer
• Settings Reference