Cannot open celx script on linux suse 9.3

[Stuffer]

Hey,

I downloaded celestia 1.5.1 from the sourceforge.net through this link:

Celestia 1.5.1 is now available for download from SourceForge:

https://sourceforge.net/project/showfil ... p_id=21302

(Some of the files have been there for a while now, but SourceForge upload problems meant that it took us a while to get all the 1.5.1 packages uploaded.)

I installed it on my system which is SuSe 9.3. Now I have the problem that I can open .cel, but I cannot open .celx which is really weird since on my WinXP-System it worked perfectly with 1.5.1. Trying to open a celx-script through "file" menu -> Open Script ... I can't even see the celx files but only the cel files. And I cannot have celestia displaying all file formats because this option is not available. Double clicking on the files in my file manager doesn't work on both of them.

What also confuses me is that the keyboard input behaves differently from what I'm used from Win. E.g. pressing the key 'l' which usually speeds up time by a factor of ten only speeds it up by a factor of two now. I also cannot display the spacecrafts coordinate system like on Win.

Is there something I have to include or install additionally especially for the script-problem?
As long as I have this problem I assume that I cannot do ScriptedOrbit either?

Another issue I was wondering about is that when I install celestia on a collegues system and include an add-on with a 3ds model and a texture on it there is horrible bucking but when I change to a cmod it is displayed much smoother. But the graphic card has the latest driver and 512 MB. While running with the 3ds the CPU was used to 100% of its capacity while with the cmod it was not. He mentioned that perhaps with the 3ds model the graphic card isn't used as intensively as it would be possible and instead the program uses the CPU and therefore runs much slower. Is that possible?
Something like textures are rendered by the graphic card but model information by the CPU?

[chris]

Hey,

I downloaded celestia 1.5.1 from the sourceforge.net through this link:

Celestia 1.5.1 is now available for download from SourceForge:

https://sourceforge.net/project/showfil ... p_id=21302

(Some of the files have been there for a while now, but SourceForge upload problems meant that it took us a while to get all the 1.5.1 packages uploaded.)

I installed it on my system which is SuSe 9.3. Now I have the problem that I can open .cel, but I cannot open .celx which is really weird since on my WinXP-System it worked perfectly with 1.5.1. Trying to open a celx-script through "file" menu -> Open Script ... I can't even see the celx files but only the cel files. And I cannot have celestia displaying all file formats because this option is not available. Double clicking on the files in my file manager doesn't work on both of them.

Support for celx scripts requires that the Lua 5.1 package be installed on your Linux system. If it's not installed, Celestia will build without celx support. I recommend installing Lua 5.1 and then recompiling Celestia. Since Celestia for Windows and Mac is distributed as a pre-compiled executable, celx is always available on these platforms.

What also confuses me is that the keyboard input behaves differently from what I'm used from Win. E.g. pressing the key 'l' which usually speeds up time by a factor of ten only speeds it up by a factor of two now. I also cannot display the spacecrafts coordinate system like on Win.

Pressing 'L' should speed up time by a factor of 10; Shift+L speeds time by a factor of 2.

Is there something I have to include or install additionally especially for the script-problem?
As long as I have this problem I assume that I cannot do ScriptedOrbit either?

Correct--ScriptedOrbit will not work unless celx scripts are working.

Another issue I was wondering about is that when I install celestia on a collegues system and include an add-on with a 3ds model and a texture on it there is horrible bucking but when I change to a cmod it is displayed much smoother. But the graphic card has the latest driver and 512 MB. While running with the 3ds the CPU was used to 100% of its capacity while with the cmod it was not. He mentioned that perhaps with the 3ds model the graphic card isn't used as intensively as it would be possible and instead the program uses the CPU and therefore runs much slower. Is that possible?
Something like textures are rendered by the graphic card but model information by the CPU?

While cmod files are generally better optimized for display than 3ds files, there shouldn't be that much of a difference between the two. Can you provide a link to the 3ds and cmod files that you were testing with?

--Chris

[Stuffer]

Chris, thank you for your answer.

Since the 3d model I used is very big and high detailled its size is about 20MB so I can't provide a link to it.
I tried it again to take a look at the two formats and what turned out was that if I use a model in .cmod (about 40MB) which is as detailled as the .3ds it causes really bad buckling as well. Although it is not as bad as with the .3ds it's not much better anyway.

But both models work perfectly with celestia on windows, even with a graphics card having less RAM (only 128MB).
Is this because of a less provided support of openGL when using linux?
Or can there be some other reason?

[John Van Vliet]

--- edit ---

[Stuffer]

I don't now where to upload such big files.
Also I do not know if I would even be allowed to.

The model is self-created by a collegue of my mine from university with a CAD-program. What I figured out is that there are many faces. I think that's why it is so big. Anyway I do not understand why on lunix it is so much worse than on Win XP to view the model in Celestia.


I can't decide which OS to use because I'm not the administrator of the Computer where Celestia is supposed to run on.
The 3d card is a Nvidia Quadro FX 3500 (512MB) if I remember correctly.

As I said we assume that it is sth. about the driver or the OpenGl in principle....

[selden]

Stuffer,

You should discuss the problem with the system's administrator.
A Quadro 3500 is a very high performance card.
It could be that the Linux system is using a software-only 3D graphics driver (Mesa?)
which does not use any of the card's 3D OpenGL hardware acceleration.

[John Van Vliet]

--- edit ---