#8206 closed patch
EGA LOOM / INDY3: Experimental bugfix
| Reported by: | eriktorbjorn | Owned by: | SF/khalek |
|---|---|---|---|
| Priority: | normal | Component: | Engine: SCUMM |
| Version: | Keywords: | ||
| Cc: | Game: | Loom |
Description
I could use some input on this patch, so please don't apply until we've had some time to discuss it.
We already know that setting the CURSOR_STATE variable causes trouble in 256-colour Indy3 (see bug #636578).
Now it seems that setting it, and probably USERPUT as well, causes problems with EGA Loom: The spinning wheel always gives you the incorrect draft, "c c c c".
This patch is based on the theory that these two variables were added at the same time as subopcode 14 of o5_cursorCommand() changed. Can anyone confirm or deny this.
Ticket imported from: #729633. Ticket imported from: patches/311.
Attachments (1)
Change History (7)
by , 22 years ago
| Attachment: | variable-experiment.diff added |
|---|
comment:1 by , 22 years ago
Makes sense, and is what we suspected; what irritates me is that in bug #636578, aquadran said in the disassembly, they are being set ?!
Also, i wonder what's about Zak256 then... it's the only V3 game not covered by this patch, I think...
aquadran, any comments? If not, feel free to apply and/or reassign to me :-)
comment:2 by , 22 years ago
| Owner: | set to |
|---|
comment:3 by , 22 years ago
haven't looked into indy but I'm pretty sure this is the right thing to do for loom
comment:5 by , 22 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → closed |
comment:6 by , 6 years ago
| Component: | → Engine: SCUMM |
|---|---|
| Game: | → Loom |
Patch against an April 29 CVS snapshot