Cavemanhead

Thanks so much for your response/enthusiasm and the depth of your answer. As far a FM goes, I'm not really asking how the plane performs relative to other planes, but rather how close is it to the actual flight characteristics of the real Mirage. When I fly DCS, that's the most important thing to me: ground handling and flight characteristics that rival the real bird... I currently fly the 109, 190, F-5E, Mig21, Mig15, SabreJet because all of these have PFMs (or EFMs which I understand are 3rd party equivalents to DCS PFM)... I have been unable to definitively determine what kind of FM is included with the Mirage (AFM?)... Thanks again for your help.

Sorry if these are old questions but I'm a little late to the game but I'm thinking of getting this plane... 1) In general, how complete is the overall functionality of the plane? What percent of the functions that the plane is supposed to have are currently working? 2) How good would you say the FM is? Is it the highest fidelity offered - PFM? If so, are there any major issues that still need resolved? Thanks.

The "bounciness" of the wheels on the 109 feels attenuated a bit (which is much better)... like it has more weight/intertia and that if it's near the stall speed and a few inches off the runway, it's not going to magically bounce 2 feet in the air, when it "drops" to the runway... The left wing snap stall when the critical AoA was exceeded has been toned down... As of now, it appears to be a step in the right direction... If you stay within the flight envelope, the plane "behaves"... I haven't done enough flying to know whether the way it now feels is simply due to adjusting the amount of output relative to the amount of input to the stick... It used to feel that very small changes in stick deflection lead to disproportionally large changes in the aircrafts attitude in some flight regimes... Anyone else that's flying Nevada only have any comments on the flight model and other tweaks in 2.03?

2.03 changes seem to be: 1) FM tweaks... Seems much more believable now as far as the how the ground behavior is... Not too simple but not ridiculously sensitive... Its like all the rough edges have been polished off leaving the 109 characteristics intact but fixing the transition to/from flight with the smoothness of the flight model... 2) Track playback seems to work. Yay! 3) Cold and dark is functional. Yay! 4) Track IR views during flyby, etc... Will take some getting used to but I think it's ok... Track IR can always be paused... 5) WWII AI more accurate... I'm not sure what has changed here... Wondering what is more accurate.

Yup same issue here... Almost makes me want to install 1.5 just to have it but don't want the additional clap trap on my machine right now... All folks who bought 2.0 have access to 1.5, yes? Sent from my SM-G900V using Tapatalk

I only fly the NTTR map. The assumption is the changes people are reporting here with the 109 are NOT applicable for those with NTTR, yet? I think the FM feels great right now in NTTR though I can see that the reported changes from 1.5 would bring 2.X it that much more in line with reality. What about cold and dark not working when starting a mission and the inability for tracks to play back properly? Are these 2 issues fixed now in 1.5?

Gavigai, does your mission work in NTTR? That's the map I'm using. QuiGon, When I join multiplayer in DCS, I don't see the servers you refer to. Is there another way to get to them other than from inside DCS?

I get a very limited time to fly so when I do, I like it to be very "meaningful"... I love the FM, etc... but I'd love to be able to dogfight online, or do some missions, etc... to force me to learn the airplane better... Right now, I do endless touch and goes (which are very satisfying), but I'd like to branch out and do more than the Take off and single dogfight missions... Are there any good mission makers out there that have made some good missions, etc...? And... What am I missing as far as multiplayer? It seems hard to catch anyone online that wants to fly WWII airplanes...

I've purchased the DCS maps and many modules... I've got $36 bonus bucks hanging out to get something before they "expire" in September. 1) What planes will be released between now and September that my bonus bucks can be used on? 2) What makes the bonus bucks "expire"? Is there any way to extend their life? What are their exclusions? Can any module be purchased with them as long as it's at full price?

Does the sale last until it releases?

What is the challenge campaign and where can I get it???

Hmmm.... Been on several times and finding anyone in any WWII planes at all (let a lone a dedicated WWII server) has been difficult... Am I supposed to do something other than use the multiplayer menu choice to get to a server?

Can I just open the mission editor and "save as" to make it more challenging AI... I think I've mastered it at the default level... I'd like to take on some human opponents but hard to find folks in the servers flying any WWII planes...

A campaign? Sounds interesting... Looking for something simple on the NTTR map that teaches me the nuances of this plane... Will the campaign do that?

It appears to me that I cannot directly post a picture and that I need to do it through a website. Do you guys have any recommendations for external websites?

My flight sim PC has dual boot Win 7 and Win 10. I currently have DCS 2.0 and a bunch of modules installed on Win 7. Can I install my DCS stuff onto the other Win 10 Boot disk?

Just a curiosity thing, but I'm assuming the developers put a low priority of making the AI of mismatches scenarios (such as a 109 vs and F16)... I say this because I built a mission with me flying a 109 and fully expected to lose when fighting an F86, A10, or F16, but I was able to bring them all down with the 109... I'll recheck their intelligence, but I believe they were all "excellent"... Comments/Thoughts?

After flying the P51, 190, and 109 and lurking... These are my assumptions of where things are relative to final release; please advise if incorrect: P-51: Final Release has already been done... Expect some minor tweaks here and there with new versions of 2.0, but basically the plane is officially released. 190: Beta stage plane has completed elements but still tweaking with final release in the future... when? 109: Alpha/Beta stage elements with final release in the future... when?

Hmmm... I read the forums here and there and just picked up this alt + enter tip... I assume it's a toggle? I have noticed some jerkiness but assumed that was normal since it only occurs in detailed scenery areas. Will have to see if vsync matters as well... Assumption is performance will suffer when on. Sent from my SM-G900V using Tapatalk

Thanks, I'll do some reading...

Thanks so much. I'll give it a whirl.

Where can I read a manual on how to use the mission editor... All I want to do is put myself in an ME 109 with a few planes doing touch and goes ad naseum as I'm practicing TOs and landings...

Thanks for the link. Yes, making movement of the flap switch to the center can become "routine" but is pretty clumsy... And you lose the visual reference of where the flaps are positioned based on the switch position (arguably a "nice to have", but not necessary)... The biggest issue is the command being sent repeatedly to the WH long after the flaps are full up/down IF you forget to "terminate" the automatic flap movement. Target works fine for me and I like the GUI so I will intend to keep it... Yeah repeating from above... making movement of the flap switch to the center can become "routine" but is pretty clumsy... To each his own I guess... But... Then you only have limited flap positions instead of the infinite amount the 109 allows by design! Thanks... I'll need to study a bit to fully grasp the script. Thanks for posting... Appreciated.

Hmmm... I think we're nearly on the same page. When I say eyepoint, I do mean the head position - or more specifically, my eyeball position as a part of my virtual head in the sim... I've been assuming that when the view recedes back from the instrument panel after the "fly" button is pressed that the view is settling to the correct head position for that particular plane such that if I could transport myself to the real cockpit seat, I'd be seeing the same thing... So, is the default position considered the "correct eyepoint" for a given plane? I started suspecting it was not when I saw a small fishbowl effect but it sounds like that is another set of values in the .lua file... I have a 1920 x 1080 monitor... Looks like some hunting is in order to get things "right"...

Thanks for info... I've been operating under a few assumptions: 1) FOV was intimately tied to the eye point... The further back one sits relative to reality, the more fishbowl things would be... What you describe makes it sound like FOV and eye point are segregated things... 2) DCS would have made the nominal default eye point "perfect" for each plane by default... In other words, when I'm in the cockpit of a 109 and my eyeball is exactly 24" from the instrument panel, then in the sim it would be close to that (set via some "average pilot model", etc...)