![]() R/programminghorror - for unintentionally bad code. r/justgamedevthings - for memes, reaction gifs, production glitches and other fun related to game development. R/ProgrammerDadJokes - for the punny bunch of you. R/ProgrammerAnimemes - for the anime referenced programmer memes R/badUIbattles - a sub for intentionally bad UI. r/learnprogramming - for those that have general programming questions r/programmerreactions - expressing the life of programmers through reaction images. r/recruitinghell - for all those horrific recruiting offers and job postings. ![]() ![]() r/itsaunixsystem - for all the embarrassing cases of hollywood hacking you find in media. r/sysadminhumor - a sub for sysadmins with a sense of humor. R/linuxmasterrace - for anyone that likes Linux memes. R/pcmasterrace - for all of the general computer/gaming memes. r/softwaregore - f collection of things that users shouldn't see. If you feel that a metadiscussion is required with the whole subreddit either request that the moderators start one ![]() If you have any thoughts on how the moderation could be improved do not hesitate to message the moderators. With regards to commenting, please follow reddiquette. If they do not appear zero-indexed you are asked to contact Friend Computer for recalibration. Filtersĭiscord Submission rules For the current list of rules, please see this page. Now - you could maybe train a model that accounts for all manner of heuristics that predict the load-times on any given system, but the complexity of it all, potential of it still failing some cases badly, and the return on investment being 'accurate loading bar that majority of people will never notice' is well - not a great pitch to even attempt.Not everybody understands the humor of programmers. Time based is theoretically most accurate but it's by far the most complexity to prepare (As you have to save off benchmarks of all your load times into your release packages) and will be wildly in-accurate for PCs with countless different specced hardware/software configurations that can completely change the time-to load. Getting precise size measurement significantly increases complexity of the process (most games/engines in fact have no idea/don't track at all how much is there left to load in actual 'bytes'), and it still won't be really accurate (some things still load faster / with less backend processing than others). it gives no indication to the user on 'how much is left to load'. Packages to load is going to give you the skipping bars with some single steps taking 90% of the time - ie. Some games do it well like Forza Horizon 5, when teleporting around the map or changing car the load screen is shown only for the time needed, if needed.Ĭlick to expand.This actually describes why the bars are mostly inaccurate. Same thing in Diablo 4, you get a 2-3s loading screen when teleporting to some areas, but going back to where you were after that is instant. I'd prefer a flickering load screen than a fake longer one. Still happens sometimes, that's really dumb. Sometimes you could see the endgame screen showing right after the game ended as it loads very fast, but that fake loading screen comes on top of that for a few seconds for nothing. So they added a fake loading screen and making it last a minimum amount of seconds, even on Series X and fast PCs. Halo Infinite did not have one during the beta, on Series X it was loading so fast that the black screen was visible for less than a second, sometimes it loaded instantly.īut for users with HDDs on Xbox One and some PCs, that black screen could be long. Some games do not need loading screens, some needs it (unless you want to spawn in the void and see the world loading around you).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |