[1.31.0.29] Saitek advanced commands issues #3858

[lure]

In order to use Havoc, DB7 and Blen4 (and to a lesser extend He111) for CAS I use a "advanced command" in the Saitek SD6 software for one of the buttons of my Saitek X45. I map everything I can from the in-game mapper and only have this command and my TeamSpeak button mapped through the Saitek software.

The command I use is one that let me ride in the bombardier position (#2) as long as I have the button pressed down and when I release the button I go back to the pilot position (#1).

This is the command:

The usage of this command is:

1. Dive on target aiming from pilot position.

2. When it's time to drop bombs hold the programmed button down.

3. You are now in bombardier position and can drop as many bombs as wanted with the usual secondary fire key.

4. When bombs are dropped release the button and you're back in the pilot seat.

This command have worked perfectly for years but it does not work in 1.31 beta. When I press the button programmed like this the following happens:

1. Client switch to bombardier position as expected.

2. The screen freezes. The sound and simulation keeps running in the background. It's like a "freeze frame" effect where the video is paused.

3. When I release the button the client switch back to the pilot position and the freeze frame ends.

This bug is a complete show stopper for me when it comes to CAS bombing with any aircraft that can't release bombs from pilot position.

[oidin]

Bug...? Maybe its intended that "easy bombing" is over.

[lure]

Bug...? Maybe its intended that "easy bombing" is over.

Well I'm axis now so I will still have easy bombing if this is a intended feature.

[oidin]

Because of Stuka?

[lutorm]

Well I'm axis now so I will still have easy bombing if this is a intended feature.

Come on, it's clearly a bug. Having the screen freeze will never be an intended feature.

[haughtkarl]

Hmmm I'll have to try that with my Cougar. I currently have mine setup to jump from pilot to bombardier to drop x number of bombs and then return to the pilot's seat. I don't have a press and release macro running.

[GOPHUR]

Ticketed #3858.

not sure what would cause this but we'll try to take a look. We have changed the input method to a newer version. Also noted we are getting reports of issue with CH control manager.

[lure]

Might add that I have TrackIR also running. There's key-binding involved in that application also however that seems to work fine in beta.

[lutorm]

I just tried programming my X52 to do that, and it works fine for me. Tried both with TrackIR and without, and on tanks and bombers.

[lure]

I just tried programming my X52 to do that' date=' and it works fine for me. Tried both with TrackIR and without, and on tanks and bombers.[/quote']

Do you run Windows 7?

[lutorm]

Do you run Windows 7?

xp x64.

[GOPHUR]

That could be the clue.

[lutorm]

That could be the clue.

Turns out it isn't. I just installed win7 x64 and it still works.

[lure]

I'm using the saitek keybinding software (SD6) to bind the "center" feature in the Track IR software (TrackIR 5.0). TrackIR have center command on F9 as default and I've mapped a button on my X45 joystick to F9. This works n 1.30.

In beta the TrackIR center command does not work. It does not matter if I press my programmed saitek button or if I press F9 directly on the keyboard: Nothing happens.

If I alt-tab out and give some other window focus the command start working again.

If I alt-tab back into BE it stops working again.

[GOPHUR]

Lure, did you try another key? One that is not already mapped?

[lure]

I upgraded to .36 now.

EDIT: Crew switch does NOT work. Screen freeze in crew #2.

TrackIR problem is related to F9 key being used by both BE and TrackIR at the same time.

Note that F9 is default Center key in TrackIR and also default Screen shot key in BE. Both enabled as default settings.

Test procedure:

1. Start BE Beta and TrackIR with default bindings in both applications (ScreenShot = F9) (Center TrackIR = F9)

2. The TiR Center command does not work while running BE.

3. Open BE keymapper and "clear keymap" on the "Screen shot" command. Save.

4. Center command now works.

5. Go back into BE keymapper.

6. Go to "Screen shot" and try to bind F9 to it. Nothing seems to happen so you must bind some other button to it. I used Escape key.

7. Now notice how TrackIR center command stop working again. Even though we didn't get to actually bind F9 in BE!

8. Go back into BE keymapper again and "clear keymap" on the "Screen shot" command. Save.

9. TrackIR center command now works again.

I also notice that if you try a lot to bind F9 key useb by TrackIR in step 6 you'll end up crashing the TrackIR. You get Red or Red+Yellow LED on the TrackIR device and you will have to restart the TrackIR software to get it working again. Followed by detect controllers in BE.

Edited April 21, 2010 by lure

[GOPHUR]

Lure what's the status of this?

[lure]

fixed

EDIT... uhm.. or I just learned to live with it... will test.

Edited June 21, 2010 by lure

[lure]

Well kindof fixed.. I guess..

Having "Screen shot" mapped on F9 in BE does not disable the center command in TIR (also mapped to F9). The F9 button is completely disabeled though as far as BE is concerned. Screenshot does not work and I cant re-map F9 on anything as long as I got the TrackIR software running. But I guess that is expected as you don't want two completely different actions on the same key anyway.

[GOPHUR]

Yeah I would think they are intercepting the key stroke before it gets to us.

[GOPHUR]

What's the status here Lure?

[GOPHUR]

What's the status on this Lure?

[lure]

Sorry I forgot about this.

Yeah it seems fixed.

It works this way right now:

-No problem with the programmed saitek button in the original post.

-TrackIR center + screenshot on same key works now in such way that the F9 key is completely blocked from use in BE. If you have F9 as both center TrackIR and BE screen-shot key you will be unable to take any screenshots but there are no problems with the TrackIR software. F9 key is not detected in BE keymapper while TrackIR is running.

If I close TrackIR with BE running F9 starts working again in BE. If I the restart TrackIR again with BE still running F9 works for TrackIR again but is blocked in BE once again.

Tested on Windows 7 64bit and 1.32.5.7

[GOPHUR]

That sounds like our input system alright. When we get to redo that I'll be happy.

Thanks bud.