All Activity

That's from the wide angled camera that captures the scene. especially in those right banking turns. Picture this: Pilot's view 12 o'clock sees the horizon, 3 o'clock high sees the horizon and 6 o'clock sees the horizon. The cameras FOV sees almost the whole horizon line at the same time/picture. what else than a massive curve should be the outcome?

Afterburner test DLSS on.trk Just to point out what it looks like on my end. I have tested it with DLSS on and off, but not uploaded these because there was no difference.

I am astonished to see that this major issue was not fixed in the following update. From my perspective a roll-back should be possible and adequate. Is even more track replays needed or what? Here is a bunch of the most resent ones. Everyone got this issue. http://eu.4ya-servers.nl/tacview/Project Overlord WWII/

2025-07-26 06:10:27.077 INFO SCRIPTING (Main): MenuRegistry - creating menus for player: Springfield1-1 |Arbitrary 2025-07-26 06:10:27.092 INFO ASYNCNET (Main): release unit 2882 2025-07-26 06:10:27.165 INFO ASYNCNET (Main): client[1] occupied unit 2025-07-26 06:10:27.166 INFO EDCORE (Main): try to write dump information 2025-07-26 06:10:27.270 INFO EDCORE (Main): # -------------- 20250726-061027 -------------- 2025-07-26 06:10:27.272 INFO EDCORE (Main): DCS/2.9.18.12722 (x86_64; MT; Windows NT 10.0.22631) 2025-07-26 06:10:27.274 INFO EDCORE (Main): E:\DCS World\bin-mt\DCS.exe 2025-07-26 06:10:27.276 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff6b6950aed 00:00000000 2025-07-26 06:10:27.278 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'E:\DCS World\bin-mt;', symOptions: 532, UserName: 'user' 2025-07-26 06:10:27.280 INFO EDCORE (Main): OS-Version: 10.0.22631 () 0x100-0x1 2025-07-26 06:10:27.283 INFO EDCORE (Main): 0x00000000006b0aed (DCS): SW + 0x999ED 2025-07-26 06:10:27.285 INFO EDCORE (Main): 0x00000000006eace8 (DCS): SW + 0xD3BE8 2025-07-26 06:10:27.287 INFO EDCORE (Main): 0x000000000088b653 (DCS): SW + 0x274553 2025-07-26 06:10:27.289 INFO EDCORE (Main): 0x00000000008468f3 (DCS): SW + 0x22F7F3 2025-07-26 06:10:27.291 INFO EDCORE (Main): 0x00000000006935ce (DCS): SW + 0x7C4CE 2025-07-26 06:10:27.293 INFO EDCORE (Main): 0x000000000088b559 (DCS): SW + 0x274459 2025-07-26 06:10:27.293 INFO EDCORE (Main): 0x00000000009facca (DCS): SW + 0x3E3BCA 2025-07-26 06:10:27.293 INFO EDCORE (Main): 0x00000000009fc0eb (DCS): SW + 0x3E4FEB 2025-07-26 06:10:27.293 INFO EDCORE (Main): 0x00000000009fad79 (DCS): SW + 0x3E3C79 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x00000000009ce615 (DCS): SW + 0x3B7515 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x00000000009ce083 (DCS): SW + 0x3B6F83 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x000000000005bd0c (WorldGeneral): wControl::Control + 0x5C 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x0000000000004508 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3D8 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x0000000000004aa2 (World): wSimCalendar::DoActionsUntil + 0x262 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x0000000000a644ed (DCS): SW + 0x44D3ED 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x0000000000a641c4 (DCS): SW + 0x44D0C4 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x0000000000a87b39 (DCS): SW + 0x470A39 2025-07-26 06:10:27.294 INFO EDCORE (Main): 0x0000000000a3c844 (DCS): SW + 0x425744 2025-07-26 06:10:27.295 INFO EDCORE (Main): 0x0000000000a3de83 (DCS): SW + 0x426D83 2025-07-26 06:10:27.295 INFO EDCORE (Main): 0x0000000002584cf0 (DCS): AmdPowerXpressRequestHighPerformance + 0x107ECEC 2025-07-26 06:10:27.295 INFO EDCORE (Main): 0x00000000010c5632 (DCS): SW + 0xAAE532 2025-07-26 06:10:27.295 INFO EDCORE (Main): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D 2025-07-26 06:10:27.640 INFO EDCORE (Main): Minidump created. Doing some testing after the patch. Local DCS Client instead of Server. Immediately got a similar crash on the previously stable Syria Cold War, pre-2.0 Pretense. Flows into the same wControl...wSimTrace...wSimCalendar::DoActionsUntil

So bub... with the likelihood of the Super Herc coming out late this year, or early next... how's that crow taste?

Small update here: Let me know if you need anything more.

I've got a few fixes going like making the 2nd Growler a jammer also. But mainly putting the attachment @Special K made into \Saved Games\DCS.openbeta\Config AND Program Files\Eagle Dynamics\DCS World OpenBeta\Config makes it go again. Should work with any MIST-based script, IMHO. Your utility may vary. autoexec.cfg

See https://forum.dcs.world/topic/376664-crash-when-landing-on-carrier/#comment-5673161 for details

Amazing Eurofighter 360° simulator video: The audio is German, but this thing is not your grand dad's simulator. Not articulated though. The shots of a guy kinda hanging on to the outside of the cockpit are kinda surreal. The guy flying is a commercial Airbus pilot. TIL the FBW likes being flown "one input at a time". The HUD has arrows that show the maximum rate of climb without slowing down, and the thing won't let you stall; they show how the thing refuses to keep stalling and puts the nose down. I wonder what software this is? One thing I notice, the world is VERY round in this sim, either this is a property of the projection dome or the Germans are actively working on debunking flat earth ;)

After the drama with the Hawk you promised that from now on you would own the source code of all third-party modules so that this can never happen again. Obviously that was a lie.

Hi Guys - an update. But first, a big thank you for all your comments and suggestions - WE HAVE IT FIXED (hopefully) Went back and checked the 'dodgy' SSD on another USB port (original USB port was a USB 3.0 so should have been OK) - same slow rating with Crystal Mark. I also had another of the same SSDs (bought them on discount for the pair) - is being used just as additional back up drive on my wife's PC. Same slow rating on Crystal Mark. Does work fine as a back up file drive anyway - so looks like the wife gets another one. They are a Seagate 2TB SSD so you would think OK. However, maybe the discounted price was for a reason !!! For info Drive H has a USB-C connection and works great. So, copied (as suggested) DCS folder back onto the original Drive D internal SSD. Did a slow repair, edited relevant shortcuts etc ...... and it worked just GREAT. Much quicker loading, runs as smooth as silk, no stuttering or lagging in both triple screens and VR .. I am in love with DCS again. So looked like those SSDs are just not up to the demands of DCS. So have placed an order for an ADATA Elite SE880 USB-C Portable SSD 2TB Drive. Specs seem to indicate that will do it. so once that arrives will copy over to that SSD and start to reinstall all those maps and modules waiting for me. So once again, thanks

Invert does it for me. Are you confirming your choice with double OK? Sometimes people just cancel their choices without thinking about it? You can also do a repair.

Where does it say that? I'll bet you $20 the real horn comes on in the first 1/4" of the throttle's travel, not the first 1/4 of the throttles full range of motion, then someone misinterpreted it, and no one went back and checked.

This horn cannot be right at all, min rpm of 1800 lets me run a little over 33" of mercury (+3 boost) before the horn sounds, and the mosquito cruises along at about 230mph. Fine, but what if I want to loiter in a spot, say in a maximum economy mode, perhaps while attempting to communicate with the navigator, or via a radio. Why do I need to listen to this horn throughout that? Please someone show me a source that says it was really like this, otherwise common sense was not consulted on this module.

I ran VAICOM PRO with 2.7 a couple of years ago and could say 'Salute' to launch off the cat (SC). Took a break for a couple of years and coming back to it and for some reason 'Salute' won't work any more. It looks like the Pilot Salute key bind changed to LAlt + LCtrl + LShft +S, so I changed the keys in the VAICOM profile, but when I give the command, I still sit there on the cat. I'm getting the Recognized: 'salute' and it's sending (Ground Crew], [Salute] but nothing happens. If I manually press the keys, then off I go. I've tried reconfiguring the key binds in DCS and VAICOM and am at a loss. Anyone have a suggestion? Thanks!

Yes, I’ve tried that too. I’ve installed DCS on both of my solid-state drives, but it didn’t improve the issue at the time. From what I’ve found through searching, this beeping sound might occur when the system freezes due to high CPU load

Lol. Couldn't make it up? Pimax managed it. Again.

And if one side has breached said agreement, repeatedly, why would you wanto to implement it? Timelines and attention to things and details being said and done outside of the box are important here.. 6 months ago on various platforms one of the main protagonists in all of this stated that ED hadn't even been in communications and/or were not responding to communications, and shouting to all who listened that ED actually went back on a deal that had been made.. IIRC this was about a release of funds... first breach of said confidentiality clause twice in the past 4 months Ron Zambarano has gone to the court of public opinion stating more or less the same thing, and that they had exhausted all measures... more breaches of the confidentiality clause... Do you not see a pattern here? Ron and his subcontractors should have stuck to "Less said, soonest mended" If the confidentiality clause kept being broken, why would you implement whatever agreement was put in place... Ron needs to take a close look at himself and realise his ego is one of the main issues here. Notice that by all accounts, he still has accesss to ED's SDK after it removed, he's not mentioned anything recently about it having been removed again...so that's the glimmer of light in this shyshow.. Nick Grey also needs to do similar.

Happened to me three times, once on 4YA server and twice in Afganistan weapons practice instant action mission. Command George to FCR area search; select target; select George weapon missile; consent to fire...instant CTD. Track attached. Edited to add: engagement with laser HF on point target worked fine, as did the traditional PHS point search and engagements. LastMissionTrack.trk

this worked for me too however not during case 3 landings (ctd occurs)

They've yet to agree to enact the agreement. I know, it's like something out of the minds of Monty Python. It's great and all, but honestly? Some assurances in a worst case going beyond "It'll work in 2.9.x" would be REALLY appreciated. I don't think a legacy version is going to cut it in the event of 4 modules going the way of the dodo. This wasn't a small install base like the Hawk was. ED's going to have to do something very, very big for consumers in that worst case scenario. I'd be a lot more gunshy about DCS in that case. I would not be alone. That's money I can put into cycling or flying.

I think I found it! It's an alternative to SlugMouse and PointCtrl. Cheaper and easier. I bought it. Works like a regular mouse. D06 Mouse on alibaba.com

Maybe the bomblets are not having time to arm. The canister may be opening but the bomblets are not arming in time. Depending on the altitude you are releasing the bombs, they need time to open and arm the submunitions. You cannot release the bombs from a high altitude and set the burst altitude too low, otherwise you are not giving enough time for the bomblets to arm. Refer to the following thread: Also, I attached a spreadsheet showing the calculated height above ground that the bomblets will armed. Line 36 of the spreadsheet refers to your first run. You released from 19,000 feet with a VT1 of 700 feet AGL. The problem with this setting, considering a standard ARM Delay of 1.2 seconds, is that the bomb will open 33.73 seconds after release and be armed at 34.93 seconds. It gives an altitude of -625.36 feet AGL, meaning that the bomblets will hit the ground before being armed. For the other bombing runs, with the burst setting at 2,200 feet AGL, it gives the bomblets enough time to arm, being able to arm at around 1,000 feet AGL over the target (lines 33 to 35 of the spreadsheet). However, the problem I noticed is that with CBU-99 you need to be right on the money when attacking the target. As precise as you should be using Mk-82s, for example. If you hit a little bit off, the bomblets won't have much effect, or none at all. And by releasing them from altitude, the bombs miss by a little and the bomblets cannot have an impact on target. See the attached track file. I make one run from altitude with no effect, and the another at low level, with much success. From my testing, CBU-99 and Mk20 work way better at low level, from 1,000 to max 5,000 feet over the target. CBU-99 Height of Function.xlsx F-18 - CBU 99 - FMU-140 High and Low.trk

thats an odd series of beeping and it definitely sounds hardware related. Start looking for issues in your device manager, try installing it on a separate disk drive not on your windows partition, and if anything try to install it on a new hard drive separated from the other hard drives. Id just remove the others - save for the windows disk drive and just go from there.

This is what is frustrating and puzzling....if there was an agreement reached 8 or 9 months ago why is the issue not resolved? That is what agreements are supposed to do, right?