Machalot

I agree it's a little touchy. You could try reducing the Y Saturation value of the axis to reduce the slew speed.

Thanks for posting this. I have wondered for a long time.

Should I repost this in the DCS 2.7 bugs forum?

Looks like you are using the binding for "Datapanel Switch In/Out", which is intended to be used with an physical switch on your HOTAS which will stay in position until you switch it again. If you want to use buttons, you should using the bindings called "Datapanel Switch Input" and "Datapanel Switch Output". Unfortunately, just like the Trigger Safe, there is no true toggle binding for that either. I have the data panel bindings set up in a way that works really well for me in VR because it's entirely on the right hand of the keyboard, and doesn't require moving hands back and forth between the HOTAS and keyboard more than once. It is as follows: Datapanel Switch Input: left arrow key Datapanel Switch Output: right arrow key (These seem to be duplicated by "Datapanel IN/OUT Input / Output Switch In" and "Datapanel IN/OUT Input / Output Switch Out (UT)". I don't know of any difference in function.) Datapanel Rotary Clockwise: up arrow key Datapanel Rotary Counterclockwise: down arrow key Datapanel 0-9: Numpad 0-9 Data panel RENSA cover OPEN/CLOSE: RCtrl+Numpad . (Note there are several similarly named bindings -- only this one works as a toggle.) Data panel RENSA (Clear): Numpad . key Navigation panel Waypoint LS SKU: Numpad Enter key Navigation panel Waypoint L/MÅL: RCtrl+Numpad 0 Navigation panel B1-B9: RCtrl+Numpad 1-9 Navigation panel Bx: Numpad + key

I don't have a reference in front of me, but it seems like the nozzle opening should also depend on altitude, Mach, and air temperature. Not solely on the thrust lever setting

What kind of button or switch are you binding on your HOTAS?

I don't have the spring loaded issue with the computer in/out switch. Which binding are you using?

It won't take long to get used to it. It does require some extra work to coordinate your flight with other Western jets that use feet, knots, and nautical miles. I use Mach to match airspeed with other jets. Some quick mental conversions I use for altitude and distance are: 300 m is about 1000 ft (exact is 304.8 m = 1000 ft) 2 km is about 1 nmi (closer to 1.85 km but 2 is good enough for most situations)

Since the 2.7 patch the F6 missile view exits just before warhead detonation. It used to stay on the target so you could watch the explosions and destruction, but now you don't get to watch the fun. Is anyone else seeing this? I can't make a track tonight but will do so at my next opportunity.

I noticed this too and wondered if it's a typo. Thanks for posting on it.

Haha ok. Read way too much into that.

What does "v no track" stand for? Edit: Oh, maybe it's "extrapolated [velocity], [with] no [radar] track"?

I don't know if GBUs are designed to hit moving targets. It could be that the CCRP logic assumes a stationary target, so it releases the bombs assuming they won't need extra energy to maneuver.

In the past when delivering GBU-12s using a buddy lase, I did not need to press uncage a second time to exit LSS, nor min-slew the TGP to update SPI. Once the TGP found the laser spot, it automatically exited LSS and updated SPI (I think it went straight to Point Track). Has that changed?

Same problem here. I move the taskbar to the right edge of the screen as a workaround when I play DCS.

I thought the Kont/Int switch is something the pilot can set and leave it. It will stay in Kont until depleted, or it will stay in Int for 6 seconds and then turn off. Am I wrong?

It would be nice if you could at least snapshot the lat/lon from the F10 map to the kneeboard so you could more easily type it into the UFC without swapping between F10 and cockpit several times.

Sounds like MalwareBytes is kind of behaving like malware!

Ok, I'll give it another try tonight. Thanks!

If the pipper vanishes off the bottom of the HUD immediately upon trigger unsafe, what should the pilot do? Climb, descend, accelerate, decelerate? Edit: After watching a few Youtube videos I think this is a direction to pull up (to the safety altitude) in order to put the pipper back on the target. Is there a way to learn the mission editor safety altitude setting from inside the jet, or the kneeboard? Edit: Chuck's Guide has the answer. It can be viewed in the kneeboard.

Which comment are you referring to?

In my testing, you don't need to hold the modifier. Once you press the desired button, you can release the modifier and the desired function (e.g. lasing) will continue as long a you hold the desired button. Edit: I see @=Panther= had already posted this. Sorry for the duplicate.

In another thread a while back, somebody fixed this problem by adjusting the anti-aliasing settings.

I believe (but am not 100% sure) the fuzes are not activated until a predetermined time delay after separation, which is initiated by a lanyard that pulls a safety pin out of the bomb on release from the pylon. If they are activating the fuze instantly at separation that is probably an incorrect model. Edit: A little more info: http://cs.finescale.com/fsm/modeling_subjects/f/2/t/129576.aspx Edit 2: Manufacturer's info pamphlet: https://www.kaman.com/sites/default/files/FMU-139DataSheet2017-PRINT-PAGES.pdf

You seem to be aware of the relatively large effect AoA has on drag. That also means weight has a large effect on aerodynamic performance in spite of increased thrust. It's not just thrust-to-weight ratio that needs to be the same, because more lift and more AoA is required to pull the same g's turn rate, increasing induced drag in all flight regimes, including straight and level. Aerodynamically they may have the same OML (outer mold line) but the 50 spends all its time at higher AoA than the 30.