| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0006702 | TinyBobble | [All Projects] General | public | 2025-02-06 17:21 | 2025-02-08 12:28 | ||||||||
| Reporter | Hexaae | ||||||||||||
| Assigned To | JOTD | Project Info | Tiny Bobble (Pink^aBYSs) http://www.whdload.de/games/TinyBobble.html | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||||
| Status | assigned | Resolution | open | ||||||||||
| Summary | 0006702: REQUEST: add improved support to emulators (WinUAE etc.). The game has gfx | ||||||||||||
| Description | GameVersion: english SlaveVersion: 1.3 (04.01.2022) REQUEST: add improved support to emulators (WinUAE etc.). The game has gfx glitches if your (emulated) Amiga uses more than 2MB of chip-mem (f.e. in WinUAE I use 8MB Chip), see this thread: https://eab.abime.net/showpost.php?p=1730084&postcount=144 despite WHD slave uses less chip-ram the game seems to have some buggy code causing gfx bugs with too much "physical" chip-ram. | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Machine | UAE | ||||||||||||
| CPU | 68060 | ||||||||||||
| CPUSpeed | Other | ||||||||||||
| ChipSet | AGA | ||||||||||||
| GFXCard | Other | ||||||||||||
| ChipMem | 2 MB | ||||||||||||
| FastMem | 256 MB | ||||||||||||
| Workbench | OS 3.9 | ||||||||||||
| KickROM | 40 - Kick 3.1 | ||||||||||||
| KickSoft | None | ||||||||||||
| WHDLoad | 19.2beta | ||||||||||||
| imported | yes | ||||||||||||
| Attached Files |
| ||||||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
Hexaae (reporter) 2025-02-08 10:13 |
Not sure is a mem allocation bug, but it's strange it's the only game for WB (it can also quit with ESC) having this sprite glitches when you enable >2MB chipmem (as I do for my Workbench), and since it is the only game (I use more than 368 WHD games, plus other games and demos launching from WB and bashing the metal chipset without troubles also with 8MB chipmem enabled in WinUAE) having this kind of issue, I suspect a potential hidden bug showing up by chance only with extra chipmem. |
|
Hexaae (reporter) 2025-02-08 12:28 |
More details: When chipram >2MB the game runs fine, quits to WB without further issues etc. except some gfx glitches like this in-game: https://ibb.co/KcsgzZhx ... black background for falling bubble, and once it passes over "1UP" this starts to flicker. My usual WB config, with std 2MB chipmem = won't happen. Quickconfig A1200+4MB fast and 2MB chipmem = won't happen. My usual WB config, with 8MB chipmem = always reproducible. Quickconfig A1200+4MB fast and 8MB chipmem = always reproducible. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-02-06 17:21 | administrator | New Issue | |
| 2025-02-06 17:21 | administrator | Status | new => assigned |
| 2025-02-06 17:21 | administrator | Assigned To | => JOTD |
| 2025-02-08 10:13 | Hexaae | Note Added: 0014382 | |
| 2025-02-08 12:28 | Hexaae | Note Added: 0014383 | |
| Issue History |