Jump to content

Speech error


Recommended Posts

2023-05-27 11:09:44.620 ALERT   WRADIO (Main): Error in wMessage::buildSpeech(), event = wMsgATCYouAreClearedForTO: [string "./Scripts/Speech/common.lua"]:674: assertion failed!
stack traceback:
    [C]: ?
    [C]: in function 'assert'
    [string "./Scripts/Speech/common.lua"]:674: in function 'make'
    [string "./Scripts/Speech/common.lua"]:1009: in function 'make'
    [string "./Scripts/Speech/common.lua"]:1552: in function 'make'
    [string "./Scripts/Speech/common.lua"]:3197: in function 'make'
    [string "Scripts/Speech/speech.lua"]:151: in function <[string "Scripts/Speech/speech.lua"]:130>

This error message suddenly popped up in the dcs.log yesterday causing some other issues. What changed yesterday ?

Link to comment
Share on other sites

20 hours ago, Chesster said:

2023-05-27 11:09:44.620 ALERT   WRADIO (Main): Error in wMessage::buildSpeech(), event = wMsgATCYouAreClearedForTO: [string "./Scripts/Speech/common.lua"]:674: assertion failed!
stack traceback:
    [C]: ?
    [C]: in function 'assert'
    [string "./Scripts/Speech/common.lua"]:674: in function 'make'
    [string "./Scripts/Speech/common.lua"]:1009: in function 'make'
    [string "./Scripts/Speech/common.lua"]:1552: in function 'make'
    [string "./Scripts/Speech/common.lua"]:3197: in function 'make'
    [string "Scripts/Speech/speech.lua"]:151: in function <[string "Scripts/Speech/speech.lua"]:130>

This error message suddenly popped up in the dcs.log yesterday causing some other issues. What changed yesterday ?

it looks like it's related to the VAICOM add-on? isn't it?
As far as I know, nothing changed yesterday, maybe you've just got on a mission where the new callsign are used, and they are not yet supported in VAICOM.

FlighRIG => CPU: RyZen 5900x | RAM: 64GB Corsair 3000Mhz | GPU: nVIDIA RTX 4090 FE | OS Storage: SSD NVMe Samsung 850 Pro 512GB, DCS Storage: SSD NVMe Sabrent 1TB | Device: Multipurpose-UFC, VirPil T-50, TM WARTHOG Throttle, TrackHat, MFD Cougar with screen.

Our Servers => [ITA] Banshee | Krasnodar - PvE | PersianConquest PvE Live Map&Stats | Syria Liberation PvE Conquest

Support us on twitch subscribing with amazon prime account linked, it's free!

Link to comment
Share on other sites

On 5/27/2023 at 12:33 PM, Chesster said:

2023-05-27 11:09:44.620 ALERT   WRADIO (Main): Error in wMessage::buildSpeech(), event = wMsgATCYouAreClearedForTO: [string "./Scripts/Speech/common.lua"]:674: assertion failed!
stack traceback:
    [C]: ?
    [C]: in function 'assert'
    [string "./Scripts/Speech/common.lua"]:674: in function 'make'
    [string "./Scripts/Speech/common.lua"]:1009: in function 'make'
    [string "./Scripts/Speech/common.lua"]:1552: in function 'make'
    [string "./Scripts/Speech/common.lua"]:3197: in function 'make'
    [string "Scripts/Speech/speech.lua"]:151: in function <[string "Scripts/Speech/speech.lua"]:130>

This error message suddenly popped up in the dcs.log yesterday causing some other issues. What changed yesterday ?

These errors are just part of the DCS Server hosting experience, you would think ED would look at the dcs.log file and maybe fix what is broken .............. but here we are

I have seen these errors in my dcs.log on my server for a very long time (I think it is related to ATC messages when players are contacting the tower etc)


Edited by HC_Official

No more pre-orders

Click here for tutorials for using Virpil Hardware and Software

 

Click here for Virpil Flight equipment dimensions and pictures.

.

Link to comment
Share on other sites

4 hours ago, HC_Official said:

These errors are just part of the DCS Server hosting experience, you would think ED would look at the dcs.log file and maybe fix what is broken .............. but here we are

I have seen these errors in my dcs.log on my server for a very long time (I think it is related to ATC messages when players are contacting the tower etc)

 

checking the old log history I have some of them, but just in the instances that is running the "newest" mission, so I guess it's related to some recent added callsign, but not related to VAICOM, but just to the core server itself, so probably yes something related to the ATC when try to use new callsign.

FlighRIG => CPU: RyZen 5900x | RAM: 64GB Corsair 3000Mhz | GPU: nVIDIA RTX 4090 FE | OS Storage: SSD NVMe Samsung 850 Pro 512GB, DCS Storage: SSD NVMe Sabrent 1TB | Device: Multipurpose-UFC, VirPil T-50, TM WARTHOG Throttle, TrackHat, MFD Cougar with screen.

Our Servers => [ITA] Banshee | Krasnodar - PvE | PersianConquest PvE Live Map&Stats | Syria Liberation PvE Conquest

Support us on twitch subscribing with amazon prime account linked, it's free!

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...