jjohnson241

Looked in Mods\Aircraft\C-101\Missions\EN\Single and found two missions for Nevada; Cold Start and Takeoff. I don't have any Nevada missions in the Quick Start folder. There are non-Nevada missions in both Single and Quick Start folders. Edit: The changelog for 1.5.2 includes Instant Action (Quick Start) and Single missions for Nevada: http://forums.eagle.ru/showthread.php?t=159201 As I said above, I've got nothing in the Quick Start folder in 2.0 and no Nevada missions in the 1.5BETA or 1.5 Public.

If they have created Nevada missions I have not seen them here. The instant action mission folder can have non-Nevada missions in the folder but they won't show when Instant Action is selected in 2.0. If you have A-10 missions in the folder, I'd delete them as they should not be there and I would not hazard a guess as to how they got there. My 2.0 update did nothing to the content of that folder.

The C-101 "Quickstart" missions in my installation are all non-Nevada map missions and don't appear in the DCS 2.0 Instant Action menu when C-101 is selected. I don't think Quickstart missions have been released yet by the developer.

Missed that. Thanks.

I'm not getting the instructors voice in any of the training missions, just a "chirp" at the beginning and then only aircraft and exterior noise. No problem in other aircraft training missions. Anyone else have this problem? Thanks

Thanks, I'll be happy now.

I'm using V1.8a from the user files here. I get a Warning from JSGME but it does not show a file conflict with any other MOD. Strange. Is V1.8a the latest version of English cockpit for the MI-8? Thanks.

Devrim, I tried this mod using JSGME and got a conflict with your English cockpit mod for the MI-8. Will they live together without conflict? Thanks.

Will give that a try. Thanks

8 Knots is nothing, certainly not strong enough to require the degree of rudder correction during take-off roll. I've submitted a Trouble Ticket (http://forums.eagle.ru/showthread.php?t=158997). I think the affect of such a low cross wind is over modeled and the sensitivity of the rudder response needs attention. As this is a Beta, hopefully they'll get it straightened out. Edit: Per the Manual, Nosewheel Steering should be disengaged after lining up for take-off. I tried without NWS and could control the plane better but still suffered drift to the left (affect of cross wind). Trying to correct that drift using right rudder input is an adventure to say the least. I believe that plane is far too sensitive to low cross winds and the reaction to rudder inputs is far too severe.

Ditto this post. I have no problem with control on take off in 1.5. Plane tracks in middle of runway throughout take-off roll. I'm not an ME guy but has anyone verified that the problem with the Nevada take off is in fact a cross wind? Looks to me that the wind in Nevada is only 4 knots. ???

"Fool me once, shame on you. Fool me twice..." Gents, I vote (and complain) with my wallet. Suffice it to say that my wallet won't open for this vendor again, regardless of the poignant admissions past and future. Very simple, pay for performance. I frankly don't care if they deliver the CC, complete the EB and/or finish the AFM work. If "they're doing their best", it's not good enough to stay in this league, IMHO of course.

If you're asking me that question, I have no idea. I was merely reinforcing your post re: the Russian Flight manual. This vendor has a history of moving very slowly on documentation and for that matter bringing their products out of the Beta stage. I wouldn't look for an English Flight Manual in the near future.

+1. The Flight Manual remains almost entirely in Russian. The Quick Start manual is in English.

Zeus, I'm going to climb on my old saw horse once again and plead that all clickable cockpit controls should have a corresponding key mapping. This simply allows for the manipulation of all controls from the keyboard or mapped to a joystick (throttle, etc.) device. Please, Please , Please. Thanks.

I pre-purchased the first day offered but I failed to post here. Anyway, I'll join the party. As a proud owner of everything DCS offers, save Combined Arms, I'm anxious to get to know this bird :joystick:

Thanks Grunf, I'll get my feet wet. Tried mission from Nellis, cold-dark, start up and slide show during taxi. Same as described above. I see that I'm not alone with the symptom at Nellis at least. LNS please take a look at this.

I'm not a Mission Editor guy. Is there a quick 1,2,3 guide as to how to do that? Thanks.

I don't know who you were addressing but I didn't have to activate when trying the Mig in 2.0. The only problem I have was the slide show I described in my post.

Updated to DCS Alpha 2.2 and tried Mig21. After mission loads with engines running, I get a slideshow trying to taxi to runway. It smooths out a bit after take-off as though whatever is trying to initialize completes (pure guess on my part). The mission I flew is a modified Hawk Free Flight mission, modified to use the Mig21 instead of the Hawk. Mission starts engines running on ramp. Radar appeared to be off or in standby. There were other aircraft operating in area. This is the first problem I've had with 2.0. I've been flying all aircraft at max graphic settings since I installed the 2.0 with no FPS problems. Something is buggy with the Mig.

Same story here. Slideshow trying to taxi to runway. Took off and it smoothed out a bit as though systems in aircraft had finally initialized (pure guess on my part). Mission I flew was a modified Hawk "free flight" mission modified to use Mig21 and no other mods. Mig 21 is the only aircraft I have FPS problems with. All settings maxed since 2.0 installed.

Hi, In this thread posted in March of this year: http://forums.eagle.ru/showthread.php?t=139903 I asked if all clickable cockpit controls would also have a key mapping so to be available to map to a joystick (HOTAS) key. The answer was Yes, all clickable cockpit keys would be mapped. Now that the C-101EB is flyable in the DCS Nevada alpha, I checked again for the appropriate key mappings and found nothing had been added for engine, electrical, communications, etc. So, I'll repeat my question and request; will all clickable cockpit controls be mapped to a key command, and if so, when?

To each their own I guess. The search for the Nevada fix has taken some time now. There are a raft of aircraft that are flyable now over Nevada. I can wait for the Mig21 fix. To assume the fix can be found and implemented by the time the Nevada map is integrated runs contrary to the evidence to date. If giving up on the working radar without any estimate for repair is the consensus, so be it.

Disagree. Nevada is destined to integrate with the "public" version of DCS. I'd rather have the problem identified and corrected now before the unification of Nevada.

Thanks, for the opinion at least. I hope ED provides a direction in the near future.