From my experience, RWR can warn you when you’re close enough to the SA-10 site but not sure if it’s consistent every time… Also, load up an HTS pod even if you’re not packing HARMs since it will increase your situational awareness, unless you’re 100% sure that you’re not dealing with serious SAMs like SA-6/10/11/15/17… Anyhow, when you’re dealing with an SA-10, the HAD page will provide you with enough info for you to determine whether or not the SA-10 fired on you… Basically, once the 10 turns red (meaning that the radar is tracking you) you can be 99% sure that the SA-10 fired on you… If you see the 10 turning red and you’re not taking evasive action, you’re asking to be shot down :mrgreen:

Have you checked “IVC Client.ini” in BMS-install-folder>Bin>x86>IVC ? I haven’t tested this out yet but I guess it’s definitely worth a shot…

PMs have been sent to Aries101 & WurminatorZA… They might just fit right in the squadron I’m part of…

@supanova:

I’m trying to understand the benefit of using Snowplow over GMT.

You should not confuse SP with the FCR’s sub-modes (i.e. GM/GMT/SEA)… SP simply fixes your FCR at 5/10/20/40 (depending on the selected range on the upper left side of the FCR) miles in front of you & keeps it there, thus not keeping the FCR on a fixed position… Once you press TMS up the FCR’s cursor position will become fixed and the FCR automatically gets out of SP mode… Now if you want to put your cursor back at the original steerpoint you simply press CZ (which should be highlighted at that point if I got it right)… An alternative exists in simply changing to the next steerpoint & going back to the previous one given that the FCR is no longer in SP… Another benefit aside from what LorikEolmin said, instead of having to slew around to find your target you can simply fly the plane pointing the nose in the direction where you want to look for potential targets…

@LorikEolmin:

Actually when you see them, you usually have a problem

Depends what’s waiting for you down there… In case it’s AAA and/or IR SAMs, then you have a serious problem :rofl:
Small arms fire can also be dangerous (in the sense that it can damage your plane & render you inoperable for combat, forcing you to RTB) if you don’t react accordingly but definitely a lesser problem that AAA & IR SAMs… But suppose you would fly over an SA-5 AD battalion that’s on its own, you should be good since it has no AAA, IR SAMs or small arms, that is in Korea KTO AFAIK… Wouldn’t know about other theaters but I assume an SA-5 AD battalion is the same in all theaters?
Anyway, in general, you don’t want to go low unless you’re dealing with a bigger threat like SA-6/10/11/15/17 although if they have a direct line of sight on you, you might as well just turn back & try to go around them cause those guys are no joke, especially the SA-10 :mrgreen:

K the output of the script is looking fine so I’m guessing the problem lies somewhere else now…

@freemind:

If I go to the Game Controllers properties/Test the x and y axis don’t move.

Ok so that implies that it’s an issue with windows not recognizing the axes correctly though I’m currently clueless as for what the issue can be…

@freemind:

Do I have to do anything in the HOTAS Cougar Control Panel?

Perhaps, the fact that I don’t have a Cougar makes things a little more difficult… What options do you have in that control panel?
What I could also do is try to remotely login to your computer (with Teamviewer preferably since that’s what I have) so I can dig a little deeper…

One question though, do you have the throttle of the cougar too? If so, is it hooked up? Not sure if that’s a problem but if you got the cougar’s throttle, it’s definitely worth trying to see what happens if it’s hooked up…

@ZeeMan90:

Some Surface to Air defence systems will not emit radar emissions. So you basically will not get a radar warning when said SA is fired upon you.
The SA10 is such a platform.

Not quite correct… SA-10 does in fact have soft-launch capability which is what you’re describing… Though it still emits radar waves which can be picked up by the HTS… If you see the 10 turning red on the HAD, you can be 99% sure that it fired on you… I also noticed that if you’re close enough to the SA-10, you will get a missile launch warning…

I think what Snowboat_mass is experiencing is simply a narrow radar beam which is only picked up by the person targeted… I’ve had multiple occasions where I (as a host) would pick up an SAM on RWR while my wingman who’s flying in close formation was not picking it up & vice versa… That’s why you should always call out “MUD (optional SPIKE if you’re getting locked up) SA-X Y-O’CLOCK” (with X being the type & Y being the directing), waiting for a response that either goes like “ROGER”, indicating your wingman sees the same, or “NAKED”, indicating your wingman doesn’t see it on his RWR… Once you’re being fired upon you should call it out, intra-flight it will suffice to simply say “DEFENDING X”, where X can be anything going from a SAM up to a type of enemy aircraft… If you’d be calling it out to inter-flight you would go all the way saying “ENGAGED DEFENSIVE X, BULLSEYE YYY Z MILES”, again X is type ranging from SAM to aircraft, YYY is the direction & Z is your distance…
You might’ve known all of this already though I thought I’d state it for consistency & while it might sound overdone, it definitely increases situational awareness which is what it’s all about :mrgreen:

It’s normal for the Cougar to disappear cause it becomes part of “Thrustmaster Virtual Game controller combined (root)”… Though it’s still weird that when you assign the axes they still don’t move… Can you verify the same thing happening in “Devices&Printers>ThrustmasterCombined>RightClick>GameControllerSettings” then select “Thrusmaster Combined” again & press properties…
Regardless of whether or not the stick moves there, it’s still not recognized correctly in BMS but it might help point in the right direction…

Not necessarily… Once you’ve found your target & supposing you were in snowplow mode, you would press TMS up & at that point the radar cursor should stick to the selected position… Your targets won’t be moving too far away from that position although it might be interesting to mark the position in case your accidently move the cursor off target… Also mind that the targets may stop moving which will make them disappear from your FCR as long as you’re in GMT mode, so when that happens you need to change back to GM mode… Another thing you could do is, once you found your contact, maintain visual on it through the TGP so you don’t lose them… As for the approach direction, it all depends on what munitions you are using… LGBs should make much of a difference where you approach from as long as you’ve got enough altitude though when you’re rolling in with clusters in CCIP for example, it might be easier to approach parallel to the target’s moving direction…

& yeah, HOTAS rocks in these situations :mrgreen:

@Wayc00lio:

I don’t use target except to turn the leds off. I use DirectX inputs.

Sent from my SM-G935F using Tapatalk

Yeah nowadays that’s possible but back in 4.32 you couldn’t assign all of your buttons on the throttle IIRC…

@Stubbies2003:

That is actually a problem with newer versions of TARGET and not a Windows specific issue as I am running a newer TARGET and it can be funky at times shutting down on my Windows 7.

Oh really? Good to know! I’ll inform my fellow squadron member