Search the Community

Hello, I've had zero issues with my DCS for the last couple years until this last while. Issue: While in the F/A-18C strafing ground targets using the M61A2 cannon, I obviously switch to A/G mode on the left, and then select the 'gun' button on the left mfd which we all know causes the A/G gun pipper to appear in the HUD. PROBLEM: Diving down on a ground target, pull the trigger, burst fires but NO AUDIO of the cannon sound emits (minor issue). I pull up and away after destroying the target and then BAM, the server either crashes (no matter what MP server I'm on) or DCS crashes. This ONLY happens when using the F/A-18C cannon in A/G mode using the a/g pipper and diving down on a ground target. ***I've already re-installed files, the Hornet, deleted mods, etc as well as verified game files.

While DCS runs in the 2D mode, it freezes when loading in the VR mode. This began right after the most recent update. Before then, I had quit using DCS as the frame rates and stuttering made missions impossible to fly. Besides, MSFS and IL-2 still functioned. After doing some research, I decided to try DCS again with a few alterations I found on the web that promised to make the sim flyable again. Then came the update. When the program began locking up, something it had never done before, I tried various solutions found on the web, none of which worked. Finally I renamed the DCS World file and did a fresh reload of the sim. I verified it was fresh, as there were none of my aircraft or mission add-ons in the directory. Yet the new reload with no alterations had exactly the same problem booting into VR. I have quite a bit invested in DCS, but unlike MSFS2020 and IL-2, have not been able to use it much due to bugs plaguing the program. Where to now? Well, let's try a rant. Before I became an “IT” boy, I was a professional pilot/mechanic snowed under with FAA regulations. After eleven years of hanging around hangers with wrenches in my pocket and 2700 hrs in the cockpit, I left aviation because I got tired of the immense complexity involved with modern flight and its constant demands for compliance with mountains of arcane regulations. I'm a real stick and rudder guy. Much of my time was spent in the cockpit of Grumman's venerable Ag Cat, but I also flew Caribbean cargo runs in C-47s and C-45s before moving on to corporate jets. The last flying I did was as a volunteer, CAP search and rescue pilot in Alaska. I quit flying altogether when the FAA began it's ramp check program where an army of clueless bureaucrats swarmed over airports demanding to see one's papers, with no perfunctory “please” accompanying their demands. I began my foray into computers in 1978 with a college course on computing that used the Apple II with its Gumby (floppy) disk setup. The first computer I ever owned was a grossly overpriced 8088 machine purchased in 1980, but then to its credit, it never needed more than 256k memory. Back then I thought a 3.5 inch "floppy" disk and a ten megabyte hard drive was advanced technology and hearing a modem "handshake" was music to my ears. When early flight sims like Red Baron and 1942: The Pacific Air War came out, I was intrigued by the store displays, but not enough to invest time or money into the technology. Besides, aviation was consuming almost all my time, money and energy. After quitting aviation in disgust, I went on to spend more than twenty years with IT, getting paid to troubleshoot the same kinds of issues I'm now having with flight sims. I worked with robotics, networks and their servers, PCs, mainframes, dedicated word processors as big as a refrigerator, (How many remember those massive, dot matrix printers and their "silencers"?) I worked on countless other computer related machines as well, along with all the software that accompanied them. It got to the point I personally knew many of the guys I worked with at tech support. I bought the first so-called "smart" phone, before they were given that name, and equipped it with a headset I modified to work with the phone so I was able to talk and work on the systems at the same time. Back in those days, off the shelf, Bluetooth headsets were somewhere in the future. When I quit, I got rid of my smart-ass phone and have not owned one since. I finally got sick of the hassles involved with troubleshooting, so I left the IT business. Now I find myself paying to troubleshoot issues that are actually worse than the problems I once encountered professionally. I am not happy about the situation. Around the early part of the 21st century, I decided computer technology had finally advanced enough to try flight simulation. To this end I purchased a gaming machine equipped with a snazzy graphics card and staffed (or is that stuffed?) it with sims like the superb Rise of Flight (RoF), Wings Over Flanders Fields (WOFF, a rather doggy flight sim) and FSX. Then to enhance the simulation, I built a rudimentary simpit with a feed-back flight stick, a throttle quadrant with wonky pots and rudder peddles that looked a like a prize from a box of Cracker Jacks, but with a much higher price. I "flew" the flat screen for a while, going so far as to buy an over sized, over priced, 72" screen that would provide a life-sized perspective. For a brief moment I was wowed. However, while these sims functioned with very little trouble, I was still sitting in a room that was plainly evident. This was fine when flying "desk top" simulators like the ATC-610 for instrument training, but flat screen sims simply did not capture the feeling of actually being in those cockpits where I had spent 2700 hours. So I turned off the computer and went back to doing other things, like building models and creating dioramas with those planes I flew and planes I had always wanted to fly. I had been following VR development since the early 1990's and knew someday it would develop into a viable technology. A couple of years ago, when VR finally reached the point where the wide FOV Pimax 8KX came on the market, I felt VR technology had finally developed to where it was worth the investment of a rather substantial sum. To this end, I bought a top of the line gaming set up dedicated solely to sim flying and built a dedicated simpit to use with the sims. I then purchased yet more sims, three to be exact and lots of extra aircraft and other addons to go with them. However, this time I left out X-Plane. I put it all together, plugged it in, fired it up, installed the sims, went through a brief troubleshooting sequence during the setup and bingo bango! This was it! I was finally back doing what I do best, but this time in the kind of cockpit where I had always longed to be. Now I could fly like I had always dreamed flying would be in my youth. No licenses, no medicals, no bi-annuals, no check rides, no pre or post-flight requirements, no turbine stink, no flight plans, no radios, no customs declarations, no logbooks, no maintenance or fuel, no waiting at the terminal for the boss's call - no paperwork, no nuthin! Just fire up the machine, pull down the goggles and go flying without having to talk first with a lizard-lipped bureaucrat. Move over Waldo Pepper, 'cause here I come. Newt: The fun and games are over, Waldo. You guys been scarin' the hell out of people for too long. Flying is getting to be big business, and people gotta figure it's safe. (Unlike the 737 max) Waldo: You can't wave your papers and ruin our livelihood just like that. (Wanna bet?) Newt: You meet the requirements in here and you can fly again. But your planes have to be licensed, your pilots licensed. No stunting over congested areas, no wing-walking. It's all in there. When you're ready for inspection, let me know and I'll come back. But until then, you're grounded. Waldo: Gee, do you think if I study real hard Newt, I might pass? Are you gonna license the clouds and the rain? You gonna put highways in the sky for people to follow? Newt: Yep. All that, too. Along with airlines and airmail, and there's gonna be big money in it too, if you're smart. Waldo: Well, I'm no chauffeur, and I'm no mailman. I'm a flyer, Newt. Newt: I'm afraid not anymore, Waldo. That kind of flying is finished. Oh Yeah? Now I can fly anytime and anywhere I desire in the kinds of aircraft I always wanted to fly, along with many aircraft I actually flew. Unless of course there is yet another technical issue with which to contend. After a flight, I simply shut down the system and move on to other matters. What more could one ask for? Maybe a program that functions without requiring several hours of troubleshooting prior to flight? My sim rig has a bright red "Remove Technical Issues Before Flight" streamer attached to it. Every pilot understands why I want to fly, instead of spending my flying time troubleshooting problems that prevent a program from properly executing commands. I note this is an ongoing process that never ends and begins anew with every update. The varying, multiple levels of various programs interacting to enable the sim's functioning makes troubleshooting a far worse nightmare than it was back before the age of Steam, a time when computers still had Diesel Operating Systems. Today when one goes to troubleshoot a problem, the first step is to figure out (read guess) which program is the problem. Worse, is it a specific program or the interaction between programs creating the problem? Like that old hair dye commercial, no one knows for sure, not even the code cowboys programming the digital nightmares they leave behind for us to unravel. To paraphrase Rodney King's immortal words, why can't all our programs jes get along? When one researches a problem online, they find a thousand different solutions of which few, if any, work. Thus one must test each solution to see if it resolves the problem. Reboot, reboot, reboot and reboot again. I am astonished at how often I see a screen shot that looks exactly like the menu screen on my computer. Yet, while the screen shot menu looks exactly the same as the one on my computer, the needed click bar or button for assigning the needed function is absent on my menu screen. This technology is so muddled, one finds themselves spending much of their time trying to figure out why they can't figure out how it works. For this I left careers in aviation and IT, only to find that I now have the worst of both those worlds. Endless troubleshooting and endless time reading reasons why I can't fly. Someday, I would like to try flying DCS again as it seemed to provide excellent flight simulation the few times I tried it. - The Flying wrench

After today’s update the HUD is gone, blank. Helmet mounted works fine. When I turn the top left wheel under HUD, then it flicks on briefly and is gone again. I deleted my lua and let dcs create a new one. Same situation. Can anybody help?

Hi folks, so my DCS crashes A LOT after 2.7 came out. Mostly when you try to load a flight for the second time after loading the game. With the AV-8B it crashes 100% of the time when you try to either reload a flight or jump out and back in for a second flight. It's extremely frustrating. Anyone else in the same boat?

Ok, the first issue is George refuses to change rocket type to SMK when commanded with Left Long on the George AI wheel. COOP mode already active when this was tried. HE rockets in Zone A and B expended/empty. Secondly, with COOP RKTs still active, if I try to select SMK (Zone E) on my RKT page, I get a crash to desktop. Unfortunately no track, since CTD.

Selecting a coord as ACQ source sometimes immediately crashes the game. I have had this happen several times over the last few days and twice tonight. The first time it happened tonight I had used the TADS to mark a point on the ground as T01 while in another players Apache. The intent was to shoot at a target marked by JTAC smoke and a laser so I dropped the target point on the smoke and set the Hellfire to Hi LOAL. Then the second I went to the coords page and selected T01 as my ACQ source the game locked up and eventually crashed. The second time I had this happen tonight was about 10 minutes ago. I was in a solo Apache landed on the ground. I got a friendly MGRS grid and entered it into the aircraft via the point page. I then setup the Hellfire for a Hi LOAL shot since my friend was going to lase the target for me. Again the very second I went to the coords page and selected the point as my ACQ source the game crashed. Unfortunately I don't have a track file for this as both times it was well past an hour into a multiplayer session and tracks never survive missions this long or full of units (I actually disable track writing when in MP to save HDD space).

Hi fellow dcs users I’m having trouble with the f18 system when I fly the hornet and go to my store page is locks all of my system up to the point I can’t select a2a or a2g iv tryed different slots and tryed repairing the aircraft as well long story short it’s a full system lock up has anyone had similar issues

When trying to use the Apache module today I noticed the cockpit was not rendering and none of my stick or keyboard inputs were working. The only thing working were my headtracker inputs. what I tried so far: - reinstalling module - dcs repair - unplugging the headtracker - try different missions in both sp and mp Any more tips are welcome

Not sure if this is the right channel for posting so if it needs to be moved let me know. As the title states, server ground units spawn dead or not at all after a server restarts. This seems to happen when the server has been running for 6-8 hours in game with restarts. The only "fix" for this currently is to manually restart the servers from the front end. This even goes for "late activated" units that you would use for a base capture, server event, etc. 2 examples: 1) we have an airfield you can capture and it will give you that airfield as a spawn. But after some restarts or run time, when the next mission loads the airfield wont let you use it. 2) we have an event on our PVP server that if you complete the event by taking out some ground units that are set to spawn in 45 minutes after the match starts. Instead of doing the events at the start of the match you have those AI assets for your team because the server see's those event ground units as already not planned to spawn. We have 6 servers running at all times, PVP and PVE missions, created by two different mission makers both using different methods to see if there is better solution for this problem. Which hasn't shown any promise. We tried everything from just using Mission Editor trigger actions to using scripts. All ending in the same result. Which again is if the server has been running for 6-8 hours or more, and the server restarts in game, that isn't from a person manually doing it on the front end, the server breaks. Our most popular server normally sees 50-75 players.(we can do 100/100 DCS can't handle it) When the server restarts from a trigger hitting a certain time, when the next time the mission loads. Base defense ground units will be dead or not spawned in. These units are essential to fight off spawn campers. Without them it ruins the experience and player count drops, then players spread rumors saying the servers are unoptimized when its not our fault that DCS is broke. The only way to have those ground units spawn properly now is to physically go onto the front end and restart/shut down the server manually every 6-8 hours. This was not an issue until about 2-3 patches ago, you used to able to let a server run for 15+ hours without having any issues. This is a huge issue and needs to get resolved instead of mission editors wasting their time looking for a fix just for the servers to break again after a new patch. -The 162nd Vipers

After playing well for an hour, removing the Quest 2 headset for a break and putting it back on my head caused a slideshow that I could not get out of even after changing various settings in the Oculus debug tool. ALso if I cycle through too many other user aircraft using F2 it eventually starts too turn into a slideshow. Sometimes recoverable, sometimes not.

Hey to all, any known issues in graphics with the last update? I attach some picsnull

Several months ago I uninstalled the F-16 module, and it was working at that time. However, tonight I re-installed it and are having problems. As soon as you spawn in all the MFD's ,etc. go blank and none of the HOTAS functions work. I can fly the jet and the cockpit switches do work. The issue is within the Viper module, as my Hornet model functions normally I have already uninstalled then re-installed again.

I'm in the Viper, game running normally. I open the screen to adjust a control keybind and the game freezes up. I can still move cursor on the screen but the blue screen with all the controls doesn't move/react to any input, nor can I close it.

Worked perfectly fine yesterday. Today I keeps crashing.

Numerous note-taking and briefing screens pop out of the screen, making immersion impossible in VR, which is a real shame. What's more, there are a few bugs that force you to start the whole process all over again... Even if the promise is good, the reality doesn't live up to it. Very disappointing.

Only im still seeing a 20 frame drop between chase and cockpit view