PlainSight

Sniper pod You're doing it wrong

HET temp was always in the yellow and i only cranked out 1214 KW. I start with 12% rod position.

How long does it take to repair? And how do you know when they're finished?

Works great, thanks. I always had to look away from screen, to find the right F key, clicking the wanted option is SOOO much easier. :thumbup:

There are HUD data plates (or whatever it's called) hidden behind the UFC. You can't see them unless you really stretch your TIR.

Chances of crossing from 37 to 38 grid are very small, so it most cases the default zone setting will work. Otherwise you can always check the mission planner, if the flight plan crosses the 42 degree meridian.

WHY ISN'T THIS PICTURE INCLUDED IN THE MANUAL?? ED spent a lot of time implementing JTAC, it's a big feature, but they left out this very important information :doh: Thanks for the info :thumbup:

Could you make one in A5 format, for the kneepad?

I'm practicing shooting gallery mission and JTAC gives me GG329668, but that's 860 mn AWAY wtf?

Did you try turning the course knob? You have to align it with the needle and press the TCN button. After you disconnect from the boom, press the NWS button to reset the system. Observe the air refuel lights, it has to go from"disconect" to "ready". As for the startup, the checklist procedure is good, but once you know all systems, buttons and drill the startup flow, there's no need for checklists. Remember to engage the bleed air switch and main supply switch, they're just below the oxy supply.They are not mentioned in checklist section

"Well, it’s just really hard to do. Looking back on it, I think the only reason we took on what we did is because we were too inexperienced to know better." Coming from the guy who created F4s DC. So there you have it. ED did the right thing to stick with simulator part and got that one right, than implementing DC and cause even more bugs and delays. ED builds its games around the plane they simulate, i don't expect a DC from them. DCS are already complex products on their own.

Rumblepad 2: Deadzone = 7 Sat X = 100 SatY = 100 Curve = 25 Curve is your friend, use it.

Is it me, or are nvidia owners in the majority, when it comes to CTD? I bet it's that effects.dll again.

Mine are little bit "weaker" (80 sat., 40 curvature), but yes, axis tune is a very good feature especially on refueling where very small and constant inputs are required. And even with lower saturation, AOA warnings still occur, so there's no worry about losing performance. When you get the hang of it, try lowering the curvature. These things are very important. Communicating with the game is really well done. All the available costumization of axes, buttons and modifiers provide tons of options for any kind of hardware and player.

If you start from ramp, check your escape maneuver settings in weapon profiles. It's set to off by default. Training mission said this can cause ccip invalid.

Cool mission :thumbup: How do you keep your planes steady? i've increased the curvature on pitch and roll axis for more precise control, but i'm still wobbling all over the place. I only get initial contact, once i break off, i cannot re-establish contact :mad: The longest contact was about 10 seconds

China hat FWD too slow??

It says YET, there's still hope! :v: :thumbup:

This is the same as the default, except the view angle.

With so much cool hardware, you should build a dedicated pit :thumbup:

Bottom is good, STPT is just visible, which is the lowest mark, but you can always adjust your seat height. Only the top hides behind the glass frame so when doing ccrp, you have to duck to see the countdown, if you need to. To me, it's a good compromise between seat position and visible hud.

Use the zoom button, or set fov to 80. It's set there, so i can use the radios more comfortable.

Yeah, maybe we're flying DARPAs UAV edition of an A10 :megalol: Anyhoo, here are my current view settings, if anyone wants to try. I have my zoom setting mapped on a hat, i cannot use TIR alone. Important for gun runs. Snap[11][13] = {} -- Default cockpit view Snap[11][13]["y_trans"] = -0.01 Snap[11][13]["x_trans"] = 0.27 Snap[11][13]["hAngle"] = 0 Snap[11][13]["viewAngle"] = 90 Snap[11][13]["vAngle"] = -15 Snap[11][13]["rollAngle"] = 0 Snap[11][13]["z_trans"] = 0 -0.01 brings camera little bit higher, so the STPT is visible by default. 0.27 on the X brings your head back, but the side of the hud is still visible. Source of all issues. 90 degrees FOV is standard in all FPS, so i use that. Nice allround setting. But this is just default. When you zoom in and out, your FOV changes.

I don't know what ED did, but HUD doesn't act like it did in BS. It's always the same size, relative to it's boundaries of HUD glass, so if you set your viewpoint further away, it will get chopped away, because the physical HUD frame becomes smaller. It's not binded to the glass, but the text just floats in the middle of the screen, separated from the HUD surface. BS didn't have this issue And the only point you see whole text is the default viewpoint. YOU have to position right to capture the text in the HUD glass.

I love all the available options. Laser-guided are my weapon of choise. When i press maverick to TRACK, i'm never certain what will it lock onto.