Truthkeeper

Maybe it was too easy spotting targets with the previous FLIR implementation... The truth is probably in the middle, but I think that once the system is opportunely tuned, this will help immersion as finding targets this way should not be easy in real life as well. As for the current implementation I suggest you to play with brightness, contrast and gain to obtain a better picture (I prefer white hot by the way)

My guess is because the warning can advise the pilot if the plane starts pointing somewhere else (like towards the ground) when you are looking somewhere else (like taking notes or using one mfd). However it's quite a PITA...

Same here. I noticed this issue in my thrustmaster mfd, but the same happens if you bind any keyboard key. I tried a dcs repair, but to no avail.

After last update it seems we have TTT and TOT working. However it's not clear to me how the commandeered speed is displayed on the HUD. In my test I set the center of the "cross airfield" near Kobuleti as target point and I start in the air about 50nm north of it. Setting a TTT of 6 minutes I receive a commandered speed of 481kts (ground speed) in the scratchpad while a chevron and a vertical segment appear below the CAS in the HUD (NAV mode) First picture shows HUD in NAV mode after reaching CS Chevron is left of the segment Same CS but HUD in AG mode Slowing down the plane I have the CS increasing and next picture shows the HUD with a CS of 509kts Chevron is still left of the segment, but closer to it Last picture was done centering the chevron with the segment just to show the corresponding GS I was wondering whether this might be the correct behavior because it doesn't seem very useful...

Doing some target range exercises using multiple weapons, I noticed how the distance at which the IR maverick locks its target had significantly reduced after last patch. In fact I used to lock targets within 10nm while now I need to stay within 4nm. Has anyone else noticed the same?

Muy bonito el buque! No van a ponerla en los DCS User Files?

Thanks for the info. So I modified the BE location putting it over my waypoint #7 (that is Fujayrah in my example) and accordingly modifying the tab in ME. Point is I don't know what change I could expect in the aircraft moving map because there's no different symbology for WP7. I mean there seems to be no change whether I chose to designate wp7 as bullseye or I didn't...

I was wondering what's the purpose of the option "waypoint bullseye" you can find in the mission editor in the tab "additional properties" (the one with three dots) after selecting one harrier. After last update I was able to display the refueling zone overlay inserting the waypoint number (#5 in my case) in the mission editor option, but I'm still at loss for the use of "waypoint bullseye" because, no matter what waypoint you select in the ME, I always read direction and range towards the actual bullseye in the HUD Any idea?

Once you create your personal loadout in the mission editor (and you save the mission) you will always find it within the other loadouts (online too)

Really good job! Looking forward for it to be released in the user files.

È un bug

Nice!

Having the same doubts myself (and similar rig with 6700k, 32gb and 1060 6g). Performance is all on 5700xt side being almost on par with 2700 super in many benchmarks. Considering it doesn't seem ED is going to support ray tracing, the power unit you've got might become a constraint considering the 5700xt needs much more watts than 2600s

It's a backup bombs delivery mode. Follow the dumb bomb tutorial mission where it is explained after the "usual" ccip mode.

Glad to have helped. I'm sure the harrier will turn out to be a very enjoyable aircraft.