与机械动力6.0.0不兼容INcompatible with Create 6.0.0
7yudinglaopin8 opened this issue · 14 comments
以机械动力6.0.0为前置时注入失败。Crash with Create 6.0.0.
1.启动游戏
2.游戏因模组注入失败而崩溃
错误报告
crash-2025-02-01_16.49.29-client.txt
forge1.20.1
模组版本1.1.2
机械动力6.0.0
Oculus1.8.0
also there is a question, is this mod still needed after create 6.0? They updated flywheel, afterall.
also there is a question, is this mod still needed after create 6.0? They updated flywheel, afterall.
Yes, it's still needed. lof of difference with/without mod.
Jozufozu (Flywheel dev), has a mod called Vanillin which actually mentions plans for Flywheel to have a first party compat with shaders. Of course the timeframe is unknown, but its at least being worked on directly by Flywheel devs.
"Flywheel 1.0, and therefore Vanillin, is currently incompatible with shaders. Work is underway to make first party compat a reality."
Yes, it's still needed. lof of difference with/without mod.
How can you tell when the mod crashes right away?
Because you can tell the difference it makes on 5.1 with and without this mod.
Yes, it's still needed. lof of difference with/without mod.
How can you tell when the mod crashes right away?
Yes, it's still needed. lof of difference with/without mod.
How can you tell when the mod crashes right away?
He must be screwing with us, either that or you should learn about what the mod does...
There is no evidence that the performance difference achieved in 5.1 with a different flywheel version will be the same as the latest flywheel.
The mod fundamentally forces the Flywheel optimizations to be applied while using shaders. This means the best performance difference you could get is the same without shaders. Now that assumes that it works and has no visual glitches that need to be patched on top of forcing flywheel to optimize.
Is that a "lot" of improvement? It depends on many variables, such as whether the compat mod can achieve 100% of the possible improvement.
But let us validate the theory that the same performance difference can be achieved with some napkin math:
Within the repo, they have the following cases:
- 14 to 34, an improvement of +142%
- 10 to 59, an improvement of +490%
- 1 to 35, an improvement of +250%
On average, you would expect +292% improvement.
With my various testing worlds, where I have very dense machines beside each other, I can measure the difference between shaders and without:
- 15 to 63, an improvement to +320%
- 37 to 72, an improvement of +94%
- 62 to 87, an improvement of +40%
On average +151% possible improvement.
As you can see, there might be some baseline improvements right away, though it can very well be the difference between the pre-mesured state from 3 years ago and the latest versions running on a different machine.
Regardless, if we look at the range of improvements for a baseline 30 FPS running shaders without compat and the possible assumptions:
| Efficiency | 5.1 assumption | 6.0 assumption |
|---|---|---|
| 100% | 117,6 | 75,3 |
| 90% | 105,84 | 67,77 |
| 80% | 94,08 | 60,24 |
| 70% | 82,32 | 52,71 |
| 60% | 70,56 | 45,18 |
| 50% | 58,8 | 37,65 |
This shows that the difference is about 64% fewer possible improvements. While it would be nice to go from 30 to 37 or 30 to 75, we have to see if there are no glitches that prevent the usage of the simple overwrite and, if so, what the overhead will be for any extra patches.
@adaliszk Just as your comment says, it's all based on assumptions. We just would like this updated for the possible optimisation it could bring. It's really not that deep.
@adaliszk thanks for explaining, bear in mind that the minimal improvement is appreciated, one single wheel halves the performance if shaders are on (my case tho)
Indeed. I am not saying we should not need for this implemented. Any improvement is much welcomed.
What I am worried about is how the hype on the unknown might sets up the wrong expectation and leads to problems later.
The devs do not deserve the extra pressure, they are doing this in their free time and get enough hate from the create teams already.
Yes, it's still needed. lof of difference with/without mod.
How can you tell when the mod crashes right away?
After updating Create to version 6.0.2, I experienced significant FPS drops around my Create contraptions, dropping from 120 FPS to 30 FPS. This is similar to the performance issues I encountered with 5.1, when I didn't have Oculus Compact installed. Installing Flywheel Compact gave me back my 120 FPS, so it's definitely needed for 6.0 still (at least for forge, 1.20.1 not sure about Iris + Neoforge).
@PanditoPie same thing occurs when using Iris + Neoforge
@PanditoPie same thing occurs when using Iris + Neoforge
That sucks to hear :(, hope the mod author gets around to doing it when they have the time, I miss my shaders lol