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

Crash when using MEK flamethrower #749

Open
SakuraBreeze opened this issue Jan 12, 2025 · 5 comments
Open

Crash when using MEK flamethrower #749

SakuraBreeze opened this issue Jan 12, 2025 · 5 comments

Comments

@SakuraBreeze
Copy link

Minecraft Version

Minecraft 1.20.1

Oculus Version

oculus-mc1.20.1-1.8.0.jar

Rubidium / Embeddium Version

embeddium-0.3.31+mc1.20.1.jar

Operating System

Windows 11

What is your GPU?

Nvidia GeForce GTX 1650

Java Version

Java 17

Reproduction Steps

  1. Take out a flamethrower(I did this in a new creative world)
  2. Press RMB to use it
  3. Game Crashes

Crash Report file and latest.log

https://gist.github.com/SakuraBreeze/465f51a1d23dea3ba64cd4ee99ef1cb8

Additional context

Starting the game takes more time after triggering this crash.I tried to remove oculus and embeddium,then everything returned to normal.

@pclance
Copy link

pclance commented Jan 15, 2025

im having the same issue.

@aabbccddwasd
Copy link

+1

@ShadyBo1
Copy link

Do you use any shader packs? I had an issue with the mekanism flamethrower crashing the game with shaders enabled.

@SakuraBreeze
Copy link
Author

Do you use any shader packs? I had an issue with the mekanism flamethrower crashing the game with shaders enabled.

I'm using BSL

@grotefigi
Copy link

It only crashed when using Oculus with a shader enabled. I tested it on sildurs shaders and complementary shader and it crashed on both. It doesn't crash when oculus is enabled but you aren't using any shader. If anyone find a shader that works with the flamethrower lmk

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

5 participants