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

Graphical glitches on the latest 2.6.1 release #1532

Open
antoniodesousa opened this issue Apr 30, 2024 · 4 comments
Open

Graphical glitches on the latest 2.6.1 release #1532

antoniodesousa opened this issue Apr 30, 2024 · 4 comments

Comments

@antoniodesousa
Copy link

What's the full name of the game (including region) ?
I tested Loaded and Keio Flying Squadron 2. But probably a lot more games are affected

What's your frontend ? (standalone, libretro, ...) ?
It happens on both standalone and libretro

What's your OS ? (windows, linux, OSX, ...) ?
Windows 11 Pro 23H2

What's your hardware ? (CPU, GPU, ...) ?
Ryzen 9 6900HX, AMD RX 6600M, 64GB RAM

What's the storage type of the game (official cd, burned cd or cd image) ?
Official CD and Redump images

If applicable, what's the format of your cd image ? (cue/bin, ccd/img, iso, chd, ...)
chd

Are you using any setting different from default ? If so, precise
Everything default

Did this game work previously ? Do you remember when ? Is it happening with other games ?
Latest release I tested were both games work correctly is 2.3.1. Any release after that has the same issues

@CloudFR
Copy link

CloudFR commented May 12, 2024

I confirm this issue, in kronos 2.5.0 opengl render is ok
with kronos 2.6.1 without opengl it is glitched

@antoniodesousa
Copy link
Author

Loaded using Kronos 2.6.1 (2.3.1 doesn't have the flickering lights):
https://github.com/FCare/Kronos/assets/10920974/ace797a0-b4ea-4a78-be87-6ec794ec297e

Keio Flying Squadron 2 using Kronos 2.3.1:
Keio Flying Squadron 2 - Kronos 2 3 1

Keio Flying Squadron 2 using Kronos 2.6.1:
Keio Flying Squadron 2 - Kronos 2 6 1

@FCare
Copy link
Owner

FCare commented May 14, 2024

Due to 46c12d6

@fafling
Copy link

fafling commented May 14, 2024

Already reported here : #1491 (comment)

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

4 participants