silverdevil

hello. i am unsure exactly what the problem is. though the log has these lines towards the end that appears to be the cause. looks to be a massive MP track. i believe there is a limit to track sizes. this is a similar post but not marked solved.

this can help. i know there are other users that have same latency and connectivity problems and VPN helped. i agree with max though i get that the real problem is with Deutsche Telekom AG. sucks.

it looks to me from your log you provided that you are having issues with getting to the DCS update server. open a command prompt and try to PING the site address ping www.digitalcombatsimulator.com Pinging digitalcombatsimulator.com [93.115.211.146] with 32 bytes of data: Reply from 93.115.211.146: bytes=32 time=113ms TTL=56 Reply from 93.115.211.146: bytes=32 time=112ms TTL=56 Reply from 93.115.211.146: bytes=32 time=113ms TTL=56 Reply from 93.115.211.146: bytes=32 time=114ms TTL=56 Ping statistics for 93.115.211.146: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 112ms, Maximum = 114ms, Average = 113ms

hello. this might be a local setting on your system. i do not see this anomaly. can you post your DCS log? it will have your graphics settings in the log for review.

hello. i tried your tests and got the following i am in USA Eastern VA. though the ping time is longer to dcs, i get 0% packet loss. typically with updates i get between 90 and 100 MB/s

good diagnosing. you should mark your post as solution. IMHO ED files getting corrupted by an outside app is not their app's issue. this is the problem of the outside app. see if you can get settings for the outside app to make it look in only the MSFS folders.

hello. lots of posts about this same thing. not virus. these files get flagged because they are encrypted. this keeps people stealing intellectual property. try this if you are comfortable add exceptions for Saved Games and the Steam folder where DCS resides. i have standalone. so my game folder will be different. https://forum.dcs.world/search/?q=virus&quick=1

hello. you may be seeing an influx of traffic because of patch. i have no delay with the three major servers. results of NSLOOKUP FORUM IP Name: forum.dcs.world Addresses: 2a01:4f8:212:3b43::2 136.243.139.132 WEBSITE IP Non-authoritative answer: Name: digitalcombatsimulator.com Address: 93.115.211.146 Aliases: www.digitalcombatsimulator.com CONTENT DELIVERY IP Non-authoritative answer: Name: 1231349722.rsc.cdn77.org Addresses: 109.61.91.247 109.61.91.245 109.61.91.244 Aliases: cdn.digitalcombatsimulator.com as you can see the IPs are all different. meaning different servers. i suggest restarting your computer. test. restart your network equipment. test. complain to your IP. wait.

agreed. the app i mentioned is provided in the MECM software center, and i chose silent /quiet switch. the app is dependent on .NET so there is no choice with silent to prompt for restart. after all that is what /quiet switch makes the app do.

ED is running the installations of the runtime updates for C++ silently. rebooting without prompt has been a known issue with .NET assemblies running silently throughout .NET 3/3.5 existence. i have an MFA component that i have never been able to get a prompt for restart when running silently. it is on hundreds of client computers. this is likely not an issue with ED code and more likely an MS issue. but it is standard practice to at least warn the user that a reboot may happen.

look for date of your C:\Program Files\Eagle Dynamics\DCS World OpenBeta\autoupdate_log.txt. look in event viewer application log for around same time. i have this entry. Log Name: Application Source: MsiInstaller Date: 8/9/2024 4:41:36 PM Event ID: 1029 Task Category: None Level: Information Keywords: Classic User: Computer: Description: Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time. i have four separate events. Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810 -- Installation completed successfully. Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Product Version: 14.40.33810. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. Windows Installer requires a system restart. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Product Version: 14.40.33810. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 2. Reason for Restart: 1. Product: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810. Restart required. The installation or update for the product required a restart for all changes to take effect. The restart was deferred to a later time. Ending a Windows Installer transaction: C:\ProgramData\Package Cache\{59CED48F-EBFE-480C-8A38-FC079C2BEC0F}v14.40.33810\packages\vcRuntimeAdditional_amd64\vc_runtimeAdditional_x64.msi. Client Process Id: 14892.

it may merely be that you do not have that key combo mapped. the mig-15 FC default keys is below. go to controls and search for "start" PS it is a good bug report because if you are told to press those buttons to do something and the AC does nothing, the mission should be remade. or you change the controls yourself to match the instructions.

hello. this log is better. i see a few things. 2024-08-07 12:05:48.348 ERROR VISUALIZER (14416): Failed assert `!(DLSS_Enable && globalMSAA != render::MSAA_OFF)` at Projects\Visualizer\Source\smSceneManager_Common.cpp:2437 2024-08-07 12:05:48.348 ERROR VISUALIZER (14416): Uncompatible graphics options DLSS_Enable & MSAA, reset MSAA = OFF for this i suggest you find Saved Games\DCS.openbeta\config\options.lua, rename to options.bak and then retry DCS. then at the very last line of the log 2024-08-07 14:00:21.419 ERROR DX11BACKEND (14416): DX device removed. Reason: 0x887A0006 for this is suggest totally removing graphics driver with DDU. then download and install latest driver. this could also mean a bad graphics card. hopefully not.

hello blackfalco. unfortunately i do not know the answer. i did a little research and came up with this video.

hello. honestly i had no idea this was a thing. but open your options.lua from saved games, search for ["radio"] = , check the true or false after the =. change to false. ["radio"] = false,

not quite getting the question or comment. what is the issue exactly? probably best not to post rants. this will likely not get any attention. but i am willing to try to help with correcting your problem.

as it has been suggested many times in the forums, report the files to the AV manufacturer. they will add them to the exclusions in their product and help everyone else that uses the the same product.

look in Saved Games\DCS\LOGS. DCS.LOG is the file you should share. if that is incomplete, check windows event viewer in Application log. look through that log for the date / time it crashed.

so there is a rather lengthy post about the support for openXR in DCS. i think i found the answer on one of the final pages. cutting out the bit -force_OpenXR in the shortcut this post particularly. hope this helps.

check your shortcut you use to start DCS. there may be a suffix in the run line that calls out openXR

hello. there is an issue with oculus and openXR with certain versions. you are likely being affected by it. if you disable openXR, does the sim run okay?

hello. the log you provided has very few lines and does not even show a crash. is there a windows event viewer entry from the time the DCS crashed. it may be a windows issue rather than a DCS issue.

hello. lots of people having oculus issues. perhaps you as well. see if this link makes any sense.

hello. is D drive accessible? is the drive external? is it formatted properly? can you post the last DCS.LOG anyway?

just to be clear. you are running both Malwarebytes and McAfee? not that important to the case. i am just curious.