Sideburns

Thank you, after a few sessions online the AWG9 TWS is once again usable in MP. The dropped tracks and whacky correlations were getting quite frustrating.

The nav sys error light after take off is usually either an incorrect runway heading, or the first waypoint is more than 180 degrees turn from runway heading direction, I'm finding there might be some issues with programmed in runway headings for Kola, and having some other nav system issues elsewhere. Going to do some more testing before reporting. Edit: Having had a quick chat with the ever helpful Myse1234 on discord it seems there is a bug with ground starts. Workaround is to re-enter the details for LS into CK37, either code or co-ordinates and ensure the runway heading is also correct. If you enter the airfield code for LS it should put all the right details in.

I would say that DCS is one of the most demanding games for my PC, pretty much a stress test. It often highlights if there is a driver or hardware issue that otherwise doesn't appear. As others have recommended try a DCS repair, try doing a windows repair (dism, sfc), update or reinstall graphics drivers and check ram timings. If you can post the DCS crash logs someone here can probably say what the issue is.

It might be because the Aim54 and R27 are still on the older missile code / behaviour, whereas the AMRAAM is effectively prototyping and testing the new missile API and code? To be honest I've lost track of what things are WIP and partially implemented, we've been waiting a while for the new missile API and code.

The natural dispersion does work quite well against lightly armoured or unarmoured targets, if you get the right attack path onto a target, practice a slight pull up manoeuvre while firing you can have spectacular effects against convoys throwing the rockets across their entire line formation.

In addition to this it can also be worth doing a Windows repair from time to time to make sure the underlying OS is still sane. https://support.microsoft.com/en-gb/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

This still appears to be an issue, any official comment from ED if TMS right short twice is the correct invocation rather than TMS right?

Finally got a chance to retry this feature, a few key notes for correct operation: Make sure the radar system is actually emitting and can be picked up by the Viggen (a few SAMs I tried didn't appear to power on, DCS things I guess) Make sure you are carrying the U22/a pod, the U22 doesn't have the silent listening feature The body of the jet seems to mask radar signals from the pod, the pod typically is mounted on the right side, also it picks stuff up in the frontal region only and is more sensitive than the RWR (picks things up further out). When the pod is receiving something the "MOTVERK" light will flash. You ideally want to fly around a fair bit and from a few different angles towards the SAM with accurate nav system for best results Return to base, land and put the master mode in "BER", this is a post flight data processing / extract mode. Check in your saved games folder, e.g. C:\Users\user\Saved Games\DCS_AJS37 for ELINTData.info, it should have some content in like ELINT: Emitter: 1 Freq: A PRF: 1800 First signal: 8:2:20 Last signal: 8:4:22 Sequence broadca: 0.1s Silent: 1.49012e-09s NW: 41:50:23 041:43:48 SE: 41:46:48 042:28:36 Combatflite is still capable of importing and showing ELINT files, but you have to go to options and select show ELINT as well as importing the file. And yeah, this wasn't very accurate given the SAM was based at Batumi river mouth xD This works about as well as it ever has done, you have to fly big laps and boxes around the area to get best results, and even then they aren't anywhere near HTS levels of accurate. I have tried this feature at low alt not at high alt. I also unfortunately don't have the Falklands map to try, but I am aware there are some hacks to get southern hemisphere working for the Viggen nav system. Perhaps these have not carried across to the ELINT feature. Edit: Also noticed, if you fly a mission with the ELINT feature and land it will then autogenerate an ELINT cartridge for a follow on mission based on the ELINT results.

I did some experiments with this about two years back against land SAMs and vessels, it was working then but even under ideal conditions (single emitter, non complicated environment, full fly around) it was not particularly accurate, perhaps at best 5-10km. But it did feel representative of a system of this era (i.e. based on INS not GPS, repurposing a directional jammer pod to act as a sensor). In a more complex environment the results got a lot more inaccurate. I will try to test again soon. Edit: It is probably also worth noting at some point the online tools for reading the U22 files broke. Combatflight also has the ability to read these files, and at the end of the day the U22 files are basically just a text file so you can read them yourself to check the DCS sim output before a potentially broken mapping tool reads them.

It might be worth testing this after dropping the bombs and also having never had the bombs on the plane but otherwise a similar loadout. A few DCS modules have had weapons drag bugs where using a weapon results in less overall drag then never having carried the weapon in the first place.

Bear in mind the RIO was typically also doing manual navigation techniques as a backup, the AWG9 was not 100% reliable!

It's fair to talk of modules going into "maintenance only" mode, but I would expect outstanding faults/bugs/inaccuracies to be fixed (the F5 has a few) and promised features to be delivered / complete (speaking generally here for all modules).

This, the F14A/B had among the first uses of microprocessors in a fighter jet, the doppler bins were handled in analogue electronics! It's a miracle it even manages TWS as well as datalink. The AWG9 TWS is going to suffer trying to track/correlate a manoeuvring target, as well as any lag (thankfully dramatic changes of position and vector seem to be minimised in this patch), but as a bonus you get a more efficient trajectory from the Phoenix when in STT.

Afaik it was kinematically overperforming, this has now been corrected but the sensors aren't operating as they should... this is due to be resolved when missile API update is rolled out.

It might also be worth disabling target motion tracking to help remove this as a potential issue. "Disable target motion measurement by going TAKT, IN, and enter 221 then press LS." Edit: Corrected the CK37 command, damn google search first result not checking due to lunch break

Also another good resource to understanding the why https://www.heatblur.se/F-14Manual/general.html#hydraulic-system TLDR: The F14 has two separate hydraulic circuits, one driven by each engine. The transfer pump allows transfer of pressure and fluid from one to the other if one is failing for some reason. On start up you want to make sure this works in case you have issues. So you deliberately test it by disabling it then re-enabling it into auto mode, with one engine on, and observing for pressure transfer between the two systems. The specific dial you are looking at is the above your left leg and looks like this, you should hopefully see one system healthy at 3000psi and the other equalise around 2400-2600 psi

Same?

Unfortunately this issues is not just one of ping. It would also be very useful for server administrators to also have a "client packet drop" monitoring capability and ability to kick clients who excessively drop packets.

Thank you, our group look forward to having their Royal Navy Foresstal class carrier back.

This has possibly been noted before As someone who makes older scenarios it would be nice to have this fixed.

Late last year, earlier this year (<Jan 2023?) skins were working on AI carriers in MP. This has been broken for this year. Oddly the skins appear fine when locally hosting the mission. This appears to be a dedicated server issue. In my case I am trying to use the RN skins (https://www.digitalcombatsimulator.com/en/files/3319581/) on the Foresstal carrier, but some other examples are reported in the previous, now closed, thread

I am consistently having the blackout on launch, F14A from Forrestal carrier.

Great news on the phoenix, also pilot body as per settings menu now? Edit: Had more time to test. Pilot body as per settings single player, multiplayer it still appears regardless of setting.

I also wondered why this had disappeared, makes sense now if it is perfectly aligned from startup.

Obligatory try a DCS repair, make sure you are up to date and remove mods, see if that improves things.