maximov

I tried the place again. One of the attached tracks is a SA342 flight, the other is an F/A-18 flight. I'm a pretty inexperienced pilot, and I don't have my joystick handy. I flew using the keyboard. So far the game is not crashing. Boulder_CityFA18.trk Boulder_CitySA342.trk

After another crash, open the Event Viewer of Windows. Next - Window Logs -> System. Save these events as *.evtx file and attach to the post.

On the one hand I see that you have a problem not only with our game. From the latest DXDiag: Problem signature: P1: DOOMx64vk.exe Problem signature: P1: glquake.exe On the other hand, I would like to help you solve this issue. I will ask some more testers to check this section of Nevada. Also ask you to reinstall the video card driver from scratch on the official ATI website. And I want to clarify the flight conditions again: 1. Map of Nevada, coordinates PV87 N 35'55'9 W 114'55'47, construction area north-east of solar panels. 2. any module (not just Hind) And we are waiting for new reports

I saw a recommendation from programmers: if you have 32 GB of physical RAM, it is enough to have the swap file enabled. This is clearly not your case. Try to add another 5-10 GB (swap file should preferably be placed on SSD). The game may freeze slightly at a critical moment, but it will not crash. I tried the minimum settings of graphics + turned off all the shadows, effects, etc. I've tried putting maximum graphics settings (i7, 32GB RAM, 1660Ti, HDD - 5400rpm). I didn't notice a significant difference in single player. Considering that the main action for the pilot is in the sky, I would reduce the quality of shadows, terrain textures, smoke from pipes... Perhaps I'm just an undemanding player? Try experimenting with the settings yourself.

The latest maps developed by ED (Syria, The Channel) are more detailed than the map of the Caucasus. This requires a significant amount of memory. In addition, your computer must keep other players on the server in memory. That is, a significant consumption of memory when using modern maps in multiplayer is a normal phenomenon. But the remaining 400 MB is really too little to keep the game from falling. In this case, you can increase the swap file, reduce the graphics settings of the game or buy additional RAM modules.

Make sure that offline mode is disabled. Copy the DCS files to a new disk or download the game again. Remember to add the new DCS folder to your antivirus's list of trusted programs. Copy the DCS folder from the Saved Games folder. Good luck!

It's funny, you have new errors in every new report. 2021-11-09 21:54:04.071 ERROR DX11BACKEND: Can't load image '/textures/HandyWind_Central_RoughMet.dds'. Reason: The request is not supported. In the first ("old") dcs.log the crash was due to unofficial mod errors. Fixed it. 2021-11-09 22:26:57.749 ERROR DX11BACKEND: Failed to create shader resource view for /textures/mi-24p_ext03_RoughMet.dds. Reason: Not enough memory resources are available to complete this operation. In the second log, the crash was caused by a RAM flaw. 2021-11-10 21:28:01.839 INFO EDCORE: C:\Windows\SYSTEM32\VCRUNTIME140.dll The game now requires an update of the C++ libraries. Did you run the repair? The necessary C++ files must be installed during the repair. But you can try to update this Microsoft package yourself: https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

SRS usually does not cause errors. But the other DiCE_ folders... must be deleted. Then the repair. please, recent dcs.log

This time there is also the possibility of a game crash for this reason. But I suggest we stop at clearing the game of unofficial mods for now.

Please delete the C:\Users\bresc\Saved Games\DCS.openbeta\Mods folder and run repair The best option is a log without the "old" prefix The next time the game crashes, please accept the offer to send a report packet to our server

The maximum frequency of the GPU at rest is 1250 MHz, and the frequency under load should not exceed 1630 MHz. What frequency did you set? Operating System: Windows 10 Pro 64-bit (10.0, Build 18363) Try to install all Windows updates. You have a pretty powerful video card, but the diagonal of your monitor is also pretty big. Try lowering your game settings and testing the game in that "cursed" place in Nevada.

dcs.log, please

I can't repeat the crash. Conditions: Mi-24, Nevada map, flight from Boulder City Airport to a point with coordinates 35'55'9 W 114'55'47. I flew between two construction cranes and flew over the construction area. There is no crash game. Please attach a dcs.log after the crash of the game. There are also no crash reports from your account on our server.

I'm not sure if this is the cause of the problem. But I would like to rule out that possibility. DCS has always been a bad fit for virtual machines. Try reading the discussion on the Steam forum: https://steamcommunity.com/discussions/forum/1/1743358239830363122/

Are you using Citrix Workspace?

If in your first reports the game crashed due to errors in an unofficial mission for the Mi-8, now the graphics card driver is failing. 2021-11-06 07:59:32.021 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2021-11-06 07:59:37.890 WARNING LOG: 516 duplicate message(s) skipped. or 2021-11-07 03:10:07.941 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2021-11-07 03:10:07.943 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED Perhaps the reason is still the unofficial mods you have installed. Does the game crash without unofficial mods? Perhaps the cause is in the video card. Does the video card have overclocking? At what frequency is the GPU and video card memory running under load? What is the core temperature when the DCS is running? Try lowering the graphics settings of the game Is there a crash in the single player game? BIOS: BIOS Date: 10/16/15 21:38:54 Ver: 05.0000B (type: BIOS) Maybe there's a reason for that as well?

Did you take these screenshots at rest? Or during the flight? What is the temperature during work under load? In addition, there are many other errors in your log. It may not fix the crash, but I would like to rule out a mistake on this side. 1. Remove mod A-4E-C 2. Rename the folder C:\Users\jason\Saved Games\DCS in any name (Temp, for example) and run the repair.

Of course, you can check this way: https://www.digitalcombatsimulator.com/en/downloads/world/stable/ But, I think you may encounter the same errors. Attach an autoapdate_log.txt here or create a support request: https://www.digitalcombatsimulator.com/en/support/ Don't forget to give a link to this forum post in this case.

From your logs: 2021-11-06 00:44:57.876 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-11-06 02:11:05.156 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-11-05 16:32:48.561 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED This is an error driver video card. If your video card has overclocking (possibly factory), remove it. Also, please read the information here: https://www.digitalcombatsimulator.com/en/support/faq/startup/#3312253

The crash was indeed caused by a video driver error. But, in addition, a huge number of errors in your report are related to the folder C:\Users\timmo\Saved Games\DCS.open beta\Scripts. If new failures occur, delete this folder. Also, you may need to pay attention to the video card.

Try back to the previous driver version (DDU utility)

Please temporarily disable your antivirus / firewall and then run a DCS repair again. If the problem is resolved, please check the presence of the E:\DCS World OpenBeta folder in the list of allowed programs of your antivirus

The video card driver may show an error in case of a long wait for a response from the CPU (response from memory). If a swap file is used (memory with a low data rate), the probability of delay (and error) increases.

E-shop is a fully automated system. Sometimes the payment is delayed by the buyer's bank. Most often, this delay is resolved within 24 hours (completely automatically). After a 3-day delay, the order is canceled. There are no phones here.

As I understand it, you were able to successfully complete your order. I can't explain the reason for the payment delay. But nevertheless, the payment was successful. We will try to review the payment stages, but it will take time. You will receive a response in the support ticket.