#Spectrum's Deeper Down dimension causing crash after a few seconds
94 messages · Page 1 of 1 (latest)
Hmm.
Mind trying a little science?
If not, take out notenoughcrashes and try again.
tried without it
i tried reinstalling the modpack and trying again but it crashed and didn't give any crash reports
The Crash Assitant window didn't even come up?
It gathers more than crash reports for diagnostic info to share.
No worries; thank you for doing this!
-# and after that, try without lambdynamiclights
without looking, i'd guess client side
alright
would make sense
Craftoria crashed without a crash report. The logs have been uploaded to gnomebot.dev:
latest.log head / tail (~28k lines) | debug.log head / tail (~12MB & ~72k lines) | PrismLauncher-0.log | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt
Mod list changes on top of the modpack:
Added mods:
[2;32memiffect-neoforge-2.1.5+mc1.21.1.jar[0m
[2;32myukamibackpacktab-1.21.1-1.1.1-neoforge.jar[0m
Removed mods:
[2;31mdarkmodeeverywhere-1.21-1.3.5.jar[0m
Updated mods:
[2;34mathena[0m ([2;31m4.0.6[0m > [2;32m4.0.2[0m)
[2;34mcomputercraft[0m ([2;31m1.119.0[0m > [2;32m1.117.1[0m)
that's what it gave
this run with or with out lambdynlights?
with
i'll start it again without
though this time it made my whole pc freeze for a moment :/
both iris and lamb ?
yes
if that stops the crash, then we can put just one back and see.
What else depends on Iris?
(besides not having shaders on... but the shaders are not mods)
monocle and these 3
yes then, that/those too.
alright, launching it rn
can't play with shaders anyway
so its not a big loss
btw, an issue for this opened just yesterday (though that may have also been a craftoria player; i didn't read the mods in their posted log yet)
https://github.com/DaFuqs/Spectrum/issues/887
oh
Still, wondering if it happens with Iris yoinked.
-# not a Craftoria player, they are on Fabric.
the same error message keeps appearing in the logs
and it crashed again
Craftoria crashed without a crash report. The logs have been uploaded to gnomebot.dev:
latest.log head / tail (~94MB & ~431k lines) | debug.log head / tail (~102MB & ~472k lines) | PrismLauncher-0.log | KubeJS: client.log / startup.log | crash_assistant_app.log | modlist.txt
Mod list changes on top of the modpack:
Added mods:
[2;32memiffect-neoforge-2.1.5+mc1.21.1.jar[0m
[2;32myukamibackpacktab-1.21.1-1.1.1-neoforge.jar[0m
Removed mods:
[2;31mcolorwheel-neoforge-1.2.7+mc1.21.1.jar[0m
[2;31mdarkmodeeverywhere-1.21-1.3.5.jar[0m
[2;31miris-neoforge-1.8.12+mc1.21.1.jar[0m
[2;31miris_shader_folder-1.3.2-neoforge.jar[0m
[2;31mlambdynamiclights-4.8.8+1.21.1.jar[0m
[2;31mmonocle-0.2.3.ms.jar[0m
Updated mods:
[2;34mathena[0m ([2;31m4.0.6[0m > [2;32m4.0.2[0m)
[2;34mcomputercraft[0m ([2;31m1.119.0[0m > [2;32m1.117.1[0m)
i think that the logs before the crash are the same
Thanks for doing this; I added your second log to that github issue, noting that Iris had been removed.
alright, its more a thank you for adding it to their github :v (i didn't think about that)
and for trying to help me
I'll get notified by github of activity on that issue, now that I've participated in it.
Will update you when issue gets fixed, or a work-around is found.
thanks
Hopefully it gets resolved but for now, no progression in Spectrum for us
In the file config/spectrum-startup.toml, try changing this line:
#Post process shaders
post_process_shaders = false
From 'true' (it's default) to 'false', as shown
Worked on my test instance.
So it didn’t crash after a few seconds?
it did not
couldn't see jack, but then it's the DD and I hadn't done any Spectrum progression... had just gone there by command.
so i guess it's supposed to be like that, if you don't have the right progression in the mod before hand?
So for this, if you’re running a server, this needs to be enabled to true, right?
Or it has to be client side
Idk; I would guess this only affects client side... it's about shaders.
Also, the server didn't crash when liamcee was testing, just his client.
I'll try it when I can
wait, mine was set to true
nevermind, i think that i somehow broke the instance, gotta reinstall it
Lol, I typed it up backwards.
Yes, have it "false" should avoid the crash.
Edited the comment now.
ah
i still reinstalled it
it said that i had the pack version 1.30 for some reasons
I think that this fixed it
i am not lagging anymore
Thank you ! :D
gotta check
i'm waiting for emi to load rn
but i think that everything works as expected (I never played with spectrum before so idk)
May I ask if you're able to explore the place now? With it disabled now
Ok, but you're on Singleplayer, right?
Ohhh, ok, now I feel safe with that thought, thank you
np
The hardware in question did not support opengl shaders with version 440.
I downgraded the shader files for the next build.
I assume a very dated /integrated graphics card?
https://en.wikipedia.org/wiki/OpenGL_Shading_Language
released 2014
OpenGL Shading Language (GLSL) is a high-level shading language with a syntax based on the C programming language. It was created by the OpenGL ARB (OpenGL Architecture Review Board) to give developers more direct control of the graphics pipeline without having to use ARB assembly language or hardware-specific languages.