Celestia Forums

Daniel,

That is a known bug reported in another thread, I think.

Phoebe.cmod was accidentally left out of the pre1 kit.

You can
a) edit* solarsys.ssc and change
Mesh "phoebe.cmod"
to
Mesh "phoebe.3ds"

b) download phoebe.cmod from SourceForge

c) wait patiently for pre2.

____
* -- Of course, there's no need to actually edit solarsys.ssc. Here's an Addon SSC to fix it:

danielj wrote:But what about Phoebe?It is invisible in Celestia 1.4.1 pre1.The locations are shown,but not the moon.

If you have dwloaded the model, and replaced it correctly in the models folder (NO other manipulations!), it must work! That's working for me with my poor install at home, so...
Didn't you confused with the two avaible models (.cmod and .3ds) ?
Jeam

Strangely enough,the phobos.3ds model works;the mesh phobos.cmod don??t.

Jeam Tag wrote:

danielj wrote:But what about Phoebe?It is invisible in Celestia 1.4.1 pre1.The locations are shown,but not the moon.

If you have dwloaded the model, and replaced it correctly in the models folder (NO other manipulations!), it must work! That's working for me with my poor install at home, so...
Didn't you condused with the two avaible models (.cmod and .3ds) ?
Jeam

Very nice splash screen

But, no levels 11 and 12 ?

I just found another bug, I think. I hit 'a' to accellerate, moved the view around a bit with my numberpad, then "F1" to stop altogether, only, it didn't stop, it simply kept slowing, and slowing, and slowing.... until Celestia simply went "poof!"--it disappeared on me completely.

I also saw a crash like Plutonian Empire did on 1.4.1 pre from the .exe disti.
The NVIDIA adapter has 64 Meg RAM. It is a GeForce 4 MX . It is used on my
AMD Athelon at 2.21 G Hz with 2 Gig of RAM. Windows XP

It ran for 10 minutes, watching planets for 400 years, zooming through star
clusters. Left the Galaxy, went to M31 and a distant galaxy. Back to Earth, out
to strange galaxies, zooming wildly with no problem. Back to Sun, out to M31,
visited distant, very bright galaxy, increased brightness, decreased, : poof !
No more Celestia 1.4.1 pre, just Windows wallpaper. Crashed Celestia,
no warning, sudden, bang dead.

Looks like a bug to me, sorry.

Hmmm. Yes...

F1 seems to do a Zeno until the speed display underflows.

Hi guys...

I have no idea what is wrong, or how to find out what is wrong. But 9 out of 10 times that I start the program it crashes before the start up screen even materializes, and most of the rest of the time it crashes while I try to maneuver around planets, 3ds models, whatever.

It wasn't doing this initially, so I don't know what the problem might be....

I'm running a 1.0ghz PIII Gateway with nearly 400mb of RAM, and an Nvidia GeForce2 GTS with 32mb of memory.

...John...

Hi,

I just wanted to point out that the "K" bug (see second post on this thread) DID NOT happen with 1.4.0.
I also confirm there's no way to see levels 11 and 12 on virtual textures.

Bye,
Brokfn

I made a patch that may fix the "K", "F1", and "Z" key issues:

...

Update: The patch has been committed to CVS. It should appear in the next release if no problems are found.

Vincent wrote:1. When you change the Timerate from a script command, Celestia still displays <Real Time> on the top right hand corner, whereas it displays the right Timerate when you change it from the <J>/<L> keys.

2. When you change the Timerate from a script command, and then pause the script, and resume it, Celestia reset the Timerate to <Realtime> whereas it should keep the previous value set by the script command.

dirkpitt wrote:If you can compile from CVS, please try this patch (cd celestia/src; patch -p0 <timerate.patch). Disclaimer: I whipped it up in less than an hour so YMMV.

DW,

Your "Timerate Display" patch has been integrated neither to 1.4.1pre1 nor to 1.4.1pre2. I read on the developpers Email Archive that Chris wants to fix this issue differently.

> Do you know if this issue will be fixed soon ?
> If not, can we use for now your patch without having problem while running Celestia ?

Thanks.

Yes, a clean fix (i.e., a fix that's not a hack) for the timerate display not synching with scripts is turning out to be a bit difficult. Currently, the only "patch" integrated into 1.4.1 is a fix for overflows. The timerate sync patch probably doesn't apply cleanly any more and shouldn't be used.