Celestia Forums

After much work the last few days, I have know confirmed, without
any doubt, that all the crashes I've been getting since 1.2.3 is because
of those darn .cms files. To make a very long story short, I have
removed all references to .cms files in the scc files. In doing so, I
made a bunch of asteroids .3ds files to use, at least temporarily, to
replace the .cms files (mainly asteroid.cms). There are actually 12
asteroids in a zip file at the following: (hope this works...)

http://www.vicware.com/space/DozenAsteroids.zip

The dozen asteroids are variations on a theme - they need there own
textures - they're very shardy.

If you're having this particular problem with Celestia, this is the
answer. I haven't had a crash since I made these changes.

Vic

Thank you so much for tracking this down . . . I still can't reproduce this problem on my computer, but I'm looking through the .cms file handling code to try and figure out what's going on. Would you object if I included a few of your asteroid models to replace the .cms models in the next Celestia release?

--Chris

chris wrote:Thank you so much for tracking this down . . . I still can't reproduce this problem on my computer, but I'm looking through the .cms file handling code to try and figure out what's going on. Would you object if I included a few of your asteroid models to replace the .cms models in the next Celestia release?

--Chris

Please use them. I'm going to try to come up with asteroidXX.jpg's for
texture maps for them. After 25 years in digital design and software
engineering, I wish I could make a living doing what you're doing.

Btw, I still haven't had a single crash since I replaced all .cms
references. It's considerably more fun to use the software now. I
only wish bump-mapping worked with my card. Next cpu, I guess.

Vic