nitrodust

Datalink seems to sometimes work sometimes not. e.g. M10, no datalink with friendlies. M09 seems to have a more completish working datalink but has no target indications. ? Maybe that doesn't work. Targets come and go, maybe awacs doesn't work well? M04, datalink seems to only work after dying and loading the checkpoint mission after shooting at the tornados. Edit: Could it be that Link16 is off sometimes? Maybe only Link 4 in enabled?

fly M10, Com2 is just static , maybe a hint of music? Also I think that Com1 is missing some static when people talk? I could be wrong though. Edit M11 has both static and music on Com2

In M5, laser mav the targets, get shot down by the igla trying to ccip . Mission restarts get shot down another time by the igla trying to ccip mission exits to result screen.

Fly to wp 7, pop up, shoot left sub, Get a notification that there is an ammo depot to destroy, (destroy 2nd sub or not?) suddenly you get the message to go to wp9 and establish datalink with your slam(er) and destroy the sub even though it's already dead . i got the destruction notification and I looked at the F7 view and they are both on fire. The mission seems to be stuck at this point. Also what is the ammo depot? I guess it's not the big tent like structure, hit that with 2 missiles and seems nothing happens.

In the mission editor. open up mission, click on waypoint from springfield 1, add 300 ft , click on the next waypoint button. Repeat about 60 times. You might have to unhide some things, not sure.

Well I never noticed this bug.

So far there have been two missions with other helicopters to follow. The one with the Hinds and the Patrols missions with the Hueys. In both missions the AI flys too low which results in: Death of the AI Pilot (Springfield 1 crashed into a tree or something) The AI flys through Trees (Guess sometimes they don't die by tree?) The AI brakes and accelerates wildly to go up. Usually there is some obstacle like a house or hill and the AI comes from like 100 kts to like 20 trying to clear it and then accelerates really hard again. The AI brakes and accelerates wildly to go down. Sometimes, especially over forests, the AI tries to fly lower only to break like crazy and then flys through trees. So I think the AI helicopters need to fly up higher so they can actually clear buildings and trees. Edit: Every WP in (at least mission 6) has their height set to the ground level, so the AI always tries to fly as low as possible, which kills it etc. The place where Springfield 1 dies is between wp 5 and 6. There is a hillside with many trees the way passes through and he tries to fly NOE according to his waypoints and always dies . To fix this I went and added 300 ft of height to every waypoint, that way the AI doesn't do crazy breaking or accelerating trying to clear building or go back to NOE, manages to clear the hill between wp 5 and 6. So far I have only watched the AI go to about wp 10 , and they fly a lot smoother this way. Using above ground height in waypoints instead of above sea level however isn't great as the AI goes into a crazy acceleration and breaking cycle trying to adapt to the tiniest bumps in the ground or houses that it overflies.

In the weapons training mission the text says there there are enemies 2 km directly in front. The helicopter is oriented North but the Enemies (on that airfield) are straight south. So really the enemies are directly behind . Can you please turn the helicopter around for future players?

Hi , I am trying to do the "Patrols" missions in the UN campaign. After delivering my soldiers, Springfield 3 and 4 are supposed to land near Lentehi. However it seems that one of them gets stuck trying to land. It is very close to the power cables and constantly tries to fly down just to quickly jump up again. It never lands and I can't continue in the mission. Is there a way to skip missions maybe?

Sending a wingman on reconnaissance can sometimes crash the game to desktop. There is a freeze first and then crash to desktop. This seems to be an issue ever since 1.5 was released. I have this in the logs: # -------------- 20151109-203803 -------------- # C0000005 ACCESS_VIOLATION at A3BE4167 00:00000000 00000000 00000000 0000:00000000 A3BE4167 009CF0F0 0000:00000000 A3BC522D 009CF380 0000:00000000 A3BEABA3 009CF3C0 0000:00000000 4D3472DF 009CF440 0000:00000000 4D347825 009CF490 0000:00000000 A3E7DAA8 009CF500 0000:00000000 A3E81592 009CF530 0000:00000000 A3E97904 009CF560 0000:00000000 A3E97854 009CF590 0000:00000000 A3F41E2C 009CFC40 0000:00000000 A3F43CB5 009CFC80 0000:00000000 57B713D2 009CFCB0 0000:00000000 BaseThreadInitThunk()+22 59795454 009CFD00 0000:00000000 RtlUserThreadStart()+34 I have 3 crash logs so far with this RtlUserThreadStart()+34 related to this crash. I also have a .dmp file, but I don't know where to send it This one is a bit strange and I sadly have not found a reliable way to reproduce it. It has happened several times now, it only seems to happen when I have played for a while. It has happened in the campaign, the insurgent instant action. As I said I have nod been able to reproduce it reliably. It does not seem to be related to the distance the wingman needs to travel. So far I have : play for a while send wingman to reconnaissance crash to desktop. Edit : I managed to reproduce the issue: In the Deployment Campaign: Narzan Valley mission fly to the ingress point shoot a few trucks and AAA command wingman to scout 2 km ahead player pilot speaks the commands the AI does not respond crash to desktop This issue is not tied to this mission. however I have only been able to reliably reproduce this in this mission, mostly due to the easier timing.

Hi, I am not sure if it's meant to be this way, but the Default cockpit has english text on the Abris and the ekran. The hud seems to be in russian . at least there is a "p" when it uses radar . to test: go to options, special, ka-50 , select the default cockpit. start any mission. turn on battery 1 and 2 start abris. start ekran. hit the mwl twice the language of both is english. Edit: it also seems that betty is in english

Hi. In the KA-50 the Abris map is blank for scales below 1:0.5 km. Other scales seem to work normally. This does not seem to be related to the instrument resolution. (256 and 512 behave the same) To test it, load any mission with the KA-50 turn on battery 1 and 2 turn on abris wait for abris to load click Nav click map then click scale + at scale 1:0.6km and above the mapworks at scale 1:0.5km and below the map is blank I recorded the issue: http://gfycat.com/TangibleRemorsefulDrafthorse

I seem to have been able to get modules running with the updater, I only tested the ka-50. I could turn on the batteries and then forgot how to look around without trackIR like described here: http://forums.eagle.ru/showthread.php?t=114030 e.g .\DCS_updater.exe install A-10C KA-50

Okay. the issue is even funnier. Having special characters AND selecting "save password" makes you fail the login. Either using no special characters or disabling "save password" lets you log in. Edit: This only fixed the issue once for me (while using a password with special characters), after restarting the game it fails again. how strange. Tabbing in and out of the game suddenly let me log in again, even with "save password" Edit2: Okay seems this is happening right now: Use a password with special characters Turn on the game, go to the password prompt, disable save password and auto login. Enter login data. The login wil fail with "Incorrect login or password" push the login button repeatedly, "Incorrect login or password" until login succeeds. Edit 3: it seems it works correctly now... no more mashing buttons Edit 4: it's not letting me log in again ^^. I guess the servers are a bit flaky at the moment.

Hi, It would seem that when logging into DCS 1.5 with the openbeta client, you can no longer use special characters in your password like {}[].+\- etc . The game complains about "Incorrect login or password". Changing the password to only use [a-zA-Z0-9] allows me to log in again. Logging into the website works fine and it used to work with DCS 1.2.