Celestia Forums

I have upload new models of Mars's moon Phobos, the asteroid 2867 Steins, and comet 67P/Churyumov-Gerasimenko, all in cmod format. The Phobos model is huge, with over 3 million triangles. The model of Steins is medium resolution, and the Churyumov-Gerasimenko model is very low resolution (presumably generated from light-curve data.)

The models are all located here:

http://www.celestiaproject.net/~claurel/celest ... apemodels/

All of the models were created from SPICE shape kernels available here:

ftp://naif.jpl.nasa.gov/pub/naif/generic_kernels/dsk/

The Phobos model will slow down Celestia immensely, even with a high end graphics card. Don't bother downloading it unless you have some serious hardware.



--Chris

I still get 80 FPS with this Phobos model
I converted the model to cmod (75 MB) with the cmodview tool but the alignment of the model seems to be wrong?

[edit]I tested the Churyumov and Steins models, the Stein model can be viewed in cmodview but not in Celestia. When I get too close to Steins, it just disappears.
I tried logging an error if there was any, but nothing about Steins in the log.[/edit]

CAP-Team wrote:...
[edit]I tested the Churyumov and Steins models, the Stein model can be viewed in cmodview but not in Celestia. When I get too close to Steins, it just disappears.
I tried logging an error if there was any, but nothing about Steins in the log.[/edit]

Hi, CAP-Team,
I do not have any problem with such models in Celestia latest SVN 5144 without the new stars rendering, but Celestia crashes when I goto to the models with your build (5144 with the new stars rendering). Moreover, the impossibility of making the models transparent as specified here: http://www.shatters.net/forum/viewtopic.php?f=4&t=16375, persist. Such "impossibility" doesn't exist with the "normal" SVN 5144.

OK model of Steins working now.

CAP-Team,

Make sure you've specified a Texture for Steins. Although the CMODs Chris has generated won't actually show a surface texture image, specifying one causes them to be drawn white. Without one, they're drawn black.

On my laptop, which is somewhat less capable than CAP's system, I get a measly 12fps when viewing Phobos. I was surprised to see that Win7 SP1 causes Celestia to use almost the equivalent of two cores in a multiprocessor system: it uses about 20% of my 4-CPU/8-thread system. A simple CPU-bound program uses only 12% (1 core). I don't know if Celestia's performance actually benefits from that, though. I'll check tomorrow to see what happens on a Win7 system without SP1.

System: Dell Latitude E6510
CPU: 8GB, 1.60 GHz Core i7-720QM; Win7 Pro SP1 x64
Graphics: 512MB DDR3, Nvidia Quadro NVS 3100M; ForceWare v258.96
Disk: 320GB, 7200RPM, Seagate ST9320423AS
Display: FHD, 1920x1080, 60Hz, 32bit color, Vizio VX240M
Celestia: v1.6.0, v1.6.1(pre-alpha),
r5147 (compiled w/VS C++ 2008 Express, v9.0.30729.1 SP)

Well, there's something wrong with the cmod of Steins, I redownloaded the model, and replaced it, since I fuddled around with that model in cmodview and converted it to ascii mod. Now it won't show anymore.

Also the orientation is wrong, as is also the case with the Phobos model.

Since I specified a Texture, I have had no problems seeing Steins. See below.
[edit: I have *not* made any changes to the CMODs provided by Chris.]

I agree that there seems to be a coordinate transformation problem. To produce the image below, I copied the definition of Phobos from solarsys.ssc, modified its name, and set the MeanAnomaly of the hires model of Phobos to be 271.3 so it'd be drawn adjacent to the "real" moon.


p.s. I'm currently running Dexpot, which provides multiple virtual desktops.
When I switch away from the desktop containing Celestia, its CPU usage is reduced from 23% to 12%. I'm guessing that a CPU-bound thread is associated with loading the display graphics... Yup: the GPU load goes from about 95% when viewing the Celestia desktop to less than 1% when viewing the desktop without it.

Hi! CAP-Team, I think there is something wrong with your build that concern the 3D models. I don't know what, nor is a your error of course. At least with Phobos that seem to run: could you please to see whether it became trasparent by setting the opacity = 0.3 or 0.03 or 0.003? (last number is indicative); in my experiment with your build, a model with opacity = 1 or opacity = 0.003 is the same, that is, it remains completely opaque.

P.S.

Even on Xp I get the quarter/half of the whole speed. At least with Speccy (free program, green meters are clickable) my quad core behave so:





When I've taken the screen shot the latest Celestia SVN (without the new stars render) were running on the secondary monitor, involved into a SS tour. Seems that just the core1 is running at maximum of its speed, the remains three cores runs at half. In fact, also the meter-bar on the primary monitor displays the whole speed at 46%. Notice that I can achieve lesser speeds when I'm using another PC without the network active. However, such a situation happens even when Celestia is not running and nonetheless, with celestia running, I never achieve the 100%.

I tried using the Phobos model in Celestia 1.6.1 RC0,but Celestia crashes.It appears that the model is TOO big!

Steins doesn?t appear to have any texture applied.The appearance is too artificial
http://img838.imageshack.us/i/steinstooartificial.jpg/