Slitherine

batesmotel wrote:There is an ancillary program (fog.exe I think) that is run when you are doing multi-player. I've found that times when I have had problems connecting to the server that I often have two copies of this running in Task Manager. If I then stop the FieldofGlory.exe process and all the fog.exe processes, then I'm normally able to connect again. Just a thought.

Chris

Yep I'm aware of that one. It's fognet.exe - if I have problems connecting - I'll usually manually close it in the task manager and then restart the computer altogether. That doesn't help for this problem though. Thanks for the suggestion however!

Well I'm back in business again.

I know that there's got to be something I'm doing that's causing this problem or conflict with Field of Glory, I just wish I knew what it was.

(Kudos btw to the developers. I was a big fan of DBAOnline back when it was really strong, and I'm enjoying FOG PC just as much if not more than DBAOnline. Which is a lot coming from me since usually I play a lot more DBA TT games vs. Field of Glory games due to the time investment required.)

Are there multiple machines connected to your NAT? Once you are working, does it matter if you then reboot and go straight into FoG as to whether it works or not?

Just trying to narrow down the issue!

Cheers

Pip

pipfromslitherine wrote:Are there multiple machines connected to your NAT? Once you are working, does it matter if you then reboot and go straight into FoG as to whether it works or not?

Just trying to narrow down the issue!

Cheers

Pip

2 computers total (one Vista/one Windows 7) and a Wifi printer. And it doesn't matter if I reboot. It seems that after its working, I get no problems for at least a few hours (sometimes days). Then all of a sudden it pops up again with the launching client window and keeps me off for a few hours (or a day). The longest I've gone without being able to connect has been around a day and a half.

I have also went the route (when I began have problems), to completely bypass my wifi router altogether and go with a direct connection from the cable modem to my computer and that didn't affect the results of whether or not I could connect or not.

Still getting the same problem again tonight. One thing that I'm noticing is that it seems to be happening mostly after my computer is turned off for extended periods of time. If the computer is just in a sleep mode or hybernate mode, there seems to be no issue after start up. But if the computer is shut down entirely (and shut down for a while), it seems to have the problem and will continue to have a problem for what what seems to be a random amount of time. I've went ahead and tried to do a few things as a test - I've disable the UAC, ran the program without a firewall (both the Comodo one I use and Windows firewall), and disabled the on access defender/anti-virus programs. Any other suggestions about stuff I may be missing? Any other programs to check for permission access maybe?

Well I got it working on my Windows 7 laptop and have no issues over there -- so until i can figure what it is I've got going on the Windows Vista PC, I'll be playing Field of Glory on Windows 7. Thanks for the Slitherine team for taking their time for helping me out with trying to work out this issue since I know for sure its something that I've done or set up on my PC that's screwing with the program and not something with the game itself. I just wish I knew what it was that I'm doing that's conflicting with it.

Okay, so I noticed something odd today (I'm stubborn and don't like giving up), and realized that I was getting an error message via a text file being updated whenever I try to run the program and the client hangs ups on the launching client screen. It says "KERNEL MEMORY CHECKING IS **OFF**".

This text files (which just reads error.txt) is created in my Field of Glory program files directory at the same level that the fognet.exe and fog.exe files are found.

I know that this can be a pretty big error (Kernel Memory that is), but maybe this could help as a starting point to offer some suggestions as to where the problem may be found? I just verified it again and every time that the client hangs up on that screen, this log is updated with the same error. Is this related to the Client not launching (seems like it may be?) or is this a non-related error?

It's not related. It's just some debug output from the game launcher that you first see.

Cheers

Pip

One thing that I'm noticing is that it seems to be happening mostly after my computer is turned off for extended periods of time. If the computer is just in a sleep mode or hybernate mode, there seems to be no issue after start up. But if the computer is shut down entirely (and shut down for a while), it seems to have the problem and will continue to have a problem for what what seems to be a random amount of time

I have noticed the same thing

Stefan2009 wrote:One thing that I'm noticing is that it seems to be happening mostly after my computer is turned off for extended periods of time. If the computer is just in a sleep mode or hybernate mode, there seems to be no issue after start up. But if the computer is shut down entirely (and shut down for a while), it seems to have the problem and will continue to have a problem for what what seems to be a random amount of time

I have noticed the same thing

One thing it probably worth doing if you aren't would be to get out of multi-player mode before your computer sleeps/hibernates. That way the game won't be left in a confusing state where the connection timed out while the computer was down.

Chris

This does make me think it might be a problem with the IP leasing or something like that causing a timeout internally. We are trying to work through the possible causes.

Cheers

Pip

pipfromslitherine wrote:This does make me think it might be a problem with the IP leasing or something like that causing a timeout internally. We are trying to work through the possible causes.

Cheers

Pip

Just as an FYI, after the issue that I had where I began to make the connection that it was only occurring when I shut down the computer rather than let the computer hybernate/go into sleep, I kept my Windows Vista computer on non-stop after FOG began to randomly work again, letting it go into sleep as opposed to shut downs and only bringing it up again to play turns. I had no issues at all connecting to the server, it allowed me in every single time (which was pretty frequently over the last two days) -- this was the single longest length of time I've had the program working in multiplayer without issues. I got home tonight and after playing a couple of turns back and forth I decided to do a quick experiment. I restarted my computer (allowing it to shut down all the way and stay off for a few minutes). When the system came back up I launched into FOG and tried to start up multiplayer and the Launching Client message popped up and hung there pretty much like clockwork. It does seem to be something related to the powering off/on thing that is causing issues.

Just thought you guys would be interested to know and I'm glad to hear you are looking at some possible sources for conflicts/problems.

The game worked perfectly for 3 full days ( new record ) never shut the pc down just on sleep mod, but today the problem was back, this is getting VERY frustrating!

Stefan2009 wrote:The game worked perfectly for 3 full days ( new record ) never shut the pc down just on sleep mod, but today the problem was back, this is getting VERY frustrating!

Maybe we can see what we may have in common...

What antivirus/firewall are you running? And are you using Windows Vista 32 bit?

Windows Vista 64bit Intel core 2 Quad Q9300 2.5GHz
Geforce 9800GT
Norton Anti Virus Windows Defender Windows Firewall

I have made no changes to anything, still sometimes it works perfectly and sometimes ( most of the time ) not at all. The thing i find most strange is that the cancel button dont work, if it was a problem connecting to fognet.exe the cancel button should still work! because that has nothing to do with connecting to fognet.exe! It would be nice to see if more people have the same problem, please everybody who has or have had any problem connecting respond and let us know how/if you solved the problem!. I run several other programs online and have no problem at all with them.

Thanks for responding..started to feel lonly with this problem.

Anders Sweden

Please can everyone who has the issue where the game gets stuck at "launching client" update to version 1.2.5, and try multiplayer again.

We've made some changes that will hopefully fix this issue, at least for some people.

If it still doesn't work, please post again, describing what happens and specifically mentioning that you were in version 1.2.5.

Thanks

EricS wrote:Please can everyone who has the issue where the game gets stuck at "launching client" update to version 1.2.5, and try multiplayer again.

We've made some changes that will hopefully fix this issue, at least for some people.

If it still doesn't work, please post again, describing what happens and specifically mentioning that you were in version 1.2.5.

Thanks

Restarted my computer after downloading the patch and it launched into the multiplayer without an issue at all. This is the first time after restarting my computer that it didn't get hung up for a while now. Whatever you did seems to have solved my problem.

Thanks!