All Activity

FYI completely uninstalling then reinstalling all Steam and the Oasis drive got everything working again. I just had a great time in the Contention Cold War server with no issues. Thanks again @mbucchia

I'd find it very entertaining to see the phrase "One Ping". Just one of many quotable quotes from Hunt for Red October.

@Floyd1212, Thank you for those supportive words and sharing a sentiment that has been brewing inside for some time. Please read along! @BIGNEWY, I digress from the main topic for a moment to address these sentiments stirring from within and as Floyd1212 kindly shared. Allow me to share my passion and support with the following: 1. I own just about EVERY module, terrain, asset pack. The few that I don't own are the Christen Eagle, MiG-19, and Hawk. I currently have 2 modules on pre-order. 2. I am one of those passionate players who support Eagle Dynamics and other third party developers. Not a day goes by without friends & family hearing me preaching from the gospel of DCS World. 3. I created a virtual squadron and rent a Fox3 server to host unit events. We play on a weekly basis and enjoy the camaraderie that often comes from military veterans. I am a proud veteran and many of my squadron-mates are also vets. This is where we go to "unplug" or decompress after a stressful week at work. 4. The modules that I fly the most are the F/A-18C Hornet and the AH-64D Apache. I would say that the hours spent in the Apache has surpassed the hours of time spent in the Hornet. Fun fact: I worked on the F-14A/B/D Tomcat and F/A-18C Hornet for many years. So you could say that I know a thing or two about these aircraft. 5. I own a few pieces of kit to help support my DCS "habit" such as WinWing F/A-18 Throttle, Stick (plus the F-16EX grip), Virpil rudder pedals, TrackIR, Cubesim monitors, and Cougar MFDs. All of these devices yield a benefit that I take full advantage of, chiefly to aid my aging eyes. 6. I have the pleasure of fixing several issues with the core and module-specific bugs. Three that come to mind: Constant heat seeker tone when playing as a MANPAD unit in Combined Arms, base coordinate error in the South Atlantic map, and the F/A-18C Pilot survival rate(*). Many of these bugs were left untouched for 9 months or past 1 year after being "fixed". As I recall, the IR tone for the MANPAD was supposedly fixed 1 year before I re-addressed the topic. Here's a 4th change: I was also responsible for pushing for a change in how sound files are stored in the mission files. Before, certain sound files would arbitrarily reset. That's like playing a game of whack-a-mole in a large multi-player mission! * - You fought me and other clients tooth and nail - claiming the pilot survival rate was perfect. It was FINALLY changed after an outcry from several Hornet players and supplying data to back it up. 7. While I don't play DCS every day, a large part of my weekends - Thurs through Sun revolve around playing in one of my squadron multi-player missions. It's not uncommon for me to fly for 6+ hours per day. 8. There feels like there is an "Us vs Them" mentality when it comes to reporting bugs. It appears the stance from any ED team member is denial of a problem or at least deflecting the problem to a user-induced problem. I'm sure there's data that may prove casual users induce many problems. For many years (and still ongoing), ED counts on a core of passionate players to submit bug reports or suggestions to make each module better. Which was the reason to have an Open Beta branch. However, constantly saying "there's no problem here" or to dismiss a bug/suggestion because I represent a small percentage of players is flatly a slap in the face. Your model for improvement was centered on player feedback. 9. I believe that a module dies from a thousand "paper cuts". I mean to say that while a module may provide a lot of features, there are fine cracks that can be easily seen when looking beyond the casual player's mentality. Here is where attention to detail will spell success or failure for a module. Hey, I want to do X...too bad. Not supported. Why is feature Y broken? You represent a minority so don't hold your breath for us to fix it. Oh, an update just broke my helicopter. Each time I start the aircraft, the CPG windshield wiper turns on and will not shut off (where have I seen that problem manifest?). 10. ED needs players like myself and Floyd1212 to identify bugs and provide invaluable feedback to improve each module. I have ranted long enough. There are a few more points that I wish to address but this is long in the tooth already. Please do not misconstrue my talking points as a personal attack or making ED appear to be the bad guy. That is far from the case. I wish to point out some examples as a learning process. I am always available to talk via DM, Discord, email, and/or experience my squadron. Send a DM if you would like to set something up. Getting back to the AH-64, I really believe ED hit one out of the park when this module was initially released. If it supplanted my time in the F/A-18C Hornet (and knowing my background) then that's one HUGE compliment! There are many small improvements that need to be made to make it a superior module. Dare I say it should be a flagship module! Making adjustments to the TEDAC display is one and wrangling GeorgeAI is another avenue for improvement. But dealing with GeorgeAI is a topic for another thread! How's that for passion and support? Now, for a little humor and to paraphrase Pulp Fiction: can we, pretty please with sugar on top, fix the effin' Apache?

Is this related? 2025-09-03 01:20:23.917 INFO Scripting (Main): event:type=crash,initiatorPilotName=Su-27,t=2572.921,initiator_unit_type=Su-27,initiator_object_id=16782337,linked_event_id=0,event_id=138,initiator_coalition=1,initiator_ws_type1=1,initiatorMissionID=1000007, 2025-09-03 01:20:23.917 INFO SCRIPTING (Main): Error in SCHEDULER function:[string "l10n/DEFAULT/DynamicBVR.lua"]:197: attempt to index field '?' (a nil value) 2025-09-03 01:20:23.917 INFO SCRIPTING (Main): stack traceback: [string "l10n/DEFAULT/Moose.lua"]:13007: in function <[string "l10n/DEFAULT/Moose.lua"]:13004> [string "l10n/DEFAULT/DynamicBVR.lua"]:197: in function 'EventFunction' [string "l10n/DEFAULT/Moose.lua"]:13412: in function <[string "l10n/DEFAULT/Moose.lua"]:13411> [C]: in function 'xpcall' [string "l10n/DEFAULT/Moose.lua"]:13410: in function 'onEvent' [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>

The main problem here is how we continuously get "realism" upgrades without any fundamental game upgrades to deal with the increased realism, further contributing to the "Digital Cockpit Simulator" problem that the customers have been complaining about for the better part of a decade. How is this damage modeling going to work with the dynamic campaign where unscripted CAS scenarios are going to be involved? Currently the only way to simulate CAS is to have everything so scripted where the friendly units are set to immortal, enemy units are set to invisible, and the friendly units are set to "fire at point" somewhere in the general vicinity of the enemy to create a fake CAS atmosphere. In short, we've got more realistic bombs operating in an arcade system.

Still broken. Not a wishlist item, broken. Supercarrier lights once illuminated the cockpit.

I can barely hear the morse code beeps from the nav radio. Is there a volume knob in the plane that I can't find? What sound/volume setting in DCS Options maybe? I have: Main Audio Out = PC Speakers Headset = Headset

Appears to be 3 degrees north on the ME. Runway heading 291, loc 288. However in flying the Viper my loc was so far right I would have hit the terrain to the northeast of the threshold. Why would the localizer be offset to put aircraft closer to that hill rather than offset south where there's no terrain? A south offset makes more logical sense due to the terrain here.

Well my experience has been great. I am having better Frametimes in DCS compared to what it was before.. The apache I flew 2 MP Missions and they both were flawless no issues at all.. For what I paid for it I am not going to complain at all. Mbucchia is a legend in my mind..

Also Phantoms abfangen! (dann eben ohne Zusatztanks ) und Ai Tornados? Wobei ich ab hier dann doch erstmal nen AlphaJet (gibt es leider nicht) vorziehen würde. Ne 104 wär auch noch denkbar. Kommt ja irgendwann was von Aerges.

500lb bombs dont kill everyone within 300m. End of argument

I fly with 3rd Guards Fighter Aviation, but I am always looking for groups.

I am working on a Linux Email Filter based on Postfix, spamassassin and amavisd on openSuSE. It's been at least 15 years since I have done that last time and with the acceptance of cloud services I thought that would never come back and deleted my old notes for Postfix etc...arrgghh. Knowing that this is full of traps and the least you want is an open relay..LoL...for the client .... I got myself a Domain, tortured Ai for main.cf. and master.cf config file help as what I researched and tried didn't load at some point. Ai is nice, it told me why it got halted, what that is about etc... nice info to build your picture again. So, next thing is a brand new openSuSE Hyper-V, configure as Ai tells me and see if the Mailserver behind it gets some mail.... if it ends up as an open relay it's only my test domain and if they put my IP on blacklist is not that dramatic. I have seen other come on a black list and it sucks if you need to get off NOW, that's a tough part, been there but wasn't the idiot to blame. Took'em days w/o mail. That's when you learn, IF you host your own Email, DO IT RIGHT ! or better leave it. Only 1 client still runs his own SMTP server and the attacks are brutal, 3 a second, name..password....endless. I need to put a box in front of it that catches all those and also filters for unwanted content. I had that as a standard for all Exchange Servers back in the days when people still had them on premise...but that's over a decade ago. What I haven't forgotten is: Don't configure an open-relay...check, check...double check. IF NOT-:::: we'll have another story LoL

As explained in the manual (chapter Mission Editor), the NVGs are there for people who want to make non-historical missions or perhaps a modern conflict, forced to use an old aircraft, or similar. Could also be important for server owners who offer multiple aircraft in a night mission. DCS is a sandbox, so the mission author can decide if NVG is allowed or not for their mission. As you said, NVG were never used on our F4 model within the timeframe it was used by the US.

The patch cannot be uninstalled at all, at least on my affected client machines. W T F ? I'll go crazy if my own machine decides to join that club I am over 60% full on all nvme drives but my Linux's SanDisk Sata Bootdrive...and 50GB transfer are a daily thing.... Already counting backwards ***D a m o c l e s ' S w o r d*** So happy that I got myself a M4 Mac-mini recently, that thing rocks and no such BS. Oh man MS, I run this old MacBook Pro 15" for 13 years now, it still runs hours on battery and hasn't let me down a single day in it's entire time. Nothing stupid, just simply working as expected. When I work on the Macs for hours I dislike the Windows Look & Feel when I get to my men's cave gaming rig. It's rough, it's forcing me to a lot of things, spies on me and now the greater family suffers Alzheimer and forgets it has "A DRIVE" from time to time. What a freaking show from MS. Just waiting for things to unfold..LOL

There is an English cockpit which is separate from Avionics Language. Sounds like maybe you are changing the Language setting, which is for the entire sim GUI.

DCS MT Deactivated Trains are fun ! Electric VL-80 Lifts off over the SuperCarrier ! Maybe the Deck crew will position tracks for the landing and parking.

skin looks good. but none of the lights on the dashboard are working with this. and the text on attitude indicator ball should have more contrast. ball is grey, text is greyish.

Thank you for reporting. If you have tacview file please send it too. How many dynamic missions you have played?

Without getting too into the weeds on this issue just step back and think about the big picture. Could the R2800 possibly have achieved the reputation for reliability it had if it worked like it currently does in the Corsair? I suggest people fly the P47 module that ED did and compare the two. I particularly like that the ED radials offer audible feedback about operating out of limits, and have partial failures or will fail overtime rather than always instant and total failure. You can fail the P47s engine, but it puts up with a lot before it quits, matching its reputation.

Before jumping in the back seat, ask Jester to designate something, then you can proceed to the back seat and proceed.

No clue what everyone is talking about not being able to go faster than 200 mph. Took off from Batumi, 50% fuel, 100% gun, no stores, default weather. Climbed at 5 minute mil power to 5000 ft and then went to rated power per the knee board 2550 rpm and 49.5 inHG MP at low blower for speed testing. Topped out around 266 knots IAS, with oil cooler adjusted to keep it below red (I think it was closed, or just cracked), intercooler open enough to keep the over temp light off, and the cowl flaps cracked. If I buttoned it up and ignored the lights I'm guessing I'd get a few more knots IAS. At 5000' MSL on a STP day, 266 knots IAS, is 285 knots CAS, or roughly 328 MPH. Well in excess of 200 mph. I then climbed at rated power to 30K, I don't recall exactly when I passed the critical altitude for the supercharger. I hit 30K, with about 37 inHG, and was climbing at 1500 fpm at 130 knots IAS, and took about 15:30 to do it in. I'm not sure what the issue everyone is having? Then engine thermal model has some oddities, but as far as climb rates, speeds etc, I'm not seeing glaring issues. I don't know how it tracks the real numbers because I've seen probably a dozen different charts that all differ now, but I'd say it's certainly in the reasonable ballpark.

Nomad, are you still looking for a REDFOR squadron?