I am running a billion 7401 adsl router with 5.71 firmware (I think thats the most recent)

I am using Internode as an ISP.

Ive passed all the checks listed above. Verified with the port checker program.

serverproxy isnt an option since im in australia.

I have put my logs and screenshots into my webspace, and you can access it here...

http://www.users.on.net/~vladesch/demigod/

Here is a screenshot of my connecton window for the first log.

and its associated log is here..

http://www.users.on.net/~vladesch/demigod/dump1.log

Note that I only experience these problems when trying to connect to US (or further) games. Australian games always work perfectly.

Not that that is a solution, because there arnt many australian games, and my ping to the USA is fine if can get past the connecting stage.

Heres another (very next game)

I actually got into the lobby this time, but aother player was stuck not being able to connect

http://www.users.on.net/~vladesch/demigod/dump2.log

Heres another... couldnt even get into the lobby

http://www.users.on.net/~vladesch/demigod/dump3.log

(It's the second game I tried to join in this log)

That's probably enough examples. Good luck, hope you find the problem.

Still having the issues above - have donwloaded software from port forward.com and my UDP ports are open as required.

It's been days since I posted in here and around the same since I even created a tech support ticket with my information. Where's the help? Even a small update on the status would be nice.

Quote for truth.

Stardock created this 'We are here to help' thread to appear as if they are helping, but its been so long and not even a reply from a mod/dev here to show that they are even READING this thread.

I've followed all the steps, and i'm still having issues.

#1 My ISP is iinet, based in Australia. URL: http://www.iinet.net.au

#2 My Router is a Belkin N1 Wireless router.

#3 ADSL 2+

#4 Follow the link: http://paste-it.net/public/zaba0a5/

#5 I have exactly the same problem as aqualeris, and i too have never made it to an online lobby. Perhaps the addition of my log may help.

Most of you appear to be ADSL users. If you've got high bandwidth DSL which achieves its speed by the use of multiple connections, that is the most likely source of issues. I've heard some good things about our progress with people who have multiple IPs though, so hopefully that will be resolved soon.

Many of your logs also show some players connecting through symmetric NAT routers which may be causing problems in the overall connection process as well. Of those posting though only Tokubetsu appears to have one himself, though. Archaic Dhaos might also but it's not as obvious from the log.

Those complaining of poor pings, please post a speedtest.net report.

I cleaned the thread up on Friday so it'd actually be readable for someone to address (I'm not the most qualified to try and interpret the logs myself). Our offices are closed over weekends, though.

Im doing the opposite of the not so usefull "where is the responce" posts. 

I agree I wish things would be better quicker.  While the game works ok for me (my only issue is my limited upload speed, a bit to slow for 5v5).   Its only been a about a week since the topic was opened, and I am sure htye are working on it.  Sometimes things take a bit of time. 

I really hope things improve for all players soon, so the community grows.  That way finding a match will be quicker simply by the sheer volume of people palying.

Many users in Australia are on ADSL - cable is the only other choice not counting wireless options.

I still haven't been able to work out if my modem is using symetrical nat or not.

What I DO know is I was able to get into the setup screen with a european guy for 5 seconds (I quit out as i was testing while looking for an australian game), but a number of other games would not get that far...

vladesch: judging by what was happening to you (you were stuck as connecting to another player, but in their connection list you showed up as fully connected to them) - i have a very good feeling that your problems will be solved by the next update. keep us up to date on how it does for you, it should be out in the next day or two at most

Thanks for that. Highly appreciate it. Previously the thread was unreadable due to the chunk of logs clogging up the page.

I'll just patiently wait this out this time round. No more tantrums. Kewl.

Played a game with some USA players and connected to a couple of USA lobbies and it worked perfectly so far. Will update this post as I play more.

Finally got a game working - had to change some ports around AFTER the patch (worked it out once disabled firewall FINALLY worked!!!!)

The new patch should have solved all the 'waiting to connect' and 'attempting to connect' issues. No need for portforwarding, serverproxy, disabling firewalls whatsoever. The new patch works right out of the box! (out of the internet, w/e)

I still have very high ping spikes in anything greater than 2v2, despite having a good internet connection. Tried forcing proxies, but no luck. Should i upload the .log file, after exiting a match in which i've spiked? Would it help? I don't crash or anything, i connect to everyone, just these damn spikes i have.

Still can't connect =/

1. DONE

2. DONE

3. Have you tried the parameter /serverproxyonly in the Demigod shortcut as a parameter? This will have us host your connection for you. - I DONT UNDERSTAND HOW TO DO THIS

4. DONE

Now, if you are still having problems, let's walk through what we need:

#1 Who is your Internet Service Provider (ISP)? - INVITEL - (HUNGARY, EUROPE)

#2 What brand and make of router are you using?  BELKIN WIRELESS G - F5D-7230

#3 What kind of connection do you have? ADSL

#4 :

[06-12-2009 18:46:52 620] Setting App Directory: C:\Program Files (x86)\Stardock Games\Demigod\bin\
[06-12-2009 18:46:52 620] loading file C:\Program Files (x86)\Stardock Games\Demigod\bin\ImpulseReactor.xml
[06-12-2009 18:46:53 079] CVPIsAppUpdateRequired
Installed version: 1.01.106
Latest version: 1.01.106 (server 1, beta 0)
[06-12-2009 18:46:54 014] GetPlayerDataByID: 0 not found
[06-12-2009 18:47:02 745] GetPlayerDataByID: 0 not found
[06-12-2009 18:47:15 482] GetPlayerDataByID: 0 not found

#5: i did have one or two decent games with ok connectivity, but then all the ping problems began. well it's just that i get low pings.  my internet connection is just fine. i tried to follow the steps that are on the beginning of the post, and then suddently i began to get runtime errors and hangs while in the game lobby. the game also didnt accept my username and password acouple of times. also while in the game lobby, I get a message that the host left the game, but he hasnt.

anyway - the biggest problem is the connectivity

Create a shortcut to demigod.exe and in the properties for it (right click and select properties) add the following to the end of the Target field:

/serverproxyonly

make sure to include a space between it and the existing text in the field.  Once you do this, try playing Demigod again.

Inconsistent and incomplete (and therefore, inaccurate) information about port setup for this game turned a few minutes of configuration/setup/testing into a couple of hours of wondering what went wrong.  I'd bet if you can fix this non-technical issue, you'd help a fair number of people.  It definitely would have helped me.

The issue:

..\Demigod\bin\DemigodManual.pdf states ports 6100 to 6200 should be opened.  It refers specifically - and only - to UDP traffic.

..\Demigod\readme.txt does not mention a port range.  It does mention you won't be able to connect if you're blocking TCP or UDP packets.  It also points out the existence of ImpulseReactorOptions.exe.  Traditionally, though I find this has become less true as the years go by, readme.txt files include newer and more-up-to-date information than the game manual.  So I dove straight over to ImpulseReactorOptions.exe and found...

..\Demigod\bin\ImpulseReactorOptions.exe UI text indicates ports > 6001 should be opened, with a range of at least 20.  The Use Default ports option actually sets the values to be 6112 - 6132.  It refers specifically - and only - to UDP traffic.

This topic introduces a fourth set of recommended parameters: ports 6112 to 6200 need to be opened in point #2, but does not explicitly mention either UDP or TCP (or both) as being the required protocols.  One might infer from Point 3 that UDP traffic is what we need to forward.

Within this topic, one user comment specifically states opening 6073 along with 6100 through 6200.  I have no idea where 6073 comes from, and I don't want to know.

What I think should happen:

Document which ports or ranges of ports, along with stating clearly which protocol(s) are required.  Get the word out.  Don't get ham-fisted with port ranges either please.  Does the game really need ONE HUNDRED TCP and/or UDP ports opened/half-opened/listening?  If not, please play nice there - there are already a few apps/games on my system wanting to use one or more ports in that range.  I'd like to minimize the potential for conflicts and confusion if possible.

If documentation is incorrect or incomplete (I think it is), please update it in a patch.  This goes for the PDF for digital downloaders, as well as the readme.txt.  And this topic thread.  ImpulseReactorOptions.exe should be updated with accurate and complete information as well, but I don't believe editing a string and recompiling is going to harm baby seals, so I say go for it.

What could have been 10 minutes turned into a 2 hour read/search/read more/test/resolve cycle.  And another 20 to get my thoughts in order for this post - so I hope it leads towards some benefit.

Seconded - I spent ages trying to get my ports working. Turns out the issue was there end as the code wouldn't work on my router/modem until after the patch, but I still spent ages trying to work out the right combination...

How about a program that diagnoses the connection issue and walks you through steps to get it setup???

It's been almost two weeks and my eticket is still open and I still can't play.

Please, someone from SD or GPG have a look on this thread, from post #88 until the end: http://forums.demigodthegame.com/352593/page/4/#2262630

I've checked my connection with a packet sniffer and tracert to all players in a 4v4 game that i've had spikes. I posted all the results there. Also someone from there, with the same problem as me, said he can play SupCom in 4v4 matches just fine, but he can't play DG without spikes...And afaik, DG and SupCom share the netcode, so maybe this could be a clue for you.

I've done steps 1 thru 4 including completely uninstalling all anti-virus/firewalls (includes AVG and Avast), I tried putting my PC into the router DMZ, buying a new modem, and upgrading my ISP service.  See Dead Ghosts post at http://forums.demigodthegame.com/352593 for everything I've tried (and I do mean everything).

My ISP is Cox Cable.  I have 10Mb/s (avg of 11Mb/s) down and 2Mb/s (avg of 3Mb/s) up.  My router is a NetGear Wireless-N Router (WNR834B v2).  I'm currently using a brand new SB6120 cable modem although I've tried with others.

My problem is Multiplayer is very, very, very (x10) laggy.  It studders so bad even in 2v2 it is unplayable and I have to leave (if the others haven't left already).  In the lobby everything is fine -ping is green and fine - i can connect to everyone no problem. But after the long wait into the arena thats when it gets unplayable.  It started off showing that my latency (in the Tab window) kept spiking every 3-10 seconds from <150 to >1000 at times.  One of the things I've tried was the /serverproxyonly fix but that didn't seem to help at all; the gameplay just studders constantly and every few seconds the lag-out counter starts counting until everyone tells me to get lost.  What I just recently noticed that while the problem hasn't gotten any better, my lag in the Tab window (from when I can see it) doesn't actually jump to > 1000ms anymore but I think that might be because of the proxy.  I've tried very many times to play and tried very many things to fix it but haven't been able to play 1 good game.

The most recent thing I've done to troubleshoot the issue was to monitor UDP packets with WireShark when I play DG; the results were interesting.  I noticed that everytime the game freezes at the lag count-down window, it shows a streak of either me sending UDP packets UP to (what I guess is the proxy server) at 74.204.71.152 (to a port like 64881 but varies) but not getting any UDP packets DOWN (to my port 6112) OR vice versa.  The streaks of 1-sided transmissions can last for hunderds of packets at a time with no reciprication for up to 5 or 6 seconds.  The times of the long 1-sided streaks coorelate exactly to when the lag-out counter window pops up and the time of the smaller streaks seem to be when my game is studdering.  Good game play seems to show up as a nice 1, 2 or 3 back-and-forths of packets to and from the server (which is not often).  Much more of a 1-sided streak longer than that is when the game studders.  

Both my ImpulseReactor.log and that packet log is here:  http://www.mediafire.com/?sharekey=467f2a767588a20a8d78a0e555291609e04e75f6e8ebb871

Also, at the same time I'm pinging www.google.com.  Whenever the multi-player game freezes, the ping response is (Request Timed Out) otherwise its good (~18ms).  This seems to be ICMP de-prioritization from my router (putting my ping requests on hold while it tries to deal with DG's packets).

Sorry if this is info overload!  Any help is appreciated!!  

I just bought the game today for digita download and i can't connect to any online games whatsoever.  I get a cannot connect to NAT servers or something.  I can see games in the lobby, and when i'm trying to connect i see how many people are in the waiting room, but I always get that message.  I haven't successfully connected to a game yet.

1) done

2) done - firewalls are all disabled

3) Done

4) Done - same as #2

1) Shaw Cable

2) D-Link

3) Cable Modem

4) http://www.paste-it.net/public/r8c2f2a/

5) When trying to connect to any type of game, or when trying to host a game, I get the message 'cannot connect to NAT Facilitator. Try again later'.