Razgriz

Thanks! This has been a very smooth and impressive aircraft launch. This is the only plane that is good enough to get me over to Redfor. :thumbup:

Seems to be an issue with MP cold starts? Or is it just me? I joined a server that had a JF17 hot started and the TGP worked.

WMD7 won't start align in multiplayer My WMD7 targeting pod won't start aligning in MP. In SP after a hot start, it started counting down and aligning as soon as I press on. In MP, when I press on, it goes to the countdown screen but the countdown never starts, only showing remain time: 0 seconds. Tried again with a fresh spawn, attempting to let the pod align after weight is off wheels. I was using auto-start. Not sure if this isn't starting up a system? Waiting a couple minutes, nothing. Pressing Cage, nothing. Pressing BIT, nothing. Not sure what to do to get the TGP on in MP.

I think the list is talking about smokewinders.

I am trying to understand the Harrier's TGP coordinates. Is it displayed in Decimal Degrees or DMS? If I try to treat it like decimal degrees, and look the location up on Google, it is way off. So assuming it outputs in DMS: On Caucasus, here is some coordinates at Sochi along with Google Maps. N4326350 E03955461 Adding spaces and a decimal to the last digit: N43 26 35.0 E039 55 46.1 Here are those coordinates now, which when plugged into Google Maps gives us a close match. 43°26'35.0"N 039°55'46.1"E https://www.google.com/maps/place/43%C2%B026'35.0%22N+39%C2%B055'46.1%22E/@43.4425524,39.9307572,1577m/data=!3m1!1e3!4m5!3m4!1s0x0:0x0!8m2!3d43.4430556!4d39.9294722 ----------------------------------------------------------------------------------------- Okay, now. Same method on NTTR, but I get coordinates that don't quite work. Here is Creech AFB: Here is the output: N3635033 W-11580892 N36 35 03.3 W-115 80 89.2 As far as I understand, on the longitude, the minutes and seconds can't be over 60. So why is the TGP outputting this? Google Maps won't accept this: 36°35'03.3"N 115°80'89.2"W

Looks factory fresh :thumbup::thumbup:

Post-patch version of Open Beta, my client showing 2.5.4.30038.

Demo track attached where I made jester punch out. Title says it all, no way I can close the menu after opening it once he's ejected/incapacitated. Video: https://streamable.com/c5bsg Latest DCS OB version cant_close_jester_menu.trk

A trick I heard from an SME here is in level flight - 800ft, inbound for the carrier break, wings swept, set your fuel flow to 4000 pph around 400kts and it will hold 400kts beautifully. Now any time I'm in level flight, I just find a fuel flow I want usually between 4000-5000pph and let the airspeed figure itself out. Then trim.

This has fixed my issue, thank you! Just to note, the button text for me was MK0 initially, then it incremented to MK1, MK2, etc. as I added markpoints.

Yes, WYPT 1 selected. However, once I add a waypoint 1 through the UFC, back on the EHSD the waypoint selection seems to get stuck on waypoint 1. I don't know if the aircraft doesn't know where WYPT 0 is automatically (like the hornet) or what?

I have been getting back into the Harrier lately and the only issues I'm having are with adding waypoints through the UFC. Following Chucks guide, I create a single waypoint (WYPT 1), then go to NAV mode while on the ground and the HUD shows 0.0 nm to both WYPT 0 and to WYPT 1. To be specific, I was doing this in the Aerobatics Online server. Spawning at Krymsk. Tried this with the INS pre-aligned and also manually aligning (INS set to saved heading only). Then enter in the coordinates for Anapa into WYPT 1. HUD provides no navigation assistance or distance to the waypoint. However, when I fly towards Anapa, I can see it on the moving map as a circle with a dot in it. Shouldn't the distance and bearing from my aircraft be showing up on the HUD instead of it always showing 0.0 WYPT(x)?

It seems asking to get a bug fixed is putting it on their wish list. :(

Engineer 2. HARM, ATFLIR, and then supposedly he will go back and tweak the FM. Yes, yes, and yes please.

The external position lights are way too dim and they do not illuminate the ground or the enviornment. You cannot see them even at nighttime from other aircraft in MP. The whole point of these lights is for them to be spotted by other pilots but right now they are too dim to serve that function. Compare the F/A-18 to an AI F-15 in the attached photos. The Hornet's red/green position lights don't even illuminate the ground. They are almost impossible to see even in the black of night. In addition, here's a video of just after dusk to demonstrate how broken the current exterior lights are. You can see the position/nav lights pop in at 0:15, when you should be able to seem them clearly the entire pass: https://streamable.com/etoww Real night examples of how bright the position lights are: 1.) 2.) 3.)

^^

Hopefully this can get fixed quickly. AACQ should be great for panic locking the closest target, right now it only gets you into a deeper hole as you lock someone ~30nm out

Currently like I said earlier you can't even see the position lights from anything farther than what seems to be ~150 feet. The 2 position/navigation lights on each wing are much brighter than the AoA indexer lights, and while both should be visible the position lights should be so bright at night that you can't miss them. Here's a video of DCS just after Dusk to demonstrate how broken the current exterior lights are. You can see the position/nav lights pop in at 0:15, when you should be able to seem them clearly the entire time: https://streamable.com/etoww Real night examples of how bright the position lights are: 1.) 2.) 3.)

Regardless of the color you just can't see the lights at a reasonable zoom level. You have to zoom in like you're looking through binoculars to see a shining light, that behavior just isn't correct at the moment.

The indexer lights are much too dim, just like the 2 position lights on each wing. You can barely even see them from any reasonable distance zoomed out. They really need to be brightened so you can actually see those lights from even 1 mile away without having to be super zoomed in on the airplane.

On the latest patch - I have been in wheel chocks on the deck of the stennis, throttled up not thinking I was in chocks, and my plane started to rotate slowly in place CCW until I collided with the Hornet starting up to the left of me. It was on the TTI server. Deck behavior is still very wonky

This worked for me for a while but no longer works. I really miss having a clear HUD glass so I can see properly on my flat 2d monitor. Does anyone have a way to get this working again?

That is my problem. The formation lights are bright enough but the wingtip lights and underwing lights are not even visible from any sort of distance. Here is a video from the CASE III mission provided by Wags. I use gamma 2.0, all 4 red/green wing lights are not even visible. https://streamable.com/rjzqm

Look at how bright the lights are in daytime conditions. I wish the DCS version had better external lights. Even the AoA indexer on the real jet is visible with the landing light on (in DCS you can't even see the AoA indexer from the ground with the LL off):

See how the lights work on a real legacy bug during/before twilight: All of the lights are very underpowered, especally the red/green lights on the underside of the wing & the nose wheel AoA lights. Edit: Is there a way I can multiply the brightness of the external lights? In full darkness I can barely even see the 2 red and 2 green wing lights.