HotTom

The bindings are a mess since the last (2.77) update. I don't know what ED genius decided to rename everything but there are many crontrols I simply can't find anymore. RPM? Thrust/Throttle? Could we PLEASE revert to the old names? What were you thinking???

None of grafspee's videos looks even a little bit like those lazy, ugly exhaust flames we have on the Mosquito. They should be very short, rapid explosions.

Ditto. The history is plenty interesting and exciting. Let's stick to it.

ED still doesn't like it.

Why in the world would you want to remove something that is historically accurate??? Learn to deal with it.

HT

I had the same problem. Linked the cockpit camera settings to my numpad (2,4,6,8) and it is simple to adjust with a couple of taps. As Aussie Pilot stated, it doesn't save the settings but a couple taps puts it right. Aussie Pilot, glad you got it sorted!

Allowing the "trainer wheels" as an option is still a good idea.

Go to settings on your main screen (the one with all the module avatars along the bottom). Settings/Controls/View Cockpit. There should be a dropdown menu with, move up, move down, move left, move right. What that really moves is your seat position. You can link the commands to switches or the keyboard. Hope that helps. HT

Thank you, Holbeach!

I came to a very similar conclusion yesterday (10/22) by a day of trial and error. Mainly, I wasn't accelerating quickly enough. Certainly glad that's sorted! Tip: If you are using the Normandy map for Mosquito, Tangmire has a long paved runway.

@Art-J: My point is that this is an historical inaccuracy that needs addressing. Whether that's a "bug" or not depends on your interpretation of the term.

Well, I'm getting there. Followed your advice. Trimmed for 120-140 mph with 10 degree of flaps down. What I am finding is that the more nose down trim I use, the better, which sounds counterintuitive to me. Somewhere around 2.2 is helping. The "snaking" starts just before the tail rising and gets worse during the tail is rising. There is a definite shift in the forces (no Star Wars pun intended) involved and it requires some rudder dancing to keep it straight. Best results are on the runways at Manston which is concrete and very wide. At best it's very sloppy. On the steel mat runways the whole process is very iffy. How about putting the assist back, please...?

Thank you, Talisman. They gave us a short delay in the update a couple of days ago but it really isn't enough. The standard seems to be 11 seconds although the delays went up to 30 seconds.

Thank you, Yo-Yo. That may explain why it works better when I take off with a neutral stick. I will give that a try.

Just an update: I find I do better with trim settings at default and leaving the stick at NEUTRAL instead of starting the roll with the stick pulled back.

The initial slow run is fine. I advance the throttle very slowly. There is some swinging before the tail comes up but it s manageable. The tail comes up and that's when I start to swing. Often right off the runway. Can't recover it with rudder or brakes. Can't avoid overcorrection. Once it goes, it's gone. Not very technical but I hope that helps.

Well, I started out with the option enabled (I didn't know it at the time) and after awhile I mastered taking off very nicely with two notches of nose down trim, two notches of right aileron trim and a very slow and conservative throttle acceleration. As soon as the update was released, I was all over the runway (and off of it frequently). I could tell immediately something had changed (I guessed the trim controls) but Basco's post about the takeoff assist told me what I needed to know. I hadn't even checked the Special menu. The change without the assist was quite drastic and I'm trying to learn how to live without it. Air starts are a possibility but I would rather take off and land from the runway. My guess is many others are having the same problem. It's otherwise a very good module (Other than that, Mrs. Lincoln, did you enjoy the play?). Please put the option back. No one is required to use it. Thanks, HT

Thank you you, Yo-Yo, for stepping up and taking responsibility. Apologies to NineLine. Being the messenger isn't always fun. That said, what is wrong with allowing the option? I will argue that, having unwittingly been using the assist, it became a nightmare for me as soon as it was gone. It DOES make a difference. Put it back, Yo-Yo, and let the customers have the choice. What's the harm?

This was my situation. I didn't check and assumed the assist was off. It wasn't. I was pretty pleased with myself with being able to master the takeoff so quickly. Well, I had help as it turns out. Now, without the assist, taking off is a nightmare. WE don't know who "the team" is (Ain't an anonymity grand! No accountability!) But NineLine has awarded himself a "Solution" medal so I suspect he at least had a major hand in it. Please, "The Team," put it back. For the player it is optional. The hard core simmer can turn it off. The rest of us can take off and enjoy the mod. Where's the harm? There is none. Put it back. It wasn't broken. Why "fix" it?

Well, tell "The Team" it was helpful to some of us and no one was complaining. If it ain't broke, you know....

The beatings will cease when morale improves, eh?

(Sigh) (Post fix today with a 2-second delay) My Mosquito still gets blown up on low passes but not quite as much. Talk about a band-aid approach! With real Mosquito the typical delay fuse was 11 seconds going as high as 25 and 30 seconds (which turned out to be a menace to following Mosquitos). This was a low level attack aircraft. It bombed from treetop and rooftop levels. DCS used to pride itself in accurate simulation. Guess that doesn't still apply. Two seconds? Really???

No1sonuk: Yes, I understand Early Access. I understand it is an opportunity for the developer to fix stuff that's broken. The lack of time delayed bomb fuses is not historical and it needs to be addressed. My comment is appropriate as this is the time to mention it. Yes, I agree with your second rude comment and I have stopped making historically accurate low passes and have switched to the also historically correct method of climbing to 3,500 feet and releasing my bombs at 1,500 feet. Because DCS bombs have very little splash effect you have to achieve direct hits with bombs and that leaves no room for error. I'm not doing the same thing over and over but I am avoiding the low passes that made the Mossie so effective at low levels (if they had time delayed fuses). This needs to be fixed. Good talk, sonuk....

Try this: Locate the indicators in the cockpit Rudder Trim: Right to the R in Trim Nose Trim: Nose down 2 Aileron Trim: Right 2 With the brakes off, power up very gradually (don't just firewall it; be gentle like the Spitfire) I don't pull the stick back to roll but either way seems to work. Try it both ways: back or neutral. Works for me. Hope that helps.