Need settings for setting up Star Wars Analog Controls

[secret80sman]

Hey Everyone,
I was wondering if anyone was using a B8 Flight Stick or other flight stick and had tweaked the analog control settings in MAME to get a "decent" performance out of it. I know it ain't gonna be a Yoke by any stretch but I am using the B8 which I understand is pretty much the ultimate flight stick and things are pretty jumpy with it. I have tried windows calibration but I can't say it is behaving anywhere close to creating a satisfactory gaming experience. 

Would a joystick map be something I would even want to look at? Suggestions please, I have searched and searched and didn't find anything about this, I'm sure there are plenty of others out there with flight sticks who don't have a yoke and could benefit from some insight.

Help!

[Havok]

I use the following settings, and it seems to work well for me:

AD Stick Y Key/Joy Speed (50)
AD Stick Y Reverse (Off)
AD Stick Y Sensitivity (80%)
AD Stick X Key/Joy Speed (50)
AD Stick X Reverse (Off)
AD Stick X Sensitivity (80%)

Deadzone .02 (in mame.ini)

I have a Ram Controls yoke and their USB interface, but I would think those settings should give you a good starting point and you can tweak the sensitivity to your liking...

[ids]

I'm hoping the previous post solves my problems, I'll try it asap.  I am getting really erratic movement in Star Wars, and seeing a strong penchant for centering.  I'm hoping the deadzone setting can at least solve the latter issue.

Using the multimeter, I see a clear linear progression from ~0k to ~5k on both pots.

Using the windoze (Win7 64b) joystick config thing, it shows the same.  Running the calibration and enable "show raw data" i see a clear linear range on both axes. (I cancel the calibration, as I understand it should not be used w/ the Ram Controls yoke and USB controller)

In the game, however, a range of movement near centre leads to no activity, until finally it jumps, at which point movement is often erratic, sometimes skipping around.  I know the game needs to calibrate, so I always start with giving it the full range of movement several times - doesn't help.

Anyway, I'll try tweaking settings.  In the interim, if there is any other advice, options, tips, etc, it would all be appreciated.  Fwiw, using fairly recent mame version, but forget exact ver# atm

Thanks

[Havok]

It won't hurt to calibrate in Windows. Keep in mind each time you fire up Star Wars, it needs to calibrate in game. Just start a game and steer the yoke in a few large circles. After that, it should work well.

** Edit **

Whoops - totally glossed over the part where you said you knew about the in game calibration.

So yes, the deadzone setting is what is causing your problem. I had the same issue until I started to tweak that one...

[ids]

Thank you very much - can wait to get home and try.  I've jury rigged a funny looking setup so I can play...until a more permanent solution is built.  Love this game, praying to all known gods, dead or alive, that the deadzone setting fixes it.  Doing the deathstar level with the "big deadzone" is quite a challenge.

[ids]

deadzone setting was a big help, but i still find erratic movement in the four corners...in a wide range in each of the four corners.  Here I am, off googling how to tie a noose

[Xiaou2]

So yes, the deadzone setting is what is causing your problem. I had the same issue until I started to tweak that one...

 Well, one has to wonder if this is Mame input design fault.

 The arcade machines deadzone settings are probably internally handled, and so the game is expecting the full range of values, to produce the proper results.

 If the values fall short, it might cause internal calibration issues... which may cause the jumping of the cursor.

 Couple that with any hardware translation from 5k to 100k.. and that might also be making issues.

 Some ideas that might help:

1) A means to be able to turn deadzone off completely is probably in order

2) Maybe a system which can give true 5k readings that are unaltered... but this would have to be both handled by mame, as well as by some of the hardware Mfgs boards.  (probably not working for any normal windows games/calibrations)

3) A means to select which type of pot then would be needed: 5k, 100k

4) A possible optional hack to the mame driver which changes the values to scale properly so that it does not de-calibrate the game consistently.

5) possible options for Arcade -vs- PC joystick.  Meaning, some PC analog pots just may not have enough values being used, because an arcade controller often uses gears for higher resolution / more values.

 New input options / ideas:

Pot = 100k / 5k
Controller (pot) Type = Arcade / PC
Deadzone = Y / N
Deadzone Values ( )
Analog Scale? (value,value)
Interpreter?  Y / N   (specialty encoder)
Interpreter type = converted values / no conversion

Edit:

 Another option might be to add gears into the mix:

Gear A = 30  teeth
Gear B = 10  (or  "none"  for both.. for pc based controls that have no gears )


 That might clear up a lot of problems with scaling PC vs Arcade controllers... as well
as provide accurate preserved data on what the controllers actually used.

[ids]

Well, here's where I stand; again, any help greatly appreciated...

Win7 64bit

mame106 32bit: yoke works fine (default deadzone, even)
mame141 64bit: yoke/star wars is unplayable; deadzone edit helps, but still unplayable

So...I could hack the hyperspin autohotkey script to launch different Mame versions depending on ROM selected, but really...

So, perhaps changes in Mame between these versions has broken something.  Or the 32/64bit thing is an issue?  Anyone with a SW yoke using Win7-64b/Mame141-64b?  If so, I'd love to see the mame.ini.  Or am I using a known busted version of Mame?

Thanks

(edit - typos)

[Bender]

seems to work on my XP x64 mame .129

[mikeporter2000]

Any luck on solving this?