gulredrel

Just to clearify, it's an air and oil cooled engine. So no water temp. Triple gauge top is oil temp, the single gauge is cylinder head temp.

Hello, with the last open beta the RNAV Navigation bearing indication is totally wrong. Was completely lost in Syria map yesterday with my mission editor flight plan. Tried alignment with typing in initial coordinates as well auto alignment which should use GPS. Present position shows strange values afterwards, but this should be a known issue. At this time at the beginning of November, Waypoint heading information was correct. It was only a problem with the presentation of present position on the CDU discplay. Now with current OB DCS/2.8.1.34667 WP navigation using CDU is completely usesless. The bearing indication is totally wrong. Distance looks okay. I created a simple test mission air start flight plan with known WP over TACANs in Caucasus. WP1 is over Kobuleti RNAV to WP1 shows bearing of 352, switching NAV source to Kobuleti TACAN 67X shows bearing 110, which is correct with the map WP2 is over Batumi Same here, RNAV bearing is 047 but TACAN 16X is located bearing 166. Distances are the same for TACAN and RNAV waypoints, so whatever is wrong is bearing indication and display on the CDU. I'm a bit concerned here. Normally I'm waiting for stable release version, but was very interested in this aircraft so I bought it on day one. Especially te CDU integration with own data card file support is a nice addition. I've now discovered quite a few bugs. Dev reports were great so I was hoping to get enjoyable hours in this bird but instead invested quite a few hours in finding quirks or trying to find if it was my fault before writing reports. I know it's open beta, but it's a bit... I would have rather enjoyed just flying in my spare time. Nevertheless, looking forward when things get polished. Thanks Jens MB-339_20221223_RNAV_wrong_direction.trk

I have flown several sorties today, same mission as above, but with zero winds. There was no problem. @Bigskill Do you know, what the wind conditions where during your MP flights?

Hello, is it me or the lighting conditions? With the latest OB 2.8.1.34437, the ejection seat safety pin looks really dark. Front seat rear seat It was the factory paint scheme in Caucasus map. Date and time in screenshot status bar, mission attached. track is quite big, but unnecessary for verification I think. Thanks Jens MB-339_Kobuleti_target_practice_no_wind.miz

Hello again, today, 3 attempts, same mission. On all three attempts I encountered the g-spikes while taxiing in the first part of the taxiway but at different places. Tracks 01 without blacking out, track 02 with shortly blacking out. In track 03 the blackout lasted very long and I switched to external view. The front of the aircraft was jittering up and down like crazy as well as the AoA value below -100 and well above +100. I noticed the massive AoA values in the status bar. Just an assumption. Could the problem be related to wind conditions, especially wind from the rear that in some circumstances this has a weird effect on taxi behavior?! Wind related front gear movements where a problem in F1 early beta too, I believe. In yesterday's damage screenshot, the AoA value is even higher. Thanks Jens MB-339_20221219_03_g_spike_taxi.trk MB-339_20221219_02_g_spike_taxi.trk MB-339_20221219_01_g_spike_taxi.trk

That's exactly the problem. It's the same mission. One time the problem occured, the second time there was no problem. Couldn't find a way to reproduce it permanently. The mission attached was used for the tracks above. I always start at ramp position 19(?, see mission for details). Startup, taxi to RW 07. In the first track above, I got the g-spike short after I started taxiing being on the main taxiway. No problems on the rest of the taxiway. After landing on RW 07 I taxied back to the same ramp position via the way behind the ground equipment. Turning to the parking spot, as can be seen in the screenshot above, I experienced the massive g-spike and damage to the aircraft. On the second attempt. nothing happened, using the identical taxi path. MB-339_Kobuleti_target_practice.miz

Single player here in Caucasus. Plane didn't explode but I had g-spikes shortly after I started taxiing, +9/-5 this didn't resulted in any damage: I did my flight and after landing taxied back to parking, during the turn at low speed to the parking spot, next g-spike +12 / -4.5 including pilot short blackout: Damage to the batteries and hydraulic system: Please find trackfile attached. Thanks edit: Added second track. Same mission, same taxi route. This time no g-spikes. @6S.Duke and @BIGNEWY Really weird, I've no further idea how to constantly reproduce this issue. Do you have any hints how we could recreate and help the devs? MB-339_20221218_bump_taxi_TO_Matra_land_taxi_bump_damage.trk MB-339_20221218_no_bump_taxi_TO_Matra_land_taxi.trk

I only did a short flight. cold start Kobuleti, taxied to RW 07. No problems with the nose wheel. After landing I went from the runway through the grass to the ramp. Even there, no problem. Will need to do further flights. Thanks @6S.Duke and IFE for the key bindings. Nice to have the weapon stations 1 to 6 and the extend / retract airbrake with intermediate positions now. I think fuze selection binding nose tail is a bit weird. It toggles from safe to nose / tail position and than to tail. from there on nose / tail and tail. the tail only binding toggles between safe and tail only consistently.

Hello, first of all, thanks for the new key binds. Now I mapped airbrake extend and airbrake retract to two switches on my TWCS throttle. Now my findings doing ramp cold start, engine running: The extend airbrake sound can be heard and loops, as long as the extend airbrake button is pressed. Even if the airbrake reaches it's intermediate position on the ground with wheels down. The airbrake retract sound stops as soon as the airbrake is fully closed even the button is still pressed. Today's update DCS version 2.8.1.34437 Thanks Jens Edit: While in the air with gear retracted, the extend airbrake sound stops, when the airbrake reached full out position, even if the button is kept pressed.

Worked for me in single player. I copied and renamed the original file in my game folder: E:\games\DCS_World_OpenBeta\Config\Effects\ParticleSystem2\smokeTrail.lua --> E:\games\DCS_World_OpenBeta\Config\Effects\ParticleSystem2\smokeTrail.lua_org I than edited the original file smokeTrail.lua within the folder with notepad++, which also has the option to compare both file versions, so you don't accidently change other values.

Bignewy posted "Weapons loadout compatibility matrix" in mini update section. There is a combination of S-8 and S-13 marked with both usable in symmetrical loadout. I don't really get it how to select between S-8 or S-13 to really effectively aim it.

Creech to Groom Lake and back.

Some tracks I posted this morning but these were lost during the forum downtime and backup. Kobuleti cold ramp start, first solo, no wind, than with backseater, more fuel and weapons, wind... Always wiggled the stick before disengaging the control lock. In the past I thought this could be a problem. Don't know, as it was no problem in the first tries. Interesting one is this: MB-339_20221208_04_massive_bump_max_weight_wind_two_seat.trk I was taxiing the same way and suddenly massive bump, g-meter maxed out at +9 / -5, nose wheel broke, nose wheel gear door came down. I guess if I were faster, I would blackout and maybe explode, cause the g-stress would be higher? The same setup, but this time no problem.MB-339_20221208_05_no_bump_max_weight_taxi_TO_bomb_lan_taxi.trk So this is all really weird. Jens MB-339_20221208_05_no_bump_max_weight_taxi_TO_bomb_lan_taxi.trk MB-339_20221208_04_massive_bump_max_weight_wind_two_seat.trk MB-339_20221208_03_no_bump_wind_two_seat.trk MB-339_20221208_02_no_bump_two_seat.trk MB-339_20221208_01_no_bump_no_wind_one_pilot.trk

Now I know, why my post in MB-339 section is no more visible. Thanks for the information.

We are all waiting for the patch to arrive. Currently Caucasus and Nevada are relatively save for me. But there are some circumstances I still don't understand, when it is happening. For me the possibility of getting the issue increases when: non-solo, heavy loaded, wobbling the stick with control lock on before taxiing, heavy breaking...

Thank, quite extensive. I guess, the issue has been solved which prevented the changes being within the last updates. Looking forward to the fix regarding taxi explosions due to fragile nosewheel.

They are practicing for an airshow in Bulgaria

Has been fixed internally. Hopefully next OB patch will include MB-339 changes, too.

For the NAV unit, there is a button BRT next to the + / - rocker. Press the button and the - on the rocker to dim nav panel and RDU. For the COM repeater display, there is a brightness knob on the VHF/UHF (COM2) radio.

Point 1 could be related to this. It's indifferent. Audio panel usage and NAV source tuning / selection sometimes leads to COM not working. My current workaround described in the thread below.

For the EB version, there are these ITT LIMITATIONS: 860°C for 5 min during takeoff 796-832°C for 30 min 795°C maximum continuous You need to reduce throttle during climb as ITT will rise. You need to pay attention after takeoff, being above 832°C greatly reduces the 30 min period. I almost always climb at max. 795°C ITT after takeoff. Regarding cruise speed and height. Higher is better for fuel economy. Check your fuel flow gauge during climb and cruise. Depending on the distance you want to fly, reduce fuel load. You won't need the fuel in the wings in most flights.

Thanks for clearing this up. That sounds reasonable. Maybe this can be added in an update of the in game flight manual as a side note to the weapons panel description.

@6S.Duke Please check the last to images on low approach (will add image captions in first post to explain what to look for and insert some markings). The NAV mode is set to VOR but the GS pointer is not moving although the GS off flag is not visible. Please try the track to see when I'm switching the NAV sources and see how the GS pointer reacts or does not in this case. Using the same mission with a different sequence of setting up the same frequencies, ILS works. So I haven't figured out, what causes the GS pointer to always being at the bottom of the ADI. When ILS is working with both localizer and glide slope, the GS pointer returns to middle position when losing GS. Not in the example above.