DT Intervals (effects on client and server data streams)

[flight1973]

Setting DT definitely affects the update rate for sending data from a BlueSky server to connected BlueSky clients, but does it also alter upstream messaging rates? That is, does setting DT affect the rate at which clients can send commands on the stack to a BlueSky server?

I am sending many ADDWPT instructions to a simulated aircraft on a server that is set to DT 1. I observed that each individual ADDWPT command was being processed at one second intervals. Is this expected behavior?

[jooste]

Hi @flight1973,

You are right. In the current implementation, network I/O is performed once every base time-step, so if you set this to a large value on the simulation side it will not check for incoming messages very often. However, if multiple messages are queued it should get them all at once, so if you send multiple commands within one second they should all be received and processed in the same time-step. Do you have a minimum working example that shows the problematic behaviour?