I tweaked the connection code today, and we also got the in game chat overlay running today, although it still needs some work.  If you'd like to try it out, follow these instructions: 1) Close Demigod if it's running 2) Download http://sd.stardock.com/impulsereactor/testchat.zip 3) Extract the files and copy them to Demigod\bin.  You may have to reboot before replacing the files if they're locked. Hit Shift+Tab to unhide the chat window.  It'll use your windows user...

Watch here and in #demigod on irc.stardock.com for updated test dlls this weekend!  This update has three changes since the version that went out with Beta 3A: 1) Increased timeout time, since it appears that some of you not in the US are having trouble with timeouts when connecting to the NAT facilitator 2) Fixed issues with special characters in overlay chat 3) Fixed a crash http://sd.stardock.com/impulsereactor/testupdate2.zip

Today's update is only to the connection code. Before certain of you go up in flames, GPG IS working on balance and other issues near and dear to your hearts.  Beta 3E is focused on the connection code, however.  If you got 0.95.033, make sure that you grab the second update from today as it fixes a problem with joining games.  As I post this, it's not up yet but it will be soon. I've spent a lot of time hammering at the connection code, plus being able to specify which ports y...

With previous versions, the connection code would randomly pick the ports to listen on.  The disadvantage of this was that you couldn't open and forward those ports manually in your router.  With Beta 3B, we included a .NET application that will let you set registry keys to specify which ports the connection code will use.  The file is ImpulseReactorOptions.exe and it needs to be run as an administrator on Vista.  Once you enable the option, you can open and forward the de...

This was mainly a connectivity update, only ImpulseReactor.dll was replaced.  + Made data packet size smaller which should help people whose routers don’t allow such large packets. The symptoms of this are losing connection to the NAT facilitator or the connection dialog showing that you are connected to someone but they are not connected to you (or vice versa) + Changed the channels some of the messages were being sent on to try to prevent one channel from getting too ...