Zyll

Yeah I tried changing that dropdown, but it made no difference, always sent the audio to my monitor speakers. Seems too obvious I would think.

At half flaps, unless you are heavily burdened, an airfield takeoff should actually just pull itself off the runway without needing to apply any pitch. It should be very smooth

How do we force SRS to use a specific output device (speaker)? I have my monitor speakers as default output device (coming from display port via my GPU), and headphones plugged into the motherboard. Apps like Teamspeak allow me to select the output device, but I can't figure it out in SRS. Thanks in advance,

I still watch the official early release video for the Hornet and get goosebumps

To add to this, in this game at least you can assume yellow is enemy, because friendly identification only requires one source, and there are no neutral targets in the game today. Someone correct me there if I'm wrong.

Did you perhaps fly out of range of AWACS or some other link16 source? Enemy (red) verification requires two sources of info, which could be your own NCTR and link 16, but that would require you to be close and at the proper aspect to the target. Most commonly, an AWACS best serves as that second data source.

Report it as a bug then

Looking forward to it!

I just got another exit to desktop w/o crash log. Here's the dxdiag immediately following: https://drive.google.com/open?id=16WX1Lp-r9p1qhugGwfvzFTPDhR55t_LU

i'm not seeing the distance to target in the HUD as Wags shows in his video. Was this part excluded from the May 8 build?

doesn't the dxdiag.txt log only get generated when there is a crash? I checked and I don't see it in the logs folder, only in an older zip file from a previous, unrelated game crash. regardless, here's the latest one I have on my machine from last month, hope it helps https://drive.google.com/open?id=1s7hq3WYta0WJWWzFEBzuVAQqySbAKUXR

Will do the next time it occurs. Thx 9L

It does not break IC, but this file will reset after each update.

worth mentioning that this NEVER happens on Caucasus. If I crash flying Caucasus, I always get a crash log, along wit the prompt to send the info to ED.

Hi team, I've been tracking for quite a while now the incidents that the Persian Gulf map just closes on me, without any crash log, and no real pattern to what might be causing it. I fly the Hornet on multiplayer maps, and when the issue occurs, DCS just closes, I'm sent back to my desktop. The last line in the dcs.log is not indicative of a core dump or anything, it can be anything really. Here's the latest example: 2019-05-01 03:39:21.783 ERROR_ONCE DX11BACKEND: texture 'mig-29c_tex01_spec' not found. Asked from 'NGMODEL' Anyways, this is the history of each occurrence. Wondering if others have seen similar behaviour? 2/27 4:50pm - PG map, viewing external friendly maverick fired by player 3/1 5:43pm - PG map, fiddling with SA and attack radar MFDs 3/16 4:46pm - PG map, cycling external views from MIG29s to SU25s 3/30 1:50am - PG map, just flying formation way up north with Hornet and Harrier 4/6 12:33am - PG map, switching from AIM9X to guns on SU25 4/10 12am - PG map, Gulf Fury, just flying to a WP 4/14 5:38pm - PG map, just flying towards air targets, checking radio on 31.000 4/26 11:52pm - PG map, looking at F10 map 4/27 2:43am - PG map, external view sitting on the carrier 4/28 3:53am - PG map, belly landing and crash at Dubai 4/29 - deleted fxo and metashaders2 4/29 12:39am - PG map, looking at F10 map

If you have your volume cranked to it's highest setting on the main SRS screen, try turning it down a bit and see if that addresses your issue.

Very nice webweaver. Thx for sharing

You would just type the freqs in, there's no drop-down to select them. As for defaults, I believe there is a config file / Lua file that your can under to enter freqs for every one if the EAM radios.

External AWACS mode. Let's you log into SRS without being in game, then your can use the AWACS panel to talk on the freqs. Nice if you are using something like LOTATC to perform GCI role.

Just to confirm, we should convert the elevation that JTAC gives to meters correct? So if he reads out 600 feet, we should enter 200 meters, right?

I have tried using the coordinates from JTAC, along with the elevation converted to meters from feet, but I'm not coming close to hitting the target. This is on the PG map if that matters. Wondering if you have any ideas?

It passes integrity check just fine.

You can also change the AWACS to a different aircraft type, then change it back again. That should fix your EPLRS task, without you needing to recreate the enroute waypoints from scratch.

+1000. Our group has this exact problem every Sunday. So far we've resorted to multiple carriers, which is not ideal. More and more big fat Tomcats on the deck is just going to make the situation worse. I too would like to know if this is something on ED's radar to address.

Yeppers. On the real throttle that's exactly what it is, a physical detent that you need to pull on the finger lift to push through.