WHDLoad MantisBT - StuntCarRacer
View Issue Details
0003512StuntCarRacer[WHDLoad Installs Games] slavepublic2016-08-05 13:352023-07-10 18:33
Assigned To 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
GFXCardPicasso II
ChipMem2 MB
FastMem0 MB
WorkbenchOS 3.9
KickROM40 - Kick 3.1
Summary0003512: Buttonwait bug
DescriptionWhen BW is enabled, and at intro screen you press a key (e.g. RETURN) and THEN joystick fire button to proceed, the keyboard won't work anymore and you can't enter pilot name or quit via QUITKEY.
TagsNo tags attached.
Attached Files

2022-05-01 12:11   
This bug seems gone as I can't reproduce it anymore. Maybe was a WinUAE issue? I'm now using WinUAE 4.9.1.

My current tooltypes:
  ExecutePostDisk=C:uae-configuration cachesize 0 cpu_speed max cpu_compatible false cpu_cycle_exact true
2022-06-27 16:29   
Tested again today and NO it's not fixed: when you are at the "Insert your name:" screen keyboard won't work...
2023-07-08 06:55   
I have updated the patch, the keyboard problems have been fixed.
2023-07-08 15:42   
Unfortunately I can still reproduce it. Launch the game with BUTTONWAIT, press SPACE, then RETURN, then joystick FIRE button... I can't enter ply1 name or quit the game.

Would be possible to move the screen a bit up (centered) when running with NTSC tooltype?
2023-07-08 15:44   
... weird, it seems random (timing dependent?). I reproduced it 3 times then I tried the 4th time and SPACE+RETURN+FIRE still worked fine...
2023-07-10 17:35   
Unfortunately I can still reproduce it randomly (it depends WHEN you press joy-fire after you pressed SPACE/RETURN?), let's say at least 1/5 times.
2023-07-10 17:45   
Sorry, but I will not look at this again, it is such a minor problem and made me waste too much time already. That it happens seemingly randomly doesn't make it any better. I will close this ticket, if I should be in the mood I may look at it again, but this will not happen anytime soon, if at all.
2023-07-10 18:29   
Believe me I understand StingRay, and I will be always thankful for your hard work keeping these games still alive and fixed on the Amiga, but... Why closing it and not leaving it as "acknowledged"? Maybe other devs can have a look? (Just asking, don't take it personally and don't get me wrong, but maybe is better to keep track of all bugs if actually still there to avoid duplicates)

Issue History
2016-08-05 13:35HexaaeNew Issue
2021-05-03 11:48StingRayStatusnew => assigned
2021-05-03 11:48StingRayAssigned To => StingRay
2022-05-01 12:11HexaaeNote Added: 0011268
2022-06-27 16:29HexaaeNote Added: 0011492
2023-07-08 06:55StingRayNote Added: 0013026
2023-07-08 06:55StingRayStatusassigned => resolved
2023-07-08 06:55StingRayResolutionopen => fixed
2023-07-08 15:42HexaaeNote Added: 0013032
2023-07-08 15:44HexaaeNote Added: 0013033
2023-07-10 17:35HexaaeStatusresolved => feedback
2023-07-10 17:35HexaaeResolutionfixed => reopened
2023-07-10 17:35HexaaeNote Added: 0013040
2023-07-10 17:45StingRayNote Added: 0013041
2023-07-10 17:46StingRayStatusfeedback => resolved
2023-07-10 17:46StingRayResolutionreopened => won't fix
2023-07-10 17:46StingRayStatusresolved => closed
2023-07-10 18:29HexaaeStatusclosed => feedback
2023-07-10 18:29HexaaeResolutionwon't fix => reopened
2023-07-10 18:29HexaaeNote Added: 0013045
2023-07-10 18:33StingRayAssigned ToStingRay =>