I've never tried, but I think I remember someone converting a Pole Position cabinet to MAME and setting the config so that LOW GEAR was always on (no key assigned, i think) and then HIGH GEAR was assigned (that's when the microswitch on the shifter gets engaged). I'll keep searching to see if I can find the build info from that.

First I tried to add a second switch in parallel with the first one, meaning that, when shiftting gears the other switch would have the same keystroke. This works, but there was an issue...wether in Hi or Low position there was a constant key press while the computer is ON which is a real bummer.

So i decided to go the other way around, ie. having the gear keystroke when the lever is neither in Hi or Low, so that there is a signal to the encoder when the lever is moved and neither switch is pressed, and I got by doing this simple connection...

It works like charm, the only catch is that you've got to have the lever in the right position at the beginning of the game.

PS - I can't really understand why the MAMEDev team don't add a simple mod to the input of this games, so that:

I knew there was a possible way to get this by recompiling MAME, but from what I saw in other threads, that doesn't always work, and as I'm not a real expert in recompiling MAME, I decided to go the other way.

I can see that this would work for 1), but not so sure about the others.

Agreed it would be very nice if MAMEdev decided upon a 'standard' method, as to my knowledge although some shifters work differently to others, shifter operation in Mame seems to be done however the driver author felt like it.

I can see that this would work for 1), but not so sure about the others.

Agreed it would be very nice if MAMEdev decided upon a 'standard' method, as to my knowledge although some shifters work differently to others, shifter operation in Mame seems to be done however the driver author felt like it.

The game that I tested this on was Out Run, and as it uses a single keystroke to change gear, so it works great. That keystroke is generated while the lever is moving and neither switch is pressed.

I got so excited playing it that I didn't even bother testing this on the others.

Well tested on Pole Position, and it's perfect

Tested on Chase HQ and S.C.I. and it doesn't work...bummer and considering these are two of my favourite driving games...bummer,bummer Chase HQ works just like you said......well back to the drawing board for this one

I'll report later

By the way, are there any other shifting methods in the other driving games?( except 4 gear, clutch, etc... which of course are a different matter)

The game that I tested this on was Out Run, and as it uses a single keystroke to change gear

Sorry, I know there are games as I describe in 3), I thought OutRun was one of them. I can't think of another off the top of my head...

Quote

Tested on Chase HQ and S.C.I. and it doesn't work...bummer and considering these are two of my favourite driving games...bummer,bummer Chase HQ works just like you said......well back to the drawing board for this one

Yeah, bummer I actually have a 4-speed shifter, so have a microswitch for each gear (I use 1st/2nd for lo/hi). It works pretty much fine with all these games, but the 'toggle' type games can get confusing as it doesn't matter which position the stick is in...and it can get out of sync...also you don't know which gear it is in to begin with.

Quote

By the way, are there any other shifting methods in the other driving games?( except 4 gear, clutch, etc... which of course are a different matter)

Not that I know of, unless a new method(s) has been added since Mame ~0.99.

I've never tried, but I think I remember someone converting a Pole Position cabinet to MAME and setting the config so that LOW GEAR was always on (no key assigned, i think) and then HIGH GEAR was assigned (that's when the microswitch on the shifter gets engaged). I'll keep searching to see if I can find the build info from that.

If you look through my old posts, I linked to the original thread on recompiling for pole position.Works great on my driving cab (Using an atari shifter)

If you look through my old posts, I linked to the original thread on recompiling for pole position.Works great on my driving cab (Using an atari shifter)

Thank you, that should come in handy

However, I have other problems with Pole Position...I started using v0.123 and now v0.125 as analog pedals do not work properly with some older versions (I was using v0.99). But there was the problem of refreshspeed not working in v0.123 (stuttery sound), and now in v0.125 refreshspeed causes some horrible noises to occur. So I will probably wait for these issues to be worked out...

Well, finally I reached a working solution, and it turned out to be an easy one.

Using the above connection, I added a two position switch like this one

It will work as a selector for two different modes with the same gear shifter, and it will all go like this

Mode 1 - works in games like Chase HQ or S.C.I.

Mode 2 - works in games like Out Run or Pole Position ( toggle method), this should also work in games that use two different inputs for Hi and Low, as long as you assign them the same letter. Like Minwah mentioned I can't really remember any game either, but if I come across one, I'll post later.

In Mode 1 there's no catch and works perfectly, in Mode 2 the only catch is that you have to engage the right gear before the game starts( as an example Out Run starts in Hi and Pole Position starts in Low).

The two position switch is really small and can go unnoticed anywhere in the CP. Above the shifter, underneath it or in here:

Finally, if you don't want to have a constant key pressed when not playing, just engage Hi Gear in either Mode.

This suffers with the same flaw with the toggle method - the stick needs to be in the correct position to start with (and also eg taking out of lo and putting it back in lo messes up the gear positions).

Another thing is that there is no way to prevent a constant keypress. I would suggest a simple switch in the ground line to basically switch the shifter on or off.

This suffers with the same flaw with the toggle method - the stick needs to be in the correct position to start with (and also eg taking out of lo and putting it back in lo messes up the gear positions).

Another thing is that there is no way to prevent a constant keypress. I would suggest a simple switch in the ground line to basically switch the shifter on or off.

Tested this connection, and here's my report

1) (toggle) - Gear set to Input 1 (gear only changes when Input 1 is pressed) doesn't work Gear set to Input 2 ( gear only changes when you release input 2, basically same as above) doesn't work Gear set to Input 1 and 2 (gear only changes when going from Input 2 to Input 1) doesn't work

2) (hold=lo) - Works fine as long as you assign gear to Input 1

3) (2 inputs) - Same as third attempt in 1) (toggle)doesn't work

Basically this connection doesn't work because both Switches are in there doing the same thing, Input 2 only sends a signal to the encoder when you release it.

1) (toggle) - Gear set to Input 1 (gear only changes when Input 1 is pressed) doesn't work Gear set to Input 2 ( gear only changes when you release input 2, basically same as above) doesn't work Gear set to Input 1 and 2 (gear only changes when going from Input 2 to Input 1) doesn't work

When you say 'Input 1 and 2', do you mean 'Input 1 OR 2' (in Mame, if you see what I mean?). ie either can be pressed? I assume so, but just to make sure you didn't really mean 'and' (ie both have to be pressed at once)...

Quote

Basically this connection doesn't work because both Switches are in there doing the same thing, Input 2 only sends a signal to the encoder when you release it.

But when Input 2 stops sending a signal, Input 1 starts.

I don't doubt what you say (I haven't actually tried it), but can't really see why this wouldn't work. Lets call the Normally Open contact 'A', and the Normally Closed one 'B'...say 'A' and 'B' are the keys the inputs of the encoder are mapped to:

Lo gear = NO = AHi gear = NC = B

In Mame, gear = 'Kbd A or Kbd B'

There is always either A or B being sent, depending which gear is selected. It only changes when you change gear. So it should work....shouldn't it?

Quote

3) (2 inputs) - Same as third attempt in 1) (toggle) doesn't work

I don't see why this doesn't work either...NO is one gear, NC is the other, job done?

(again, not doubting your results, just trying to get my head round why it wouldn't work )

When you say 'Input 1 and 2', do you mean 'Input 1 OR 2' (in Mame, if you see what I mean?). ie either can be pressed? I assume so, but just to make sure you didn't really mean 'and' (ie both have to be pressed at once)...

I meant assigning (in MAME) both inputs to gear shift, as the games that use this method only use one keystroke to change gear.

I don't doubt what you say (I haven't actually tried it), but can't really see why this wouldn't work. Lets call the Normally Open contact 'A', and the Normally Closed one 'B'...say 'A' and 'B' are the keys the inputs of the encoder are mapped to:

Lo gear = NO = AHi gear = NC = B

In Mame, gear = 'Kbd A or Kbd B'

There is always either A or B being sent, depending which gear is selected. It only changes when you change gear. So it should work....shouldn't it?

I don't see why this doesn't work either...NO is one gear, NC is the other, job done?

(again, not doubting your results, just trying to get my head round why it wouldn't work )

You're getting this the wrong way around. A NC connected switch sends a signal when it's not pressed, so when you engage the gear shifter (ie press the switch) the signal is cut off.

You can do a simple test to try any connection, just grab two switches (any kind), connect them in which ever way you want, open Notepad and test the keystrokes

I meant assigning (in MAME) both inputs to gear shift, as the games that use this method only use one keystroke to change gear.

But, using AND (both inputs pressed at same time) or OR (either input can be pressed)? Both can be done in Mame, but the latter is needed here for this to work.

Quote

You're getting this the wrong way around. A NC connected switch sends a signal when it's not pressed, so when you engage the gear shifter (ie press the switch) the signal is cut off.

I know what NC is (I didn't say anywhere NC connects when the switch is pressed?)... Effectively using these 2 contacts on one switch, they are two inputs to your encoder. So although the NC signal is cut off when the switch is engaged as you say, the NO signal connects. So with these two terminals connected to two encoder inputs, one of the inputs is always 'live'.

Quote

You can do a simple test to try any connection, just grab two switches (any kind), connect them in which ever way you want, open Notepad and test the keystrokes

I don't need to In the connection I described, either 'A' or 'B' would be constantly sent, depending whether the switch is closed or open. At no point would no keystrokes be sent. (edit: dependant on keyrepeat, but either way, one of the inputs would always be live).