For the record, I do :NicoDE a écrit :I tell the game about my "router" by generating a GS.bin with a custom tool.
ifconfig eth0 add 207.212.235.17
Which redirects pod requests to my local server.
For the record, I do :NicoDE a écrit :I tell the game about my "router" by generating a GS.bin with a custom tool.
Welcome to the clubDfg a écrit :Interest : high , spare time : low. :-)
I'm open for any advices and templates.Dfg a écrit :I'm fairly experienced in linux development [...]
Many thanks for the hint.Dfg a écrit :For the record, I do :
ifconfig eth0 add 207.212.235.17
I'm always interested in more information about the protocol, though I don't have precise questions right now.NicoDE a écrit :Are there any open questions regarding the library/protocol that I should try to answer first?
Else I would continue to work on the third connection component (the library reconnects to the IP/port returned in the CreateSession/JoinSession reply - like the ConnectionRequest to a server(arena)).
Code : Tout sélectionner
UserName
Password
1
UBI SF
UBI SF
207.212.235.17
18723
Sounds good. Is there anything I can help you with?Dfg a écrit :I had some time to work on the router / server (I'd like to keep with one program for both the server and router) and things are progressing.
It is created/rewritten in the game directory when POD receives a reply to the GetRouterList message.Dfg a écrit :What is exactly the gs.bin file ?
You're the one !NicoDE a écrit :Maybe I should try to fix the performance (input lag) issues first
(I'm currently implementing a "V-Sync" loop to give POD more time to handle input events)