Celestia Forums

Hi,

I am using Celestia 1.4.0pre-FT1.2 (ans also it happend with celestia 1.3.2) under GNU/Linux (Kubuntu 5.10) and there are some minor planets that I can't see, like Phobos, Deimos, Eros, but another like the moon is visible.

My computer is a Samsung Laptop X05 with an Intel 855 video card (more information at the end of the email)

The Open Gl path is set to: Multitexture. It is the reason? I have a 16 bit colour depth. I have to increase it?

Best Regards!


15: PCI 02.1: 0380 Display controller
[Created at pci.244]
Unique ID: ruGf.uPZsHx1Lru2
SysFS ID: /devices/pci0000:00/0000:00:02.1
SysFS BusID: 0000:00:02.1
Hardware Class: graphics card
Model: "Samsung Electronics 855 GM"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x3582 "855 GM"
SubVendor: pci 0x144d "Samsung Electronics Co Ltd"
SubDevice: pci 0xc009
Revision: 0x02
Memory Range: 0xf0000000-0xf7ffffff (rw,prefetchable)
Memory Range: 0xe0080000-0xe00fffff (rw,non-prefetchable)
Driver Info #0:
XFree86 v4 Server Module: i810
Driver Info #1:
XFree86 v4 Server Module: i810
3D Support: yes
Color Depths: 16
Extensions: dri
Options:
XF86Config Entry: VideoRam 16384
Config Status: cfg=new, avail=yes, need=no, active=unknown

These are probably binary cmod files.
What are your kernel and gcc versions?

hi,

My kernel:
2.6.12-9-686,

and the gcc:
gcc versi?? 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)

Regards,

Daniel Alomar

Hi,
Well, it looks like that since kernel 2.6.12.n (built on gcc-4.n by the way), binary cmod models are no longer rendered.
This is definitely a bug I have been reporting about for some time.
Nobody seems to care about it here, most people are with windows and the only answer I got was about trying to fix the files with a damn Windows utility
There are very few Linux users with the latest kernel and gcc apparently.
OK, enough rant, in the meantime, you can use the 3ds models instead of the cmod models.
The ones you are looking for are in the models folder.
Just edit the *.ssc file accordingly so that they call the *.3ds files instead of the cmods.
Good luck

Boux,

If you're referring to my suggestion to try regenerating the files using cmodfix, that's not just a Windows utility. The source code for the CMOD manipulation utilities is included in the CVS archive and can be compiled to run under any operating system.

Someone who sees the failure needs to build Celestia with debugging turned on and use a debugger to step through the code to find out what's going wrong. Since it does not fail on any of the systems used by the developers, they can't find the problem.

Selden, the problem is that the developpers never said anything about the kernel version they are currently using.
One fact is that all major distributions have recently moved to kernel versions higher than 6.12.n, kernel 6.13.n being now widely introduced.
At the same time, gcc-4, in their flavours 0.1, 0.2, 0.3 and even higher are already the norm.
Kernels, Xorg and many major components are now built with and require gcc versions higher than 4.0.0.
When a somebody is saying something like "it works for me, check on your end", sorry but I think this does not make any sense.
Another fact is that there is a possibility that the standard Celestia release is no longer fully compatible with the latest Linux distributions.
I have loaded a clean FT 1.2 on a brand new install of Mandriva 2006 (kernel 2.6.12.12 with gcc-4+) and the symptom is still there.
I have also loaded an 1.3.2 rpm just to be sure. Same problem.
For sure, I can invest some time in debugging the thing.
I am just amazed by the lack of interest for Linux.
One exception, Fridger was kind enough to send to me his own build for Glut (you know, the no-brainer very basic vanilla Linux version).
Guess what? Binary cmods don't load. Exactly the same as with my own build.
Well, after all these are only zeroes and ones, aren't they?

Still chasing the bug: operation cmodfix'ing.
I have installed FT1.2 on a Win2K machine and cmodfix'ed a couple of big binary models (Discovery and Pod1), re-converting them to both ascii and binary formats with various combinations of options.
All formats show up in Win2K as expected.
Uploaded the 'fixed' files with their different versions to the Linux box.
Ascii models show up, binary ones still don't.

Hi,

Changing .cmod for .3ds into the scc files work for me.

There is a discontinued support for the .3ds files? Which advantages have cmod in front of 3ds files?

Maybe a (provisional) solution will be to generate a patch file for linux distributions to change this extensions inside the scc files....

Best regards,

Daniel Alomar

dan-solo wrote:Hi,

Changing .cmod for .3ds into the scc files work for me.

There is a discontinued support for the .3ds files?

My understanding is that there are no plans to remove the 3DS code currently in Celestia.

Which advantages have cmod in front of 3ds files?

Performance and editability.
When showing a large model that has been converted from 3DS to CMOD, Celestia runs at 1.5 - 2x the framerate.
ASCII CMOD files can be edited to modify things like surface textures. 3DS files require the use of a binary editor.

Boux wrote:Still chasing the bug: operation cmodfix'ing.
I have installed FT1.2 on a Win2K machine and cmodfix'ed a couple of big binary models (Discovery and Pod1), re-converting them to both ascii and binary formats with various combinations of options.
All formats show up in Win2K as expected.
Uploaded the 'fixed' files with their different versions to the Linux box.
Ascii models show up, binary ones still don't.

Boux,

but then there must be something else. Since that glut version I snet you and all my other versions of FT1.2 including Windows load/display binary CMODS, for sure.

I made many checks.

Cheers,
Fridger

You are right, there /must/ be something else.
But what and where?
At least, we know a number of facts:
With KDE:
- it works on Mandriva/Mandrake with kernel <= 6.8.nn with gcc 3.nn
- it does not work with Mandriva /Mandrake with kernel >= 6.8.nn and gcc 3.nn
- it does not work with both Mandriva/Mandrake or (K)ubuntu with kernel 6.12.nn and gcc-4.nn
With GLUT:
- it does not work with Mandriva/Mandrake with kernel 6.12.12 and gcc-4+, even with your own build.

i to have noticed that cmod's arent working
fedora4 kernel (2.6.14-1.1653_FC4)
and gcc -4.0.2-8.fc4
NVIDIA-Linux-x86-1.0-8174-pkg1 driver
i first saw this in win xp but seeing as i was about move to linux , i thought just win and forgot about it .

also mesa is not installed because i found that cvs code was building and installing but not runing only crashing apon startup