ContraStorm

This started happening to me right after the last patch. I even removed all my mods and also repaired the game, and the game keeps crashing exactly at the same time. I have sent about 20 crash reports already.

I understand this issue may have been raised previously, but I would like to bring attention to the persistent problem with the thickness and fuzziness of the Heads-Up Display (HUD) on the F/A-18 when users are utilizing resolutions higher than 1080p. It's concerning that despite the passage of several years, this issue remains unresolved. I urge you to prioritize addressing this issue, as it significantly impacts the user experience for many of your customers. Thank you for your attention to this matter.

I'd like to bring up a point that may have been mentioned before, but I believe it's worth addressing. When engaging Air-to-Ground (A/G) mode on the F/A-18, there's an automatic switch of radars that I find inconvenient. Specifically, I suggest that Eagle Dynamics consider removing the automatic switch of the right DDI to Ground Radar when A/G mode is selected. Personally, I prefer the ability to manually change radars based on my needs. Typically, when I choose A/G mode, it's either to utilize A/G armaments, check my air-to-ground armaments, or configure them in-flight. An additional issue arises when transitioning from the ATFLIR on my right DDI to A/G setup. The automatic switch to ground radar upon selecting A/G mode is not only undesired but also disruptive to the flow of my activities. In summary, I propose the removal of this mechanic as it proves more annoying than beneficial. Having control over radar changes would enhance the overall user experience by eliminating unwanted interruptions during critical moments.

dcs.log

Here is a log of a session I just did. It seems to crash when I have AV-8Bs land on my carrier and when they collide on one another when they are landing the game crashes. 2023-10-08 05:43:28.340 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2023-10-08 05:44:07.438 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2023-10-08 05:44:12.438 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3840, 2160] 2023-10-08 05:44:15.290 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-08 05:44:15.290 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.000000 2023-10-08 05:44:15.290 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 1.000000 2023-10-08 05:44:15.290 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-08 05:44:15.290 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 1.000000 2023-10-08 05:44:16.912 INFO GUI_MAP (Main): levelformap=1 2023-10-08 05:44:18.811 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-08 05:44:18.811 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.500000 2023-10-08 05:44:18.811 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 0.666667 2023-10-08 05:44:18.811 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-08 05:44:18.811 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 0.666667 2023-10-08 05:44:50.190 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-08 05:44:50.190 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.000000 2023-10-08 05:44:50.190 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 1.000000 2023-10-08 05:44:50.190 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-08 05:44:50.190 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 1.000000 2023-10-08 05:44:52.809 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-08 05:44:52.809 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.500000 2023-10-08 05:44:52.809 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 0.666667 2023-10-08 05:44:52.809 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-08 05:44:52.809 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 0.666667 2023-10-08 05:47:33.360 ERROR GRAPHICSVISTA (Main): Can't open model AV-8BNA-OBLOMOK-ELEVATOR-L.

I am guessing this is what you are looking for, right? 2023-10-07 23:44:31.828 ERROR_ONCE DX11BACKEND (25136): texture 'carrier_miniboss_roughmet' not found. Asked from '' 2023-10-07 23:44:57.610 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-07 23:44:57.610 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.000000 2023-10-07 23:44:57.610 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 1.000000 2023-10-07 23:44:57.610 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-07 23:44:57.610 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 1.000000 2023-10-07 23:44:59.273 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-07 23:44:59.273 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.500000 2023-10-07 23:44:59.273 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 0.666667 2023-10-07 23:44:59.273 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-07 23:44:59.273 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 0.666667 2023-10-07 23:45:20.119 ERROR_ONCE DX11BACKEND (22420): texture 'kabinaNight' not found. Asked from '' 2023-10-07 23:46:47.063 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-07 23:46:47.063 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.000000 2023-10-07 23:46:47.063 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 1.000000 2023-10-07 23:46:47.063 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-07 23:46:47.063 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 1.000000 2023-10-07 23:46:50.367 INFO EDTERRAINGRAPHICS41 (Main): instancer factors has been changed. Update lod buffers. 2023-10-07 23:46:50.367 INFO EDTERRAINGRAPHICS41 (Main): distanceFactor = 1.500000 2023-10-07 23:46:50.367 INFO EDTERRAINGRAPHICS41 (Main): instancerDetailsFactor = 0.666667 2023-10-07 23:46:50.367 INFO EDTERRAINGRAPHICS41 (Main): forestDistanceFactor = 1.000000 2023-10-07 23:46:50.367 INFO EDTERRAINGRAPHICS41 (Main): forestDetailsFactor = 0.666667

I'm hopeful that the issue I'm experiencing is a result of something I might be doing incorrectly rather than a problem with DCS itself. However, in case it's related to the software, I've included the crash report below for your reference. Here's a breakdown of the steps leading to the crash: 1. I launch DCS and proceed to the mission editor. 2. Within the mission editor, I load the mission I've been actively working on. 3. To verify the proper functioning of the triggers I've set up, I start the mission. 4. After initiating the trigger to begin the mission (currently, there's only one mission in progress), my game crashes a few minutes later. If anyone else has encountered a similar issue and has insights on how to resolve it, I would greatly appreciate any guidance or solutions offered. ------------------------------------------------------------------------------------------------------------------------------------------------------------ Log Name: Application Source: Application Error Date: 10/6/2023 8:45:12 PM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: DESKTOP-QLMRPE8\Christian Computer: DESKTOP-QLMRPE8 Description: Faulting application name: DCS.exe, version: 2.8.8.43704, time stamp: 0x64e3b65b Faulting module name: edCore.dll, version: 2.8.8.43704, time stamp: 0x64cd6d2c Exception code: 0xc00000fd Fault offset: 0x0000000000179447 Faulting process id: 0x0x838 Faulting application start time: 0x0x1D9F8CEC9281F00 Faulting application path: D:\DCS World OpenBeta\bin\DCS.exe Faulting module path: D:\DCS World OpenBeta\bin\edCore.dll Report Id: 8fc4beb2-511f-4af3-86c4-ada3cb559bbf Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2023-10-07T03:45:12.9252448Z" /> <EventRecordID>44887</EventRecordID> <Correlation /> <Execution ProcessID="11056" ThreadID="11628" /> <Channel>Application</Channel> <Computer>DESKTOP-QLMRPE8</Computer> <Security UserID="S-1-5-21-696764075-3389263234-3526540566-1001" /> </System> <EventData> <Data Name="AppName">DCS.exe</Data> <Data Name="AppVersion">2.8.8.43704</Data> <Data Name="AppTimeStamp">64e3b65b</Data> <Data Name="ModuleName">edCore.dll</Data> <Data Name="ModuleVersion">2.8.8.43704</Data> <Data Name="ModuleTimeStamp">64cd6d2c</Data> <Data Name="ExceptionCode">c00000fd</Data> <Data Name="FaultingOffset">0000000000179447</Data> <Data Name="ProcessId">0x838</Data> <Data Name="ProcessCreationTime">0x1d9f8cec9281f00</Data> <Data Name="AppPath">D:\DCS World OpenBeta\bin\DCS.exe</Data> <Data Name="ModulePath">D:\DCS World OpenBeta\bin\edCore.dll</Data> <Data Name="IntegratorReportId">8fc4beb2-511f-4af3-86c4-ada3cb559bbf</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event>

The guy that directs your aircraft only seems to give directions with his left arm to the left side. Is there a way for him to use his right arm to give you directions to the right side of him?

I have been working on this mission for a week now and I am almost done with it. Everything worked perfect when I ran the mission on my own. After I did a test on it with another player I asked him to let me know if he saw the whole Briefing on the side of the screen and also the photo that I put on there while the message was being shown on the screen. I also asked him if he could hear the audio message which was an audio .wav file that said exactly what it said on the messages that were on his screen. I also tried He told me he could see the messages and also the picture, but not the audio. I also used an .ogg file and I got the same result. I played around with the trigger a bit but I still can't seem to get it playing when I make the mission into a multiplayer game. If someone knows what I did wrong and could help me get this mission going with my audio that would be great. Thanks again.

Wow, no one has yet replied to your post since March. I googled the same problem that you are having and found this post from google.

I started playing today after a few days from not playing DCS. First I started playing in a 4YA server. As I started the game I then realized that my left DDI was not turning on. I thought I did something wrong but in that server the planes start hot. So I knew that I didn't do anything. I of course double checked it was not the server and I went to another sever and this one was one that starts all aircraft cold. I started my f/a-18 and the same thing happened. My right DDI turned on but my left DDI never turned on.

So

I knew someone would say something like that. I guess that is why the US only uses the Air force and Navy to win Wars. Come on man, think a little, use your brain. The units on the ground will never be visible to air units at all. All ground battles would never be shown on the f-10 map. The only way a pilot would know where ground players units are is if they request assistance from air units, that's the only way anyone would find out or if you accidentally find a unit while using your litening or atflir. That way they should almost never be bothered unless they need help from us above.

I just wanted to say one thing that is really missing in this game. That is communication with ground units. I usually feel a "disconnect" to why am I going to go bomb this airbase? There is no real aspect to the reason why I am going to go bomb this airbase or units on the ground. I know the game is telling me to go bomb this place, but there are no men on the ground needing my assistance. There is no feedback from ground units what so ever. I feel that that is what pilots in this game need. Some feedback of what they did for units on the ground. That would bring a whole different level of immersion to the player. There are people who enjoy and would rather go FPS in a world like this. I mean just imagine... There is a team of players wanting to take a base or a city. They are pinned down and need some CAS. They call for Air support and you are the nearest plane around their AO. You take the call and head to their location. Of course the men on the ground know how to tell you the exact instructions on where they need the hit and what weapon to use. You say RGR and head there and unleash hell. After you did you job you get praised by the players for helping them on their mission. Now you, as pilot, you feel more accomplished and satisfied as a pilot. Not only will the player feel more satisfied with what he did on his mission but he will want to play the game more often. My suggestion is to include a FPS aspect to the game. Not only playable men on the ground but also to improve the play-ability of the current ground vehicles that are available.

Another thing on air refueling that I have noticed is missing is the white stripes on the hose. Its just a black hose in DCS.

I have 504 not 500

Each time that I use harms on my F/A-18c it will not pick up most radars from enemy radars when I go TOO mode and select Hostile only. I did notice that when I change the TOO mode to All rather than Hostile only it will pick up the enemy radars better, but not always.

I do change PRF setting on the F/A 18. I changed everything you can in order to really see the problem with it. I would understand if the F/A-18 only used AN/APG-65 (range 72km = 44.7) miles, but the F/A-18c also used AN/APG-73 which has a range of 60nm which would be 69 miles. @dorianR666I see what you are saying, but this happens to all planes on the f/a-18s radar. Its not just small planes. I think the developers should look into this more carefully and get the actual facts about the radar that was used in the f/a18c.

I noticed after the 2.7 update that when I fly the F/A-18 Hornet that I am no longer able to lock any targets no father than 30 miles away. I can see them on my D/L, but I cannot seem to get them to show up as a target that I can lock onto. I have been testing the f/a-18's radar in a server where you can see enemy planes on the F-10 map and you can see the altitude of the enemy. I zone my radar to their altitude and nothing. So basically I cannot lock onto a target until they are under 30 mils away from my F/A-18 which makes the F/A-18 a good target to go after since it can't lock onto its target until its too late.

Let me try other games and see if I experience the same thing. I have a GTX770 with a SSD drive and my multiplayer settings are LAN. Hmmm I have no idea of what could be going on.

Well looked at my ping like I always do and it was under 50 ping like it usually is. Is there an option to update the game or does it update automatically when I start the game? I just want to make sure that my game is up to date with the recent update.

I did all that you just said, deleted my user saved game file for DCS and then I uninstalled the game and then I played the game on one player mode and the slow motion of the plane and everything else was there while I had my FPS showing. It showed 145 FPS in one player mode. I then played the game in multiplayer mode and I also turned on the FPS just to keep track of it. My game still skipped in location, or would do things a second or more after I did it. I then started looking at the FPS of the game while I was in multiplayer mode and the framerate stayed constant at 90 fps. And all this was done with default settings that the game starts with right after you install the game. So it is definitely the recent patch they put on.

I have also been experiencing the same thing recently. Here is a link to my post that I just made today. http://forums.eagle.ru/showthread.php?t=115778

Well since 2 days ago I have been trying to figure out what has been going on with my DCS. I only have the A-10C aircraft and I always fly it every day. I would always only join servers that had a good ping for me. 2 days ago I went on and I noticed, after my plane was ready to taxi to the runway, that I would increase the throttle and I would hear the engines increasing in throttle but my plane would be traveling slow or not at all and then a few seconds later the plane would be somewhere else in the game at full throttle. Not sure if anyone had been going through the same thing recently but it is really annoying. Another thing that I have noticed too is that when I play single player mode it seems like I am flying in slow motion a bit. The motion of the plane seems slower as if an old man was flying the plane. I don't know if some recent patch caused my game to act this way or not. If any of you have been experiencing the same thing that I am going through and found out what was going on, please let me know so that I can fix this problem as well. Oh and I have also re-installed the game twice now and the same thing keeps happening over and over again. Thank you for your time,

Hello guys, I wanted to find out how to acquire the freqs for JTAC. I sometimes see JTAC listed on the multiplayer briefing, but I almost never see what freq it is on. Is there a default freq that it is always on and is that the reason why some multiplayer servers don't list what freq it is on on the briefing? My other question is when I have the freq for JTAC and use it, I almost never get a response. I have it on FM and have the right FM freq on the radio. Do I have to be close to a certain location in order to get a response from JTAC, or is that just a bug in multiplayer server?