Summary

The original exporter was based on some posts by @123321 in the Discord #world-editing channel back in May, so all credit to him for working it out in the first place.

Theres a video which outlines this process Here.

Versions and requirements

This guide was initially written with game version 1.6 of Cyberpunk 2077.

• Wolvenkit >= 8.8.1 or the latest Nightly

• Blender 3.3 or newer

• Cyberpunk add-on for Blender 1.2.0

Exporting Streaming Sectors to Blender

To export a location, you need to know its files — you can either pick them from our list or go and find them (and add them to the list, please).

3. Open Export_Sector.wscript by double-clicking on the file name

   • You may get a pop-up: "Trying to open a system file. Should a local copy be created?" If so, click Yes.

4. Optional: Check What else the script can do for you below if you want to get fancy.

5. Click "Run" (it's on the top left of the script editor)

This will export all your .streamingsector files to glb/json for the later import into Blender.

// You can add sectors to the list, or add them to the project 
// list of sector files (paths need double slashes) you can leave empty if in project
// can use just filenames if their in the _compiled\default folder
const sectors=[
    "interior_-48-31_2_0",
    "interior_-24-16_1_1",
]

Importing to Blender

1. Import your streamingsector with the Cyberpunk Blender IO Suite. For full instructions, check the corresponding wiki page - the documentation below might be outdated.

   1. Open Blender

   2. Optional: Turn on the Blender console so you can watch the pot boil (unnecessary, but psychologically reassuring). It's under Window -> Toggle System Console

   3. Select File -> Import -> Cyberpunk Streaming Sector

   4. Open the .cdmodproj file in the root of your Wolvenkit project directory

   5. Optional: Check the "With Materials" box in the side panel This will make the process take four times longer!

   6. Wait (see the orange warning box below)

2. Optional: As the meshes will be scaled and positioned according to the map coordinates, they're probably off-screen. You can center the camera by completing the following steps:

   1. One or more meshes should still be selected. If not, do that now.

   2. Move the cursor to your selection (Hotkey: SHIFT+S)

   3. Select View → Align View → Center View to Cursor

Importing back into Cyberpunk

Summary

Created by Misoru

This guide will teach you how to turn a world object into a lootable container.

Requirements

• Latest version of Wolvenkit

• Working .streamingsector with the object you want to make lootable (if you haven't done this yet, follow this guide)

Step 1: Create your loot table

Before making your object lootable, we first need to create the lootTable that we'll later reference in our .streamingsector, and add it to our Tweak .yaml. Below is an example:

LootTables.Loot_misoru_ronin_case: # Loot table identifier
  $type: gamedataLootTable_Record
  lootGenerationType: dropChance
  lootItems:
  - $type: gamedataLootItem_Record # Append a separate entry for each item you want added to your container
    dropChance: 1 # Value from 0 to 1 determining % drop chance
    dropCountMax: 1 # Max quantiy of this item
    dropCountMin: 1 # Min quantity of this item
    itemID: Items.Preset_Satara_Ronin # The item added to your loot table
  maxItemsToLoot: 1 # If more than 1 lootItems, change this number accordingly
  minItemsToLoot: 1 # ditto

Step 2: Verify your object's components

Open the .ent for the object you want to make lootable and verify its components include entries like gameInventory, gameinteractionsComponent, and GameplayRoleComponent. These components are all commonly included in .ent files for base game containers and may be a requirement.

Step 3: Identify your object in your .streamingsector

Open the .streamingsector containing your object and find its nodes entry.

Under instanceData, create handles for LootContainerObjectAnimatedByTransform, then add the lootTable we created in Step 1 and define the persistentState to LootContainerObjectAnimatedByTransformPS. Leave everything else default.

You're done!

Your object should now be a lootable container. Load up your mod and test it out. If it's not working, verify you defined your lootTable correctly (or use a base game lootTable for testing) and edited the correct .streamingsector nodes.

Summary

This guide shows you how to enable an object's embedded collision for entities without (items that you can walk through).

It's a direct follow-up to Adding Objects to the World.

Wait, this is not what I want!

• If you want to create AMM: Custom Props for AMM, check the corresponding guide. Note that this mechanism applies for them as well!

Requirements

• Wolvenkit 8.12.0+

• You know how to Archived: Merging World Additions via ArchiveXL

• allmeshes.archive and updated allpaths file created by KeanuWheeze - this will help us to edit new ent files with embedded collisions.

Find an eligible object

Not every object contains an embedded collision, so we first need to check if your desired mesh has one.

• Once in-game, search for the item you want to spawn; I'll be using base\meshes\base_environment_decoration_furniture_industrial_industrial_table_industrial_table_g.ent

• In the Spawned menu, click on Copy Path to clipboard to get the current .ent path.

• Open the .ent file and look for the mesh component in its components array.

  • If the selected entity is from allmeshes (starts with base\meshes\ ), then there is probably only 1 entPhysicalMeshComponent called custom_mesh

  • If not, it means your entity is from the vanilla game; in this case, search for the component that has Mesh in its type (entPhysicalMeshComponent, entMeshComponent, etc...)

• In the mesh, click on the blue arrow to open the mesh in a new tab (we don't need to add the file)

• Decisive moment: Open parameters and look for a meshMeshParamPhysics

Activate mesh collisions

Turning it on is pretty simple; we only have 2 things to change, all in the .ent file previously added:

• Update the filterData and change the values like in the screenshot. Those values determine which entities can collide with, and how to simulate the collision.

• Change the navigationImpact setting to Blocking. (Other values exist; they haven't been documented, but you may have fun with them.)

• Optional: depending on the item, you may want to enable (or not) lighting-based shadows. You can do so by setting these 3 properties to Always.

In our test case, I renamed the file as mod\embedded_collision_test\decoration\industrial_table_g.ent.

• If the path of your ent changed, don't forget to add it to the allPaths.txt file used by Object Spawner.