changing K & L values - possible?

[hank]

...Aarg, I can't get it to work. I haven't been able to figure out the problem yet.

How exactly does it fail?

- Hank

[bongox]

On choosing the script, an error window pops up and it displays:
"{" expected at start of script
and the option to click ok.
I have tried to figure out why it doesn't work, but by comparing it to other working scripts I haven't been able to locate the problem, which I'm convinced is simple and in front of my nose, but i don't have any scripting experience outside of a little 'lingo' scripting in Director.
Any suggestions you might have would be greatly appreciated!
Cheers

[hank]

On choosing the script, an error window pops up and it displays:
"{" expected at start of script
and the option to click ok.
I have tried to figure out why it doesn't work, but by comparing it to other working scripts I haven't been able to locate the problem, which I'm convinced is simple and in front of my nose, but i don't have any scripting experience outside of a little 'lingo' scripting in Director.
Any suggestions you might have would be greatly appreciated!
Cheers :)

Make sure that the file extension you give the script file is .celx (rather than .cel).

- Hank

[fsgregs]

Hank:

Thank you so much for the script to change the time ratio. It does work. However, the time speed display does not change to 5X faster when you press the L key. It still reads Real time (even though the clock is running 5X faster). What line would I add to the script so that it detects the time ratio change and prints "5X faster" or 5X slower, or 25X faster, etc??

Thanks in advance

Frank

[hank]

Hank:

Thank you so much for the script to change the time ratio. It does work. However, the time speed display does not change to 5X faster when you press the L key. It still reads Real time (even though the clock is running 5X faster). What line would I add to the script so that it detects the time ratio change and prints "5X faster" or 5X slower, or 25X faster, etc??

Thanks in advance

Frank

Frank,

I think that may be a bug in the version of Celestia that you are using. It seems to work correctly in my recent CVS build.

- Hank