mrkline

When switching radar modes, the AWG-9 suddenly ignores any azimuth or elevation controls and snaps to the centerline. But as soon as you touch the azimuth or elevation controls again, it snaps back to its previous position.

The desync is still present - the pilot and RIO see different arm states for the seats, and only the pilots' actions seem to have any effect. Also, when arming the seats, a strange loop sometimes plays instead of the usual click:

The DCS engine has known issues with spotting, summarized here (with data to back it up): I hope we see improvements there soon, thought I'm told it's been a contentious topic for some time.

Several folks on Reddit are reporting the same issue:

The RIO seems to black out whenever the pilot pulls any significant G. It seems like all of the accelerations the pilot produced in the last few moments (probably in the last packet between the two clients?) are instantaneously applied to the RIO, causing immediate GLOC. What's extra curious is that when the RIO blacks out, he seems to multiple times in a row:

When both players spawn in the cat, the pilot sees the wings back in oversweep, as they're supposed to be on a cold start. At the same time, the RIO sees the wings swept all the way forward. Once the pilot starts manipulating the wing sweep handle and the wings begin moving, the RIO sees the wings teleport back and forth before his view syncs up to what the pilot is seeing a few seconds later. Watch the video! Unless you're suggesting that improper startup can cause your wings to enter some Schrödinger's paradox where they are both swept and unswept, I'm going to chalk this up to a netcode issue, not bad procedures.

Several people (myself included) are finding the performance especially bad in the back seat, more so than in front:

That's fine - it's worth reporting either way.

Multiplayer. Longer loading times and crashes to desktop mid-flight. Running out of VRAM as best I can tell. i7 4790k 24GB RAM GTX 1060 with 6GB VRAM M.2 SSD

My pilot and I joined a cold start spot within seconds of each other and both had great pings, so I don't think those were factors.

When cold starting in multiplayer, the RIO cockpit shows the wings fully extended. When the pilot sweeps them forward, they bounce around before finally syncing:

There seems to be some desync going on between the pilot and the RIO: Arming seats as a RIO seems to have no effect, both from the pilot's view and according to the game.

VRAM seems to be a larger issue than before. When I load into a busy server (DDCS), my 6GB of VRAM is nearly pegged: I haven't been able to make it through a flight without crashing. (This is using the same graphics settings that have been very stable since I started playing DCS this past July.) The rest of my system is fine:

Also when rejoining MP as RIO, binds behave like you're in the pilot seat. I rejoined and tapped the button that's bound in the front seat to Weapon Select Hat SW, and started hearing a Sidewinder tone.

Thanks, Cobra! We're all really looking forward to next week. A quick question about symbology: the F-14B NATOPS mentions a steering tee that should display on the HUD and VDI, along with an ASE circle that should appear on the VDI once you have a lock. I haven't seen these in any of the preview videos. Am I missing something? Are they not modeled yet? My first guess was that the NATOPS is for a newer avionics suite than the one Heatblur is modeling, but one of the pilots in the 1989 Gulf of Sidra shootdown. EDIT: Jabbers just replied with

Thanks for the link! It's a shame there's no public bug tracker - I'm sure none of us want to give Heatblur more work by posting duplicate bugs, but the forums aren't the easiest to search.

This isn't a Viggen-specific issue IIRC - DCS seems to despawn any weapons you've fired when you respawn. However, they continue to exist so long as you stay in the spectator view when you die, and don't go back to the role selection menu or the F10 map.

After an attack run (IIRC, dive bombing with low-drag bombs), a cursor appeared at the bottom of the radar screen, near ownship position: It stayed there even if I started entering a fix (which brought up a second cursor where I would expect one to be): Or even if I turned the radar off:

After landing in LANDNING NAV master mode, the approach vector line is stuck on the radar screen during following sorties, even if I reset systems after landing by switching master mode to BER (per manual pages 133, 168, 246). The ILS light also stays on in the warning panel, even once you're quite far from the runway:

Duplicate of https://forums.eagle.ru/showthread.php?t=230920 This doesn't have anything to do with one's TrackIR profile or sensitivity. All planes have TrackIR movement constraints (since suddenly stopping the camera doesn't induce vomiting like it does in VR :P ), but the Viggen's lets you stick your head through the canopy.

Awesome! Is there a bug tracker for submitting issues? I found a few typos, but posting them in Reddit or the ED forums sounds way too chaotic, especially once you try to avoid duplicated reports.

Make it two rectangles! I got a short video to demonstrate:

Sorry, maybe I wasn't clear. I was saying that the Heatblur-provided sounds still have problems, and your mod fixes them. Things sound great in your mod - thanks again! The good news is that Cobra is now aware of it:

I'm still hearing the looping/popping in the current open beta. It seems most noticeable when going from idle to military power: (compare this to how the same behavior sounds with Devrim's Viggen sound mod: ) But it seems to happen (sometimes more noticeably, sometimes less) whenever you make any significant change in power. I've annotated a 12 minute flight with the timestamps where you can make the loops/cuts out most clearly:

First, thanks for making multiplayer flight plans populate the kneeboard pages in the recent update! Having the QFE and other info handy really simplifies mission planning. However, waypoints seem to be missing, and the ones that do show up have odd names. The following map marks generate the following plan: B1 seems to be missing entirely, M2 is called "B3 B2", and M3 is called "B4 B3".