Hallo Franz..

über die ganzen Jahre habe ich an dir gesehen , dass du extrem Motiviert bist.
Da ziehe ich meinen Hut

Vielen , Vielen Dank ...


Gruß
Mark 1

Great, works perfectly - many thanks!
This 'DATA' dial seems to be a bit more complicated - my first trials were not successful.
For read() it's not allowed to add a field(0x18), so I've tried it this way(?):
io = (ioport.ports[":IN.0"]:read())&0x18
But a following command
ioport.ports[":IN.0"]:field(0x18):set_value(io)
changes the 'MENU dial again!?

What I'd like to do is to switch to "P-P on" mode, and later back to "P-C on" again - the first is done by Down-Right-Right-Right-Up.
Could you please tell me the exact command sequence for this task?

__________________
Meine Webseite: https://fhub.jimdofree.com/

void analog_field::set_value(s32 value) for analog_field 0x18 should not be able to affect analog field 0x07 (the mode dial). If it does, maybe a bug in MAME? Or a mistake in your script?

I don't know the exact steps, I haven't tried it.

Well, it's rather my wrong script.

I've tried it with these steps:
but the data dial didn't change at all, only the menu dial changes with each of these commands.

__________________
Meine Webseite: https://fhub.jimdofree.com/

io = ((ioport.ports[":IN.0"]:read())&0x18) >> 3
or maybe / 8 if LUA can't do shifts

Then
if io == 0:
do sequence: 0, 1, 3, 2, 0

or if io == 1:
do sequence: 1, 3, 2, 0, 1

and so on

Also, in case the user has put it into the Options menu already, start the menu dial with ready, then go to options.

Well, no matter what values I set for field(0x18) - the data dial doesn't change at all.
Could it be that this data dial is a digital port (instead of analog)? IIRC I've seen in ioport.cpp that this set_value() only works for analog ports!?

But no problem, I don't want to annoy you (and me) any longer, so I give up now.
I only needed to change the data dial for using the Edit-Mode (Player-Player) - a function that would be useful but not absolutely necessary.
More important was your first hint about clear_value() to reactivate the cursor keys again!

Thanks for your help,
Franz

__________________
Meine Webseite: https://fhub.jimdofree.com/

I didn't try it, but maybe the value needs to be shifted.
so not 1,2,3, but 0x08,0x10,0x18

Hi,

dank hap's Hilfe konnte ich nun auch das Problem mit den (nach bestimmten Funktionen) nicht mehr reagierenden Cursortasten beheben.

Außerdem habe ich nun doch noch eine Methode gefunden, um den Edit-Modus durch direkte Änderung eines Bytes im RAM ein- und wieder auszuschalten (wobei das Ausschalten sich ziemlich kompliziert gestaltet hat).

Kurz gesagt: jetzt geht also beim Saitek Blitz im Prinzip alles, was auch bei den anderen Engines funktioniert, auch der Edit-Modus - nur der Setup-Modus fehlt, aber der ginge nur, wenn man auch die Cursortasten für das DATA-Einstellrad per Plugin steuern könnte, was aber eben nicht funktioniert.

Also einfach das Blitz-Plugin hier im Anhang nochmal herunterladen - die Einträge in die WinBoard- und Arena-Konfigurationen kommen dann mit der nächsten Version.

Grüße,
Franz

Angehängte Dateien

Blitz_Plugin.zip (1,1 KB, 6x aufgerufen)

__________________
Meine Webseite: https://fhub.jimdofree.com/

I've already tried this before with <<3, but that didn't work,too.
Maybe it's in fact impossible to handle this data dial with any usual ioport commands.

But it's no problem, because I could now also switch to and from Player-Player mode by directly manipulating a byte in the RAM.
Of course it had been much easier if you had implemented these 2 dials with 'normal' buttons that could also be used with the mouse and be 'pressed' in the plugin. I've looked at the driver, but my MAME knowledge is not sufficient to make the necessary changes there.

Thanks anyway for your help!

__________________
Meine Webseite: https://fhub.jimdofree.com/