Author Topic: Error "unexpected keyword argument 'beep'"  (Read 3387 times)

Airbuspeter

  • Newbie
  • *
  • Posts: 22
Error "unexpected keyword argument 'beep'"
« on: May 31, 2025, 10:25:13 pm »
have the couatl error message with fenix and PMDG.other planes i dont know.
couatl v5.0 (build 5765)
panic log started on Sat May 31 22:20:56 2025

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
  File ".\GSX\assistanceServices\__init__.py", line 2679, in do
  File ".\GSX\assistanceServices\__init__.py", line 4644, in showMessage
  File ".\GSX\__init__.py", line 1377, in showMessage
  File ".\common\youcontrol.py", line 185, in showMessage
  File ".\common\youcontrol.py", line 112, in showMessage
TypeError: showMessage() got an unexpected keyword argument 'beep'
{'User Pos': (51.28105917503429, 6.767160955454283, 39.2211 m, 2.86053 m, 276.02394894765325, -0.0009440176491612012, 0.001745329238474369, -0.0013876988971911351, 3.18211187210083, 1.0), 'Airport': 'EDDL', 'Requested parking services to': 'Terminal - A-Pier (A1-A16) | Gate A2', 'Requested assistance services at': 'Terminal - A-Pier (A1-A16) | Gate A2'}
« Last Edit: May 31, 2025, 10:29:24 pm by Airbuspeter »

ChrzOC

  • Newbie
  • *
  • Posts: 31
    • OCNET Networks
Re: Error "unexpected keyword argument 'beep'"
« Reply #1 on: May 31, 2025, 10:34:24 pm »
Aircraft: Fenix A321
GSX Ver: 3.5.4

Problem:
After requesting catering, after the trucks are in place, and just prior to the two handlers spawning in the trucks after the doors are opened, Couatl will crash with the error listed below.
Been using GSX for years and haven't had issues, however since this most recent update to 3.5.x I have had numerous crashes similar to this. Yesterday when using 3.5.3 it was during pax boarding, after updating to 3.5.4 today I'm seeing it during catering.

This particular catering crash occurs at any airport, with any operator, the below example is from FSDT KIAH.

***UPDATE*** The error also occurs during refueling. It seems it occurs at the point when the "BEEP" is supposed to occur notifying you that the catering or fueling trucks are in place.


Couatl Log

channel.balance =  -1
AssistanceServices.showMessage() Catering vehicles are in position WHITE
emulateText_MSFS [GSX] Catering vehicles are in position WHITE 3.0
Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 4672, in waitWarningFunc
  File ".\GSX\__init__.py", line 1368, in showMessage
  File ".\common\youcontrol.py", line 185, in showMessage
  File ".\common\youcontrol.py", line 112, in showMessage
TypeError: showMessage() got an unexpected keyword argument 'beep'
{'User Pos': (29.983871781894976, -95.33839340384121, 32.7525 m, 2.85323 m, 0.10996884324125872, 0.0022183606506008457, 0.001745329238474369, 0.00010234175875839006, 3.18211187210083, 1.0), 'Airport': 'KIAH', 'Requested parking services to': 'Terminal C|Gate 39', 'Requested assistance services at': 'Terminal C|Gate 39'}

Panic Log

couatl v5.0 (build 5766)
panic log started on Sat May 31 16:10:54 2025

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 4672, in waitWarningFunc
  File ".\GSX\__init__.py", line 1368, in showMessage
  File ".\common\youcontrol.py", line 185, in showMessage
  File ".\common\youcontrol.py", line 112, in showMessage
TypeError: showMessage() got an unexpected keyword argument 'beep'
{'User Pos': (29.983871781894976, -95.33839340384121, 32.7525 m, 2.85323 m, 0.10996884324125872, 0.0022183606506008457, 0.001745329238474369, 0.00010234175875839006, 3.18211187210083, 1.0), 'Airport': 'KIAH', 'Requested parking services to': 'Terminal C|Gate 39', 'Requested assistance services at': 'Terminal C|Gate 39'}




Anything I can do to fix this please let me know, as GSX integration with the Fenix A321 is basically unusable right now. (The issue also occurs if Catering is just called from the GSX menu as well).
I haven't checked to see if it occurs with other aircraft yet, I am going to check that shortly.
« Last Edit: May 31, 2025, 11:04:01 pm by ChrzOC »
-ChrzOC
(OCNET Networks)
Mechanical Design Engineer, CFI/MEI, AvGeek

ChrzOC

  • Newbie
  • *
  • Posts: 31
    • OCNET Networks
Re: Error "unexpected keyword argument 'beep'"
« Reply #2 on: May 31, 2025, 10:35:37 pm »
same. I just posted a topic on this as well.

For me it's during catering requests with the Fenix A321. At any airport. Same exact error.
-ChrzOC
(OCNET Networks)
Mechanical Design Engineer, CFI/MEI, AvGeek

ChrzOC

  • Newbie
  • *
  • Posts: 31
    • OCNET Networks
Re: Error "unexpected keyword argument 'beep'"
« Reply #3 on: May 31, 2025, 10:45:12 pm »
By the way:
MSFS2020 ver. 1.38.2.0 (current)
Windows 10, DX11

I saw another topic where someone was having the same exact issue in MSFS2024 as well though.
-ChrzOC
(OCNET Networks)
Mechanical Design Engineer, CFI/MEI, AvGeek

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 53111
    • VIRTUALI Sagl
Re: Error "unexpected keyword argument 'beep'"
« Reply #4 on: May 31, 2025, 11:06:25 pm »
The problem (which happened only if you turned down the Verbosity slider) is fixed by running the updater now.

ChrzOC

  • Newbie
  • *
  • Posts: 31
    • OCNET Networks
Re: Error "unexpected keyword argument 'beep'"
« Reply #5 on: May 31, 2025, 11:10:09 pm »
thanks,

Yes I also noticed that the verbosity setting I had was not applying (all messages were appearing on screen).

Going to update and test now.
-ChrzOC
(OCNET Networks)
Mechanical Design Engineer, CFI/MEI, AvGeek

ChrzOC

  • Newbie
  • *
  • Posts: 31
    • OCNET Networks
Re: Error "unexpected keyword argument 'beep'"
« Reply #6 on: June 01, 2025, 01:26:32 am »
**Update**

Yes, it looks like this error was resolved with running the update tool for the most recent build.
Thanks.


A Few other issues:

1) I still see that the verbosity slider is not functional though. (All messages still appearing on screen despite the slider being in the "OFF" position)
2) Progressive boarding/integration with Fenix A32X not functioning correctly (Pax counter in EFB stops after 13 passengers), which causes the fenix boarding progress to hang even after GSX completes all boarding.
3) Services exclusion list keeps pushing all services to the exlude (right side) list after each update, requiring you to manually update the exclusion list after each update.

I can create new topics for these if you like.
-ChrzOC
(OCNET Networks)
Mechanical Design Engineer, CFI/MEI, AvGeek

wolfbaronx

  • Newbie
  • *
  • Posts: 4
Re: Error "unexpected keyword argument 'beep'"
« Reply #7 on: June 01, 2025, 02:24:53 am »
Hello

Please note that all that is mentioned below never happened on previous releases

Situation
- PMDG 777-200ER
San Francisco A1V
- when loading field and boarding after gate attaches there is a message to not load fuel until truck is there
then this crash
```

couatl v5.0 (build 5765)
panic log started on Sat May 31 17:21:13 2025

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 4672, in waitWarningFunc
  File ".\GSX\__init__.py", line 1377, in showMessage
  File ".\common\youcontrol.py", line 185, in showMessage
  File ".\common\youcontrol.py", line 112, in showMessage
TypeError: showMessage() got an unexpected keyword argument 'beep'
{'User Pos': (37.61398149854816, -122.38736554933226, 8.04168 m, 4.08755 m, 339.9527052093771, 0.013452901955889517, 0.013962633907794952, 0.00010487008820020708, 4.078833590698243, 1.0), 'Airport': 'KSFO', 'Requested assistance services at': 'Intl Terminal, Pier A|1V'}

```

- Also totally different aircraft face the same exact error with this "beep" traceback
It was horizon 787-9 and in EPKK some random parking there. Happens after boarding is initiated consistently


I noticed that 2 new updates where available back to back but it looks like it introduced a glitch? I like this program but this kills my flight experience
« Last Edit: June 01, 2025, 02:26:41 am by wolfbaronx »

ChrzOC

  • Newbie
  • *
  • Posts: 31
    • OCNET Networks
Re: Error "unexpected keyword argument 'beep'"
« Reply #8 on: June 01, 2025, 02:38:47 am »
see the topic just below this one, I had this issue earlier.

Update/Refresh to the latest packages and it will fix this issue.


There are still other issues though, if you are using the Fenix (Progressive boarding).


Update (Topics now merged)
« Last Edit: June 01, 2025, 02:42:09 am by ChrzOC »
-ChrzOC
(OCNET Networks)
Mechanical Design Engineer, CFI/MEI, AvGeek

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 53111
    • VIRTUALI Sagl
Re: Error "unexpected keyword argument 'beep'"
« Reply #9 on: June 01, 2025, 02:40:02 am »
Again I've merged posts reporting the same error. The problem (which happened only if you turned down the Verbosity slider) is fixed by running the updater now.

Airbuspeter

  • Newbie
  • *
  • Posts: 22
Re: Error "unexpected keyword argument 'beep'"
« Reply #10 on: June 01, 2025, 09:28:05 am »
after landing and at gate i deboard. with this crash.see Text attachement

AUA9085

  • Full Member
  • ***
  • Posts: 134
    • My Youtube Profile :)
Re: Error "unexpected keyword argument 'beep'"
« Reply #11 on: June 01, 2025, 09:34:04 am »
I am seeing the same on a remote Stand during Boarding


couatl v5.0 (build 5766)
panic log started on Sun Jun  1 09:32:13 2025

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
  File ".\GSX\assistanceServices\__init__.py", line 2679, in do
  File ".\GSX\assistanceServices\__init__.py", line 4644, in showMessage
  File ".\GSX\__init__.py", line 1377, in showMessage
  File ".\common\youcontrol.py", line 185, in showMessage
  File ".\common\youcontrol.py", line 112, in showMessage
TypeError: showMessage() got an unexpected keyword argument 'beep'
{'Airport': 'LOWW', 'User Pos': (48.11440930868661, 16.57068169184834, 185.777 m, 2.84306 m, 205.96322557728988, 0.00016299017589776918, 0.001745329238474369, 0.00019506970596750567, 3.18211187210083, 1.0), 'Requested assistance services at': 'E - Parking Positions | E 49'}

ACSoft

  • Full Member
  • ***
  • Posts: 175
Re: Error "unexpected keyword argument 'beep'"
« Reply #12 on: June 01, 2025, 10:08:40 am »
I have the same problem !

See attachment

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 53111
    • VIRTUALI Sagl
Re: Error "unexpected keyword argument 'beep'"
« Reply #13 on: June 01, 2025, 10:24:15 am »
Again I've merged posts reporting the same error. The problem (which happened only if you turned down the Verbosity slider) is fixed by running the updater.

ACSoft

  • Full Member
  • ***
  • Posts: 175
Re: Error "unexpected keyword argument 'beep'"
« Reply #14 on: June 01, 2025, 11:50:00 am »
**Update**

Yes, it looks like this error was resolved with running the update tool for the most recent build.
Thanks.


A Few other issues:

1) I still see that the verbosity slider is not functional though. (All messages still appearing on screen despite the slider being in the "OFF" position)


I confirm this, problems with verbosity.

In my case, I had the bad idea to apply the OFFLINE installer, which was obviously not corrected ! So, I got the inital bug again !

I fed up with this ! So I went back to 3.5.3 using the previous OFFLINE installer. It seem to work now