limbo696

I can't believe that some of the basic functions of the aircraft do not have a keybind (e.g., course selector knob)....very annoying.

I appreciate the list was hoping for something like this....it's superior to the left-hand placard in the MIg-12,..similar to the RSBN list. I suggest adding the DCS map grid location Edit: Okay, the "code" is the map grid for some of the stations but some do not correspond to the in-game map. For example, channel 1 Kislovodsk Arc station in sector 2/II is listed at GJ96 (NW of Nalchik). However, the in-game map shows a grid coordinate of LP16. Channel 2 (1182 freq) in 2/II has the right grid but I cannot find the town "Teplorechenskiy" near the tower in the in-game map. Instead, the tower is located in the city of Shaumyanskiy.

Chuck's guide is incorrect. The 3 NDB buttons act as the range selectors (low, mid, high) when the Far/Near switch is in the near position. The official Mig-15 manual has not been updated to reflect this.

How is spotting in DCS "more or less broken?" I've found spotting to be much easier in DCS than it is in real life. Spotting is a skill too....I've been flying WWII sims (i.e., IL-2) seriously for a year now and my spotting skill is WAY WAY better than it was when I first started. Spotting, hunting, and navigating is half of the fun if you are serious into WWII sims and I definitely prefer full realism servers with no icons. I even think that being able to have the computer mark your position on kneeboard map is a form of cheating. Is there a Teamspeak for the Dogs of War servers?

I was unaware of this thread despite trying a search before I posted and it is here: http://forums.eagle.ru/showthread.php?p=2276058#post2276058 I kept failing the mission myself and I found issues with both the speed and the headings. As far as headings, I went into the mission editor and used the ruler tool to get the true heading. I then subtracted a magnetic variation of 6 degrees. This yielded headings of 121 and 37. I never had much issues with making the first waypoint but was coming in to the right of the airfield on the second waypoint and significantly short in distance, so I had to fly over 500 KPH IAS to get there on time. This was with the mission that was in my folder; I did not try the updated missions I just found here. However, I very rarely did not make the first waypoint so I'm not sure what the issue is here....look into the mission editor and see where the target point is exactly and use dead reckoning if needed. You are aiming just to the left of that hill near the coastline on the first waypoint and the airfield on the second. I frequently had to ignore warnings about heading and speed.

For kicks, I am doing the official campaign that comes with the Dora module. I was on mission #4 where you have to navigate at a certain heading and speed for a certain number of minutes and I failed the mission 4 times in a row. This frustrated me because I know how to fly a specific heading and speed, so I checked the editor. To win this mission, you need to be within two different navigation zones at an appointed check time. The problem is that both the dictated headings (125 and 40) and speed (450 KPH) are not necessarily accurate enough to put you within the navigation zones at the check times (5 and 9 minutes after mission start). I think the mission does not take into account both (1) magnetic variation and (2) the scenario wind speed. For example, I had to fly a heading of 30 degrees at 500+ kph to get inside the second check zone instead of the dictated heading of 40 and speed of 450, and there is a head wind in this case. I think this needs to be fixed so that you are provided with more accurate headings and speeds and/or make the navigation point zones larger to be more generous.

I played the training mission last night and heavily damaged one of the AI planes engines and it was terribly smoking. When the AI slowly pulled away with me and his damaged engine even though I was at full WEP and trying to fly efficiently as possible, I was like WTF? This happened to me on like 3 or 4 occasions.

This is still not fixed in the scenario--very confusing to someone that is new the heli.

I have a quick question concerning the victory conditions of AAT10, Missile Employment. According the the verbal instruction, only the tanks should be targeted (i.e., T-72s) for the moving convoy which is the last target. I killed the three tanks in the convoy but I was told by the instructor to "reengage." I then killed some of the armored personal carriers before deciding to return to base. When I parked, I failed the mission because I did not kill all of the targets. So what exactly is the victory condition here? Do I need to kill the entire convoy (which is only doable with many gun passes since the missiles are limited) or just the three tanks? If just the three tanks are suppose to be killed, is it an error to tell the student pilot to "reengage" and that not all the targets were killed? The stand-alone practice mission of this campaign mission instructs to kill the entire convoy which is different unless my memory is completely failing me.

Okay, I was able to fix following the instructions on this page: http://forums.eagle.ru/showthread.php?t=114030

Okay, my system was updating to 1.2.9 when it stopped because I had the A-10c PDF manual open with a reader software and the install program was not able to overwrite the file. The updater then quit working and now when I try to run DCS World (either through DCSupdater.exe or dcs.exe) the game will not load and nothing happens at all. How to fix? I'm not running any mods.

Anybody!?! I'd like to go NVIDIA given that most of the flight sim community say that NVIDIA cards run the sims better but it's a bad time to buy NVIDIA right now with their cards approaching 50% more in price for comparable performance to AMD. This is making for a difficult decision for me.

Yep, solved my problem here when trying to set some snap views...had a joystick axis set to zoom which was automatically resetting the zoom keys function. Thanks.

For most people, you have to hit the engine start up keys (left-alt Home and left-ctrl Home) first for the left and right throttles to become responsive. Otherwise, they register no movement when you move your physical throttle/slider.

Sort of frustrating to see that for one of my first missions I try to to get a parked aircraft to start up and taxi away from the player plane and see that I cannot accomplish this due to a bug. This is a deal breaker for so many missions it seems.