Problem when trying to play some files
Forum rules
Please help to make this forum more useful by checking the FAQs before posting! Keep it clean, keep it civil, keep it truthful, stay on topic, be responsible, share your knowledge.
Please help to make this forum more useful by checking the FAQs before posting! Keep it clean, keep it civil, keep it truthful, stay on topic, be responsible, share your knowledge.
Problem when trying to play some files
I keep getting this fatal error message - '{' expected at start of script. - and then nothing else.
-
John Van Vliet
- Posts: 2944
- Joined: 28.08.2002
- With us: 22 years 3 months
re
some more information is needed
you are missing things like
Your Operating system
the version of celestia this is
the NAME of these scripts ,and where you got them
you are missing things like
Your Operating system
the version of celestia this is
the NAME of these scripts ,and where you got them
Your Operating system - Win 10 Pro
Version 21h1
build 19043.1466
the version of celestia this is - version 1.6.1.0
the NAME of these scripts - Fire Kats
and where you got them - don't remember & source appears to be gone. I've had them for years.
PS - there are several files by various sub names and so far all have given the same results
Version 21h1
build 19043.1466
the version of celestia this is - version 1.6.1.0
the NAME of these scripts - Fire Kats
and where you got them - don't remember & source appears to be gone. I've had them for years.
PS - there are several files by various sub names and so far all have given the same results
No answers?
Any ideas, anybody?
@Bob_F
The error message
'{' expected at start of script.
means either that you are trying to invoke a .CEL script which is damaged
or that you are trying to invoke a .CELX script which has had its .CELX file extension truncated to .CEL
A .CEL script must start with a { (aka left brace or left squiggly-bracket) and must end with a } (aka right brace or right squiggly-bracket) followed by a line terminator.
In other words, the commands in a .CEL script must be encapsulated by squiggly brackets ( {} )
This is unlike .CELX scripts. They are written in the Lua programming language and require that there not be any encapsulating brackets.
.CEL and .CELX scripts are plain-text files which you can examine and edit using any text editor. You must NOT use a word processor to examine or edit them. Notepad is an example of a text editor. WordPad and Microsoft Office Word are examples of word processors. Word processors insert binary control codes which specify the format of what you see when you look at the files. Celestia does not understand those binary codes. It is possible that someone made the mistake of trying to edit or examine the .CEL scripts with a word processor. If that's the case, it might (or might not) be possible to modify those scripts with a text editor to make them work again. If they're acually mis-named .CELX scripts, then you just need to change the files' extensions from .CEL to .CELX
Many people like the 3rd party text editor Notepad++. Personally, I use emacs.
My comments above apply to all versions of Celestia running on all supported operating systems.
The error message
'{' expected at start of script.
means either that you are trying to invoke a .CEL script which is damaged
or that you are trying to invoke a .CELX script which has had its .CELX file extension truncated to .CEL
A .CEL script must start with a { (aka left brace or left squiggly-bracket) and must end with a } (aka right brace or right squiggly-bracket) followed by a line terminator.
In other words, the commands in a .CEL script must be encapsulated by squiggly brackets ( {} )
This is unlike .CELX scripts. They are written in the Lua programming language and require that there not be any encapsulating brackets.
.CEL and .CELX scripts are plain-text files which you can examine and edit using any text editor. You must NOT use a word processor to examine or edit them. Notepad is an example of a text editor. WordPad and Microsoft Office Word are examples of word processors. Word processors insert binary control codes which specify the format of what you see when you look at the files. Celestia does not understand those binary codes. It is possible that someone made the mistake of trying to edit or examine the .CEL scripts with a word processor. If that's the case, it might (or might not) be possible to modify those scripts with a text editor to make them work again. If they're acually mis-named .CELX scripts, then you just need to change the files' extensions from .CEL to .CELX
Many people like the 3rd party text editor Notepad++. Personally, I use emacs.
My comments above apply to all versions of Celestia running on all supported operating systems.
Selden