[T3D 1.0] - zealous attempts to connect to port 53535
by Rick Church · in Torque 3D Professional · 08/16/2009 (5:57 pm) · 5 replies
When I start Torque 3D.exe it attempts to connect to localhost port 53535. I wasn't aware of this with Beta 1-4 because my firewall blocked it and it would stop after 2 attempts.
But with B5 T3d doesn't stop. It blasts out attempts at a rate of 500 / sec and causes my atheros wifi app to jump from 0 to 50% of memory resources. Eventually it blocks all network traffic.
Other then setting my firewall rules to give t3d.exe permission to connect is there something else I need to do?
This seems to be a bug since the previous versions handled being blocked very differently.
But with B5 T3d doesn't stop. It blasts out attempts at a rate of 500 / sec and causes my atheros wifi app to jump from 0 to 50% of memory resources. Eventually it blocks all network traffic.
Other then setting my firewall rules to give t3d.exe permission to connect is there something else I need to do?
This seems to be a bug since the previous versions handled being blocked very differently.
#2
In Beta 5 I re-worked some of this to reduce the start time of the toolbox (90% of the toolbox start time was based on the order of things), it looks like there's an unintended result as to how it's operating now, thanks for sharing.
08/24/2009 (8:21 pm)
This is the Torque Toolbox... I do some basic TCP port checking to handle multiple instances to respond smartly (tell the other instance of the app to re-focus etc).In Beta 5 I re-worked some of this to reduce the start time of the toolbox (90% of the toolbox start time was based on the order of things), it looks like there's an unintended result as to how it's operating now, thanks for sharing.
#3
08/24/2009 (8:37 pm)
Hm wouldn't it be simpler to use a named mutex, which is the usual method?
#4
1) can communicate back and forth a bit, someone requested the ability to load multiple versions of the Toolbox if they are located differently, this allows me to add a feature like this
2) a single cross-platform implementation since I'm calling into an existing TCP library (Qt, which is used for all the GUI elements in the Toolbox)
Though using a basic named mutex is always a fallback. Looks like my tinkering for Beta 5 caused it to go a little crazy though.
08/24/2009 (8:50 pm)
We could, the benefits of using a simple tcp port is two-fold1) can communicate back and forth a bit, someone requested the ability to load multiple versions of the Toolbox if they are located differently, this allows me to add a feature like this
2) a single cross-platform implementation since I'm calling into an existing TCP library (Qt, which is used for all the GUI elements in the Toolbox)
Though using a basic named mutex is always a fallback. Looks like my tinkering for Beta 5 caused it to go a little crazy though.
#5
10/02/2009 (11:04 pm)
Matt, it's still a problem in T3D 1.0 
Torque 3D Owner Kenneth Holst
Default Studio Name