FoundryMC / Veil

Upgrade your modding potential with cutting-edge rendering and game-engine features. Built for modders, by modders.
https://foundrymc.github.io/Veil/
GNU Lesser General Public License v3.0
325 stars 12 forks source link

Crash #27

Open Liam5095 opened 4 months ago

Liam5095 commented 4 months ago

Description When starting minecraft using runClient it starts for around 3 seconds and then crashes with the reason: Process 'command 'C:\Program Files\Eclipse Adoptium\jdk-17.0.10.7-hotspot\bin\java.exe'' finished with non-zero exit value 1

To Reproduce Steps to reproduce the behavior:

  1. Install Veil Library
  2. Start Minecraft
  3. Game crashes

Expected Behavior For the game to start

System Information Please provide the following information:

Ocelot5836 commented 4 months ago

Can you provide a log or more information?

delishoes commented 3 months ago

I think i am having the same issue as the author. I am using veil v1.0.0.275 for minecraft 1.20.1, forge 47.3.5, Windows 10. here is the log

Xyndra commented 3 months ago

@delishoes If you are using IntelliJ, please go to Project Structure -> Libraries and check for duplicates / version mismatches of any lwjgl stuff

Gaxalco commented 3 months ago

I am having the exact same issue as delishoes but when I go and check for any duplicates / version mismatches of lwjgl stuff there doesn't seem to be any. I have the same logs as delishoes*

Capture d'écran 2024-08-23 152652

Gogo64pro commented 1 month ago

Same here, I am getting the error for the linux package (I'm on windows) Entire log I was getting the same error as Liam, but after checking for duplicate or mismatched version packages and finding nothing wrong

cakeGit commented 1 month ago

Same here too :/ removing the packages doesn't do anything (reload Gradle reimports them) and I cant find a way to exclude the LWJGL libraries from the import, seems they're shaded, and looking in IntelliJ shows the packages are integrated.

My guess is its caused by this, since versions before 1.0.0.220 seem to work fine (this is what I've been doing for now), and seems about the same time as the commit: image But idk if removing this would break more things,