Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
04537 Graphics Major Always Nov 26, 2011, 17:47 Mar 15, 2012, 03:11
Tester NekoEd View Status Public Platform SDLMAME
Assigned To Resolution Unable to reproduce OS Linux
Status [?] Closed Driver
Version 0.144 Fixed in Version Build Normal
Fixed in Git Commit Github Pull Request #
Summary 04537: All vector games: Vector games show corrupt graphics with antialiasing enabled
Description All vector games I've tested (across several drivers) display incorrect graphics with antialiasing enabled. I have tested this across two machines with identical results on each.
Steps To Reproduce Boot a game that uses vector video.
Additional Information Turning antialiasing off (-noantialias) will result in the graphics displaying correctly.
Github Commit
Flags
Regression Version
Affected Sets / Systems All vector games
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
10
User avatar
No.07897
Tafoid
Administrator
Nov 26, 2011, 17:55
I'd say there must be some SDL specific post-rendering going on which might be corrupting the video output. I'll build an SDL Windows build and see what happens.
User avatar
No.07898
Tafoid
Administrator
Nov 26, 2011, 19:12
Windows SDLMAME doesn't seem to have an issue. I tried -video opengl and -video soft (only display option available) and tried tempest, starwars and startrek... noticing no difference in behavior for any game tested. On windows, anyway, antialias is default "1" (on) so I tried "-noantialias" as well with no difference in results of display.

Perhaps someone else can discover an issue. Do you have any previous binaries that can be tested to try to find a regression spot?
User avatar
No.07905
NekoEd
Senior Tester
Nov 27, 2011, 18:58
edited on: Nov 27, 2011, 19:18
The oldest I have available is 0.143u9 and it happens there, as well. Sorry I don't have more info.

Playing around with different settings seems to produce different results, this may be some very specific issue, but we should wait and see if any SDLMAME/Linux users experience this too. I can provide detailed system info if necessary, as well.
User avatar
No.07907
Fujix
Administrator
Nov 29, 2011, 16:22
Maybe "SDL-specific flag" is needed?
User avatar
No.07911
R. Belmont
Developer
Nov 29, 2011, 19:51
edited on: Nov 29, 2011, 19:52
MAME itself does nothing differently when -antialias is enabled. It just tells OpenGL to draw anti-aliased, so this is likely to be a driver issue. BarnacleEd, what's your video card model and driver version?
User avatar
No.07912
R. Belmont
Developer
Nov 29, 2011, 23:18
edited on: Nov 29, 2011, 23:18
QMC2 and I have verified proper operation on various Linux systems with Nvidia cards and the Nvidia binary "blob" driver.
User avatar
No.07913
NekoEd
Senior Tester
Nov 30, 2011, 13:52
Here is the info you requested, R. Belmont, for both machines:

Miku: Linux/x64 kernel 3.1.0, Intel Sandybridge Mobile (GT2+) using X.Org driver version 2.16.0, SNA enabled. (CPU is an Intel Core i5-2520M)

Tsukune: Linux/x64 kernel 3.1.0, Intel Sandybridge Desktop (GT1) using X.Org driver version 2.16.0, SNA enabled. (CPU is an Intel Core i5-2500)

These are both, of course, the integrated graphics located on the Core ix CPU die. The Intel driver is open source, with DRI using SNA and AIGLX enabled.
User avatar
No.07947
Tafoid
Administrator
Dec 6, 2011, 03:03
edited on: Dec 6, 2011, 03:04
I'll set this up for Direction Needed. Maybe R. Belmont can further speculate as to your specific issue.
User avatar
No.08345
Tafoid
Administrator
Mar 14, 2012, 23:44
Is this still an issue with your set up, BarnacleEd? If not, please close as no one has been able to duplicate this and might very well be a driver issue related to your unique setup/OS configuration.
User avatar
No.08346
NekoEd
Senior Tester
Mar 15, 2012, 03:11
It actually occurs on the UI as well, it cuts off the borders of the UI boxes. However, I've worked around this by always disabling antialiasing. Since nobody else has reproduced this, I'll just assume it's some strange personal problem.

Closing report "Unable to Reproduce."