Alphamale

Ok, I got it. But while we're talking about G-effects, is it working correctly in this sim? Because I have those effects enabled under options and have taken enough negative Gs to blow my eyeballs outta my skull and smash against the canopy without any indication of "Red-out". In fact, I've never seen red-out indication and "Black-out" only happens once in a blue moon even though I've pulled up sharply enough in a 400 kts dive to lose complete control of the aircraft with no "black-out" tunnel effect.

So, you're saying we should not hit AP until the plane has stabilized. You don't mean just nose down.

Sure, ths happens every time I use Active Pause in a Campaign Mission Engine_cutoff_AutoPause.trk

In campaign mode, when I use active pause, the engines will cut off and I can't restart them causing me to eject. Is this supposed to happen?

Drats, I was sorta hoping you'd skip along the water before you start to sink.

I haven't experimented much with this so, just asking. If so, can you also perform belly landings in water?

You're right, I just tried that now. But it really takes a yank to get it to move.

I don't think it locks up nearest target. But what I have experienced,is that the PAC1 stage will not allow nose correction. It simply locks the plane in the precise dive angle it was at the pressing. PAC 2 alone seems to stabilize(lock) but as it's firing the 30mm, it allows me to "walk" the point of impact up as I apply joystick pullback. Applying PAC1 prior to PAC 2 seems to ignore any joystick input as you're firing. I originally thought this was supposed to be the other way around. I sometimes use the "Binocs" hack along with Active Pause and the pipper dot does NOT move to the target when PAC 1 is engaged.

But that's the problem. I don't want the pinky button on JS1 as the NWS. I want to use B4 on JS1 as a SHIFT button which is what I'm used to. That's why I had to remap the NWS/Laser over to throttle. When I did this I was unaware that it conflicts with the script file. Then there's the distinction of whether a key should be mapped as a key press or have a DX function. After I sorted that out, I then saw reference to a CMS mapping. How is that enabled by the program. All this was new to me. So you see, I really wanted to keep the majority of your assignments in realistic HOTAS form, except for the pniky button and BTN 2 which I do not use for Master mode, but rather as a MODE change button based on the three lights on the two sticks. I want to use the full potential of these sticks because I have no MFCD panels (USB) that I can map functions to (i.e. I want all the functions I'll use or as many as I can get, on these two sticks). I have a Thunderseat Cockpit chair that puts me pretty far away from the keyboard. Therefore, I have to place the keyboard on my lap in between two stands for the sticks. Little by little, I'm mapping frequently used keys from the key6board to the sticks. That is why I need the SHIFT key funtions AND I'm finding I need the MODE change ability as well. I know this is not the true HOTAS setup, but it's close and until I get MFCD panels, the alterations will do for the time being. Anyway, as I said above, it is now working and I have assigned NWS/Laser to another throttle button. If you'd like to see what I have done, I'd be more than happy to send my alterations to you and maybe then you can see what I'm doing and perhaps give me some suggestions. I feel like I'm not clear about what I've changed. Thanks Frosty

No that is exactly the file that I had to alter. See that file calls for strict button assignment for HOTAS to match RL. I wanted pinky on FS for another purpose. But because the script that came with that map file had to change, so did the map file itself. An I just got these sticks and am not that familiar with the Command Mapping app. In addition, I recently got A-10C. So I'm not spending the majority of my time learning a new programming app as I should, because I'd like to play the sim more of the time. Too much stuff to learn. But I do appreciate your file and have finally modified it to suit my taste to the point that it's working well now. Actually, that link about CH Fightersticks does not tell you EVERYTHING you need to know about programming it. It makes a lot of assumptions about the knowledge level of the reader with the CH software. But I applaud you for your contribution anyway. Check six.

Yeah, I got it. But now I lost Nosewheel Steering/Laser. I was messing around with the scripts. See, I have the pinky button on the FS set as a Shift function key(this was the way I used it on my old Thrustmaster F-16 stick), so I had to move what is normally the default HOTAS function for that key(nosewheel/laser) over to the throttle. I chose BTN2 which is pinky AFT. But the script that came with the CH HOTAS file that I DL'd had the pinky button defined a different way. After deciphering the syntax, I had to change Pinky Aft which is JS2.B2 to JS2.B4 then change button 2 on throttle from mapped mode to DirectX function and set it as CM Device 2 Control BTN4, if all that makes sense. Anyway, now when in A-G mode and GUNS selected with GUNPAC armed, I now get PAC1 when I depress BTN2 on throttle and when I pull trigger (BTN1 on FS), I get PAC2 which I guess allows me to strafe longitudinally and if I just pull trigger without PAC1, then I get spot density fire from the 30mm thru PAC2 alone. Is this the way it should work? I guess I'll just have to map NWS/Laser to another key on throttle. Thanks EN Whoa!! I just checked it again and I had it backwards. With PAC2 alone, I can walk the rounds up a longitudinal path and with PAC1 engaged first and PAC2 trigger second, I get locked in spot firing.

This is what I'm trying to do. But it seems I'm having problems determining whether this is a DX command or a "mapped keypress". I do get PAC2 when I depress BTN 1 on Joystick1 (which is the CH FS), but this trigger is designated as a DX button and shows as Joy_BTN1 in game options. I have P assigned as a keyboard key for Gun (first stage trigger). But no matter how I mess with the CMS scripts or button assignments, I can never get PAC1 to display on the HUD prior to pulling the trigger, which will employ PAC2 until I release the trigger.

So, you're saying you really don't need PAC 1, but without PAC 2, you can't fire?

Could someone briefly explain how this is supposed to work for GUNS? I have a CH FS and Pro Throttle with Saitek pedals. The fighterstick, as you're probably aware, does not have a dual stage trigger. I've tried a few users' profiles and scripts that mimick the dual stage process, but how does that process actually work? Are you supposed to engage PAC 1 first to stabilize the aircraft and then fire with PAC2? Or should you just be able to have PAC 2 available? The FM doesn't really go into detail about this. Thanks AM

Yeah, plus I did not have the SAFE modes set. I will have to refer to the manual more often...hehe. While I'm addressing it here, let me say that this is really hard. I wonder, do all of you who have mastered this, do you advise tweaking the joystick axes to reduce their "twitchy-ness"? Also, just when I think I'm right under it, it seems that the tanker wants to weave around making it more frustrating. Is there a macro that does this automatically so I don't kill myself and ruin my current profile?

Can anyone give me the link to a good refuleing mission WITH in-flight audio on the proper procedure including which radio calls must be made prior to hooking up. Also which controls must be engaged. I have a couple but none of them tell you which buttons to push and which requests must be made. In my trials, I did engage the fuel slipway (I think) and made some Pre-contact request, but the tanker never lowered the refueling boom. I did have the correct freq for the tanker set and did receive permission for pre-contact ans I did have the TACAN set correctly, but he never lowered it even tho I was right on his tail.

Yeah, I get it. But that brings up another point. When you are in CCRP mode with an IAM, you wait for the MAN/REL cue to hold down the pickle button and the ordanance releases at the optimal time, right? Your HUD text color is GREEN. With all the glancing around I'm doing, I sometimes miss that cue. BUT, if the color for that cue turned RED instead of staying GREEN, I'd definitely see that out of peripheral vision and get the button down in time. Why haven't they thought of this IRL? Also, couldn't they do this with the seeker range as well? In which case, it WOULD be screaming.

Even if I had aborted, the missle was away and I was flying towards the AAA, so why not take the shot? Evasive maneuvers would still have kept me in the area at these speeds.

Well, in this mission, I had taken out SAM as I approached TGT and was attempting a MAV lock on ZSU when as I passed a ravine in the mountains, it unmasked a SA-15 that just started painting me, but I was in zoom mode locking the AAA, so I enabled full auto ECM and continued the lock on the AAA. I mean it WAS in the FOV and I had to take the opportunity of locking and firing. What else ya gonna do?

DAMN!:doh:

BTW, in other sims I could gain enough altitude to use a CCRP delivery and walk my way over the target for a pickle without regard to ANY ground air defense. What's the ceiling on this sim for something like a SA-15?

Agreed. This sounds like the best course of action.

Again, no not in a leisurely setting. I mean doing all this while dodging incoming missles. :smilewink:

You're kidding me! It cannot be because of the level of "Classified" information. We had those with Longbow and FA/18 Hornet

No, I mean beyond Narrow Field. With the TGP, I have three levels of mag. The Wide view, Narrow view and then Zoom view. With the Mavs, you just have the first two. Being 55, my eysight is not that good. It's kinda hard to View the MFCD page from normal cockpit distance while in Mav SOI and see a particular dot as a SAM, even in Narrow View. If I try to zoom my in cockpit view, I lose control of the plan too easily.