Search the Community

In the sequence of this topic which is now closed: While opening DCS today, I noticed that there was an update today - DCS 2.9.13.6818 - and I was pleasantly surprised to learn that this update was supposed to fix this problem as it's stated in the changelog: Fixed: Damage model - Pilot cannot survive any explosive hit. And this fix not only applies to the F/A-18 but also to the F-16 and F-5E. Actually and since I own FC4, I can confirm that this problem also affects the FC F-5E. But and unfortunately after updating DCS and then making some extensive tests with the F/A-18, I didn't notice any changes/improvements at all regarding the pilot survivability when being hit by missiles. It's exactly the same as it was before the update! I didn't have the opportunity to test the FC F-5E and I don't have the F-16.

Hello dear pilot friends, I'm posting here because I think I've discovered a rather disturbing problem on the viper, I haven't found any other post mentioning this but this may be explained by the fact that if other people have a similar problem, they haven't been able to establish the origin. As the title indicates, these stutters occur when the altimeter radar is active, this is easily reproducible when I perform a dive or roll climb below 5000 feets. (See Track files) I was flying Hornet and recently switched to Viper, so I can't know if this problem appeared with an update or something in my computer configuration or if this is reproducible to other people. What I can say with almost complete certainty after having looked into the problem for several weeks and having tested almost every possibility of adjustment, is that the problem only occurs on the Viper among the other planes that I own (Hornet, Mirage 2000, F-15 FC3..etc) I first started by completely reducing my graphics options, tested different nvidia settings, tried different power plans, with and without HAGS, disable full screen optimization, disable core parking, add exclusions to windows defender, set high performance options in windows display settings, repair DCS, Clear all shaders caches, game and direct X, Disable hot plug, disable usb selective suspension but nothing was able to remove these stutters. After trying all these solutions I looked into the various electronic systems of the Viper and that's where I was able to understand that deactivating this simple switch solved the problem. With my current settings I was able to eliminate 98% of stutters for which I was able to determine an origin, 1% still remaining unexplained to me but only very rarely occur randomly and do not constitute a serious problem, remaining 1% that I can with certainty attribute to the ALT Radar of the F-16C. I can reproduce the problem on each map that I have, whether in a quick mission or via the mission editor, but my most convincing tests are taken from "Free Flight" on the Gulf map, you will be able to see by looking at the track that I release my load to go to cat 1 and give more agility to our bird.(Sorry if there were pedestrians down there) It would be interesting to know if other people are able to reproduce these jerks under the same conditions as me to determine if this problem deserves a correction from the devs or if unfortunately only my configuration is responsible. I'm certainly forgetting things to add so don't hesitate to let me know. Otherwise please excuse my English google translate but unfortunately this is my only way of communicating with you Despite its 5 years, my PC configuration with my settings still holds up quite well on DCS Configuration : Windows 10 22H2, Intel I7 10700K, Asus Z490-E, DDR4 32Gb (2x16Gb) G.skill Trident Z 3600Mhz, Rog Strix 3060Ti, Nvme SSD Samsung 970 Evo plus 1Tb, SSD Samsung 860 Pro 1tb, SSD Samsung 850 PRo 256gb, Asus PG279QM 240hz G-Sync, Hotas TM Warthog + Viper TQS Throttle. Nvidia Drivers and Panel settings : -566.03 (Old driver but which works very well for me (I am one of those who do not update if it is not broken especially since Nvidia missed the latest drivers) -Low latency mode: ultra -Power management mode : Prefer maximum performances -G-SYNC : ON -V-SYNC : Use 3d setting and OFF in game (Better for me on DCS) -Shaders cache size : 10GB (unlimited tested too without any changes) Windows Settings : -High power plan -Game Mode : ON ( tested OFF also ) -Game bar : OFF -Hags : OFF -Full Screen optimizations : Unchecked Among the attached elements you will find the comparison between Radar Alt On and OFF, I have also attached the use of my processors on msi afterburner because I suspected that radar alt led to a more intensive use of the cores when activated but by comparing this does not ultimately seem the case, the two seem similar... (?) Thank you for reading, I look forward to your feedback ! ViperStuttersRDRaltON.trk ViperStuttersRDRaltOFF.trk dcsRDR_ALT_ON.log dcsRDR_ALT_OFF.log DxDiag.txt

I noted this morning following the recent update that there appears to be a bug with Navigation/waypoints After start and standby alignment in the F16 I entered the coords for the runway threshold to help get me home especially when low on fuel. Usually the HUD reads 1 mile to WP while parked. However today it reads 55 miles/WP. The figure of 55 miles does not change regardless of the distance from the Airfield. I have undertaken this procedure many many times in the past and am confident this is not operator error. Worth investigating please. Many thanks in advance Nuggetz

Hab einen großen Bullahith mit meiner F 18 C .Hab herumgespielt mit einigen Mods und plötzlich sind alle Raketen weg.Ich kann das Flugzeug nur mit Bomben und Treibstofftanks bestücken im Missionaeditor.Irgendjemand eine Idee wie man das beheben kann? Danke.

Hi all, maybe I'm missing this somewhere, or perhaps it's not a feature - which I'm hoping can/will change - but my IHADSS in VR is about 1.5 to 2 inches too high for my sight picture. I know with the KA50 there is an option to move the targeting sight up/down for vertical eye centering, but not seeing anything currently in the Apache to do this.

I’m having an issue with my jet’s HSEL not working. I flew with a squadron mate tonight and his worked as expected. Here’s what I do used the HDG switch to a heading of my choosing(or enter the heading via the UFC) turned my jet in the general direction of the heading I wanted (though not the actual heading) selected A/P on the UFC Colonized HSEL on the UFC Nothing. The jet drifts left or right but never locks in on the heading I wanted. In the cockpit, HSEL on the UFC is colonized and HSEL shows up on the left DDI as a caution. Does anyone have an idea want I am doing wrong?

Anyone else having issues with the hotfix from today? I updated my server, the GUI sees it, but won't connect, says server error. All my missions in the server list have disappeared, and it won't let me add anything. I have the core game installed on my server rig as well as the server, when I updated I did the core game first, then run the updater from the server folder. Usually when I update the server it looks first into the core game for the files, and downloads the delta. This time it did not appear to do that. I ran a server repair (had to copy the updater repair .bat into DCS World Server folder). Said it was repaired successfully after I ran it. When I run the server it gives the correct version on the splash screen (8394). When I run the GUI, it says server detected, it seems to connect, but I get the server error message in the bottom left, and it won't let me start the server at all. I completely rebooted my server rig, the problem persists. I'll try and find the server log on the server rig and post it

Hi there, I tried to open a support ticket, but a video file is too large... so I put it here: The frequency of a blinking light changes with the zoom. 4070 card with most recent drivers. Why is this? Thanks! a-10 master caution.mp4

Was flying mission 11 in the new Ground Pounder Sims Campaign for the Viper, Last Out: Weasels Over Syria, and while I was trying to knock out the final set of mission targets I encountered a set of bugs that were new to me and made completing the mission exceedingly difficult. 1st the HTS pod stopped locking targets. I was not in Markpoint mode, nor did I, to my knowledge, change any settings or do anything that would cause the HTS to stop locking targets, but I could not lock any radar emitters on the HAD screen. Specifically I was trying to get the Snow Drift Radar but I couldn't get any of the others I tried either. Possibly related to this, maybe not, the TGP would not stay on the currently selected Steerpooint or locked point/area/INS track SPI. It continually popped off where I wanted it looking and, as far as I can tell, just started looking dead north of its own accord. I could CZ it back to the steerpoint for a moment, but it would jump back off to the north after somewhere between 0.5 and 5 seconds. Sorry for the very large trackfile, it is a very long mission. https://www.dropbox.com/scl/fi/pr7kpe1gzdqk096bcdllc/Weasels-Last-Out-M11-Vipers-1.trk?rlkey=4xb78i7n24trubcuhz6qszcp7&st=b0i4ry0y&dl=0 I start experiencing the bug after the first two SA6's are gone and while trying to engage the SA11 site. Should be about 1 hour in.

I tried GBU-12 on LST mode, but it does not track the laser or its not following it. I made a mission using dcs briefing room and used JTAC. When I used my laser, it worked and when I used LST, it didnt. When I used my laser code and watched it with F4 view, I can see it spots the laser and try to follow it, but when it comes to LST mode, it works like non-guided bomb. To check JTAC's laser, I used Maverick with LST mode, the Maverick worked. GBU-12 LST NOT WORKING.trk

There's a long standing persistent bug with the AZEL page. In about 1 in 10 of my Hornet flights I have an empty AZEL page, no DL or radar contacts. I've tried cycling AA/AG, I've trying cycling power off/on on the DL, tried changing weapons, nothing seems to jump start it's functionality. It only resolves if I re-slot. Does anyone know what causes this bug? Maybe some cold start switch activation order that should be avoided? I can't figure it out. Edit: It's happened to me in hot start too, so disregard what I asked about cold start switch activation.

These switches tend to randomly fire AIM-9s and AIM-120s since the update toiday Dogfight Switch – MISSILE OVERRIDE/CENTER UNCAGE Switch Dogfight Switch – DOGFIGHT/CENTER

After 2.9.8 update, in an instant action, the Eagle radar doesn't swing again. Sadly i don't know why, my DCS doesn't keep the tracks to update here. Anyone has the same issue again?

Hi ace pilots, I wanted to tell that the F-18 Hornet speed brake has a bug. When the speed brake on the Hornet is extended, it can no longer be retracted. I have tried every button config (OFF, Retract/OFF, and retract bound to STRG+B or to various of my HOTAS buttons) but the speed brake does not respond anymore after releasing, and stays fully or half extended. Please fix this bug because I need the speed brake at all landings. I wish you a wonderful christmas time, kind regards JetCat

I'm having an issue with Kobuleti remaining neutral at map launch even though there are red units (and no blue ones) spawned there. Anyone know why this happens, or why this only appears to happen on Kobuleti and not other airports?

Reproduction: Master A-G, CCRP Enable VIP, enter data Press OSB 10 to cycle sighting point at least once Disable VIP Enable VRP, enter data Press OSB 10 to cycle sighting point Crash occurs on underlined action. F16 VRP sighting crash.trk Ancillary note: DCS is restricting VIP/VRP mode selection to only pre-planned modes and data entry to when VIP/VRP modes are enabled. VIP/VRP should be selectable in any master mode (although only having an effect in preplanned modes) and data entry is possible at all times.

is it normal that when you start a mission in the instant action menu like "free flight" or landing or in Training menu, like "rolling and take off", that your viper has the main eletric switch power off. That means thar as soon as you enter the aircraft all system go down. You can quickly switch power on but then everything is f*d : INS (, HUD indications, ...).

So occasionally when i fly the viper (usually after harsh manoeuvring but not in dogfights) The viper flcs decides that stright and level is now impossible and random surface movements do sound good. It results in many (10 or so a second) random and sometimes quite harsh movements of the control surfaces and the aircraft. I have tried enabling digital backup doesn't really help. Sometimes changing the stores config or the gear will fix it sometimes temporally sometimes permanently. I have attached a link to the log sorry its long this bug is really random and i havent determined what the cause is so cannot replicate quickly. Log file https://drive.google.com/file/d/1k2yGR-_4VUw-a4h_KHptrdX1GlRcNeM5/view?usp=sharing Tacview file https://drive.google.com/file/d/1TweGp-0TIPx2hjXsAUbfn5RGYUM_GSGp/view?usp=sharing

Trying to build a multiplayer mission and cannot get a Blue F-5 to spawn at Novorossisk. Other aircraft (A-10A, UH-1) work fine and the F-5 happily spawns at other bases. Any ideas please?

I don't know if it is a VR bug or an F-16 bug but the green flood lights and the flashlight (alt-L I think) on the cockpit only works on the right eye. Landing lights and NAV lights are working fine. I use a RTX3070 with HP Reverb G2.

If you're using the new callsigns you won't be able to AAR. After hours of searching this is what I seemed to trace it to why the tankers wont respond. tankerstestnewcallsign.trk tankerstestoldcallsign.trk

Sometimes refueling/rearming in multiplayer doesn't work from time to time. Happened to now a couple of times, that after the refuling - copy - rearming - copy dialogue, either refueling, rearming or both never happens. The problem can be solved by a shutdown of the aircraft. Immediately after the engines spool down rearming and refueling are complete. I can't add a track because they're too long because it happens not all the time.

In the last few updates, the Consoles and Inst Pnl light knobs won’t turn using my mouse. The cursor will indicate I have focus on the knobs when I hover over them, but the knobs won’t turn.

It worked before the latest OB Update but isn't working anymore after the latest patch. Secondary monitor goes black but there are no exports showing up on them. Where do I even start to look?

I have noticed a strange thing with the AWW13 link with slam on the wep option , whatever the station choosen, the AWW13 will link the slam correctly. for exemple, if i choose to fire a slam on station 8 and i choose the station 2 on the wep option , the link works I think it's a bug otherwise the wep option wouldn't give us the choice of the station Another thing , i can link the AWW 13 even after the slam has been released. i would have thought i had to link BEFORE the release . Is it like that in IRL ? Thanks for your reply