this post was submitted on 02 Jul 2023
76 points (95.2% liked)

Games

32371 readers
1226 users here now

Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.

Weekly Threads:

What Are You Playing?

The Weekly Discussion Topic

Rules:

  1. Submissions have to be related to games

  2. No bigotry or harassment, be civil

  3. No excessive self-promotion

  4. Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts

  5. Mark Spoilers and NSFW

  6. No linking to piracy

More information about the community rules can be found here.

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago

I have a bad solution to this:

  1. measure the mean and std. of loading times for a given loading task on a wide variety of machines, store this
  2. when a user encounters a load that needs a bar (above a certain time threshold), compare their machine to those stored to get a mean/std
  3. go to your desired confidence level above the mean (say 99.9% of all cases) and use that as a loading time.
  4. progress the loading bar smoothly for that time. If the loading is done before that DO NOT end early, just keep going and record the new time to work it into the mean/std (which should probably be reported back to the dev and fetched by the user's machine daily)
  5. If it goes over on time, just dismiss the loading screen just very very slowly transition to the game, and if its still not done just crash the game. If we cant have an accurate loading time we won't have any loading time.

This should annoy enough devs and users alike and make them admit that fake loading bars are better than accurate ones.