![]() ![]() ![]() I CAN NOT connect using 192.168.0.140:20545, which should resolve to the same machine, shouldn't it? On machine 192.168.0.140 I run both server and client. It gave me the idea to test if I could connect to my own machine, not using localhost, but using its local ip and something surprising came up. That door is not 100% closed though yet, as im a software dev, not network admin. ![]() I checked through all the settings on my router to see if I had any bad port forwards or NAT no turned on etc, but I couldn't spot anything amiss. I also tried setting port to 20454 with -port but still couldn't connect to it from either machine. I tried copying the server files to it and turning firewalls off for all the computers. If I connect to localhost:20545, I can connect fine. I tried installing Connect Buttons by wondible, which allows me to type in an ip and a port. I can see its the local server I started manually and not a newly spawned server as the server in the command prompt is logging wall of text. If I Host the local server AND start up the client on the same machine using Single Player | AI Skirmish will connect fine to the local server. Server -allow-lan -headless -game-mode Config I tried running server locally with following command: I have tried a lot of things since, but havn't been able to connect and play on LAN yet.ģ machines now, to rule out 1 machine being bad: (yes pastebin for that piece of text is weird, but tell steam sends a http 403 when I try to post that here) Which will in this case connect to the server:port, fill in your own data for it, the port can be set on the server via a parameter when running it in the console Inside the console of the main menu or game listing scene you can run a command like this: Basically that is a standlone chrome-debugging tools program that connects to the PA UI. Go inside the PA directory, there is a coherent directory with a debugger. Get pamm and search within it for "connect" or similar, I forgot the exact name of the mod. If those fail for whatever reason you cant see the server.Ī simple UI mod can solve this by offering a connect to ip:port option. What PA lacks is a simple UI to do "connect to ip:port of a server" directly, the default UI relies fully on the broadcast messages of local servers and the playfab webservice server listing for online servers. PA is client-server while SupComFA is p2p. Originally posted by JR:Sup Com FA handles LAN using direct IP to the server and direct port. So how is this implemented differently in Planetary Annihilation, except that it obviously seem to use auto port and a broadcast protocol? Sup Com FA handles LAN using direct IP to the server and direct port. When using Supreme Commander FA and setting up a LAN game on 192.168.0.140, 192.168.0.141 can connect fine. local client connects fine to local server, but other PC can't see the game. I tried running server locally from command line with debug settings, but no dice. I am a software dev, so its not like tech is foreign to me - still I can't get this game to work on LAN. The host has 32 GB ram 4790k with 4 cores and 8 threads via hypert hreading, so it shouldn't be hardware problem.īoth machines can ping each other and host can ping localhost fine. They can play together fine when connecting over the internet. Making a game with host game locally checked on 192.168.0.140, makes it so 192.168.0.141 can not see the game. 2 different log in names, 2 different steam accounts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |