Silversmith

Just allowed DCS updater apply the strange Update from/to the same version I mentioned above, it did a VERY TINY update, took about 2 secs to install. Since then the problem has gone away completely !! NO other changes made. Looks like can close this one.

Its not VR specifically, Identical crash occurs in same circumstances when running with VR disabled in Options/VR

Bizarre, just started DCS Open Beta and got the attached UPDATE notification updating from /to the same version !!! DCS Updater 2.9.17.19 17_04_2020 11_48_21.bmp

Just noticed similar sounding issue on the previous DCS version of 2.5.6 https://forums.eagle.ru/showthread.php?t=268986. Suggestion was that was a display driver issue. I had crashes only after the latest update (was fine before) and I am on the latest Nvidia display drivers, and have been having crashes before and after applying the latest Oculus driver update . So may be a different cause. Note issue doesa NOT occur if in Multiplayer fly a mission, then return to Spectators and flay a new role. Only occurs when mission is exited via debriefing, then a new misison is started or attempt to watch track.

Hmm, interesting we are both running in VR. Must try again with the headset off in SPECIAL/VR and see if the crash still occurs.

.. ran a REPAIR. Had no effect on problem, crash still occurs as described above.

Remove VR headset. Press ALT & TAB to select the crashlog window. You can then use TAB to move between the buttons, and SPACE to press the required button.

Following update to latest version of Open Beta . On loading DCS and selecting any involving F16 mission (Caucusus) runs fine. Quit mission normally to debriefing screen. If I either attempt to watch the track from the just ended mission (WATCH TRACK button) or Exit back to mission selection screen and attempt to start another F16 mission (either same mission or different mission) then DCS Crashes during the loading screens. Suspicious the log seems to show a problem with the (new?) afterburner sounds, but I may be misreading it. Log zip attached Each crash has also transmitted corresponding Log to ED. Multiple crashes .. Happens every time. dcs.log-20200416-230906.zip

No GUN in the German version. Crazy building a plane so manoeuverable with no gun. Given the way DCS is used we need a version with the gun, otherwise won't sell so well as it might .

The warbirds fare very well against the modern jets in a turning. Grim Reapers did one of their Videos on the subject.

Shader mod had virtually no impact on my Frame rates, I've removed it since its a pain to have to remove then reapply it each time DCS is updated. Happy with my performance anyway. Suspect benefit comes for lower spec machines.

Issue 1 should have been cured by installing the latest release of Vaicom, the previous release showed exactly the symptoms you describe on version 2.5.6 . Suggest you check you are on the latest version. Issue 2 I had this after update. The Vaicom entry in export.lua (Saved Games/DCS.openbeta/scripts/export.lua) had moved to first line within the file. DCS doesn't seem to like this, no idea why. I moved it to 2nd position using notepad++ editor and started working ok. (so my export.lua contains in this order Tacview vaicom srs) MAy or may not help you, but worked for me

Suspect the 2.5.6 update may have broken some of this, in particular 2.5.6 changed the expected location and folder structure of sound files. For me since 2.5.6 the F10 menu options respond as expected, but I get no associated sound.. Still works fine in the stable version at 2.5.5

Getting a TWS lock in the F16 seems HUGELY sensitive to aspect angle. Head on at 40 miles... 3 x Mig 23 easy tms right locks and switches targets with no problem. 15 miles at 40 degree aspect angle .. no chance, won't lock any of them. I don't know how accurate this is to real life.

Slow in a F16 (i.e. below corner) is not true. Look at the video Wags posted of the EEGS radar gunsight in actual real life use against a (not trying very hard) Typhoon. He is down around 170 kts at some points. and manoeuvring well F16 has a small turn radius down there and its power allows it to still manoeuvre a low speeds. If you only fly above corner you are wasting a lot of the F16 potential envelope. Indeed in DCS at 500ft Huns only the F16 can sustain 220 kts at 3.4g and 16 dps turn rate and a 1400ft turn radius. That is very fightable , especially against a Mig29 obsessed with corner.

I believe AACQ will only be 'seeing' one locked target at a time.. it converts to a STT lock once target is acquired, so no other targets to 'step through'. You have to break the lock and reacquire another one. Only in TWS (maybe LTWS? ) does the radar store multiple active targets that can be stepped through (using the undesignate) button.

Works fine for me. I don't use a target profile though, works fine just with standard DCS control mapping for button and axis setup. Never needed Target for any DCS module.

Finally bit the bullet and implemented DCS 2.5.6. since I couldn't get the updated VAICOM working with the old DCS 2.5.5 The VAICOM update worked perfectly with 2.5.6

I created an Alias in the Vaicom editor of 'Carrier' because it refused to recognise Stennis. Works a treat now (Tacan Tune Carrier)

Interesting. Worked for me in a single player mission where my plane was set up in Mission Editor as PLAYER, But not in either Multiplayer, or Single Player where my planes was one of several set as CLIENT. Should get the ROLE SELECTION screen at the start of a Client mission, but get nothing. I've tried installing several times with vanilla DCS 2.5.5 (no Mods whatsoever) and the same thing happens each time. If I reinstall the previous version of Vaicom everything works fine. What could I be doing wrong I wonder? Perhaps if I manually install Vaicom 2.5.16 rather than allowing it to auto update it will work. I'll give it a try.

The update appears INCOMPATIBLE with 2.5.5, do NOT apply the auto update if still on 2.5.5 If you do you will have to REPAIR DCS. (For some reason the Vaicom update suppresses the Role Selection screen in DCS so prevents you joining any mission with CLIENT slots )

I allowed the Vaicom auto update run whilst still on DCS version 2.5.5 No longer get the Role selection screen, so impossible to select a client slot to join a mission. Worked fine before the Vaicom update. Makes no difference if Viacom is running or not. Only way out was to repair DCS. So suggests the update is NOT compatible with 2.5.5 ? After repairing DCS 2.5.5 DCS works normally. Starting Voiceattack/Vaicom after the repair resurrects the problem so IF ON DCS 2.5.5 do NOT allow Vaicom to auto-update until you are on 2.5.6

Updated version of Vaicom, Associated Chatter and AIRIO are now available that are 2.5.6 compatible. Thanks Hollywood

Check your antivirus quarantine files ... Lots of folk on the 2.5.6. update are having ''worldgeneral.dll'' detected as virus infected and deleted into quarantine. Looks like the new DRM is spooking many anti-virus programs. What version are you on? 2.5.5 or the new 2.5.6

Many thanks, the time you put in is much appreciated by everyone.