2023 - November - Blastaway - Ended

@jabiruloQuote:
It looks like your devices have (also) analogue controls. Are they properly calibrated? Do you have the option to disable them and use the digital controls only?

@saimo

yes has an ANALOG button (like START/SELECT ones), but seems doing nothing, at least on amiga.

https://www.ewent.com/en-us/usb-double ... ucceeded-by-pl3330-ew3170

@jabirulo

I guess that the Y axis of (at least) one of the analogue sticks is sending jittering data. You should check that they are properly calibrated and send a stable 0 signal when not in use. Maybe the AmigaInput preferences could help with that (I don't know, as I don't have a device with analogue controls). Also, are you using them or the D-pad?

13 hours ago somebody paid a huge amount for Blastaway, matching the highest payment ever made for any of my games! The visits and the payments for Blastaway (and the same goes for all my games) are so scarce that I guess the generous user must be somebody from here, so... thank you so much!

@saimo

Using AmigaInput prefs test shows ok, no jitter of sticks.

using SDL gamecontroller for calibarting (took me a while) and then using testgamecontroller ok too.
I'll update my re-calibrated joypad to SDL/SDL2 github ASAP.

@saimo

Well deserved Simone and hope you get more purchases during this competition

@jabiruloQuote:
I have no idea what SDL gamecontroller and testgamecontroller are.
Did you try with the D-pad? If so, does anything different happen? What happens if you don't touch any control?

It looks like your problem is related to the workaround I have added to have digital controls work under Windows. More precisely, Windows (sometimes?) reports and handles digital controls as analogue (I have verified this personally) and SDL eventually spits out these values:
* up or left: $8000 (-32768 if seen as a signed integer);
* down or right: $7fff (32767 if seen as a signed integer);

So I have added this handler for the axes (analogue directions) events reported by SDL:

It does the same thing for both the horizontal and vertical axes, so, given that you're having problems only with the vertical movement, something must happen somewhere between your device and SDL. From the behaviour you described and the code, I guess that SDL, for the vertical axis, is (often/constantly) returning values other than $8000 and $7fff.

Unfortunately I can't offer any further help as I no longer have a working AmigaOS 4 machine, neither have I an analogue controller - and, on top of that, I don't have time to dedicate to development at the moment (and it's been so since quite a few months, i.e. after the release of Ring around the World).


@328gts

:)

Score update





PS. Saimo, keep up the good work, and donation will come to your pocket :D

The scoreboard has been updated. VooDoo takes the lead with 410,800 points!

@saimo

Using Dpad and stick same behaviour.

controllermap and testgamecontroller are part of SDL archive (test drawer).

Ok, no problem if won't/can't be fixed/workarounded.

TiA

@VooDoo

:)


@jabirulo

Quote:
Then SDL is detecting and reporting continuously vertical axis events. I can't do anything about that :/

Could you try the game on Windows using the same controller and possibly another controller with analogue sticks, please?

@saimo

ok, will try as the windows version ASAP.

My score 65045 https://i.postimg.cc/0NrXPmrn/IMG-20231110-004856.jpg

What a great little game! I will make a point to go back to itch.io and donate on this one.

Thanks for the scores @TSK and @MartinW! The highscore list has been updated!

@saimo

tested under windows 7 (the .zip not the installer version).

Plugged the gamepad and without calibrating launched Blastaway.exe and up/down works fine, doesn't get stuck, player moves smoothly

@all

One more generous payment arrived, so once again I guess it's somebody from here - thanks a bunch!


@MartinW

:)


@jabirulo

Quote:
Thanks for the test and the report!
Given that the Blastway code is identical for both Windows and AmigaOS, that tells us that:
a. the joypad hardware is OK;
b. the Blastaway code is OK;
c. the problem must be in the SDL library that the AmigaOS version of Blastway is linked to (1.2.13) or...
d. ... in the AmigaOS/AmigaInput drivers and/or in their configuration.
Since nobody reported this issue before (and, as far as I remember, controllers issues in general, other than the aforementioned issue caused by Windows) relatively to my games (Blastaway, BOH, Huenison and KOG), which all use the same code base and SDL library, I suspect that the problem is d.

If you have the SDK installed, you could try to build Blastaway against an alternative version of SDL as follows:
1. download the objects archive from https://www.retream.com/Blastaway/othe ... away-AmigaOS-objects.lha;
2. unpack the archive somewhere;
3. replace libSDL.a with another static version of SDL of your choice;
4. run make.
Then, put the resulting executable in the Blastaway directory and run it.
Note: I can't offer support if for whatever issue (dependencies, memory faults, etc.) you might stumble upon.

@saimo

Well deserved donations for sure! Blastaway is ace! Would be cool to see more for AmigaOS 4 from you in the future. Maybe QEMU is an alternative if you don't have a compatible computer? Keep up the great work!

post deleted

297870
https://i.postimg.cc/cL7GcVmz/IMG-20231112-021729.jpg