So we don't have a specific hardware issue. If I instead turn Bridge B into the server, then Bridge A as Intrepid displays the same behavior. I have two identical bridge setups and if Bridge A is the server, Bridge B running the Intrepid as the issue.
It's like the datastream is getting clogged up along the pathway of secondary bridge to server back to main screen. Using the Saitek X52 Pro on any secondary ship creates what appears to be positional lag on the Main Screen for that ship and a SEVERELY reduced capability to ascend/descend. I had mentioned this after my last convention but this past weekend's convention allowed me to narrow things down a bit. View Member Profile Send Email Find Member's Topics Find Member's Posts mmesich
0 kommentar(er)
