Playing via a remote ShadowPC (Windows 10) on a Macbook Air M1 with no other mods installed.

The game hard crashes as soon as I enter a new world with the exit code -1073741819

Turning off all Rubidium in-game settings changes nothing.
Starting Minecraft with no JVM arguments changes nothing.

debug.log
latest.log

Every single Forge port of Sodium I have tried crashes this way on my ShadowPC except for Chlorine (which is abandoned). But, surprisingly, Sodium on Fabric works perfectly lol

oh shit supporting M1 is so annoying

Just want to point out, this is an issue with the actual VM ShadowPC running Windows 10. My M1 mac is just streaming the ShadowPC so it shouldn't matter

Upon seeing yesterday's update, I installed it in hope that this issue was resolved and upon doing so I noticed the following:

Whenever I spawn on land, the game immediately hard crashes.
Whenever I spawn in an ocean biome however, I can walk around for 2-6 seconds before it hard crashes.

Also, enabling/disabling any combination of settings changes nothing. Installing Oculus also changes nothing.

I hope this helps!

I feel like somehow the port from Fabric to Forge has made this mod incompatible with VMs. Because Sodium on Fabric runs great on my ShadowPC

Is there crash-report?

The game crashes so hard there's no crash log, so all I could get are these two logs:

debug.log
latest.log

Also recorded a video for you:

Did you install the mods of Magnesium/Rubidium Extras and Magnesium/Rubidium dynamic lights using curseforge or gdlauncher or something similar?

No, what you are seeing is a fresh profile of 1.16.5 forge v36.2.35 with only Rubidium installed and nothing else.

Also, I am not using gdlauncher or curseforge or any other launcher. Just the vanilla launcher and I drag/drop the .jar file into the "mods" folder

So, the newest update hasn't fixed the issue, but I have done some research and testing on my own and get this:

Rubidium is a fork of Magnesium, right? So I tested all of the old Magnesium versions and discovered that only "sodium reforged 1.3.2" runs normally. All other versions seem to be causing this crash. Very weird

oh shit supporting M1 is so annoying

Actually not. Apple is just dropping Support for Legacy Technology.
Using Zink to Support Vulkan would increase the Framerate drastically, since we could use modern technology here without rewriting everything.
Zink+MoltenVK on macOS and only Zink on every other Plattform.