-
Notifications
You must be signed in to change notification settings - Fork 13
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
wakes-0.2.4 crash (on Vulkan mod?) #69
Comments
Wakes is listed as incompatible with Vulkan in their list. I would recommend just using Sodium |
What list are you talking about? No I will not "just use Sodium", Sodium while better than Vanilla, SUCKS! I can max out my Minecraft settings AND have X32 render distance on Vulkan mod, with no stutters. |
Also Wakes 0.2.2 didn't have this crash, but it's effect was broken |
|
Yet it is. Also why wouldn't it be a difference, Vanilla is using old libraries while Vulkan mod uses Vulkan which is much newer and more efficient.
? |
Thanks for stating the same thing I said three days ago.. in this same thread. |
Calm down mate. Probably not going to get help being rude. Just trying to help find a solution. Sodium works perfectly for me, it's very compatible and works with Wakes + shaders. You also might be able to max out your settings and render distance while staying above 100fps, like I do. Vulkan seems to be incompatible with a lot of mods - I wouldn't call it a renderer with a lot of worth in that case. Pretty much everything on fabric is compatible with Sodium because mods are made to work beside it. Here's the list of Vulkan's incompatibilities: xCollateral/VulkanMod#226 Since visuals were broken with Wakes 0.2.2, it's a given that Vulkan could not be compatible with the current version of Wakes thus causing crashes. This could be due to an update of code or features to either mod, thus rolling back to different versions may fix the issue. |
You coming here with mods I am already well aware of is not gonna help this..
Again, I am aware of my fps with Sodium vs Vulkan and Vulkan mod wins.
I've been testing mods with Vulkan since 2022 and have my own compatibility mod list, that other great people contribute to.
Of course it's due to an updated code. I would not recommend anyone to roll back to a lower version of Vulkan since the newer the version is, the better the performance and compatibility with mods is. It's a Wakes issue and I understand if Goby56 does not wanna partake in researching what causes this at this time. |
Alright well, it seems as if I can't give my free time services here. Not everything I say may be correct but I'm guessing if your attitude was less autocratic, the mod developer may even consider helping you out with your crash. Have a nice day. |
You're the ass here. I keep saying I don't need your opinions, yet you keep showing up. |
Describe the bug
Crashed on world load, Few seconds in.
Expected behavior
No crashy
To Reproduce
Try with Vulkan?
Screenshots
Hardware and OS
W10
Versions
Additional information
java.lang.NullPointerException: Cannot invoke "net.minecraft.class_5944.method_34586()" because "shaderInstance" is null
at net.minecraft.class_286.method_43433(class_286.java:1041)
at net.minecraft.class_289.method_1350(class_289.java:41)
at com.goby56.wakes.render.DynamicWakeTexture.render(DynamicWakeTexture.java:93)
at com.goby56.wakes.render.WakeTextureRenderer.afterTranslucent(WakeTextureRenderer.java:53)
at net.fabricmc.fabric.api.client.rendering.v1.WorldRenderEvents.lambda$static$22(WorldRenderEvents.java:222)
at net.minecraft.class_761.handler$cli000$fabric-rendering-v1$beforeClouds(class_761.java:6860)
at net.minecraft.class_761.method_22710(class_761.java:1283)
at net.minecraft.class_757.method_3188(class_757.java:1098)
at net.minecraft.class_757.method_3192(class_757.java:866)
at net.minecraft.class_310.method_1523(class_310.java:1327)
at net.minecraft.class_310.method_1514(class_310.java:888)
at net.minecraft.client.main.Main.main(Main.java:265)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:470)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
The text was updated successfully, but these errors were encountered: