Textures & Add-on Downloads, For new Celestia users.

[Darkmiss]

Add-0n List Canceled.
I'm not qualified enough to post this list. (apparently)

[Phule]

How would you go aobut making the .bmp work on the 16k earth. I can't get it to work on anything.

P4 2.0
512mb DDR
128MB DDR TI4400
Win XP SP1

[selden]

Celestia does not understand BMP files.
You have to convert them into JPEG, PNG or DDS

[JackHiggins]

BMP's work perfectly for me for some reason- (true color-32 bit only though) I only use them for asteroid and small moon textures though as the file sizes are so large...!! I can't get DDS textures to work & JPEG's work only sometimes...?!

I'm the guy whose computer took 35 minutes to load the big star database though so you'd expect other strange things to happen as well...

Oya actually as well should bumpmaps work on a TNT2Pro 32MB card?

[Phule]

Selden,
Is there anything that can convert them easily. I tried GIMP but it seems a little complicated.

[Guest]

DDS files work fine for me on my ATI Radeon 8500DV

[Sum0]

Bitmaps in Celestia are back-to-front, for some weird reason. JPEGs are much easier and better than BMPs for just about everything.

[selden]

Phule,

I'm CLI oriented myself, so I use nvdxt to convert other formats into DDS. It seems simple enough to me. For example, the command

Code: Select all

nvdxt -file filename.tga -dxt1

creates filename.dds out of filename.tga at the same resolution.
The NetPBM utilities can do similar things with other formats.

Sum0,

Presumably you're writing about separate texture maps that are used with 3ds objects in Celestia. It would be nice if Chris could fix that.
(texture maps used with planetary spheres seem OK)

[John Van Vliet]

Has anyone else had problems with using the comand line with win XP
it seems that the comand line is not very saported in XP,Also the
dxt tool v1.0(the german GUI for nvdia ) creats a file on the c drive
C:\\Program (not to be confused with C:\\Program Files). This file called program then trips the CLR,shuts down the tool and gives me a name warning.


The tool only works in my Fox Server directory
C:\\FoxServ\www\ -But it works

[Darkmiss]

it works fine for me

I have the exe file and a bat file ( nvdxt -file *.tga -dxt5 ) placed in my textures root directory
(you need DXT1a for spec and alpha maps)


then i put the TGA file in there too, the run the bat file
then a dos box comes up and takes about 1 to 5 mins to compile
depending on TGA size.

I have Windows XP pro,
Service pack 1,
512m ram.

[alegator]

I downloaded the file cassini.zip from the link:
http://www.bt.homepage.btinternet.co.uk ... assini.zip
and installed the cassini.3ds file in the models folder of Celestia, but I'd appreciate if someone could tell me what lines to add to the solarsys.ssc file in order for celestia to be able to display the spacecraft.
Thanks.

[selden]

You have to install a .SSC file defining Cassini's trajectory.
Some are at http://www.lns.cornell.edu/~seb/celestia/spacecraft.html
Change whatever SSC files you use so that they specify "cassini.3ds" instead of "galileo.3ds"
Make sure cassini.ssc is in the extras directory and that cassini.xyz is in the data directory.

Celestia reads all of the ssc files it finds in extras and adds their objects to its internal database. If there are bugs in some of the ssc files, it'll silently ignore those. The new objects defined by the ssc files will be added to the appropriate Navigation/Browser menu items.

[Guest]

i just downloaded the moon8k dds texture linked at the top of this topic and installed it by simply changing the 'texture' property in solarsys.ssc (this is correct right? or should i be playing with the bumpmap & bumpheight settings as well??)

it looks great at most distances, however when i get to a certain point a weird ring of corruption shows up around the moon (see below)... is this a problem with the actual texture or is it something in my setup?



any help appreciated


avatar

[chris]

i just downloaded the moon8k dds texture linked at the top of this topic and installed it by simply changing the 'texture' property in solarsys.ssc (this is correct right? or should i be playing with the bumpmap & bumpheight settings as well??)

You may want to turn off bump mapping with the 8k texture . . . The bump map is only 1k, and will probably be distracting with such high res base texture. Comment out the bump map by putting a # in front of the BumpMap line.

it looks great at most distances, however when i get to a certain point a weird ring of corruption shows up around the moon (see below)... is this a problem with the actual texture or is it something in my setup?

It sounds like you're running out of texture memory, and the driver is overwriting part of your 8k moon texture. You're probably better off with a 4k texture. It's also possible that getting rid of the bump map will free up just enough texture memory that the problem will go away.

So what graphics card are you using?

--Chris

[Guest]

ok i took out the bumpmap as you suggested, although this hasn't affected the problem.

i've updated the image above with one that shows slightly more clearly the way in which the corruption fades in/out at a certain point. it always appears in the same place and only on the moon (not the earth which im also running an 8k texture on)

my basic system specs are thus:

athlon xp 2000
512meg
geforce 4 ti4200 agp8x 128meg


cheers


avatar

[avatar]

sorry, forgot to mention i'm running celestia v1.2.5 on windowsXP with directx 9.

[jean-michel]

I have a similar 'ring of corruption' issue with earth, using an ATI Radeon 8500Le card under xfree 4.2.1 (and 4.2.99.4) running on a GNU/Linux box. A colleague has also run into the same problem with a different radeon card.

This issue does not arise with any other 3d applications, so it might be a quirk with celestia, or a portion of the drivers that celestia excersizes and nothing else does.

[jean-michel]

I have a similar 'ring of corruption' issue with earth, using an ATI Radeon 8500Le card under xfree 4.2.1 (and 4.2.99.4) running on a GNU/Linux box. A colleague has also run into the same problem with a different radeon card.

This issue does not arise with any other 3d applications, so it might be a quirk with celestia, or a portion of the drivers that celestia excersizes and nothing else does.