Once I got off the ground it was a total joy to fly. Question regarding the canopy, are there certain stress limits that are introduced when it’s open? I’m overstressing a lot on takeoffs but landings have been pretty easy for me, aside from my last flight when I decided to open the canopy on final and got my flight ended by an overstress as soon as it opened. The manual mentions to close it right after takeoff but no mention if it can be open for landing. I can’t help but think I must be doing something wrong.
I have seen a preview where the guy has it open for both. I have been flying with it closed. But I am guessing your speed on approach is what matters here.
Yeah my guess would be speed but I was near 100MPH which Is below rotation speed. I assumed it was due to how much I was pulling back the stick because in that scenario I was out of trim and was pulling back on the stick quite bit, in addition, I’ve found that I have more success on takeoffs with a very light touch on the stick else I overstress.
I had this happen a few times. I closed the canopy and it stopped. I thought you were supposed to takeoff and land with it open but might be wrong.
It’s pretty amazing how things look in VR right? However, everything has been modeled accurately. For instance look at the trim knobs on a 2D screen then look at them in VR.
Yea so it looks like Asobo are forcing a crash if you have an exit open and since the Canopy is considered an exit, this is the issue. I’ve raised this with Asobo because you are 100% correct, for most of these old birds your T/O and Landing are all with the Canopy open in case you need to make a hasty exit!
Ah! THAT is the reason for the canopy being open? LOL.
You can actually disable the stress crash detection in the MSFS assistance menu. Its bugged anyway, so might as well turn it off 
Thanks. Yeah, the take-off roll in this P-40 is nothing like I’ve been experiencing in the Spitfire and the Corsair, which is a good thing! The only thing that stops the Corsair from careening left off the runway for me is right toe brake. I feel like “handful” and “dancing” are much better descriptors for taking off in this P-40, whereas “almost wacky” and “unstable” is probably how I would describe the others.
Anyone having some sound issues? I’m getting what sounds like an additional idle engine sound being added to whatever other sounds are going, and it pops up seemingly randomly. The first time it happened I thought there was an AI P-40 on the ramp next to me firing up as I was doing start-up procedures, but then it happened once in flight, and another time it was immediate right after I loaded cold and dark with the engine off. The sound sticks to my plane too.
Not to compare everything to the other warbird add-ons, but the Corsair doesn’t do this. You can happily fly it along with the canopy open without triggering an overstress. In fact, that’s how I usually fly it. I pull the RPM and throttle way back and fly low to gawk at scenery like I’m in a heavy, fast open-cockpit bi-plane.
Yea they most likely aren’t using the declared variable (A:CANOPY OPEN, Boolean) and using a local private variable instead (L:My_Awesome_Var,Boolean). We could do that do but it would then require redoing some extra code in the sounds to use that variable instead of the declared one.
About the sound problem, i had that too in the helicopter and the coursair a few times the last days, so it’s a new bug from Asobo or some addon interference.
Thanks for the feedback, i have seen a report somewhere of people having problems with AI sounds being way too loud. W’ell check it out.
Well that explains my issues with the overstress warnings, because I definitely was being gentle! I think for now I’ll disable overstress as that open cockpit sound is just too good to go without.
haha Yea it’s soooo cool to have that canopy open
Hey folks, I’m chatting with The Flying Fabio in about 5 mins!
Come and join in!
That’s ridiculous. Nobody crashes because they forgot to close the door. Grr…
Who ever decided it’s ok to let software developers make decisions on their own? sigh
Time for a story/lesson from Dr. Smirnov this morning about crash detection. 
Let’s put it this way… I was a big fan of leaving Crash Detection on as I wanted to be aware when I make fatal flaws. Then the folks at PMDG Forums actually had a few nice points…
I posted “how come when I start flight at some airports, no matter what I do, I get an instant crash?” The aircraft seems to slam to the ground slightly when it first loads and that triggers a crash… (which in P3D automatically triggers a loading of your default scenario - that means loading different airport, different plane, etc - HUGE pain)..
The answer was: “Set crash detection to off!!! Who flies with it on?”
My response: “but but but but but… I mean, I just had a tail strike on landing - it’s kind of nice to know when I SERIOUSLY mess up”
The most reasonable response from PMDG people was: “So you had a tail strike! Why in the world would you want to have your flight end when you have that??? There is a whole checklist of procedures just waiting for you to execute specifically designed for tail strike scenarios??? You are missing out!” See, PMDG has basically EVERYTHING modeled and documented - including pilot error, crash landing scenarios, etc - that’s part of their appeal…
All of a sudden something clicked. I said to myself “You know… that’s a good point. NOT ALL crashes end in everyone dying instantly - tons of them have highly survivable scenarios and in certain aircraft, you can run proper procedures after things go terribly wrong!” Since then, I have no “MORAL” conflict with disabling Crash Detection.
Yes! Also, it’s more fun when you actually hit something and the plane gets kicked around or flips over instead of just getting a black screen.
Jumped into the cockpit and my immediate impression was ‘Oh’ and not in a positive way. Sorry but being a Milviz Corsair owner from which to make a comparison, the cockpit textures, whilst they do their job in this Tomahawk, are clearly not to the same level of detail. Trying to sum it up or quantify it here, but the cockpit reminds me of X-Plane ones. The textures just seem flat in places and lacking realistic detail like they’re missing that level of authenticity and element of realism that Milviz did so well. You can see right through clearly to the engine bulkhead where the guns go through but there’s no darkening of the textures or shadow there. Some of the weathering and marks look a little fabricated to me. They maybe little things but they soon stand out and spoil the element of immersion.
The default view position is too far back (easy fix mind) , however with a number of the gauges, the numbers in them are partially blurry 
It maybe me but the twin synchronised .50 Brownings don’t seem to line up with the housings in the fuselage.
Cockpit controls seem to all work well and actions are smooth. Clever use of the 50 Cal MG’s though for the RTDM 
Take off is your default tail dragger boot full of rudder white knuckle ride , with 3 notches of elevator trim dialled in. External animations work well and look good. Engine sounds are fine, not knocking it out of the park but not shabby either, although when increasing the throttle the layered engine sounds of each stage do seem to fade out noticeably quickly into the next one as engine revs and speed picks up.
Elevator response feels fairly measured using the Honeycomb yoke at -50% sensitivity, likewise with the aileron response. It flies well enough to me and once trimmed up behaves itself nicely without any dramas.
Landing went without event although the visibility in this aircraft on landings is challenging. Get your head out the window job! Probably worse than the Corsair in that respect.
FPS both interior and exterior was good for me so no complaints there.
It’s got visible guns though , but can’t see them making it to the store version 
To summarise, for me it’s got some good points overall, just let down by some of the textures as for me the cockpit textures > everything else. By comparing this to the Corsair, that’s probably a little unfair as I’m comparing a well established and respected developer to one that’s new to the game, but for me that’s the standard to aim for and the only comparison I can make right now. Of course there’s a price difference here too to consider. If I was after a WW2 fighter and had the funds, I’d still go with the Corsair, but if you want something a little less demanding and less in depth, obviously cheaper, can live with the texture quality or just like the old Warbirds full stop then for sure give it a look.
Any info on the sound package that is included? I’m curious to know if it uses Wwise or Legacy sound package and if it includes a soundai package for multiplayer. Thanks.