Help - Search - Members - Calendar
Full Version: Startup Commands
Heynow Software Forums > Savitar Software Application > Bug Reports
Stormy
Savitar didn't crash, so I have no crash log this time, but my startup commands no longer fire with 1.3b2, or they fire well into the session. I don't know if this is unique to 1.3b2, to me, or fixed in 1.3b3.

Stormy smile.gif
jay
> my startup commands no longer fire with 1.3b2, or they fire well into the session. I don't know if this is unique to 1.3b2, to me, or fixed in 1.3b3.

Well, are they firing or are they late? It makes a difference knowing this when I address your bug report.

I use startup commands in many places, I haven't seen them not fire. Could you give more details please?

/Jay
Stormy
QUOTE (jay @ May 7 2003, 02:59 PM)
Well, are they firing or are they late? It makes a difference knowing this when I address your bug report.

I use startup commands in many places, I haven't seen them not fire. Could you give more details please?

Actually, they're firing late; when I'm already well into the session after having to log in manually. smile.gif

When I start up Savitar, I double click the world icon in my folder (though this also happens when I double click the Savitar program icon). It connects to my world and then it just sits there. I end up having to log in manually, and go about business as usual. About an hour or so (my timer is set to 56 minutes), the triggers finally fire setting my ##task, as well as various other routines I go through including entering username and password.

Hope this helps some. smile.gif
Stormy
Stormy
I've just started using the latest build and my startup commands still only fire minutes, sometimes hours, after having to manually connect. Admittedly, some of my worlds/windows still act as they're supposed to (suprisingly, my staff alts wink.gif ), but most of them do not. For expediency, I've had to set my ##tasks while connected only to have my startup scrips fire at some point later and I either have double tasks, or I have to go in and manually kill one. I'm not sure how much better to explain it, but I hope it can be fixed.

Thanks,
Stormy
jay
I found and fixed this bug today.

The fix will be in the upcoming 1.3b5 release. If anyone is currently having this problem with 1.3b4, email me and I'll give you a pre-release of 1.3b5.

Thanks Stormy

/Jay
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2024 Invision Power Services, Inc.