Flywheel version goose chase
Devalut opened this issue · 21 comments
Describe the Bug
What version do I need to launch the game?
Attached shows the error message when trying a different version of fly wheel.
Each error message points to another and it's seems unplayable.
Using the latest ones for 1.1.6.5 results in this crash:
com.jozufozu.flywheel.backend.loading.ShaderLoadingException: Could not load all shaders, see log for details
Full log:
https://pastebin.com/hWe0GDdJ
Reproduction Steps
1.Fresh install of above and beyond pack 1.3 for 1.1.6.5
Expected Result
I honestly don't know anymore.
Screenshots and Videos
Crash Report or Log
No response
Operating System
Windows 7
Mod Version
0.3.2g
Minecraft Version
1.16.5
Forge Version
36.2.33
Other Mods
No response
Additional Context
No response
Additionally I've isolated the two mods on a fresh install and still get the same results.
From your screenshots:
You messed around with the settings and files:
Your forge version: 36.2.33
Default is: 36.2.20
Default create is: create-mc1.16.5_v0.3.2g.jar (requires flywheel in the range 1.16-0.2.3 and above and below 1.16-0.3
Default flywheel: flywheel-1.16-0.2.5.jar
Which also satisfies the requirement for supplementaries of 1.16-0.2.3 and above
Your files are named:
flywheel-1.16-0.2.5 (2).jar
create-mc1.16.5_v0.3.2g (5).jar
So you definitely messed around with them, instead of just installing the pack.
The Error in the initial log says:
Could not load all shaders, see log for details.
Not 100% sure, but that could mean the flywheel mod file got damaged, as the shaders should be contained within.
md5 sums as on my system:
84ec13d5bccfa71a09783ecb6e089b20 *create-mc1.16.5_v0.3.2g.jar
0964200fddbd4ff67dfab63c5aae161a *flywheel-1.16-0.2.5.jar
1.16 is not being updated any more
An acute observation that is greatly appreciated, however I'm not after a 1.16 update I'm after the cause of a bug so I can use the mod.
If you know anyone who can look at the logs and find the cause of this issue (As I can't even start the mod.) I'd be very grateful.
EDIT: Furthermore I'm certain it's on my end because of how rare this bug seems to be, but being a layman to the error logs my only recourse is singing for my supper on here.
Thanks again for responding I didn't think anyone would be after the 7th day.
Sorry, didn't fully read your report, just glanced at the version. Looking at it further, you should be here instead https://github.com/simibubi/Above-and-Beyond
Sorry, didn't fully read your report, just glanced at the version. Looking at it further, you should be here instead https://github.com/simibubi/Above-and-Beyond
My bad I should've mentioned that I've narrowed it down to flywheel and create only, so CA&B is not the issue.
EDIT: Here's the log using Only the latest for 1.16 (Flywheel & create) and nothing else:
https://pastebin.com/7d3BUwkJ
Have you tried different Create / Forge versions?
Yes, but the error from flywheel still remains.
Can you refer someone who can check the log, because i'm certain it should be something on my end.
You messed around with the settings and files:
Yes, it gave me the same error and I originally had the issue with the fresh install modpack so I've reinstalled seperate version to rule out the modpack; but now it's been made clear that flywheel & create are the offending mods.
Your forge version: 36.2.33
I tried both, 36.2.33 & 36.2.20 with Latest java and 1.8.0_311 with the latter
Default create is: create-mc1.16.5_v0.3.2g.jar (requires flywheel in the range 1.16-0.2.3 and above and below 1.16-0.3
See attached images.
So you definitely messed around with them, instead of just installing the pack.
You are mistaken and I apologize for leading you to such a conclusion.
Thanks for responding!
See attached images.
They are worth nothing.
Posting 8 images that just show one line of a log is not helping at all and will not allow anyone to figure out what is wrong...
None of the images shows the versions of all mods mentioned in them and you said it yourself, these were different things you tried.
With the original files you had an error. Okay.
But you made it into: "I have to try many versions of create and flywheel and none of them work", beside the error obviously not being the versions (as those work for a few thousand players). Maybe it was a corrupted file or it is windows 7, your java version or a combination, but surely not a version mismatch. That was introduced by your tries to fix the original error.
They are worth nothing. Posting 8 images that just show one line of a log is not helping at all and will not allow anyone to figure out what is wrong...
None of the images shows the versions of all mods mentioned in them and you said it yourself, these were different things you tried.
My deepest and heartfelt apologies for the egregious crime against humanity and life itself.
I assumed it would cut down on "Did you try X version of flywheel?".
With the original files you had an error. Okay.
But you made it into: "I have to try many versions of create and flywheel and none of them work",
It should go unsaid that I would keep trying different methods until it worked, was taking the "I have to try many versions of create and flywheel and none of them work" route as you say wrong of me?
beside the error obviously not being the versions (as those work for a few thousand players). Maybe it was a corrupted file or it is windows 7, your java version or a combination, but surely not a version mismatch. That was introduced by your tries to fix the original error.
Give me some parameters to work by.
It should go unsaid that I would keep trying different methods until it worked, was taking the "I have to try many versions of create and flywheel and none of them work" route as you say wrong of me?
No, but turning it into the title and main problem of this issue.
This issue is not titled "Create A+B 1.3 not starting for unknown reasons", but "Flywheel version goose chase"
Create A+B is a complex mod-pack here, with lot of interweaving dependencies. In such cases just replacing one file will cause more problems than it solves.
Now, to get this closer to being resolved:
- Clean install of Create A+B, no edits, no replacements.
- Start it and upload the crash-report and the normal log file.
Now, to get this closer to being resolved:
- Clean install of Create A+B, no edits, no replacements.
- Start it and upload the crash-report and the normal log file.
From what I can see no crash log appeared, but here's the Normal log & Crash log (Thanks to SurprisedPikaa)
crash reports should be located in \Create- Above and Beyond\minecraft\crash-reports , just making sure you checked there?
crash reports should be located in \Create- Above and Beyond\minecraft\crash-reports , just making sure you checked there?
Excellent, thanks again!
https://pastebin.com/vhWxnVyV
It seems the shaders can not be compiled as indicated by these lines:
[08:14:50] [Render thread/ERROR] [co.jo.fl.ba.Backend/]: Shader compilation log for chiselsandbits:model.vert: Vertex shader failed to compile with the following errors:
[08:14:50] [Render thread/ERROR] [co.jo.fl.ba.Backend/]: Shader compilation log for create:rotating.vert: Vertex shader failed to compile with the following errors:
But there is no error number or detail following that, just the shader source.
Following that it crashes as Flyheel tries to load the shader...
Maybe the debug log has details, but I have no experience with shaders.
Pastebin can't handle the size:
debug.log
tobi-blackscale & SurprisedPikaa, Appreciate your help and effort into this matter.
Sadly that does not tell me anything more... Just that 2 shaders (chiselsandbits:model.vert and create:rotating.vert) are not compiling
I have no idea what part of the system is responsible for shader compiling, but I could imagine some reasons
If shader compiler is written in java, the java version would have an influence on it.
If the compiler is "borrowed" from directX or openGl, because it compiles for the graphics card in use, updating DirectX or the graphic card drivers could help....
But again, I have no idea how that stuff works in detail.