RTTRemote Server-Client fail to connect
-
Oak,sorry for the trouble but it’s a little bit confusing the previous post about settings, at least for me…
can u pls clarify Client and Server settings?
thx in advance -
Okay, so what we do together with Subzero is
we have opened the TCP Port on both our routers,
we have excluded RTT apps from our Firewalls,
Client sets servers external IP, the same we would use if we were trying to connect on him as Host for a flight,
then we tried all possible options in server.ini and cannot connect RTT.
Saying options:
0.0.0.0
127.0.0.1
Local IPSubzero, do I forget something?
-
nop that’s all
-
Okay, so what we do together with Subzero is
we have opened the TCP Port on both our routers,
we have excluded RTT apps from our Firewalls,
Client sets servers external IP, the same we would use if we were trying to connect on him as Host for a flight,
then we tried all possible options in server.ini and cannot connect RTT.
Saying options:
0.0.0.0
127.0.0.1
Local IPSubzero, do I forget something?
Ok guys I reproduced your setup as I have 2 seperate WAN internet connections in my office and was able to get RTT working over WAN. Can you try with another port. On my router even so I would be able to setup prot forwarding on the standard port used by RTT I wasn’t able to get a connection as it’s out of the range of allowed ports for my router. I switched both client and server to port 8881 and forwared only on the server WAN 8881 to local 8881, no need for port forwading on the PC running the client. Just deleted the firewall inbound rules for RTT and let generate new ones on next RTTServer start.
Another thing that comes to my mind as I have multiple router running, some of them need a router restart after setting up port forwarding in order to be effective.
Last but not least if you were previous able to host a BMS MP on the Machine that should run the RTTServer that would mean at least the BMS and IVC portforwarding is working you could also try to connect RTT over one of the IVC ports for testing i.e 9987
On the server machine you could use wireshark to see if the request from the client machine are even comming through the router and firewall. Filter the Wireshark recording to the Raknet protocol (that’s what RTT is using)
So running wireshark even with the RTTServer not running but the client running you should see connection request over the raknet protocol on the port you have forwarded.Succesfully connected RTT client to a WAN IP Address
-
Oak, many thanks for the detailed post! We will have news tonight and report here our conclusions…
-
One question, in the Client.ini, should the Host IP be that way
xxx.xxx.xxx.xxx
or followed by the port too, like that xxx.xxx.xxx.xxx:PPPP ? -
Oak, many thanks for the detailed post! We will have news tonight and report here our conclusions…
So you know that for a backseater setup you could do way more than just extracting MFD, RWR. For Gauges you could switch to MFDE in a networked setup you could get all gauges from the cockpit with,RTT_fake_BMS all data from the server/host shared memory.
With Helios in combination with the Helios keypress sender/receiver you could even build a virtual cockpit in the client side and send inputs from the client to the host in 3d so like a full working backseat trainer with all switches -
One question, in the Client.ini, should the Host IP be that way
xxx.xxx.xxx.xxx
or followed by the port too, like that xxx.xxx.xxx.xxx:PPPP ?In the client.ini with HOSt as the WAN IP of the Machine running RTTServer
NETWORKED = 1
HOST = xxx.xxx.xxx.xxx
PORT = PPPPcheck your PM in about 5 minutes
-
SUCCESS !!!
:clap2::lalala::humble::peace::bowd:
-
SUCCESS !!!
:clap2::lalala::humble::peace::bowd:
So only to my RTTserver? Or did you manage to get your setup working as well?
-
So you know that for a backseater setup you could do way more than just extracting MFD, RWR. For Gauges you could switch to MFDE in a networked setup you could get all gauges from the cockpit with,RTT_fake_BMS all data from the server/host shared memory.
With Helios in combination with the Helios keypress sender/receiver you could even build a virtual cockpit in the client side and send inputs from the client to the host in 3d so like a full working backseat trainer with all switchesMan, you are way ahead! We have been wondering if it is possible to send inputs from the back to the front seat!
We are heading directly to Helios ASAP!Oak, many many thanks! Me and my team, we are really GRATEFUL for you invaluable help!
-
No, not yet, but since we had a good connection together and RTTRemote works fine, we will sort it out in between us too.
We will post again later on for that result. -
Oak, everything works perfect! We only had a permanent freeze after about one hour of flight, but that is another issue.
Many thanks again for the great help!
-
Oak, everything works perfect! We only had a permanent freeze after about one hour of flight, but that is another issue.
Many thanks again for the great help!
The freeze is a known BMS bug and according to devs already fixed for U1. It affecting any tool that uses SharedTexturedMemory so regardless if RTT, MFDE, Helios, YAME. My personal experience the “heavier” the mission the less likely the freeze.
If i fly a SP TE with only one jet the freeze is most likely within the fiirst few minutes. I have flown all our UOAF ssaturday events with 20-30 human pilots in 4.35 multiplayer with KTO Bear Trap day one Campaign without a single texture freeze so far