gulredrel

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.

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.