Skip to content
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

The vision of mangohud changes between normal and broken #1300

Open
rado84-github opened this issue Apr 16, 2024 · 0 comments
Open

The vision of mangohud changes between normal and broken #1300

rado84-github opened this issue Apr 16, 2024 · 0 comments

Comments

@rado84-github
Copy link

rado84-github commented Apr 16, 2024

Describe the bug
IDK how more clear to explain it than what I wrote in the title, so I'll explain it in the below section with screenshots.

List relevant hardware/software information

  • Linux Distribution: Arch Linux
  • MangoHud versions: Extra/0.7.1; AUR/mangohud-git 0.7.1.r20.g5598fda-1
  • GPU: Nvidia, driver 550.67

To Reproduce
Steps to reproduce the behavior:

  1. Run native linux ETS2 v1.46 or newer.
  2. Stop at a traffic light or border inspection.
  3. While the truck isn't moving, observe mangohud vision quickly changing between the "normal" screenshot ("normal" means what you customized it to look like) and the broken vision. Looks almost like an animated GIF.

Expected behavior
Vision shouldn't change no matter what you do in the game.

Screenshots
Normal vision - what I have customized it to look like:
normal

Broken vision:
broken

Additional information
At first I had the Extra version 0.7.1 but when that started happening while waiting on a traffic light, I installed the git version because it's a month newer than the Extra version. And just when I thought the git version fixed the problem, it started happening almost all the time for as long as the truck isn't moving.

Then I realized that 2-3 months ago this problem didn't exist because:
• The GPU driver was another version. Now it's 550.67.
• Xorg wasn't updated 2-3 months ago. It was updated a day or two ago.

IDK enough about mangohud but I'm gonna take a wild guess that the combination of these two things updating caused this issue. I have frozen the game at version 1.46 (for other reasons) and it's been like that for many months, so the cause can't be the game itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant