D-Day

Secondary airfields have to have a nine in the second digit slot to identify it as the second. Batumi is 01, so the primary code would be 9001 and secondary would be 9901. See p.178 in manual. Long and Lat can be entered too.

Hi, I have noticed another NAV related issue. I am having mixed results with creating a BX-1 markpoint over land based on a radar contact (field of tanks). I was able to create the markpoint over a target area then flew over the target area about 10-15 km and turned around to find the markpoint had moved quite a distance to the side which was way off from the original BX-1 markpoint. I repeated this several times with the same result. Another time, I could not create a BX-1 markpoint at all. After creating the initial markpoint and it displaying on the radar screen I slewed the cursor which moved the cross to where I wanted the markpoint then hit TV to move the circle over the cross to the new position but the circle would not move and lock over the cross. One more time trying to create a BX-1 markpoint and it worked fine and maintained it's position. I'm not sure if I am doing something wrong since I just started using markpoints in this manner or if this could be another NAV issue related to the HUD and course ring problem.

I'm having the same problem but only noticed it in multiplayer so far. I tried one of the single player instant action missions and it worked fine. The HUD just shows numbers on the left and right and the course ring around the radar is locked in the 0/360 degree position at the top.

Congratulations PilotRyan! I just got a new computer and really need controllers now! Thanks for the opportunity!

I totally deserve this because I'm still flying with a MS Sidewinder Joystick that's so old (like 1998) it's not even made in China but Malaysia instead! At least it has the twisty rudder thingy! :joystick:

I'm having the same problem. Since updating to the newest version of 1.5, half of my modules are asking for keys: F-5E, L-39 and Mi-8. No hardware changes.

Nevada will be an Easterly declination so it will be the opposite from above. Easterly Declination: Mag to Grid - ADD. Grid to Mag - SUBTRACT. Westerly Declination: Mag to Grid - SUBTRACT. Grid to Mag - ADD. I'm relatively new to DCS and have mainly flown in the Caucus map so far, anyone please correct me if I'm wrong. So far my understanding is that the map in the mission editor and the runways are True North but the aircraft report magnetic headings in their instruments like HSI, etc. I'm not sure if DCS World is modeled after real world declination or not but Nellis AFB is currently 11.8 degrees Easterly declination, so 281 (Grid) from the map in the mission editor minus 11.8 is 269.2 (Mag). Close but not exact to 267 still unless the ruler lines in the mission editor were roughly drawn to get 281 degrees causing the difference. One last thought, magnetic declination is constantly changing, so does the declination in DCS stand still in the time when the map (Caucus or NTTR) was created or is it being updated to match the real world declination every year?

Zilch, I had the same problem after updating and after a little bit of trial and error figured out that another script in export.lua apparently was interfering with Tacview's export (CDU App). I went back to a clean version of the export.lua and it works fine now. Not sure if that was really the cause but got it to work for me.