How to skip the loading screen (downloading configuration updates...) when change to Game Mode or Boot.
How to skip the "Downloading Configuration Updates" Screen, it's always appear when enter Game Mode or boot into system. Like give user a config menu item to skip, and request updates manual?
What is the issue with the screen? Usually it is just checking if an update exists which only takes a few seconds.
Without it, we cannot apply changes to Steam configuration. It allows us to dynamically set game configurations to enable games to work without making new OS releases.
Having manual updates wouldn't make much sense.
Sometimes, I just wanna fast boot my machine, and play game inmediately, don't care about system update. Emmm, like Windows system update, not always notify me to updates at it boot. Not a big problem, but if user can decide it will be better.
And when offline, the update screen also appear, I think when no network, maybe cannot downloading update?could allow user use any button skip it, and update next time.
Agree with Op sometimes it feels like it take too long. I would also rather omit this screen, can we maybe download said configurations in background?
Steam does not allow us to modify its configuration while it is running. So downloading in the background means we would have to apply fixes on the next boot. This could cause confusion and unnecessary support requests.
What config/files exactly is this screen loading? It can take like 15~20sec in my machine some times. Does it make sense to be this slow? Can we speed it up somehow?
What config/files exactly is this screen loading? It can take like 15~20sec in my machine some times. Does it make sense to be this slow? Can we speed it up somehow?
yes, 15-20s, at least 3s-5s.
Steam does not allow us to modify its configuration while it is running. So downloading in the background means we would have to apply fixes on the next boot. This could cause confusion and unnecessary support requests.
Force downloading things when my machine use my phone hotspot, not sounds good. I dont want to update my system every time I open it, I can accept update next time. If I face the emergency situation, I want update it manual.
It is checking for updates on the chimera-data repo (https://github.com/chimeraOS/chimera-data) and downloading a zip of the repo contents if it has changed. This file is about 130 KB.
If it is taking 15-20 seconds, then it is waiting for the network to come up, which Steam would have to do anyway.
These are not system updates. It is just small configuration updates so we can deliver an optimized experience for users even without doing a new release of the OS, for example, when a new game is released that needs some specific configuration to work, or to add a new release of GE Proton.
The chimera-data repo/files are not modified that often.
Maybe reducing the frequency it runs then like only once per week, but put some mechanism is place to force the update manually
We are discussing potentially hooking this up to Steam's update system where OS and Steam client updates currently happen. My only concern is it could be confusing as people will see update notifications, apply the update, restart, and see no version changes.
We are discussing potentially hooking this up to Steam's update system where OS and Steam client updates currently happen. My only concern is it could be confusing as people will see update notifications, apply the update, restart, and see no version changes.
at least, skip when machine offline? Only update when online.
We are discussing potentially hooking this up to Steam's update system where OS and Steam client updates currently happen. My only concern is it could be confusing as people will see update notifications, apply the update, restart, and see no version changes.
at least, skip when machine offline? Only update when online.
It is skipped when offline. Most of that screen is just waiting to for the WiFi adapter to initialize. This needs to happen whether or not you are online because it's the only way to know if the machine has an active Internet connection or not.
Simply put the splash screen is there to stop questions related to longer than expected "black screens" while waiting for steam to start up. On the Steam Deck you see the Steam Logo while Valve does the same stuff in the background.
The configuration updates that are pushed are extremely small in size and is not pushed every reboot. I suppose the current splash screen wording used is a bit misleading. It's waiting for the network to initialize and starting up steam. It simply checks to see if any updates are available.
These configuration updates are for games that would otherwise be broken due to games expecting Steam Deck hardware. Simply turning this off would mean users would need to add launch parameters for many games by themselves and we'd get tons of help requests asking why a game works on Steam Deck and not ChimeraOS.
I'm not sure forcing a "check for update" input that would also trigger Steam client/OS upgrades is a better solution because if I just want to play my game now that would slow that process down because now I'm waiting for much more than just a few kilobytes of configuration updates.
After years of using ChimeraOS, I've been noticing this stage of the startup taking a REALLY long time. In the past it only took a few seconds, but now I'm finding myself waiting up to 10 minutes, if not longer.
I'm not sure what changed and if it's software or my internet or some sort of weird cdn routing, but it's odd and pretty frustrating when just switching back and forth between desktop and game mode.
If there's any particular logs I can get pointed to that might provide insight on this, I'd take a look.
After years of using ChimeraOS, I've been noticing this stage of the startup taking a REALLY long time. In the past it only took a few seconds, but now I'm finding myself waiting up to 10 minutes, if not longer.
I'm not sure what changed and if it's software or my internet or some sort of weird cdn routing, but it's odd and pretty frustrating when just switching back and forth between desktop and game mode.
If there's any particular logs I can get pointed to that might provide insight on this, I'd take a look.
Can you try disabling chimera temporarily and see if it boots faster again?
systemctl --user stop chimera
After years of using ChimeraOS, I've been noticing this stage of the startup taking a REALLY long time. In the past it only took a few seconds, but now I'm finding myself waiting up to 10 minutes, if not longer.
I'm not sure what changed and if it's software or my internet or some sort of weird cdn routing, but it's odd and pretty frustrating when just switching back and forth between desktop and game mode.
If there's any particular logs I can get pointed to that might provide insight on this, I'd take a look.
Can you try to upgrade to ChimeraOS 46 (unstable)? We have reworked the splash screen so that it displays more details of what is happening. It should hopefully reveal what is taking so long in your case.
After years of using ChimeraOS, I've been noticing this stage of the startup taking a REALLY long time. In the past it only took a few seconds, but now I'm finding myself waiting up to 10 minutes, if not longer. I'm not sure what changed and if it's software or my internet or some sort of weird cdn routing, but it's odd and pretty frustrating when just switching back and forth between desktop and game mode. If there's any particular logs I can get pointed to that might provide insight on this, I'd take a look.
Can you try disabling chimera temporarily and see if it boots faster again?
systemctl --user stop chimera
This won't do anything. The chimera service and the startup splash screen are entirely independent.
Can you try to upgrade to ChimeraOS 46 (unstable)?
Yah. Is there a changelog somewhere? While I'm normally fine jumping into pre-releases, this setup is used by my kids so stability and generally having expectations on the changes are super important for this setup.