ID:1013361
 
(See the best response by Tom.)
When I click ¨Play Now¨ the computer starts downloading the resources, but then the Blue Box says; ¨Connecting...¨ and I always wait more than 40 minutes and the game never loads.



WHY?!
I WANT TO PLAY!
That happens to me as well... If I let the BYOND client download the resources and it doesn't work on the next attempt, I close everything BYOND related and I try again. It usually works for me at that point.

Personally, I have no idea what causes that...
Which games would this be, and what OS are you guys on?
I use Windows XP. The only good OS on the planet! lol

(Don't flame me for using it either, I detest all other Operating Systems.)
I use XP Pro x64 as my Windows OS, so .. P:

I have got a similar issue, and have had it for a fair few versions now. My general feeling was it's an XP x64 thing, but it seems it's common to XP. Before I nail down a cause and test-case, it would probably be nice to get some input from Tom or Lummox on whether XP is still supported.
Well, if it's not... Then my time with BYOND will come to an end. I will not upgrade my OS...
Are you all using windows XP 64 bit?

Running Windows XP home edition 32 bit, I don't seem to have encountered this problem before that I recall.

At Queen of Pancakes:

Try checking your firewall settings if GenesisMagician's suggestion doesn't help. Check To make sure that BYOND.exe, Dreamseeker.exe, and Dreamdaemon.exe are not being blocked, restricted, etc.

Good luck!
I have Windows XP Pro SP3.
In response to Stephen001
Best response
Stephen001 wrote:
I use XP Pro x64 as my Windows OS, so .. P:

I have got a similar issue, and have had it for a fair few versions now. My general feeling was it's an XP x64 thing, but it seems it's common to XP. Before I nail down a cause and test-case, it would probably be nice to get some input from Tom or Lummox on whether XP is still supported.

XP should be fully supported (and Lummox JR in fact develops on XP). This sounds pretty critical, so please try to get us a test case (in particular we'd like to know in which version this started happening and whether it happens for all cases).

For me, this has happened since the 4.x client was released. I will grant that it does not happen all the time. I really don't know if it's even the clients fault, it could just be a coincidence in general based on the game(s) we try to play.

I have no evidence to back that claim though.
Once my XP x64 install is in a sane and fairly vanilla state, I'll grab you some traces of it. I'd understand though if XP x64 specifically is not supported.
Is there any way I can assist in this?
I'm not sure how useful it'd be to them, but you could run ProcMon and capture a bunch of output when accessing a game that fails to start for you.

http://technet.microsoft.com/en-us/sysinternals/ bb896645.aspx

Here's a quick how-to on it: http://blogs.msdn.com/b/dswl/archive/2010/01/10/ how-to-capture-a-process-monitor-trace.aspx
I've never used this before, so... What am I looking for? lol
You're basically looking to make a big dump file, which you can upload somewhere and share as a link here.

This video may help guide you http://www.youtube.com/watch?v=vy4kB6v97_M
In your case, I think you want to filter for dreamseeker.exe
That was my next question and I ran it. Do you want the pml file?
Yeah, if you share a link to that, then they can load that up hopefully and see the trace.
The file can be downloaded here.

http://cybergamingcorp.com/downloads.php?cat_id=3