Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
PCs with Nvidia+Intel cards use the Intel one with Fabric, but Nvidia with vanilla, resulting in a perceived massive framerate drop caused by Fabric
See original GitHub issueNot sure if that can even be solved by Fabric alone, but it should at least be made known/public.
When Vanilla MC starts the game, it passes net.minecraft.client.main.Main as the main class name to java.exe.
When Fabric starts the game, it passes net.fabricmc.loader.launch.knot.KnotClient.
Unfortunately, the Nvidia control panel has a long list of games that should use the external GPU instead of the internal one. This list includes net.minecraft.client.main.main:
Which means, after installing Fabric, Nvidia won’t recognize the fabric-started java.exe as one of the programs that should use the Nvidia card, falling back to the Intel one, resulting in a big frame rate drop.
More info in today’s Discord discussion here: https://discordapp.com/channels/507304429255393322/507982463449169932/732948809650274415
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:24 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I don’t know as I’m not NVidia, but adding
-DFabricMakeNVidiaHappy:net.minecraft.client.main.Mainor-DFabricMakeNVidiaHappy=net.minecraft.client.main.Main(first has a : and second a = ) doesn’t help.-DFabricMakeNVidiaHappy=" net.minecraft.client.main.Main "does, however. Note the blanks between the "s and the “class name”.Ok that’s good to hear, and sounds like something I can test with. I will look into adding this.