| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 02074 | Flip Screen/Cocktail | Minor | Always | Aug 3, 2008, 01:24 | Jun 10, 2012, 02:59 |
| Tester | Robbbert | View Status | Public | Platform | MAME (Self-compiled) |
| Assigned To | Resolution | Open | OS | Windows XP/Vista 32-bit | |
| Status [?] | Confirmed | Driver | |||
| Version | 0.126 | Fixed in Version | Build | Normal | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 02074: mooncrgx: Sprite cutoff in cocktail mode incorrect | ||||
| Description |
3. The sprite-cutoff area is incorrect for player 1, but correct for player 2 in cocktail mode. See attached snaps: 1. Sprite cutoff at bottom 2 and 3. Sprite not hidden at top |
||||
| Steps To Reproduce |
Watch the attract mode for a while. Set to cocktail mode and play both players to at least the second stage. |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | mooncrgx | ||||
|
Attached Files
|
 0004.png (3,244 bytes) Aug 3, 2008, 01:28 | ||||
| 0001.png (3,189 bytes) Aug 3, 2008, 01:29 | |||||
| 0003.png (3,086 bytes) Aug 3, 2008, 01:32 | |||||
 No.01896
Tafoid Administrator
Aug 3, 2008, 02:55
|
The 1st issue (3rd and 4th stage enemies are corrupt) is covered in 02072. Splitting the remaining two issues as separate bugs. Please avoid adding combination bugs like this in the future. They will most likely require different fixes and when combined, are harder to maintain on this new bug system and causes more work for us. |
|---|---|
 No.01902
Robbbert Senior Tester
Aug 3, 2008, 07:44
edited on: Aug 3, 2008, 08:35
|
I've made a new bug for the general sprite cutoff problem (02077). mooncrgx is special, because it is ROT270 (unlike the rest which are ROT90). Therefore mooncrgx needs its own "galaxian_sprite_clip" parameters. |
 No.01903
Fujix Administrator
Aug 3, 2008, 09:07
|
This report is for the cut-off area issue now, isn't it? But #2077 and this report are for the same issue. What did you duplicate the report for? |
|
No.01905
Robbbert Senior Tester
Aug 3, 2008, 09:33
edited on: Aug 3, 2008, 09:36
|
They have different resolutions. According to Tafoid, different fixes require different bug reports. I'm only following his orders. |
 No.01906
etabeta Developer
Aug 3, 2008, 09:44
|
yeah, in this case I think the different ROT flag is the key for not being a duplicate |