ruprecht

+1, good for developer updates

This is correct also for the Targeting Mode Control Panel and Master Caution Reset in my experience.

It's a BetaInnovations GammaRayV2, wired direct to the switches. The issue's definitely in the software - it seems it only sends key down, and for most apps that's enough. Will keep poking around, thanks

Hi Gadroc, The keyup event is my issue. I've built a Weapon System Control Panel as seen here: You can see at 1:30 when I press Reset, the light stays lit and doesn't go off until I hit backspace. The pushbutton is mapped to the key backspace, but it seems that the software only sends the key down event, not the keyup event. I'm wondering if theres any way to force a keyup via keyboard mapping rather than Lua direct. Appreciate that this may be a "feature" of the specific keymapping software I'm using (BetaInnovations F4IM).

can the stop action be bound to a key? e.g. for master caution or the targeting mode control panel? cheers

Vista and Win7 had fullscreen multimonitor disabled due to some issue with DVD licensing or something. It's across all applications and games, not just DCS. the issue is not present in XP.

1.0.1 didn't (and can't) fix the windowed mode issue. That's a limitation of the OS.

Paying careful attention to this, I did notice that when I was careful to keep the Shkval circle inside the Vikhr reticle for both shots, they came off in pairs; and when I allowed the recoil from the first shot to take the second out of parameters, the second shot failed. In the second case, I definitely get uncommanded launch when the cooldown comes off if a target is still locked. It's like the fire control system "queues" a release, which is blocked while the first missile is inflight, but unblocked when that cooldown comes off. This doesn't seem to be the issue I get, but thanks Yes, it is set to the default simple keystroke for weapons release. That said, I have noticed a slight difference between keystrokes issued via 3rd-party software and direct keyboard keystrokes. For example, if you assign targeting mode reset (Backspace) to a switch in the betainnovations keymapping software, it works but the switch in the sim "locks down". Pressing Backspace directly doesn't give this issue. However, testing in Notepad etc reveals only a single Backspace, so I'm not sure exactly what's going on, and I say again that I never get uncommanded release if I don't touch the salvo switch. Still trying to get to the bottom of it.

I know, it's insane isn't it. I found the same with the Master Caution light - which starts off at 0.0, then on at 0.3, then off at 0.2 etc. What is so hard with 1=on, 0=off? Trial and error my friend!

Having not fired an aircraft-mounted weapon for real, I'm just speculating, but there would be vibration and recoil through the airframe, but generally not through the controls in a modern aircraft. I've heard that a long enough burst from the A10's cannon can actually stall the aircraft due to the recoil. While I agree that the FFB effects are a little bit hollywood, remember that this is the developer's way of giving the player the sense of airframe vibration through a sim that usually offers no other way to do it. Until devices such as the 3rd Space vest are commonly in use, that is the only tactile feedback method available and is not really meant to simulate *control* shaking per se.

exactly - like the cougar force mod

Interesting Flim - I must say I started thinking like Pogo, that it's a stick in search of a sim. Certainly for me, as soon as I discovered it probably wasn't force feedback, I started thinking about the G940 instead. What does the X65F have for you over the Cougar, other than the split throttle, that makes it worth the money? 300+ euros for me to go from an X52 to X65F - which it seems gives me only force transducers and a split throttle - doesn't seem worth it to me, when the majority of my simming in the next couple of years will probably be DCS:BS and A10C, plus maybe some Rise of Flight. If I still played a lot of the Falcon franchise, things might be different though. It seems the decision will come down to force transducers or force feedback (notwithstanding cost and pedals). If the X65F turns out to be both tensometric and force feedback through some technical wizardry, I'll have one faster than you can say "how do I get it in the house without the missus seeing". Though even now I'm wondering if a centre-mounted tensometric stick would still work well for BS/A10 even if not FFB. I'm pretty used to the trimming after all, and it removes the need to mod it with a shaft extension...

Just finished my Weapon System Control Panel. Pretty happy with the results! Though I think performance will increase a bunch when I refactor it for UDP instead of TCP. Only problem is I can't run my custom C# driver client on the sim rig, possibly something to do with Win7_64. It runs fine over the network to my XP_32 machine. Any ideas? Do I have to compile specifically for 64 bit, or is it a User Access Control issue or something? I install it as administrator, but it fails install and I can't even run the .exe directly, silently crashes every time.

FYI, the problem was my soundcard. I had an Asus Xonar DX PCIe which is supposed to be a high-end card. When I swapped it out and instead used the PCIe breakout board that came with my mobo, not only do I not get any stutters any more, but I'm hearing sounds I've never previously heard. It's possible that it is a driver issue with Win7_64 support I guess.

Posted a track here showing the viks launching singly when long was selected. The launch is at about 24:45, on the Abrams, after I drop the Kiowa. http://imagehost.radsy.com/VAAF/VAAF_Expo_02_Convoy_GoodRun.trk I couldn't reproduce the uncommanded launch issue tonight, as I say it is inconsistent and sporadic. If I encounter it again, I'll save the track. And for some reason when I ran the track, I crash at about 33 min, which is a shame because I didn't in the original mission and went on to do a really nice quickstop :)

Reasonably sure, and I have checked but will recheck. Theoretically though, if the trigger was flashing, I would see this issue regardless of the switch position. If I never touch the burst switch, I never see this issue.

Amazing rig. I believe the 4 camera configuration will unavoidably give you these areas of overlap and your only real area of control is in your FOV and zoom settings. Tweaking these might help you lose the overlap, but may create other issues such as reducing your FOV to an unacceptable level. I also use TH2G and use a single centre view spread over 3 monitors. There is some weirdness caused by the bezels (which, to be fair, goes unnoticed after about a minute into the flight), but there is no overlap. Good luck and please post photos of results. Cheers

Quite possibly, and I will check the mappings, but I thought it a good idea to see if anyone else had experienced it. Seems that you have also seen the inconsistencies in vikhr pairs? I will record one tonight.

I've observed a couple of wierd things that seem to be related to the long-medium-short burst switch on the Weapon Status and Control panel. Firstly re Vikhrs. Often if I select a medium burst for a double-tap, only one missile will come off the rail when I shoot (and yes, I do keep the trigger depressed for a couple of seconds). This is using auto mode with a valid lock and launch authority. This in itself is confusing and inconsistent. Additionally, often when this happens, if I keep the target locked, as soon as the 6-second cooldown comes off, I get an uncommanded launch of 1 or 2 missiles. What the? I have also observed uncommanded firing of cannon, rockets and vikhrs under the following circumstances: - I have previously fired vikhrs or rockets using a long or medium burst - I have reset the shkval - I uncage the shkval - I select cannon, rockets or vikhrs - whoooooosh uncommanded launch This never occurs with short burst selected. Is this a bug or a feature?

Check the link, but it's at QUT Kelvin Grove. Not sure I'm afraid, I'm holding out for the Saitek X65F.

You'll be able to buy (or win!) a G940 at the Oz Flight Sim Expo in Brisbane 10-11 October. Say hi if you come along, I'll be the guy in the dark grey cockpit with the ACESII seat flying DCS. Also if you want to hook up with some other aussies flying DCS, try vaaf.net cheers

1. I googled "armored vehicle recognition guide" and the fourth result was a decent PDF from EECH. 2. I usually release pairs unless I'm hitting him from behind. Viks are the best weapon you've got against Abrams, though it's possible to kill them with AP cannon.

... and the A-6

Standard procedure when storing and datalinking target is: - Ground-stabilise Shkval over target and lase - Select target type - press MEM to store (icon appears on ABRIS) - press target type to send - press aircraft # to send to (or all) - press target type again to cycle to specific target to send (will flash on ABRIS) - press SEND No turning off Shkval required.

My new standard checklist. Very nicely done indeed.