| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 07137 | Color/Palette | Minor | Always | Nov 1, 2018, 11:00 | Apr 25, 2019, 13:48 |
| Tester | star2root | View Status | Public | Platform | MAME (Self-compiled) |
| Assigned To | Resolution | Open | OS | ||
| Status [?] | Confirmed | Driver | |||
| Version | 0.202 | Fixed in Version | Build | ||
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary |
 07137: coco3, coco3h: Artifact/color set switching using the F1 key not working correctly. |
||||
| Description | Using the game Castle Guard (as reference, this occurs in most pmode 4 games), if I have the Mame settings set to standard artifacting and I press the F1 key as the computer starts, the text screens change to their alternate colors, but the pmode 4 graphics remain reversed and the "fireball" remains blue. If I change the artifact setting in Mame to reverse, that affects the pmode graphics and the "fireball" is red. | ||||
| Steps To Reproduce | Run a pmode 4 graphics program after pressing F1 at the emulation startup with artifacting set to standard. Compare the red/blue colors to what you get when not pressing F1 at startup. | ||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | Verified with Original | ||||
| Regression Version | |||||
| Affected Sets / Systems | coco3, coco3h | ||||
|
Attached Files
|
|||||
 No.15719
Tafoid Administrator
Nov 3, 2018, 21:18
|
So, the original COCO3 allowed this artifacting to be reversed when you boot the machine with F1 held down? Ok. It does seem to change things when you do that, but I can confirm that the settings/status is not transferred to the TAB > Machine Configuration > root:GIME > Artifacting option and that is what determines it. Also, from what I read this is only possible in COMPOSITE video and not in RGB - not sure if that is respected or not as well. |
|---|---|
 No.16378
star2root Viewer
Apr 25, 2019, 13:48
|
Any updates on this? |