this post was submitted on 10 Feb 2025
27 points (93.5% liked)

Mildly Infuriating

36867 readers
117 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-The Community !actuallyinfuriating has been born so that's where you should post the big stuff.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 2 years ago
MODERATORS
 

This happened to me a few times lately.

Half Life 2 VR Mod - Played it for ~4 hours, before all of a sudden it won't launch. I click on play in Steam, and after 3-4 seconds, nothing happens, then the play button is active again. No errormessage, nothing.

Resident Evil 2 Remake - I have almost 15 hours in it, almost finished the Claire campaign, when from one day to the next it won't launch. Just a black window pops up for one second, then it just stops, the play button is active again, so this game also leaves the user hanging without any errormessage.

Look, I have been gaming on PC since 2000, and with 25 years of experience, these situations are infuriating for me. I have my goto steps (check file integrity in Steam, update nVidia drivers, ec.) and if those don't work, I look on the Steam forums, google, etc for solutions, so eventually I'm gonna figure it out.

But dear gamedevs, please, please, please for the sake of less savvy players, include at least some clue of what the user should do. A blanket statement to the effect of "game failed to launch, please try the following: verify game files, uninstall then reinstall game, make sure you are on the latest drivers for your GPU, etc etc. If game still won't launch, visit our FAQ page here, where we listed all possible solutions..." could suffice for people who just want to play. At least they would not be totally stumped, and would have some options before they also google the problem, but man... Also, maintaining a FAQ about launch issues, bugs, crashes, etc. would be expected for a paid customer to have support for their product...

I somewhat understand that in 2025, game devs can expect everyone to eventually google what they don't know, but an errormessage would still go a long way in establishing a communication with the user in the time of crisis - "Hey, we failed now, but we have some general ide about the problem, here are some general options, and here is where you could seek further help" is an essential part of customers support - even in 2025, and it's so basic, I don't even understand why I am still talking about this.

TL;DR - User loses it over games that don't show errormessages after failing to launch.

top 6 comments
sorted by: hot top controversial new old
[–] rtxn@lemmy.world 6 points 1 week ago (1 children)

Games actually provide lots of debugging information, but not in an easily accessible manner. It is usually printed to stdout or stderr, which is to say, to a terminal output, and you'll only see it if the game executable is launched from a terminal or the outputs are redirected to a file.

[–] Sati1984@lemmy.world 2 points 1 week ago

Yes, for you and me, this is useful information. But here is where I think, for less savvy users, even a blanket error would be really helpful, focusing on next steps the user can try.

[–] donuts@lemmy.world 5 points 1 week ago* (last edited 1 week ago) (2 children)

I ain't here to defend shitty game dev practices, but maybe there's no error message because the game can't launch at all? Like, there's nothing to report about because the game never got a chance to load properly.

Have you checked the event log? Maybe that will give you a clue.

Edit: another common culprit is antivirus nuking game files, but that shouldn't happen to games you've already played, so I doubt that's the case. Still worth a mention though, just in case.

[–] SpikesOtherDog@ani.social 4 points 1 week ago

Symantec has watched me execute the same script I wrote dozens times before suddenly deciding that it is malicious.

[–] Sati1984@lemmy.world 1 points 1 week ago

Thanks for the tip, and yes, I can do that, I can check logs, but the point of my post is to have some information that a less experienced user can access and get a clue on what to try next.

BTW in the case of RE2remake, the solution was to switch the game to the beta branch, redownload it, then launch it again - it worked, but I only know this, because of a post on the Steam board of the game. Here is where a blanket error would come in handy ("try this, this, and this, then switch to beta and try that, etc."), if there is absolutely no information about the nature of the error.

[–] barsoap@lemm.ee 1 points 1 week ago* (last edited 1 week ago)

But dear gamedevs, please, please, please for the sake of less savvy players, include at least some clue of what the user should do.

Look at the logs. Submit the logs in your bug report. I agree that displaying a message box would alleviate user confusion but a) that won't contain the info devs will need to actually solve the issue, dialog boxes are too small, and a gazillion of bug reports saying "Game tells me 'cannot initialise gfx window'" aren't helpful and b) what if the message box fails to display. I mean technically writing to log can also fail but then the user probably is noticing that their disk is full in some other way so it's not as much of an issue.

The ideal situation is having a secondary process watch the actual game process, if something goes wrong it will give you the choice between displaying the logs and just submitting a bug report. Another uncomfortable truth is that without a tech-savy user at the other side, some bugs just can't be diagnosed because it's a "works on all of our machines, we have no idea how yours is different" type of situation.

...and if the engine you're using doesn't come with that kind of thing built-in no devs won't write it. It's a PITA to do when you're not acquainted with the code that actually does do the basic windowing etc setup and there's more important bugs to squash and features to creep.