Also if you didn't update with the full installer, I recommend using that. It makes sure that DirectX is properly setup on your system to support the new features.

I used the full installer when installing.

Wait, this also confuses me.

everytime I attempt to open Dream Seeker in the webclient

Dream Seeker and the webclient are entirely different entities. Do you simply mean that you're trying to open DS from the site?

Also, does this happen only with one game, or with multiple games? What games have you tried?

I need to know if the other 509 builds have the same issue for you. Please download some of those and test. Try 509.1314 first, then try some earlier ones if it still has the issue. I need to know where the problem first occurred.

Also try these games; they work for me so they ought to work for you too.

byond://LummoxJR.Runt##local
byond://Gazoot.Quickstep##local

DevDuelist wrote:

I downgrade twice before the problem stopped. I stopped at 509.1315

I don't understand; 1315 is the current build.

There's no change in 1314 that could explain what you're seeing. The only change that could even run client-side is a minor one to the .dms parser, which doesn't come into play in earlier games and also doesn't appear to have any potential for an infinite loop.

If you go back to 1314, does the problem return?

Okay, I'll probably need a little specialized help here, since I can't seen this issue for myself and there's nothing in the code that explains this change. Since I want to fix this immediately if there's an infinite loop issue, here's what I need for you to do:

1) Install a debugger. The Windows debugging tools are a decent choice.
2) Run Dream Seeker in 1314 like you've been trying to do.
3) Once Dream Seeker hangs, attach the debugger to dreamseeker.exe, and then pause execution.

Before that, though, I have some followup questions. I did see a change in 1313 itself that might explain an issue if you have some weird security software running--and it's vaguely possible that the change actually went into 1314 instead of 1313 as planned. (The dates don't tell me enough to be sure.) That could only happen, though, if you're trying to join a game remotely or installed locally, not if you're trying to run a game directly from Dream Maker.

- Were you in fact launching Dream Seeker from Dream Maker, as in hitting Ctrl+R on a project of your own? Or, were you only trying to launch from the site? The original post is very confused on this point.

- What security software and/or firewalls do you have installed? What happens if you disable it temporarily?

The results I'm seeing on the webserver are consistent with the change I'm thinking of not having gone into 1313 as intended, and some kind of security software freaking out over the change. For clarity, the change I'm referring to is one that altered the ad serving URL so that I can, in the future, add functionality to allow hub owners, server admins, hosts, etc. to prepay to skip ads.

The reason I asked about Dream Maker is that if you're writing a project and hit Ctrl+R, that should never attempt to launch an ad or the "Your game will begin shortly" box.

Do you have any security software besides Avast? And I'm referring specifically to something like Avast's web shield, not the antivirus, so you'd want to make sure you disabled the right thing.

Something is really fishy, because no one else has reported a problem with 509.1314 like that, and the only possible culprit is that code change. All that change is doing is adding to a URL query string, and I have ample evidence that that's working for other people--yet I don't see a single request matching it for you.

I assume you were using 508.1299 before you initially upgraded, yes?

My best advice at this point would be to try the steps I outlined above for getting a debugger attached to dreamseeker.exe while it's hanging. What I basically need there is, once you can pause the execution where it's hanging, for you to go back in the stack until you end up in dreamseeker.exe or byondcore.dll or what have you, and take some screen shots of what the debugger shows you at those points--such as the assembly code. That would be an enormous help for me to track down the issue.