gulredrel

Currently I'm not looking at the AoA gauge. Roughly reference speed, depending on weight, use about 140 to stabilize approach, keep RW threshold around the center gunsight glass. Check vertical speed gauge to get roughly 700 fpm and for touchdown attitude and flaring bottom of gunsight glass at the end of the runway / horizon. Try some touch and goes and keep an eye on vertical speed if you have too much fuel. I find this relatively easy to land with these reference points.

Hello, as stated in a different thread I checked the indication of the whiskey compass. Didn't took a video as capturing using win + g results in a video with black flickering, whatever I need to change. Anyway, it is easy to reproduce. Do the following: start at a heading of 030 and begin a left hand turn when reaching 000 / 360 position, the compass stops than begins a +340° turn over to the heading of 340 or whatever you reached in the time the compass rotated instead of going the -20° from 360 to 340 in the same rate as during the turn also works in a right hand turn crossing the 360 position Thanks Jens

Hello, I wondered if this is correct but I noticed, the armament panel always shows RKT on all stations, regardless of what is loaded. Only after engine start and the station indicators show correct loadout. So is default / off power showing RKT or should there be something like stripes for INOP when not powered similar to the anti-icing indicators? Battery off, armament showing all RKT: Battery power only, armament showing all RKT: Engine running, correct loadout displayed: Thanks Jens

Hello, there were earlier occasions, when ILS glide slope was not working, but couldn't trace it really. Now it appeared again and I think it is something with initializing NAV system and VOR. Track attached to see, what was done. From memory I only can describe the symptoms. cold ramp start Kobuleti engine on INS on and aligning during alignment tune VOR to ILS and switch NAV mode to VOR Result: Glideslope pointer at the bottom of HSI taxiing, switching master modes or whatever, GS pointer stays at bottom of the instrument and shows no reaction. Localizer needle works as intended I think GS is working, when you only switch NAV master mode to VOR, after INS is fully aligned or something like this. Please enlarge to better see image markings. Beginning of RW, far in front of intended touch down point: VOR selected, LOC captured, GS pointer at bottom of ADI TACAN or RNAV selected: GS pointer at bottom of ADI together with off flag: Approach far below GS: VOR selected, LOC captured, GS no off flag, GS pointer at bottom of ADI; should be at top of ADI to bring me up to correct glide path: Thanks Jens MB-339_20221119_no_glideslope.trk

Just an assumption, I noticed "ö" in your username within the log. Maybe that's a problem for the module which in DCS general is not for you? Do you have the chance to create a different user profile with a username not containing umlauts.

Do you mean the whiskey compass? Is it this or just maneuvering? Haven't figured it out yet but yes, looks strange as sometimes the maneuvers were not too hard to induce such violent rotations. But OT here, we should file a different report.

Noticed this too, but got used to closer watch at the 100th needle.

A bit weird, yes. From autoupdate_log.txt, files were updated again, so don't know... Will fly it anyway if there's time, still much enjoyable when taking care of that front wheel.

Fingers crossed. First module for IFE. We don't know how ED's development kit supports config, branch and release management and such things. Hope they will work out a stable working process for the future. HB or other 3rd party developers had times when their changes didn't make it into updates.

I think as Caucasus was the first map and doesn't have as much bumps and slopes on taxiways as Syria or other newer maps which will be more accurate in this regard.

Just did a short flight in current OB 2.8.0.32937. I did not explode, but experienced blacking out at almost the same spot as shown in the picture above while taxiing back to parking. Don't know if touch down was too hard, but don't think so. I did hard braking, that's true, but even if the gear would be damanged, you should not black out taxiing below 10 knots going over a bump. MB-339_20221117_Kob_taxi_blackout.trk

Today's update was open beta 2.8.0.32937, but yes, the old file is back.

Some files in my DCS_World_OpenBeta\Mods\aircraft\MB-339 folder have today's date (MB339A.dll, FM config.lua, some training missions and so on...), so maybe there were changes, but they are only missing in ED's patch notes or are these changes which were missing last time but were present in change notes. I guess @6S.Duke is busy finding this out. Update: There is a message on discord, that the changes didn't make it in the patch. They are working on it. Don't know it this means, there will be an ED hotfix? I guess something has changed, the warning panel looks a bit better. There previously was a background which was too black. This is no more the case or it's my eyes

Al-Minhad takeoff and sunrise Dubai tour...

Hello, Don't know, if this has been reported, couldn't find something via search or didn't use the right words. RW centerline lights are blending through the fuselage at Al-Minhad while rolling over them. If it's modell specific, please feel free to move to MB-339 section. Thanks Jens MB-339_Dubai_tour.trk

No Halloween thing, just rctrl + num* on keypad maxed out. It's called "zoom external in". There's also "zoom external out" and "zoom external normal" to reset.

Hello, the ejection seat safety pin is completely missing in the rear cockpit, when it has been put on the canopy in the front seat. Easy to check in SP mission with both cockpits occupied, no blind flying hood installed. Front and back seat safety pin in seat: Front seat pin in canopy - rear seat pin completely gone, must be in the co-pilot's pocket I assume Thanks Jens

Did a flight in Nevada, 2°C at ground level. Front seat pitot heat on all the time. No ASI freezing. In the backseat, pitot anti ice was off. switched to the rear, ASI was at zero, turned rear seat pitot anti-ice on. Some minutes later, ASI showed airspeed again. So don't know, maybe there is something different in MP as I fly only SP. Some more moon pics. current date is perfect, moon sets late in the morning. I guess this is a no fly zone, but no one stopped me flying over Yucca Flat testing site in the sim

Thanks to the mission editor feature with sunset, sunrise, moon phase preview it's way easier to get this.

Uh, okay. I always turn pitot anti ice on before takeoff. Never happened in SP to me. Experienced engine icing. Do you flipped it on only after icing warning or loss of ASI?

Hello, just did a navigation flight following a flight plan. CDU was set to data page, showing WP number and range / bearing to current steer point of the flight plan as well as the RDU does. While overflying a waypoint the steer point on the RDU and the steering information and distance on the HSI changed to the next steer point. The data display is still showing data of the previous steer point: Only after pressing "mode" and "data" on the control panel, the information on the CDU display show the steer point info which is identical to RDU and HSI now. Thanks Jens MB-339_ftpl_data_pages.trk

On in both cockpits? I think, there are two, one for each cockpit and pitot sensor.

Same for me, present position on data page 3 is weird. Navigation works as intended, heading and ranging to WP01 is correct from aircraft's position, so only data pg. 3 displaying something strange. Being on the ramp at Kobuleti, the present position display points to a place in the western Black Sea. MB-339_present_position_bug.trk

Hello, as the title says, for the altimeter to show correct altitude above sea level, you always have to set it to 1013 mbar, regardless of the mission editor barometric setting. I did the following settings in Kobuleti cold ramp start, where field elevation is around 60 ft. Mission editor QNH: 760 mmHG - 1013 mbar - standard OKAY Mission editor QNH: 753 mmHG - 1004 mbar (test below standard pressure) altimeter 60 ft you need to set 1013 mbar: When setting QNH of 1004 mbar, it will show -750 ft at ground level in Kobuleti (I think it stopped at this value earlier, cause the instrument is unable to show lower vaue) Mission editor QNH: 775 mmHG - 1033 mbar (test above standard pressure) altimeter 60 ft you need to set 1013 mbar: When setting QNH of 1033mbar, it will show 2700 ft at ground: But now for some flying... trying some non standard settings and running in issues where I need to find out, if it's me or not who is doing strange things. Working in software quality assurance real life I'm infected with the need to do some root cause analysis So @6S.Duke don't slap your coders or me. DCS is quite complex and really needs fundamental testing. So many things to deal with. PS: Tracks show complete ramp start takeoff and an ILS approach. In some occasions I have the problem, that the glide slope does not work. It stays at the bottom of the ADI, no off flag visible. Clean new mission didn't have this, so maybe it's something with the different mission, which was copied from stable and I only changed player aircraft to MB-339 or something completely different with sequence of switching from TACAN to RNAV or VOR and so on... PPS: It's related to the following and we thought there was no bug, but it only really works as intended with standard pressure set in ME, so I created the new thread with details above: Thanks for checking Jens MB-339_760mmHG_1013mbar_KOB_ILS.trk MB-339_753mmHG_1004mbar_KOB_ILS.trk MB-339_775mmHG_1033mbar_KOB_ILS.trk