Various Bugs and other Things

[maikchaos]

I just started a trial period for this plane today and here is my first impress.

I've only tried the cold start and the landing tutorial and a own created mission so far. I flew with the latest Beta and DCS MT, if that makes a difference.

• The first thing I noticed is that there is only one toggle switch for many switches (Bat/Gen/Flaps/master arm etc.)
• Then it kept beeping annoyingly (TCN/ILS?) even with the battery off and all volume controls off. -->looks like a bug in all tutorial missions
• in a own mission, no beeping even if you set the tacan correctly and turn volume on... no beeps
• There is no clickspot for the NWS advisorxy light, you have to set a button first.
• com menu as keybind on controller does not work
• no or very low rudder authority between 50 an 120 knots at start/landing hard to hold the plane at runway
• axis indicator always show full brakes
•  if you start taxiing with SB partially deployed  and with full flaps deployed you get a black screen and the plane gets damage or explodes
• The ability to stay in flight in the curve is ... strange with full flaps and gear down, even with a low roll rate and 150 knots, you hardly have a chance of keeping your nose up and not stalling. it goes better with a full loaded then with a clean AC
• When landing at 115 knots (as required in the tutorial) it is the same, hard to hold the plane without stalling
• below 100 knots as the touchdown speed should be, the plane stalls.
•  

 

Edited August 31, 2023 by maikchaos

[gulredrel]

You may want to go through different other bug postings (radio...) and the known issues list (brake axis indicator, missing keybinds).

Especially the taxi bug is known and regarding the devs notes it will be fixed in an upcoming update. Currently you can get around when setting no wind in ME if you are in single player.

Canopy needs to be unlocked, there is a safety catch to prevent the canopy from shutting inadvertently.

NWS button on the stick is normal in a number of planes; there can't be a usable click spot at the front of the stick.

This is all described in the manual.

Landing speeds greatly are influenced by gross weight. So just fly AoA and observe sink rate regardless of speed (AoA indicator also known bug isn't quite right).

We are waiting for news from the devs which are said to arrive at the end of August.

[maikchaos]

28 minutes ago, gulredrel said:

Canopy needs to be unlocked, there is a safety catch to prevent the canopy from shutting inadvertently.

Thx for hint yes, forgot that

28 minutes ago, gulredrel said:

NWS button on the stick is normal in a number of planes; there can't be a usable click spot at the front of the stick.

 

The cold and start tutorial says "Click on the NWS Advisory light to engage NWS"  with a big yellow frame on that light, so it should be a clickspot there.

 

I have now flown the rocket tutorial and have followed all the steps. nevertheless, i could not fire any rockets, neither with the buttons on the stick nor with the keybinds of the keyboard

Edited August 31, 2023 by maikchaos

[gulredrel]

1 hour ago, maikchaos said:

The cold and start tutorial says "Click on the NWS Advisory light to engage NWS"  with a big yellow frame on that light, so it should be a clickspot there.

Okay, the light should only be an advisory light, no button. So the text is maybe just wrong in the tutorial.

Regarding the rockets, never had problems firing them. Salvo takes quite long if selected, but single fire worked. Will try and take a screenshot of weapons panel and keybinds.

[maikchaos]

49 minutes ago, gulredrel said:

Okay, the light should only be an advisory light, no button. So the text is maybe just wrong in the tutorial.

Ok sorry you are right i just missunderstood that. indeed we should push the nws button and check the light.

Is it just me who has the error that the TCN beeps all the time during the tutorials? Can you turn it off somehow? If you just want to find your way into a new plane, it's extremely annoying

 

[gulredrel]

On the audio panel there should be a knob for TACAN and another for ILS/VOR audio volume. Either tune it down to min or disable the tone by pushing or pulling the knob (can't remember which position is on/off).

[maikchaos]

I already tried that, but that does not work i set all the knobs to off but its still beeping.

It's the C&D Tutorial  Mission. It's beeping from the start of the mission even with the AC completely unpowered/engine off and all radios off

 

Edited September 14, 2023 by maikchaos

[gulredrel]

Started the cold start training mission myself. I've no idea, where the morse code is coming from. It's constantly morsing _ . _ . which should be just a C(?). Had a look at the training mission in ME but there's no corresponding sound file which is looped causing this. There's also some radio static noise in the background even with everything switched off.

Maybe @6S.Duke could have a look at this.

[maikchaos]

Thanks for testing, so it's not just me. Unfortunately, this is the case in all MB339 training missions that I have tested.

[6S.Duke]

Thank you for reporting the morse signal bug, it has been added to our bug tracker.

Inviato dal mio ASUS_I005D utilizzando Tapatalk

[gulredrel]

38 minutes ago, maikchaos said:

Thanks for testing, so it's not just me. Unfortunately, this is the case in all MB339 training missions that I have tested.

I imagine the missions are based on the same template. So it will appear everywhere. Maybe it is something with initialization for the training mission that is hidden in the mission file and can't be seen by just opening the mission in ME.

Anyway, IFE will figure it out.

[gulredrel]

6 hours ago, maikchaos said:

I have now flown the rocket tutorial and have followed all the steps. nevertheless, i could not fire any rockets, neither with the buttons on the stick nor with the keybinds of the keyboard

Following settings worked to fire rockets single from outer wing pods with the press pf the "fire weapons" button which I have on my stick:

[maikchaos]

Thanks for your help but sorry I'm giving up, as long as you can't even taxi safely to the runway with the plane, it's simply unusable (damaged/exploded 6 times now in last 20min).

It's good that there is a trial program so I didn't have to buy it to find out.
Maybe there will be an update until 14.09. otherwise again in half a year

[gulredrel]

As said above, if you are flying SP and using self created mission, just set wind speed at groundlevel to 0 m/s and you will not have any issue while taxiing.

[MAXsenna]

Thanks for your help but sorry I'm giving up, as long as you can't even taxi safely to the runway with the plane, it's simply unusable (damaged/exploded 6 times now in last 20min).
It's good that there is a trial program so I didn't have to buy it to find out.
Maybe there will be an update until 14.09. otherwise again in half a year

Just taxi a little slower. I've experienced it only once after landing on Nellis.
Basically all of the missions have the annoying ghost VOR "C". Guess it's something with the missions. Especially those with voice overs.
The "blind" IFR training mission and the last one in the campaign don't. No voice overs. Have no idea if that's related

Sent from my MAR-LX1A using Tapatalk

[maikchaos]

It happened to me in Kobuleti in the Caucasus, right when I started rolling. The speed was almost zero then.

I'll test it with the wind, thanks @gulredel

Edited September 1, 2023 by maikchaos

[6S.Duke]

It happened to me in Kobuleti in the Caucasus, right when I started rolling. The speed was almost zero then.
I'll test it with the wind, thanks @gulredel

The problem is related to the angle of attack rate. There is a bug connected to this value which causes enormous forces and moments around the aircraft which cause the damage or explosion. The fix will be available with the next OB patch.
At the moment missions without wind are not affected by the bug.

Inviato dal mio ASUS_I005D utilizzando Tapatalk