-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Start-up animation delay #773
Comments
The change was done to find a balanced solution that would satisfy the 59% who voted for Fadeless keeping and 41% for removal at #737. So instead of removing the animation entirely, I made it 4x faster than vanilla and configurable. I can still consider tweaking the value even faster or adjusting other settings of RRLS, but at this point I don't think setting it to 0 seconds is a good solution. |
The problem I have with this is that we are introducing an artificial delay, which didn't exist before. In my opinion, given that it is configurable, those who want can reactivate the splash screen animation. For most people, the loading screen isn't that spectacular and any half-second saved is a good thing. |
I encourage you to join our Discord and read the full conversation of the "Remove Fadeless" thread to get the full context on why this change was made and what other alternatives were proposed. |
Decided that the current value of 0.5s is still a good balance of "improved speed" vs "being jarring". This matches the previously ran public survey of FO users' benefits. Luckily, the value is also easy to change for those who prefer 0s, 2s or something else - |
What config to change
According to the 5.6.0 (latest update for the modpack), FO now has a previously-non-existent 0.5 seconds delay for the splash screen.
It should be changed back to zero seconds.
Why should it be changed
I see no reason to keep an artificial delay of 0.5 seconds for the splash screen.
It doesn't matter the context: the less delay it takes to load, the better.
Additional details
No response
The text was updated successfully, but these errors were encountered: