07032: ddragon, ddragon2 and all clones: Sprites are cut too early on the right edge of the screen

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07032	Graphics	Minor	Always	Jun 26, 2018, 18:38	Jun 26, 2018, 23:09

Tester	Mamesick	View Status	Public	Platform	MAME (Self-compiled)
Assigned To	hap	Resolution	Fixed	OS	Windows Vista/7/8 (64-bit)
Status [?]	Resolved			Driver	technos/ddragon.cpp
Version	0.198	Fixed in Version	0.199	Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07032: ddragon, ddragon2 and all clones: Sprites are cut too early on the right edge of the screen
Description	Look at the uploaded video, sprites disappear too early on the right edge of the screen. Exactly it seems 8-16 pixels.
Steps To Reproduce	Just watch the attract mode
Additional Information	This bug is based on current self-compiled GIT. Since a new release is already scheduled, I thought it was useful post it now. Regression is very likely this commit: https://github.com/mamedev/mame/commit/d6a53357a56f1e2d1249b9e29e0ff117967b0a8b#diff-a37d0ebef312b173c5115ae873c9a20a
Github Commit

Flags
Regression Version	0.199GIT
Affected Sets / Systems	ddragon, ddragon2 and all clones

Attached Files	ddragonb_1.zip (1,277,909 bytes) Jun 26, 2018, 18:38 Uploaded by Mamesick Video of attract mode that shows the bug

No.15222 Mamesick Senior Tester Jun 26, 2018, 18:43	Note that it's fine in 0.198 but the "Version" field is required to post a bug so I had to use the 0.198 value. I haven't anymore a GITHUB account so I wasn't able to post the issue there.
No.15223 Tafoid Administrator Jun 26, 2018, 23:09	Thanks for the report. Thanks to your heads-up, we got this covered before release happening very soon. Strictly speaking, a better place for WIP bugs like this would be an external forum. Even mamedev.org, mameworld.info, bannister.org or a number of other Dev frequented forums or even IRC could be used.. A GIT account is the preferred way to comment on a bug and note a regression, however. MAMETESTERS, as designed, can only log version to version regressions and fixes.

No.15222

Mamesick

Senior Tester

Jun 26, 2018, 18:43

Note that it's fine in 0.198 but the "Version" field is required to post a bug so I had to use the 0.198 value. I haven't anymore a GITHUB account so I wasn't able to post the issue there.

No.15223

Tafoid

Administrator

Jun 26, 2018, 23:09

Thanks for the report. Thanks to your heads-up, we got this covered before release happening very soon.
Strictly speaking, a better place for WIP bugs like this would be an external forum. Even mamedev.org, mameworld.info, bannister.org or a number of other Dev frequented forums or even IRC could be used.. A GIT account is the preferred way to comment on a bug and note a regression, however.

MAMETESTERS, as designed, can only log version to version regressions and fixes.