fixed Request Start-Up bug / Radio menu

[YoYo]

In my opinion, another issue regarding the radio and menu from the last DCS Open Beta 2.9.1.48111.

Start up.

Before the last patch:

- you could request for start up (cold engine)

- after this the request line from the menu was disappearing

- after this there was a new line about taxi to the runway

After the patch:

- request line from the radio menu is present all the time, even if you finish the whole process (manual or auto)

- no possibility to ask about taxi

- the line regarding taxi appears as a response only as a speech of ATC (immediately) after starting taxi

I added 2 tracks (sorry both was recorded in VR):

1/ test - manual C&D start in Mi-24P - even after starting the engines and avionics, there is no option to ask for a taxi and Request Start Up is present all the time

2/ test2 - auto start AH-64 - the same

This applies to all modules in my opinion. There's something wrong with the logic in radio menu. Before this patch was ok.

test.trk test2.trk

It's also easy to check it yourself. Take ME and insert a plane/helicopter with a cold engine. Check the radio menu and ask for permission (with radio on). You'll see it doesn't go away.

btw. every map, every airfield (so menu issue after this patch).

[YoYo]

This also means that we will not find out about the right direction of runway for take off before taxiing, which was possible before last patch. It looks as if someone ate a piece of code and therefore after the request for permission to start up the menu did not jump to the next one (request for taxi). 

[Flappie]

Thanks for the heads up. Issue reported.

[Rudel_chw]

On 11/19/2023 at 7:53 PM, Flappie said:

Thanks for the heads up. Issue reported.

 

Thanks @Flappie ... unfortunately, this bug still persists after today's update to 2.9.1.48335 

 

[YoYo]

57 minutes ago, Rudel_chw said:

 

Thanks @Flappie ... unfortunately, this bug still persists after today's update to 2.9.1.48335 

 

Yes, not solved.

Radio wasnt touched according me in this patch, this bug is present still too:

 

[YoYo]

Hi, any chances for the fix in December OB patch? The same missing names of FARPS. So both cases = as it was. Nothing new.

[Flappie]

3 minutes ago, YoYo said:

Hi, any chances for the fix in December OB patch? The same missing names of FARPS. So both cases = as it was. Nothing new.

This issue has been fixed internally. The next OB update should contain the fix.

[YoYo]

Great! Thanks for good news 

[Flappie]

Fixed with today's OB update.

[Rudel_chw]

2 hours ago, Flappie said:

Fixed with today's OB update.

thanks  will test it tonight, as this issue impacted one of my missions  

 

EDIT: Just tested, works perfectly now, thanks ED  

Edited December 19, 2023 by Rudel_chw

[YoYo]

4 hours ago, Flappie said:

Fixed with today's OB update.

Right. Its back to normal , solved, TY!