Descriptive Problem Summary:
When people play on my game (http://byond.com/games/rushnut/reo2dn), if they close the game, it removes it from the games at the bottem, but when the game reboots, the game restarts up for some reason.
Numbered Steps to Reproduce Problem:
Join my game (byond://92.12.37.98:3061)
Close it, sometimes it does actually close, so it might be somthing to do with the players computer.
Then ill reboot and it will reopen dream seeker
Expected Results:
Game closes
Actual Results:
Game restarts
Does the problem occur:
Every time? Or how often?
Most of the times to people who it actually happens to, never to anyone else
In other games?
No
In other user accounts?
Didnt test
On other computers?
Didnt test
When does the problem NOT occur?
Well, i dont really know, it just sometimes doesnt happen
Workarounds:
None i know of
ID:67610
 May 4 2009, 6:03 am
|
|||||||||||
| |||||||||||
|
May 6 2009, 4:09 pm
|
|
Volcomkewl
 |
hmm, it closed out fine for me I have a dekstop Dell Xp Home edition maybe its just vista doing it. Vista has some problems with byond.
|
Volcomkewl wrote:
hmm, it closed out fine for me I have a dekstop Dell Xp Home edition maybe its just vista doing it. Vista has some problems with byond. Were you on my server? Because it seems to only effect me, and it also seems to only effect players and not the host By me, i mean my server | |
I've never seen it happen, but I think I have an understanding of how it could happen, but the timing would have to be pretty good.
When you close a Dream Seeker, the program itself isn't automatically closed, merely hidden. Dream Seeker needs to contact the hub and notify it of it's impeding closure. Prior to 430 (I think), a number of users were reporting abnormally large closing times of up to and including one minute (we'd click the X and the program wouldn't shut down for a while). To rectify this, the appearance of a shutdown was provided, so the program could gracefully shutdown in the background. So in theory, if a hidden DS in the middle of it's shutdown procedure, suddenly up and received a reboot message, it could override the shutdown and cause Dream Seeker to refresh, thus reappear. Producing the same symptoms as your bug report. Unfortunately, I can't mark bug reports as plausible. So I'm just going to leave it alone, but there is a possible explanation for you. It'd take Tom or Lummox to verify that scenario is what's happening, or something else entirely. | |
Tiberath wrote:
I've never seen it happen, but I think I have an understanding of how it could happen, but the timing would have to be pretty good. This sounds alot like it, As i recently found that it DOESNT close, It simply is hidden and is still open in task manager. This is a problem as it doesnt close, ever. Meaning I'm often left with 5-7 different Dream Seekers or Dream Maker's open. This is both problematic and begins to clog up my computer without regular checks =/ edit: I tested on an older copy of BYOND, (428 I think) And the problem never occurred... | |
So you're actually having issues with invisible Dream Seeker instances? And you're sure they don't go away after a certain amount of time?
IIRC, Lummox once made mention to me that Dream Seeker should kill itself after one minute (maybe two) if it still hasn't managed to complete it's closing routine. If you are having trouble with invisible Dream Seeker instances, that is a problem indeed. Please make doubly sure that the DS instances are there, and they're closure just isn't being delayed. | |
Tiberath wrote:
So you're actually having issues with invisible Dream Seeker instances? And you're sure they don't go away after a certain amount of time? They don't ever close, and if I double click them I can reopen the specific window. | |
I'll mark it as a high priority in order to attract the attention of one of the developers. With any luck, they'll be able to shed more light on your problem.
Not being able to duplicate the error myself however, is an annoying problem. Does this only happen with your game, or does it happen to others as well? | |
Tiberath wrote:
I'll mark it as a high priority in order to attract the attention of one of the developers. With any luck, they'll be able to shed more light on your problem. once I realised that it was still open in Task Manager, I can confirm that it's not just my game, And I doubt its just me, my game just flagged it due to its often reboots compared to other games. | |
I found the source of this, but forgot to update the bug report.
It seems that if on a skin the quit procedure is not set to .quit, and a player uses the cross to close the window, it simply hides it, as I described. Surely pressing the cross should be set to always close the game, no matter what the programmer has set it to. | |
The on-close command is irrelevant, since if you close the main window the .quit command will always be sent. So if you're seeing a specific case where closing the window doesn't close DS, then something else has to be the cause. If you have a demo of this please let me know. You can post it here or email me at LummoxJR@aol.com.
| |
