Minhal

Currently moving to a new hoster afaik and also being reworked a bit. IIRC it should be back end of the week. Edit:

Just checked again, mixed up several tracks from earlier. Good you asked again! This one is equally long as the broken one but seems to play - at least for me. Fire starts around 0930 hours. Seems to be a gearbox fire that then spreads to the engine. Been doing a lot of stuff while on the ground, checking controls and stuff while photoshopping MFD inlays Been fiddling with the SPPU. Not sure if i broke something along the way that maybe have caused the fire. Hind fire.trk

The track is not usable sadly. Was sitting on the ground cold and dark for more than an hour going through my controls. That 15 minutes flight was just after that. I'll post one if it happens again. People really should. I wish there were more general failures due to wrong handling in DCS. Like engine fire in the C-101EB when you do not obey engine limits. Birds bring at least some unpredicability. Do birdstrikes appear in the debrief as an event? Would be helpful to analyse this issue.

Just had this too for the very first time since flying the Hind. Happened after about 15 minutes on the Syrian weapon range IA mission. Have random failures off but birds at 100%. Might just have eaten one.

Briefing says one is armed with guns, bombs and rockets, text/voice intro says one is armed with guns and bombs. But fuselage and wings are empty. Mossie no bombs no rockets.trk

May indeed be the taxi light. Just recently put it on a switch and might have had it in extend position by accident. Will try later.

Seen that too the last days, was not the case in the past. Think it is a bug.

That's awesome. Having something like this publicly available is a treasure chest. Cheers Calgary

Boy, i am so looking forward to this! Did you guys do laser scans?

Just gave it a try. Running at 1080p, the dot fading does a nice change. Thanks for bringing attention to this and working on this mod. Hope ED can implement to the core features and further refine it (missile issue and the like).

The flaps lever got three positions: up (raise), neutral (stop) and down (lower). Lower the flaps fully, then raise them again by putting the lever in the up position. Once in the desired position, set the lever to center (neutral) position. This will hold the flaps in the current position. Sounds a bit like you only set up and down in your controls and missed the center setting?

I thought about this a bit and did some testing. I think this is a bug. Or i got some confused Friday Did a test mission on Caucasus i attached. QNH is 30.00 inHg | 1016 hPa | 762 mmHg QFE is 29.84 inHg | 1010.60 hPa | 758.01 mmHg Elevation MSL for all aircraft should be 148 ft | 45m (according to F10 map) as the elevation of the apron does not vary. A-10C shows ~150 ft for 30.00 inHG FW-190 D-9 shows ~45m for 1016 hPa Mosquito shows about ~170ft for 1016 hPa -- incorrect Spitfire shows about ~180ft for 1016 hPa -- incorrect TF-51 shows ~160ft for 30.00 inHg -- incorrect P-47D shows ~125ft for 30.00 inHg -- incorrect F-16C shows ~150ft for 30.00 inHG C-101 shows ~150ft for 1016 hPa AJS37 shows ~45m for 1016 hPa Su-25A shows ~45m for 762 mmHg Mi-24P shows ~20m for 762 mmHg -- incorrect Mi-8MTV2 shows ~45m for 762 mmHg I put in airstart slots too because i thought it might also relate to the airstart bug i reported. But it is only the Mosquito, Spitfire and P-47D that start with an false set altimeter. TF-51 and Mi-24P are correctly set on airstart. @BIGNEWY could you kindly move this over to the bugs section? Probably best the general bugs section, not P-47D, since it affects several modules. Altimeter test.miz

Elevation usually differs around the airport on the other maps, but on Normandy 2 the elevation is all the same over the whole airfield on most airfields (check when you move the cursor around in F10 map, upper left near the longLat). Checked for Funtington (where my plane sits) at parking spot, treshold, along runway: airfield is all flat and 125ft MSL. Airfield elevation on charts is the elevation above MSL at the treshold location as this is the only elevation relevant. I set the QNH to 29.92 in the mission editor. Not sure what you mean with "for that aerodrome", you might confuse QFE (altimeter shows zero when on the treshold) with QNH (altimeter shows treshold elevation above MSL when on the treshold)?

Reporting it for the P-47D, though i found this happening on several other warbirds but not all. Usually on airstart, the alitmeter is set to QNH (tested with A-10C, F-16C, AJS37, Mi-8MTV2). This is not the case in P-47D, Spitfire, Mosquito. The FW-190 D-9 on the other hand is set correctly to 1013 mbar with a mission QNH of 29.92 inHg, so it is not a common warbrid issue. Did not test the other warbirds since i do not have them. I tried the Normandy IA mission Beachhead patrol for the attached track. QNH for the mission is 29.92 inHg. Altimeter is set to 31 inHg on start (maximum setting for the alitmeter). P-47D Altimeter.trk

Sitting at Funtington airfield, which has a field elevation of 125 ft MSL (according to F10 map). QNH is 29.92. Set it so in the mission editor. Setting the altimeter to 29.92, i am off by 25 ft. Is this just a warbird/P-47D thing, an error on the Normandy 2 map (happens on all maps) or am i missing something?

Is this helpful? Frequencies were set by the ground crew afaik, so not change in cockpit.

Good point, did not think about this. But not really workable sadly as your movements are still relative to the front of the plane. So if you look left physically, the pilot leans "left" (relative to the front of the plane) to "look over his shoulder" (see video). Also all the XYZ movements are still relative to the planes 12 o'clock. Physically leaning left makes you lean "forward" (direction to the pilots seat). Mossie.mp4 I'll take some time the next days and make this a wishlist item, no clue why something crucial was not in from the start.

Awesome find indeed. Just sponging this Why isn't this a sticky yet?

null"This mission starts with your aircraft on final approach for landing. You may land immediately or enter the pattern for multiple approaches. There are no threats." C-130 on the runway: "Hold my beer". The attempt before this i got blown to pieces by an AI P-47D that went right through me on the runway. Sometimes your friends are your worst enemies i guess.

Ah damn, thanks for clarifying. Thats really a deal breaker sadly. Snapview is not an option since my brain is so accustomed to TrackIR, it really does not like switching between static and moving cockpit view. (Or forced movement, since i was happy to see one can deactivate the automatic cruise/gunsight shift). Operating back there with TrackIR really asks to do some weird gymastics over some time, so this is not an option either. Guess i'll give it two weeks and check out everything else on the Mossie and maybe make a wishlist item for this. Pressing 3 for a rear looking navigator position should be possible and easily solve this.

In the real plane, i guess the navigator turned 90 degrees left on his seat to operate all the equipment back there. Just trying the Mossie on trial and i could not find a viewport that would replicate this and is suitable for prolonged operation in the rear. Just the forward looking when pressing 2. Am i missing something?

Great to hear you like this. I think with Europe (Channel and Normandy available) and Pacific (Marianas WWII coming soon™), North Africa would be a nice addition for WWII. We do not have correct aircraft for that time frame today. But if there is a map available already, aircraft module developers have incentive to make modules for this map. Also, having then done the ground mesh for east Lybia in WWII, it could be used as foundation for modern Lybia map. Which i think folks would love too There is much potential.

Since you have the ground mesh of the area done already and experience with the region: did you ever think of doing a 1942 map next of the area Tobruk to El Alamein?

The tailwheel on the P-47D does not self center. So when unlocked for taxi, it will maintain the left or right position and you'll keep turning. Check in F2 view when you use differential braking and you'll notice. Got to apply opposite brake to end the turn and align the tailwheel straight again. For takeoff, align the tailwheel straight down the runway. Then use the tailwheel lock lever on the lower right of you seat to lock the tailwheel in position. Once you are aware and did a bit of taxi, it becomes second nature quickly.

Thanks for going through this epic task! Translating is way, way easier when you have the source in a format where you can just copypasta. I typed so much Swedish text into Google translate before you went on this journey, it is a wonder i am not fluent A huge contribution that makes this great module even more enjoyable! Truly appreciate the time you sunk into this. Especially when you feel burnt out, best is to pass the flame and let others carry on.