ok, lets try this. in both of those same two procs, replace:
    client << browse({"
<script>
window.location.href="?asset_cache_confirm_arrival=
[job]"
</script>
"}
, "window=asset_cache_browser")

with:
    client << browse({"
<script>
setTimeout("window.location.href='?asset_cache_confirm_arrival=
[job]';", 100);
</script>
"}
, "window=asset_cache_browser")

and for shits and giggles, you can also try replacing them with:
    client << browse({"
<meta http-equiv="refresh" content="0; url="?asset_cache_confirm_arrival=
[job]" />
"}
, "window=asset_cache_browser")
MrStonedOne wrote:
ok, lets try this. in both of those same two procs, replace:
>   client << browse({"
> <script>
> window.location.href="?asset_cache_confirm_arrival=
[job]"
> </script>
> "}
, "window=asset_cache_browser")
>

with:
>   client << browse({"
> <script>
> setTimeout("window.location.href='?asset_cache_confirm_arrival=
[job]';", 100);
> </script>
> "}
, "window=asset_cache_browser")
>


Took a long while to load and I got the Great Wall of Red Text again. Still freezing, but I think the clock is a bit more responsive every few times the freezes cease for just a half second. http://puu.sh/sNEhO/b930b75802.png

I'll test your gits and shiggles one in a bit.

MrStonedOne wrote:
and for shits and giggles, you can also try replacing them with:
>   client << browse({"
> <meta http-equiv="refresh" content="0; url="?asset_cache_confirm_arrival=
[job]" />
> "}
, "window=asset_cache_browser")
>

Same story, freeze, red wall of text. Just as I tested this, my other server, the one I tested the other code on, got its tish together and counted down to the start of the round normally, but it took 9 minutes or so, as usual...

When I reset my para code, I don't get the red wall of text. I just get this: http://puu.sh/sNF2S/b13fb02c57.png

This is really ticking me off... Do you have any other solution?
I'm not seeing what's wrong with that last image.
(Not Responding) is probably a clue.
I HAVE FOUND A SOLUTION!

CCleaner cleaned the registry and some other things and now, for some reason, SS13 is working like it has never worked before.

So fast. Much love.

I just got the program today and--well--anyone who has this problem, I suggest you give CCleaner a try. My computer, in general, is much faster, too...
In response to Puckaboo2
Puckaboo2 wrote:
I HAVE FOUND A SOLUTION!

CCleaner cleaned the registry and some other things and now, for some reason, SS13 is working like it has never worked before.

So fast. Much love.

I just got the program today and--well--anyone who has this problem, I suggest you give CCleaner a try. My computer, in general, is much faster, too...

Awesome. I bet there was something interfering with the browser that was hard to catch. I'm so glad you found a solution at last. Thanks for letting us know.
I'm so happy I can has spessmen back. I appreciate the help you and MSO have given me and I hope this thread helps other people, too. Feel free to lock this, if you want.
Page: 1 2 3