Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Can someone verify this for me?
I made two crons. Cron 134 has no date requirements, no pre/post hold-off. Duration is 0. EnableOn is "b1". Duration is 1, and OnStart is "b10".
Cron 133 has no date requirements, no pre/post hold-off. Duration is 0. EnableOn is "b10". OnStart is "!b10". OnEnd is "b11".
I made a mission that when accept, sets b1 (among other things). The mission never terminates.
What I expect the crons to do is that, after I accept the mission and set b1, a cron would activate b10, and another cron would activate b11. This happens once everyday, so will happen whenever I land&takeoff;, or do a hyperspace jump.
--- entering game adjusting sounds showing intro screen drawing stuff drawing more stuff changing window attributes playing game landing on spob 207 (Moonview) evaluating ncb set string 'B1' (beginning mission ASDF (128)) evaluating ncb set string 'b10' (activating cron 134) evaluating ncb set string '!b10' (activating cron 133) evaluating ncb set string 'b11' (terminating cron 133) terminating cron 134 entering system 131 (Alphara) evaluating ncb set string 'b11' (terminating cron 133) evaluating ncb set string 'b10' (activating cron 134)
The "terminating cron 133" happens twice, even though it only got activated once. Can someone verify that the same behavior occures on real macs (I use an emulator)? I don't understand why cron133's OnEnd got evulated twice (aside from Emulator doing things it's not supposed to do).
Thanks a lot,
Pan Sola, Eater of Snacks
------------------ Fundraising to buy a mac so I can play EV:N without using a Emulator (too slow with carrier combats) or taking over my best friend's computer. Please send all contributions via paypal to panguim@uclink4.berkeley.edu Making a TC based on J.R.R. Tolkein's works. (url="http://"http://www.ev-nova.net/forums/viewtopic.php?t=935")http://www.ev-nova.n...topic.php?t=935(/url)
Wait, I'm confused. Are you expecting the cröns to somehow end a mission?
------------------ Moderator- (url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/forumdisplay.cgi?action=topics&number;=9&SUBMIT;=Go&mrxak;=cool")EV Developer's Corner(/url) | (url="http://"http://forums.evula.com/viewforum.php?f=18")mrxak's Assorted Webspace Forum(/url) | (url="http://"http://forums.evula.com/viewforum.php?f=48")Starcraft Forum(/url) | | (url="http://"http://directory.perfectparadox.com/profile.php?id=00008")My Profile(/url) (url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/search.cgi?action=intro")Search First(/url) | (url="http://"http://www.AmbrosiaSW.com/webboard/Forum9/HTML/003091.html")Need Testers?(/url) | (url="http://"http://www.AmbrosiaSW.com/webboard/Forum9/HTML/003196.html")Need Developers?(/url) | (url="http://"http://www.evula.com/survival_guide/")EV/O/N Survival Guide(/url) | (url="http://"http://www.AmbrosiaSW.com/games/evn/addons.html")Nova Addons(/url) | (url="http://"http://w00tware.ev-nova.net/")NovaTools(/url) | (url="http://"http://www.ambrosiasw.com/cgi-bin/ubb/forumdisplay.cgi?action=topics&number;=31&SUBMIT;=Go")Bomb's Plug-in Guide(/url) (url="http://"http://www.evula.org/mrxak/")mrxak's Assorted Webspace(/url) | (url="http://"http://www.ambrosiasw.com/cgi-bin/vftp/dl-redirect.pl/TheChallenge102.sea.bin?path=evn/plugins&file;=TheChallenge102.sea.bin")The Challenge v1.0.2(/url) | (url="http://"http://www.evula.org/mrxak/Haikus/haikuarchive.html")The Haiku Archive(/url) | (url="http://"http://www.evula.org/mrxak/EV/N/mbspt/mbspt.html")mrxak's Big Secret Plug-in/Tutorial(/url) | (url="http://"http://www.AmbrosiaSW.com/cgi-bin/ubb/postdisplay.cgi?forum=Forum10&topic;=007599-2&whichpost;=mrxak11-06-200203:22PM")mrxak?(/url) < . . . . . >
I think he wants the mission to start a cycle of the second cron repeating over and over every time you advance the date. Its very confusing, ill have to try it in nova.
------------------
Quote
Originally posted by mrxak: **Wait, I'm confused. Are you expecting the cröns to somehow end a mission?
**
No, the cron isn't supposed to end the mission. Andcarne is on the right track, though since there's a lot more code that I didn't reveal (and I took some of the stuff out of what I did reveal, since they aren't immediately relevant to my question), it'd be impossible to figure out what I'm trying to do.
But when I turn in my mrxak challenge, you'll find out (-:
My primary concern in this topic is the double-termination of a cron when it only got activated once. I want to know if the same behavior also happen on a real mac computer.
I tested my crons on a real mac (G3 on OS 9.2.2), and I still see all my crons terminating twice even when they were only activated once. Can anyone figure out what's going on?
I do not recall exactly, but with an outfit I made, a long range radar (basically a glorified vellos area map) used a cron every day to give the player a map. I recall it would not work unless (this is the part I cannot recall) the pre/post holdoff or the duration is not 1. I believe it was the duration, though. Try setting it to one.
I'll have to check once I get home, then I'll post again.
------------------ Eat blazing electric death! (url="http://"http://www.evula.org/infernostudios/ept/")Unofficial EV Port(/url) Beta 2
Originally posted by SpacePirate: **I do not recall exactly, but with an outfit I made, a long range radar (basically a glorified vellos area map) used a cron every day to give the player a map. I recall it would not work unless (this is the part I cannot recall) the pre/post holdoff or the duration is not 1. I believe it was the duration, though. Try setting it to one.
Just wondering if anyone, especiall SpacePirate, have looked furthur into this issue...
I remember originally I had duration set to 1, but then the cron only happens every other day (a cron can't start the same day it ended, and duration=1 means start one day, end the other day), and I still get two terminations per activation.
Question that might help determine if this is natural Nova behavior: have you tried looking at a pilot log of a Vell-os pilot to see if the mapping crön they have exhibits the same behavior?
And, if you let me play Devil's Advocate for a moment, is it really a problem? It's unusual, yes, bit does it really affect anything? I'm not asking facetiously, believe me -- I'd like to know.
------------------ Starfleet Adventures: A Star Trek TC for EVN (url="http://"http://www.ev-nova.net/forums/viewtopic.php?t=145") Discussion Board (/url) Starfleet Adventures (url="http://"http://www.ev-nova.net/forums/viewtopic.php?t=71")Progress Log(/url) It is better to feed the goat than it is today.
Originally posted by UncleTwitchy: **Question that might help determine if this is natural Nova behavior: have you tried looking at a pilot log of a Vell-os pilot to see if the mapping crön they have exhibits the same behavior?
And, if you let me play Devil's Advocate for a moment, is it really a problem? It's unusual, yes, bit does it really affect anything? I'm not asking facetiously, believe me -- I'd like to know. **
It does affect things, though I can probably find ways to worked around them (at least all my current crons have been changed to duration 0, so whatever goes in the OnEnd field can be put in the OnStart instead, avoiding the problem). But from just reading the EVN bible I would totally not expect this behavior, so it bugs me a lot.
It was a major issue originally when I was toggling bits, and wonder why they never change, and I found out they got toggled twice for every cron activation and cancelled out...
I have been design plug-ins where I use one of the control bits as a "ready bit", if you study comp sci. So one cron/mission would set a bit, which another cron sees it and will be activated, and turn off the cron. But the double-termination might cause cron1 to turn a bit on, cron 2 to turn it off, and then cron 1 will turn it on again when I don't want to. I'll simply be forced to make sure I avoid using the "OnEnd" field when doing these things in the future.
Sorry for digging up old stuff, but this issue hasn't been resolved, and I'm hearing the last call for bug reports, so I need help figuring out whether the double-termination of cron upon single activation is a bug or not...
Pan Sola