Chroma Logs

This log extends the BSMG Environment Log Page with more/updated information. Also if you havent yet, please read the Chroma ID section from the Environments Page to learn about Chroma ID's.

Settings

Because fetching Chroma logs (Environment Enhancement logging) is classified as "Debugging", there are some settings that we need to change in order for Chroma and BSIPA to recognize we have those intentions. These settings are located in configuration files in your BeatSaber/UserData folder. You will want to open Chroma.json and Beat Saber IPA.json, then make the following changes. (Remember to revert these settings )

Chroma.json

Set PrintEnvironmentEnhancementDebug to true | So Chroma knows to dump the environment enhancement activity.

Beat Saber IPA.json : Debug

Set HideMessagesForPerformance to false | So BSIPA doesnt hide logs when a mod logs over the HideLogThreshold (Chroma will log alot, especially on Group lighting envs) Set CreateModLogs to true | So BSIPA creates a log specifically for chroma, instead of having every log to just one file.

Fetching logs

Now we fetch our environment logs! But first we must make sure we have a simple map that minimally uses chroma so it logs the environment. To do this, create a new map, and in Chromapper hit the environment removal button. Create a new entry and type in BigSmokePS (Targets the smoke particle system). Then save.

Next, run the map in BeatSaber. Preferably exit after a couple seconds when the environment loads.

Now its time to find the log! Go back to your BeatSaber installation directory and go to Logs/Chroma/EnvironmentEnhancementManager directory. The latest.log file is what you're looking for. If everything works properly, you should see your environments objects. Preferably, I would clear or delete the latest.log each time if you are doing more than one environment, unless you restart the game each time.

Cleaning up logs

If you want to drop the logs into Regex101 or release publicly, you probably dont want the [DEBUG XX:XX:XX] before every object. So its recommended to remove that. You will also want to remove the BigSmokePS removal log that chroma spits out all the way at the bottom of the log.

Tooling

For those who would like early access to a log fetcher tool ive been developing, just DM me for it! It was used to gather all 191 Chroma Log files in this repo! It took only about an hour to do this and upload them. If you are looking to just fetch one log, from loading up beatsaber to having a fully processed log file, it should take less than one minute. ( It will be released on this repo when I deem it ready )

Features:

• Automatically set proper settings for log fetching (Reverts when you close the app)
• Creates a map in CustomWIPLevels for you to use for logs (Deletes when you close the app)
• Captures a log, processes it, and spits it out into a user-defined output folder in one click
• Customizable file naming (Environment Name, BS Version, Timestamp)