Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.37 mod doesn't work #60

Open
madding1602 opened this issue Jun 29, 2024 · 3 comments
Open

1.37 mod doesn't work #60

madding1602 opened this issue Jun 29, 2024 · 3 comments

Comments

@madding1602
Copy link

Hello everyone. I've recently installed the 2.9.2 version for 1.37. However, the mod doesn't seem to work. It recognizes the mod as loaded, but the menu on mod settings is completely blank, and when I enter solo to get a song, I don't get the mods tab to change settings for chroma, and when trying to play chroma compatible songs, they don't change. Is there any way to solve the problem? TIA

@madding1602
Copy link
Author

UPDATE: After checking the files on the headset with my PC, I found the JSON which stores all values for ingame settings. Settting all of them to true applies Chroma effect on songs. The mod loads and works on the game, but the part related to menu is the one that's not working

@Yingste
Copy link

Yingste commented Jul 20, 2024

For anyone else that was also having trouble at least for me it is the Chroma.json file under /ModData/com.beatgames.beatsaber/configs/Chroma.json
changing all of the false tags to true enabled chroma for me.

Running 1.37 on Quest3 with mods loaded from MBF

@eMelgooG
Copy link

I had the same problem. After I updated the software of the quest, the songs started recognizing the mod

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants