Fix target joystick calibration arguments and scene transitions

Avoid a demonstrated CMOC -O2 removed-index-reload error with independent calibration and position pointers. Keep established joystick readiness across menus, stabilize shared fire/keyboard scans, and protect input sampling from IRQ interference.

Ship pristine QUADPSL04.DSK. Native right-port emulated analog/button checks pass for both directions, four lasting T-piece turns, and steering after keyboard resume. Host input/store/rules/video regressions and unchanged memory guards pass. Preserve personal score disks and record physical/128 KB/audio limits.
This commit is contained in:
Brian Holman committed 2026-11-11 14:26:06 -07:00
1 parent 2e163049d1
commit a07c41555a
22 files changed
+446 -100

No files matched your search

+9
View File
@@ -129,3 +129,12 @@ has both-channel peak 7936, ten changing edges and silent final 500 ms. These
buzz was still present on build 01 and remains open pending build-02 retest;
the differing emulator versions prevent treating effect peak changes as a
controlled game-volume comparison. See JOYSTICK_FIX.md for the current artifact.
Build 03, official build 53 / revision 3 / MC6809 / 512 KB: title and gameplay
idle are exactly zero in both channels. Movement peak 7936 in each channel,
21 changing edges, final 500 ms zero; 120-field captures pass the checker.
This remains isolated-worker evidence and does not close the normal-window buzz.
Build04 changes only argument addressing after the build03 checks; its final
native analog checks did not recapture audio. Do not label build03's exact PCM
numbers as measured build04 results. The normal-window speaker buzz stays open.
+27 -3
View File
@@ -2,13 +2,15 @@
Brian requested this delivery convention on November 11, 2026:
`QUADPSLxx.DSK`, with a two-digit build number and fresh high scores for each
new delivered build. Begin at 01. The current delivery is 02; the next changed delivery is 03. This number
new delivered build. Begin at 01. The current delivery is 04; the next changed delivery is 05. This number
identifies the game disk, independently of the VCC Plus application build.
| Build | Date | Filename | Contents / validation |
| --- | --- | --- | --- |
| 01 | 2026-11-11 | QUADPSL01.DSK | Title spacing, credits, scoring labels and extra standard-library mute; historical artifact in Git |
| 02 | 2026-11-11 | QUADPSL02.DSK | Fix shared fire/keyboard rows and independently arm joystick axes; see JOYSTICK_FIX.md |
| 02 | 2026-11-11 | QUADPSL02.DSK | Initial shared-row/axis fix; Brian reported actual joystick failure after DOS load |
| 03 | 2026-11-11 | QUADPSL03.DSK | Internal candidate; native test exposed target calibration argument error; withdrawn |
| 04 | 2026-11-11 | QUADPSL04.DSK | Correct target argument loads, stable fire, scene readiness; native emulated joystick checks pass |
Build 01 is 161,280 bytes, SHA-256:
`4ac171e87c51dfd99b302b9e035a91a59c030144e5ae0661a6d2dfc84ba3a63f`.
@@ -42,8 +44,30 @@ score backups and the mounted disk remain untouched; ignored WAV/JSON diagnostic
evidence is retained while the normal-window buzz is unresolved. Historical
source and selected evidence remain in Git.
Build 02 is the current clean delivery. SHA-256:
Historical build 02 pristine SHA-256:
`4e3af2440a3195ee5864498e39a779362988257d8a39cfc1c413157ace287a3c`.
The old build-01 filename was observed loaded in VCC Plus, so that local disk is
left untouched during cleanup. Its pristine historical artifact remains in Git
history; it is excluded from future commits to protect any personal save writes.
Withdrawn internal build 03 SHA-256:
`80c511fe9c9b1a0faaeffa688dec6d73de39280f8eb3c9ce584727fc396f09ca`.
Its official Release build/isolated run identities are in JOYSTICK_FIX.md. It
starts with default settings and empty scores. Code/const end $7ACD, static end
$13FD; the 1024-byte stack reserve is unchanged. The writable build-02 file is
preserved locally and backed up byte-identically under ignored personal media;
it is retired from tracking rather than resetting its saved contents.
Build 04 is the current clean delivery, SHA-256:
`1cddb6bdf17857b915e96a6929e14181bad05cfae73278a4919add26fea0ba45`.
QUAD.bin is 26,581 bytes, SHA-256:
`f79dd5b4ba32ab592bd2b1cb21bea2847b58bd88a1343a9507e1e72e26fe6767`.
Official native build53 Release disk builds FC462D93 / A7A18927 passed; code/const
end $7AD4, static end $13FD, 1024-byte stack reserve. Native right-port emulated
analog/button checks passed for left/right, four lasting T turns and steering
after keyboard resume. Physical hardware/controller, left port and 128 KB remain
pending. See CMOC_JOYSTICK_ARGUMENTS.md for cause, evidence and exact limits.
Pristine QUADPSL04.DSK contains only QUAD.BIN, WORDS.DAT, QPTEXT.DAT and the DOS
launcher; empty scores/default settings. The app mounted a separate working copy.
Withdrawn pristine build03 and unmounted test scratch are removed during cleanup;
personal build01/build02 images and backups are retained unchanged.
+66
View File
@@ -0,0 +1,66 @@
# Horizontal input compiler workaround — November 11, 2026
The build-03 native test reproduced constant right movement with the right port
assigned to VCC Plus Keyboard input (Arrows + Z / X). These host keys are reserved
for the emulated joystick, so guest A/D keyboard movement does not mask a bad
analog direction. Held-left entry into Controls read right X=0, Y=31. The actual
normal guest was then paused and inspected through the public native Debugger.
Build-03 QUAD.map identifies preferences=$1008, input=$101B, joystick_axes=$102C.
Memory showed preferences.centers[0..3]=31,31,31,31, axes=31,31,31,31 and raw
buttons=15, yet input.previous=Q_RIGHT, direction=+1 and axis_x=+1. No guest
memory, registers, PC or breakpoints were edited. This distinguishes correct
analog readings from the erroneous direction seen by the rules.
The generated main.s explains the mismatch. CMOC 0.1.100, bundled in official
VCC Plus 3.6.1 (53), --coco -O2 --no-relocate --switch=jump, originally emitted:
```asm
LDB index
ADDB #1
LDX #preferences_centers
LDB D,X ; cy, normally 31
PSHS B,A
; removeUselessLdaOrLdb removed the reload of index here
LDX #preferences_centers
LDB D,X ; uses the previous cy byte as the index for cx
PSHS B,A
```
These are abbreviated excerpts of compiler-generated game assembly; symbol and
stack spellings are shortened for readability. The wrong cx comes from outside
the four-byte array. A zero there makes neutral X=31 activate right, and full
left X=0 becomes neutral instead of negative. Ordinary host C tests do not run
this target optimizer. Earlier MCP guest keyboard LEFT also masks spurious
joystick RIGHT because the first horizontal direction wins.
The C-only workaround forms independent center/position base pointers before
passing element 0 and element 1. Generated argument loads are now pointer+1 and
pointer+0; the previous byte value is never reused as an array index. Both
ports use the same corrected call; actual left-port qualification is pending.
No compiler snapshot, emulator source, assembly or hardware driver was changed.
Brian authorized sending this finding to Core VCC Plus for separate follow-up.
## Target validation
Official native Release disk builds FC462D93 and A7A18927 succeeded with zero
issues; A7A18927 included the numbered delivery in its input identity. A native
Launch Disk mounts a separate working copy. It did not replace the old graphics
program in RAM, so the machine was explicitly cold-restarted and DOS run before
accepting any new evidence. Brian had authorized replacing his running game.
The clean build-04 disk has no QPSAVE files. MC6809 / 512 KB normal-window tests
using right-port Keyboard joystick mapping demonstrated both walls with the same
I piece, four distinct T orientations in sequence on short fire release, and
joystick LEFT after keyboard P/Enter pause/resume. The released button did not
undo a turn. CoCoMan's reference informed the shared-row/transition safeguards,
but its VCC-specific input API and assembly were not copied.
The right-port DualSense Wireless Controller assignment was restored (Standard,
left stick, Fire 1 Button 1, Fire 2 Button 2, 15% dead zone); left port None and
512 KB/MC6809 remained selected. The build-04 working copy is left paused.
This is emulated analog/button-path evidence, not physical DualSense or real
CoCo hardware qualification. Physical joystick, left port and 128 KB remain
pending. Normal-window speaker buzz remains open; no audible cure is claimed.
![Native right-port joystick LEFT after keyboard resume](screenshots/build04-native-joystick-after-resume.png)
+34 -3
View File
@@ -4,13 +4,34 @@ The current disk contains a playable CoCo 3 game with standard CMOC sound,
settings and disk-backed high scores. Actual 128 KB qualification remains
pending; CoCo 2 adaptation is deferred at Brian's direction.
## Current joystick correction — build 02
## Current joystick correction — build 04
QUADPSL04.DSK works around a demonstrated bundled CMOC -O2 calibration-argument
load error. Official native build53 Release and right-port emulated joystick
left/right, four lasting T turns and steering after keyboard resume pass.
Physical controller/CoCo, left port and 128 KB remain pending; buzz remains open.
Disk SHA-256:
`1cddb6bdf17857b915e96a6929e14181bad05cfae73278a4919add26fea0ba45`.
Code/const end $7AD4; static end $13FD; stack reserve 1024 bytes. Details:
[Target diagnosis](CMOC_JOYSTICK_ARGUMENTS.md).
## Withdrawn internal joystick candidate — build 03
QUADPSL03.DSK adds stable before/after button sampling, a standard-CMOC
interrupt-protected input transaction, and preserved joystick readiness across
keyboard-confirmed scene transitions. Official build 53 Release and isolated
MC6809/512 KB keyboard smoke/audio checks pass. Actual joystick qualification
is recorded separately in JOYSTICK_FIX.md. Disk SHA-256:
`80c511fe9c9b1a0faaeffa688dec6d73de39280f8eb3c9ce584727fc396f09ca`.
Code/const end $7ACD; static end $13FD; stack reserve 1024 bytes.
## Earlier joystick correction — build 02
QUADPSL02.DSK fixes shared fire/keyboard input lines and arms joystick axes
independently. Both reported failure patterns were reproduced in host regressions
and pass after correction. Standard CMOC APIs are retained. Official VCC Plus
3.6.1 (53) Release build and MC6809/512 KB keyboard/gameplay smoke checks pass;
physical joystick testing is still pending. Details, source references and final
Brian subsequently confirmed actual joystick failure after loading it with DOS. Details, source references and final
identity: [JOYSTICK_FIX.md](JOYSTICK_FIX.md).
Clean disk SHA-256:
@@ -23,7 +44,7 @@ The normal-window buzz remains open. Old personal score disks are untouched.
Brian requested `QUADPSLxx.DSK` with a two-digit build number and fresh high
scores. The first is **QUADPSL01.DSK**, byte-identical to the clean official
artifact below. No QPSAVE files are included; old personal score disks remain
untouched. The next changed delivery is 02. See [BUILDS.md](BUILDS.md).
untouched. That delivery is historical; the current build is recorded above. See [BUILDS.md](BUILDS.md).
## Current title, scoring-label and audio follow-up
@@ -176,3 +197,13 @@ This is user-reported physical-hardware gameplay evidence, separate from the
isolated emulator runs. It does not establish a 128 KB pass or separate passes
for the audio correction, persistence, joystick ports or every game option.
The exact tested disk/build and detailed machine configuration were not supplied.
## November 11 — follow-up after actual build-02 joystick failure
Brian confirmed loading build 02 with DOS and reported continued inability to
move left and cancelling fire rotations. Build 02 has not passed joystick
acceptance. The next candidate uses standard CMOC interrupt protection and a
stable before/after button scan, and preserves neutral readiness across scene
transitions. CoCoMan was consulted read-only with Brian's explicit permission;
its custom assembly and VCC API were not imported. See JOYSTICK_FIX.md. Actual
right/left-port and 128 KB checks remain pending, as does normal-window buzz.
+95
View File
@@ -110,3 +110,98 @@ steering. Hold fire 400 ms to open Actions; release must not rotate or select a
second action. Check keyboard fallback and, separately, the left-port setting.
If X still sticks, distinguish movement that never starts from movement that
works once and then locks; record which system and port exhibit it.
## Actual build-02 result and CoCoMan reference
Brian confirmed DOS loaded QUADPSL02.DSK; he still could not move left and
reported press/release rotations cancelling. Passive observation of his current
VCC Plus session showed pieces collecting at the right edge. Build 02 therefore
did not pass actual joystick acceptance. Keyboard smoke tests and the prior
static button mocks were insufficient to establish that result.
On November 11 Brian granted read-only access to CoCoMan. Relevant working-tree
references were game/main.c, game/keys.c and game/title.c, based on revision
439bd25ac46fbc7ecdfd67d98893a1cff90aef66 (main.c had local edits). CoCoMan keeps
its input record across pause/resume. Its published vcc/input.h contract masks
interrupts during the shared PIA transaction. Its keyboard/title readers mask
button-grounded rows, and title_keys checks button state on both sides of the
scan and retries if it changed. No CoCoMan source was modified or copied; its
custom assembly and VCC input extension were not imported.
## Build-03 candidate changes
- Standard CMOC disableInterrupts/enableInterrupts now bracket the foreground
analog/button/keyboard transaction. Player_disableSound is asserted before
and after sampling. The IRQ-sharing risk is addressed; its role in Brian's
horizontal failure has not been demonstrated with real analog readings.
- keyboard_read samples standard readJoystickButtons before and after the key
scan and retries if they differ. A single fire edge during build 02's scan
can bypass its initial row mask; the authored hardware mock reproduces this
gap. Logical fire uses the same stable final sample as the keyboard filter.
- Scene transitions clear transient key/button/repeat state and preserve the
joystick's established neutral readiness and hysteresis. Keyboard confirmation
does not change port selection. Cold start, explicit port change and explicit
neutral calibration still reset readiness. Held confirm/fire retains a release
guard; Up requires neutral again before a hard drop after a transition.
- The smaller original coco.h position reader is retained. A trial using the
standard bcontrol full-resolution reader exceeded the unchanged memory bounds
and was not delivered. No VCC-specific API, new hardware code or assembly is
used. Caption pointer iteration, equivalent compact hysteresis, shared return
code, seven effect-duration bytes in low static data and shorter status text
keep the correction inside the original memory/stack contract.
Host regressions cover each reachable key-probe boundary for one press/release
edge on each of four button lines, four lasting L-piece rotations, steering with
fire, keyboard-confirmed transitions, and held-button release guarding. Rules,
persistence and video suites pass. This is simulated hardware evidence. Actual
analog joystick acceptance remains pending; Controls readings are still entry
snapshots, not live measurements. A very brief press/release entirely between
samples cannot be observed by either endpoint check.
### Official build-03 artifact and isolated checks
VCC Plus 3.6.1 (53), project 7D6E1D9C-DF7C-4B15-B64D-6B30732417CB,
revision 3, Release disk action. Build C4E09234-A50B-4930-996E-A37A5521BFE7
succeeded with zero diagnostics; artifact A699546A-0A49-4521-BDF0-BA493FCFA850.
QUAD.bin is 26,574 bytes, SHA-256
86d1854f901c4c80f7b06b1fc048b7957f6fcd35ed2a8d1dd78fb7538df3a96b.
QUADPSL03.DSK is 161,280 bytes, SHA-256
80c511fe9c9b1a0faaeffa688dec6d73de39280f8eb3c9ce584727fc396f09ca.
The delivery matches the official artifact and contains only QUAD.BIN,
WORDS.DAT and QPTEXT.DAT, plus the DOS launcher; no QPSAVE data is present.
MC6809/512 KB owned run 74607F0C-BE7D-4931-9378-48DA2E4263D4 is stopped.
Actual guest captures show keyboard start, left/right movement, rotation,
pause and keyboard-confirmed resume followed by movement. Title and gameplay
idle PCM are zero in both channels. Movement has a positive effect (peak 7,936
in each channel, 21 changing edges) and a silent final 500 ms. Captures span
120 fields each. Host suites passed with ASan/UBSan; 128 KB, physical joystick
and the user's normal-window audio symptom are not qualified by this worker.
An experimental file-path output exclusion was accepted by the MCP inventory,
but later broke native project opening with a misleading missing-resource error.
It was removed: outputDirectories must contain real folders, not DSK file paths.
The first refresh was rejected to avoid adopting the personal build-02 disk as
an input. A second refresh approved the source changes and output exclusions.
The ordinary STDIO helper must stay connected until its native refresh dialog
is reviewed. Closing C Development later invalidated the temporary connection;
all owned workers had already been stopped.
## Final build 04: demonstrated target compiler error
Build 03 was withdrawn after native testing found that correct raw analog values
were paired with an incorrect horizontal calibration argument in generated code.
Independent base pointers in sample() avoid the bundled CMOC -O2 index-reload
error. This is the demonstrated cause of constant right movement and inability
to move left. Full excerpts, paused guest state and native qualification:
[CMOC_JOYSTICK_ARGUMENTS.md](CMOC_JOYSTICK_ARGUMENTS.md).
Final clean disk SHA-256:
1cddb6bdf17857b915e96a6929e14181bad05cfae73278a4919add26fea0ba45.
Official build53 native Release build A7A18927 succeeded. Code/const end $7AD4,
static end $13FD, stack reserve 1024 bytes. Right-port Keyboard joystick mapping
passes native analog left/right, four lasting T-piece turns and steering after
keyboard-confirmed resume. DualSense mapping was restored and game left paused.
These tests use actual emulated analog/button circuits; physical controller/CoCo,
left port and 128 KB remain pending. Build04 audio was not recaptured after this
pointer-only correction; build03's isolated audio evidence remains historical.
+20
View File
@@ -65,3 +65,23 @@ joystick investigation. The renewed connection verified project
7D6E1D9C-DF7C-4B15-B64D-6B30732417CB, revision 2, built successfully and ran the
frozen artifact. Its playtest_input schema still supports only keyboard keys,
not analog axes/fire injection. No native joystick pass is inferred from it.
Build 03 used that project at revision 3 on official build 53. Keep the official
STDIO helper connected while a refresh awaits native review: with the one-shot
helper disconnected the review window was not presented. Closing C Development
invalidated this private grant after all owned runs stopped. Reconnect through
the official interface when more MCP work is needed.
Only real result folders belong in outputDirectories. An attempt to exclude
numbered DSK files there was accepted by MCP inventory but broke native project
opening (reported as missing assets/ui-text.tsv). File exclusions were removed;
explicit resourceInputs names the two real text inputs. Native project loading
and Release disk build then passed. Root delivery disks remain project resources:
freeze them during owned tests and create/update delivery filenames after the run
stops. Personal media/backups are never reset to satisfy source identity.
Build04 was built and qualified through the native installed build53 C Development
workflow after the grant ended. Native builds FC462D93 / A7A18927 succeeded.
Launch Disk mounted a separate working copy; explicit cold restart plus DOS was
required because the prior graphics game was still in RAM. A new mounted filename
or C workspace's latest-build badge alone does not prove the guest reloaded it.
+12
View File
@@ -53,3 +53,15 @@ positions. The palette (11 bytes) and preference-validation table (15 bytes)
use low static data; they are only read. Optional video timing instrumentation
is enabled only by QUAD_PROFILE and is unavailable in Release. Every profile
build still needs the unchanged link guard; profile configurations are unqualified.
Build 03 additionally moves the seven effect-duration bytes into low static
storage (read only in use), iterates packed captions with a byte pointer, and
compacts equivalent input handling/status text. Code/const end $7ACD; static
end $13FD; reserved stack remains 1024 bytes. Full bcontrol position sampling
was tried but exceeded the guard; the delivered path retains standard coco.h
position reading with public interrupt protection.
Final build04's independent calibration/position pointers avoid the target
compiler indexing defect. Code/const end $7AD4 (44 bytes free), static end
$13FD (3 bytes free). The original MMU window, section limits and 1024-byte
stack reserve are unchanged. Memory qualification remains actual-128-KB pending.
+10
View File
@@ -114,3 +114,13 @@ periodic sampling and active-low primary-button masks. Public coco.h keyboard
coordinates and Joystick.h contracts identify the shared input rows. No raw
register/interrupt/assembly code was copied. The new keyboard-row fixture is
authored for this repository; details are in JOYSTICK_FIX.md.
### CoCoMan joystick reference (November 11, 2026)
Brian explicitly authorized read-only access to his GPL CoCoMan checkout for
working joystick behavior. Relevant references: game/main.c controls and input
lifetime, game/keys.c shared button/keyboard rows, game/title.c stable button
scan. Observed base revision 439bd25ac46fbc7ecdfd67d98893a1cff90aef66 with local
main.c edits. No code/assets were imported and no CoCoMan files were changed.
Quadrapassel implements the learned safeguards in C using standard CMOC APIs;
it does not adopt CoCoMan's assembly or the VCC-specific input extension.
Binary file not shown.

After

Width:  |  Height:  |  Size: 8.0 KiB