Author Topic: WinApe - strange key combination issue (moving right + up or down?!?!)  (Read 1975 times)

0 Members and 1 Guest are viewing this topic.

Offline Xyphoe

  • 6128 Plus
  • ******
  • Posts: 890
  • Country: gb
    • GX4000.CO.UK
  • Liked: 320
  • Likes Given: 179
Hi there,

Strange issue occurred today with some key combinations failing that previously were fine!

For some reason using the joystick (joystick enabled) and mapped to keys in WinApe - whilst moving to the right, the up or down function does not respond. But fire does.

So I tried reconfiguring the keys in the game so that O - P - Q - A - K = Left - Right - Up - Down - Fire
Now the right + up/down worked (with fire), but up+left+fire didn't! It accepted and moved the player up and left, but no 'fire'.

Very strange!

This has always worked fine for me for god knows how many months/years!

The LAST thing I did with WinApe, and I have a few versions installed - is bugger about in previous versions so I could record my Vendetta longplay, because all dumps crash in the later versions of WinApe but it worked in WinApe 2.a13. At some point I accidentally had multiple copies of WinApe open and I think I made some changes in Settings (I can't remember what) - I'm wondering if this has messed it up? I get the same key combo problem in the versions I have installed now!

Please help if you can, this is delaying me doing new videos :(

Thanks!

(edit - I'm on Windows 7, usual desktop PC)

Offline Xyphoe

  • 6128 Plus
  • ******
  • Posts: 890
  • Country: gb
    • GX4000.CO.UK
  • Liked: 320
  • Likes Given: 179
Just wondering, does WinApe share common settings across versions installed?

I'm not 100% sure, but it looked like the .kbd settings loaded the first time I opened the usual version of WinApe I use seemed to be the ones I used in previous version (that was used for my last recording), I think I may have loaded my usual file not thinking too much about it before I realised something was up.

Does WinApe store anything in the registry? I've only found one entry in regedit but it doesn't seem to contain a value of interest.

I also found a WinApe exectuable in Users > [user] > AppData > Local > Temp > WinApe

Would copy and pasting the WinApe.ini file help?

Offline Executioner

  • Supporter
  • 6128 Plus
  • *
  • Posts: 783
  • Country: au
  • WinAPE Developer
    • WinAPE
  • Liked: 391
  • Likes Given: 60
Hi Xyphoe,

Yes, you can copy the WinAPE.ini file from one version to another. It's weird that you're just having an issue with that in WinAPE. I had the same issue trying to play a ZX Spectrum game on JEMU yesterday. I wouldn't be surprised if M$ has buggered up the Windows 7 x64 keyboard drivers :)

Offline Executioner

  • Supporter
  • 6128 Plus
  • *
  • Posts: 783
  • Country: au
  • WinAPE Developer
    • WinAPE
  • Liked: 391
  • Likes Given: 60
WinAPE doesn't use the system registry at all. I hate the registry because it's slow and it's much easier to find and read/edit INI files.
I just tried Freddy Hardest with the keys QAOPK and it all seemed to work fine on my Win 7 system. Which game are you trying to play?

Offline Xyphoe

  • 6128 Plus
  • ******
  • Posts: 890
  • Country: gb
    • GX4000.CO.UK
  • Liked: 320
  • Likes Given: 179
Wow, good timing - as I was heading over here to post that I've got it working now!

I think it must be to do with how WinApe saves profiles and data to the .ini file when closing. Somewhere along the line with having multiple versions of WinApe open simultaneously it's got itself in bit of a tiz!

I was ready to delete all versions off this PC and copy across the working one on my other PC... when I thought I would test again first and noticed - a different 'profile' was loaded and I had a black screen! Plus the .kbd file loaded was for an old version of WinApe?

After selecting the right profile and resetting, then choosing the right .kbd file - then closing WinApe. Then re-opening - it all loaded 'as it should'.
Strange. As I did muck about with something similar last night.

Anyway, the upshot is it is now working. Why it caused some 'key clash' or combination issue is a mystery to me.

Last oddity is the snapshot of the game I was testing in (Gun.Smoke) taken last night still had the issue, but resetting and loading the game again it was working fine and no key clash!

Very odd.