Sideburns

You paid for a simulator, not an arcade game. Besides, it is still fast.

Really nice update, good to see the Viggen receiving this extensive level of attention.

I think the files have changed, just the changelogs have not made it through?

F-14A-55-GR 157991 F-14A 12th prototype (redesignated Prototype #1X) used for high-speed handling tests, modified for single-crew operation a/c stricken 30/09/1990

Aye, just to highlight one of several good points. The new AI BFM jinking and manoeuvres are now not terrible and really highlight how dated the gunsight on the F14 is, vs say the F16. Thankfully the jinking and manoeuvres can be fairly predictable atm, you can spot moments of minimal vector change but you will need to position your nose ahead of time and rely on the gun boresight a lot more and not solely rely on the radar directed gunsight. Also getting in close can obviously help land the shot, as can spraying a line of bullets over the possible moves the enemy could make.

I think I had this issue MP while multicrew. Pilot said the music had started (uncommanded tape player start), I couldn't hear it, he couldn't stop it, I could as RIO?

I am also having the frequency hop issue, observed in an MP session with two full crew F14B and AV8b on server with latest DCS-SRS. Radio frequency was indicated correctly in each cockpit but SRS showed a 0.005Mhz frequency hop. Unable to find a work around at this point, unsure if it is a random, time bound or activity bound uncommanded frequency increment, but I would guess it it is to do with PTT presses. Edit: From the DCS-SRS discord

Thanks for a great server Alpenwolf, I've had many memorable missions on your server.

As a former Saitek X-55 owner it is probably the x-55/56. Mine worked fine give or take some twitchiness on the throttle thumb axis for about 6 yrs. A powered USB hub improved but did not remove the twitchiness issue. After 6 yrs use the throttle ghost button presses started. Being DIY minded I opened the throttle up to find poor quality, thin wires fraying and breaking. Cutting out the old wires and replacing with new was tricky given the narrow clearances involved, but it is possible. I solved the ghost press issue but shortly after upgraded to a TM Warthog, other than missing the thumb axis I haven't looked back.

Cool stuff indeed, love hearing of the history of military tech development and testing.

I had also noted this issue, the track loss at launch, and assumed it was the radar or TCS picking up the missile for some reason and prioritising the tracking of the missile over the TWS targets.

Back to the point on contemporaries, the F14 in 1975 was an absolute world beater (M2+, agility, 6 active missiles, large PD TWS radar, A2G capable). This is a great overview of the development history of the jet (the link here skips to the TFX requirements).

Amazing work, and a great improvement. Thank you for your efforts. I have continually recommended your slew upgrade to other TM Warthog owners and will continue to do so.

Looks to be a great update. "Fixed an issue with the AWG-9 track logic to avoid tracks being thrown by aircraft launching air to air missiles." - This would explain a lot of lost tracks in TWS if the AWG-9 is getting confused by tracking munitions

Amazing, thank you. Truly an encyclopaedic knowledge of the Viggen.

In answer to the original question, and hopefully constructive feedback for ED: I originally played a lot of warbirds with "thatotherWW2sim:1946" during the late 90s into early 2000's while Flanker / LOMAC series was modern jet focussed. Pleased to see DCS venture into WW2, purchased a FW190D9 shortly after release based on personal preference for the FW190 series. Initially not a lot of WW2 servers, but slowly built up with additional WW2 aircraft releases (Note I remained just with the FW190D9) It felt like there was a "golden age" of multiple, well populated WW2 servers based on the Caucasus' before the various ww2 maps and the asset pack released. New map and asset pack released, I wasn't willing to purchase, but many WW2 servers moved to these maps and the pack. Feeling locked out from DCS WW2 now as limited, low or no population WW2 servers available to me. Easier to find active multiplayer for cold war and modern jets in DCS. Pleased to see the FW190D9 engine cut out bug fixed, but why did it take many years to realise random engine failures were always set on for this plane after the many bug reports on this issue? Also the issues @=475FG= Dawgermentioned. Gone back modern iterations of "thatotherWW2sim" for warbirds as it was less buggy and as it was cheaper than buying the necessary map and asset packs to partake in DCS WW2. Sometimes take out the DCS FW190D9 for a joyride, but it has become a hanger queen of sorts. Just my own experience.

Cheers for sharing sources, I am aware of this source and as before it is tricky to find a definitive answer on the "what is the Rb24j" question.

It certainly improved things for me, however I am noticed a lot of variation in stuttering with windows, graphics and driver updates recently. But I also run DCS BIOS and the UFC android app which can introduce their own latencies.

@DSplayera while back there was a similar but different issue spotted with the Rb24j, values affecting manoeuvrability were out and then corrected. The issue is described at But the key detail for your own report is "The Rb24J has been updated to be in sync with the AIM-9P parameters, should be in the next patch.". In my own brief research there were a variety of explanations as to what the Rb24j is meant to be, but the dominant explanation is an improved Aim9-B to Aim9-J standard with some local Swedish improvements (better seekers, electronics, guidance logic and laser fuse for warhead, etc) meaning it was equivalent to an Aim9-P series Sidewinder. Do you have a source for aligning the Rb24j to the Aim9-J base model? I think HB are deliberately modelling the RB24j to be an Aim9-P equivalent. https://www.aef.se/Flygvapnet/Notiser/Sidewinder.htm

I would also recommend changing process priority to see if this helps, you can obviously load the game up and use task manager to do this as a test rather than the registry or script hacks described here

Have you tried reading the manual? http://www.heatblur.se/F-14Manual/weapons.html#launch-modes

Same with the Forrestal, feels like it misses wire 4 by about 1-2m.

Great comments, just as an addition: The optimum AOA of 5 and 8.5 for climb and cruise are indicated on the AOA indicator as the square and the triangle for easy reference. Around 15-17 units AOA (the highlighted thick white bar in the middle of the AOA unit indicator, or just above it) will give best sustained turn at around 320-340knots. If you want to BFM in the F14 you should practice this to get muscle memory holding 320-340knots at 15-17 units aoa in your chosen F14A/B model for max sustained turn when you need it.* 320-340 knots at sea level is about the 6-7 o'clock position on the speed gauge, save time by not properly reading the speed dial in a dogfight but gauging it by position. As stated a million times before, when approaching 15 units AOA start using more rudder to roll. Once you are past 15 units AOA roll quickly become more dependent on rudder rather than the spoilers and stabilizers. *Note BFM is not just about max sustained turn, but it is good for this to be second nature / muscle memory so you can focus on the fight. Edit: Having watched Puck's interview on the Tomcat this also highlights manual control of wings and 25 deg at 420 knots can give some pretty good turn rates / G's as well.

Having just done a RIO session the cockpit looks a lot nicer from the changes, cheers.

Seems like a fair suggestion, leave it up to server owners and mission makers if they want to simulate war or training conditions.