Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06783 Graphics Minor Always 13 days ago 12 days ago
Tester wuemura View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Open OS Linux (64-bit)
Status [?] Confirmed Driver
Version 0.192 Fixed in Version Build 64-bit
Summary 06783: Lines across the screen appears if GLSL and prescale = 1
Description If GLSL and the prescale = 1 are enabled at the same time is possible to see lines across the screen braking the graphics, this is not direct related with machines because the same defect happens on different machines.

If prescale =2 or 3 the defect is gone.
Steps To Reproduce ./mame64 -video opengl -window -maximize -filter -prescale 1 -gl_glsl sf2ce

If you remove "-prescale 1" or "-gl_glsl" the defect vanishes, it only happens if this options are used at the same time.
Additional Information It only affect Linux, Windows doesn't have this issue.
Flags
Regression Version
Affected Sets / Systems
Attached Files
png file icon mamebug-01.png (872,202 bytes) 13 days ago Uploaded by wuemura
png file icon mamebug-02.png (498,001 bytes) 13 days ago Uploaded by wuemura
wuemura
png file icon mamebug-03.png (1,119,841 bytes) 13 days ago Uploaded by wuemura
Relationships
There are no relationsihp linked to this issue.
Notes
2
User avatar
No.14491
Tafoid
Administrator
12 days ago
edited on: 12 days ago
AFAIK, you can't use opengl/glsl sliders if prescale is greater than 1.
Anyway, the behaviour seems confirmed, but not I'm sure what can be done about it.

Tested Windows: -opengl -gl_-gl_glsl

User avatar
No.14492
wuemura
Tester
12 days ago
I'm just reporting the behavior, besides "-window" and "-maximize" I don't use any of the other switches. I was helping a user out that uses this settings and this behavior started.

It could be a good idea to block options that it's not suppose to be used together, like if enabled it will automatically disable the other, or will be faded out and vice versa. Specially if no developer is available to fix this now, it could prevent new reports in the future.

Thank you @Tafoid.