Saitek SST software / AV8R problem

[Bucic]

Long story short - a key combination e.g. RCtrl+PgUp is programmed to joystick button and confirmed working using Saitek Profiler built-in tester but Black Shark (Controls menu as well as in-game) sees only PGUp presses. Does anyone know what can be the problem? All works fine with other sims and I've already tried clean reinstalls of latest drivers and software.

[HitchHikingFlatlander]

Have you tried to switch it to left control? Worth a try can't remember if DCS rctrl/lctrl is specific or not but in most other programs you can use either ctrl button. I've programmed the AV8R with SST as well and haven't had a similiar problem.

[Bucic]

It is specific. The command is Right Ctrl+PGDwn for example (right engine cut-off) and I've programmed a command in SST as such - Ctrl+PGDwn. DCS sees only PGDwn. Can you try to program the xact command in your SST software and check it if it's working in DCS (both in UI and in-game)? It would explain everything and would tell me if I should hit Saitek forums instead (I would prefer not to...).

[crazysundog]

Yes, I've had this problem. I resolved it by changing the commands in Blackshark to be [Application+PGDwn]...the Application key is also known as right Windows key I think. (to the left of rightcntl)

 

Then program the SST software to match the keycommands in Blackshark!

[Bucic]

Thank you very much, crazysundog! I wonder if it should be fixed by ED or Saitek. It would be a chore to remap more than two commands and can cause possible conflicts or lack of free key combinations.

[Feuerfalke]

You have to map this as a macro, not as a single keystroke to make it work. :smilewink:

 

Works fine here, this way.

 

 

The problem seems to be that the software translates the normal keypress programming in a very short impulse, apparently to short for the inbuilt delay of some critical functions in DCS. The "problem" doubles with low framerates, but this is not limited to DCS.

Edited September 17, 2009 by Feuerfalke

[Bucic]

Thanks Feuerfalke!

 

Do you guys have a profile - AV8R for DCS BS? I haven't found anything on the forums.

Edited September 17, 2009 by Bucic

[Bucic]

There is a solution!!!

 

Theres three things ive changed regarding my X52pro-

 

1. Im using the updated input.dll that was offered up as tempory fix due to a know bug.

 

Link- http://files.filefront.com/13879427

 

In INPUT game was discovered sad mistake. The game does not recognize the key combinations in the case of utilities adjust INPUT various programmable joystick profile joysticks.

For example, this means that when you press the joystick button causing klaviaturnoe combination "Ctrl-C" game sees only a "C".

This is not the system settings INPUT inside game. That is, those who configure tip through the game interface may not have to worry.

We certainly correct this bug in the patch, but now, so you can use native utilities adjust joysticks, we vykladyvaem new library NewInput.dll, which is attached to attachmente.

ATTENTION! The library did not pass the full cycle of testing, so its use is at your own risk.

Installation:

1. Create a backup copy of the original file C: \ Program Files \ 1C \ Eagle Dynamics \ Ka-50 \ bin \ stable \ NewInput.dll (376 Kb)

2. Unzip the new file NewInput.dll (380 Kb) of attachmenta and replace the original.

 

2. The second fix was supplied by "Slayer" some time back.

 

-The SaiDOoutput is a service, it is under the services tab of Task manager , not the processes.

-Do yourself a favor and remove the lua-direct_output.dll from your "C:\Eagle Dynamics\Ka-50\bin\stable\" folder...or wherever you have installed the game.

 

This should take care of most of your problems

 

Link- http://forums.eagle.ru/showthread.php?t=34158&highlight=x52

 

3. I edited my DCS controller config to remove all DCS asigned input commands except axis commands. eg: if I open my DCS config you only see keyboard commands, and axis. Do this in both "Real" and "Arcade" configs. If you dont do this then your DCS and SST profile may conflict.

 

Source: http://forums.eagle.ru/showthread.php?t=42425

[Feuerfalke]

DON'T!

 

The NewInput.dll will crash the patched version of BlackShark!

[Bucic]

I haven't updated yet. I installed it just a few flight hours ago and I will probably have to unistall it soon for another few months.

 

So you mean that 1.0.1 does not fix this issue? It looks like it doesn't http://forums.eagle.ru/showthread.php?t=43547

[Feuerfalke]

I don't know if 1.0.1 fixed the issue, but as noted in the statements on the forums and IIRC in the readme as well, several things about input-recognition have been changed. Apparently enough to make the old NewInput.dll no longer compatible with the new routines.

 

If the problem persists, maybe ED will release an updated version of that dll-file?

[HitchHikingFlatlander]

Thanks Feuerfalke!

 

Do you guys have a profile - AV8R for DCS BS? I haven't found anything on the forums.

 

 

I do have one but I've modded my AV8R to be a collective control (see respective thread here) and the commands are all collective related, so if your using yours as a stick it wont apply.

[thinkr]

HAVE THE EXACT SAME ISSUE!!! Any fixes as of Recent? It does the same thing with me LCTRL+T doesn't work and even the windows key combo I have does the same thing it just presses the key not the Ctrl Addative. I posted my problem in the Saitek forums here. :joystick: READ the latest Post in this topic... http://www.saitekforum.com/showthread.php?t=18209

 

Here's what I said...

Oh well now it seems there is a new problem.

I set Trimmer Reset to "LCtrl+T" Activated by holding the Pinkie switch and pressing the "C" button under the MODE1+Pinkie drop down. I thought everything was fine and I even tested it in the profile and it works it says "CONTROL T control T" when i press it.

Edited January 16, 2010 by thinkr

[Bucic]

I don't know. I think the best way would be to ask on the Bugs and Problems section of the DCS forums if this has been reported already and is being under investigation. While you're at it you could also ask if acknowledged bugs are assigned with numbers and in such a case what bug number is/will be assigned to this bug.