Celestia Forums

I??m not understanding what??s happening.
Although I have 1 GB of dual RAM and a fast 6600 GT,Celestia freezes when I try to run a script as simple as Solar System Tour.Even when I shut out all programs,the freeze occurs.
Is it possible that 128 MB of VRAM is not enough to run scripts well?Or maybe my video card have some kind of problem?
What I know is sometimes,my video card drops the core clock from 500 to 300 Mhz.Is it related to the freeze?Is my video card broken?

Your video card is running at 300 MHz in 2D on the desktop and switches to 500 MHz as soon as the driver is required to render 3D content.
That is absolutely normal.
The 128 MB graphics memory should be enough, with some texture swapping occuring on the bus if very large textures are to be loaded/unloaded, irritating, for sure, but not critical.
That kind of behaviour can be related to:
- a weak or poor quality power supply
- an improper AGP aperture value in the bios (if it is an AGP card)
- fast write and/or sideband addressing activated but not well supported by the hardware (if AGP again)
- outdated or uncleanly installed drivers
- video card not sitting down firmly in its slot
- corrupted Celestia file(s)
- bloated Windows install with stale dlls and registry keys all over the place
- interrupt conflicts
- broken hardware (memory...)
- overclocking
Investigate each case above, one by one, first harware, then software.
Now, you did not tell us anything about your rig: os, cpu, bus type, psu specs, Celestia version...
Does this happen with other 3D apps? Is it really a hard "freeze" or a return to the desktop? Did you test your memory? Did you run a stress test of the system? Do you run a monitoring tool to check temperatures and power supply stability under various conditions?
This would give you valuable hints.

OS: Windows XP SP2 Pro
CPU:Athlon64 3000 "core Venice" socket 939
Bus type: DDR400
PSU specs:Thermaltake w0009 Pure Power 420W
Celestia 1.4.1

I don??t know how to run a stress test.My temperatures are OK.I didn??t do any overclock.It??s a hard freeze and not a return to desktop.
It??s easy you to say,since you have an ABSURD system,that I can??t afford even 2 years from now...

Boux wrote:Your video card is running at 300 MHz in 2D on the desktop and switches to 500 MHz as soon as the driver is required to render 3D content.
That is absolutely normal.
The 128 MB graphics memory should be enough, with some texture swapping occuring on the bus if very large textures are to be loaded/unloaded, irritating, for sure, but not critical.
That kind of behaviour can be related to:
- a weak or poor quality power supply
- an improper AGP aperture value in the bios (if it is an AGP card)
- fast write and/or sideband addressing activated but not well supported by the hardware (if AGP again)
- outdated or uncleanly installed drivers
- video card not sitting down firmly in its slot
- corrupted Celestia file(s)
- bloated Windows install with stale dlls and registry keys all over the place
- interrupt conflicts
- broken hardware (memory...)
- overclocking
Investigate each case above, one by one, first harware, then software.
Now, you did not tell us anything about your rig: os, cpu, bus type, psu specs, Celestia version...
Does this happen with other 3D apps? Is it really a hard "freeze" or a return to the desktop? Did you test your memory? Did you run a stress test of the system? Do you run a monitoring tool to check temperatures and power supply stability under various conditions?
This would give you valuable hints.

hmmm...

it seems that most of the left-over activities in this Forum concern new bot logins and the various never-ending NO-GO problems of Daniel!!!

What a pity...

Bye Fridger

t00fri wrote:hmmm...

it seems that most of the left-over activities in this Forum concern new bot logins and the various never-ending NO-GO problems of Daniel!!!

What a pity...

Bye Fridger

Unfortunately, you are right.
I just wasted my time. If I do know about anything, it's about computers and how to diagnose a malfunction through a basic set of steps which all together are making a standard method to trap the root fault.
The main cause of problems are always: 1/ the user 2/ the hardware 3/the software 4/ the user's laziness
Bah, as I get older, the cooler I feel

What I did wrong?I only want you to answer my question.This problem is recurrent and I would like to know the cause.It had been happening in every version of Celestia...
I am only wondering if a script is more hardware intensive than the still images and how much.

Boux wrote:

t00fri wrote:hmmm...

it seems that most of the left-over activities in this Forum concern new bot logins and the various never-ending NO-GO problems of Daniel!!!

What a pity...

Bye Fridger

Unfortunately, you are right.
I just wasted my time. If I do know about anything, it's about computers and how to diagnose a malfunction through a basic set of steps which all together are making a standard method to trap the root fault.
The main cause of problems are always: 1/ the user 2/ the hardware 3/the software 4/ the user's laziness
Bah, as I get older, the cooler I feel

danielj wrote:What I did wrong?I only want you to answer my question.This problem is recurrent and I would like to know the cause.It had been happening in every version of Celestia...

It is really not the task of this forum to tele-repair people's hardware or general software installation!

I bet your problem is either due to some hardware issue specific to your machine or (more probably) it is due to your familiar, dangerous "fiddling" with installation matters! After all it's NOT the first time that you seem to encounter "mystical" problems that nobody else encounters...Also now: NOBODY else encounters the crashes/freezes you are describing.

Take your parallel installation (using the installation shield in both cases) of TWO quite different versions of Celestia (1.4.1 and 1.3.1) that you described a few days ago!

It is not relevant on which partitions these two reside. What is relevant are the /possibly colliding/ entries that the installation program puts into the REGISTRY! That's why in Windows it is always emphasized to delete older versions before updates are installed with the installation shield. But you don't seem to care about such basic rules...

When doing such things, you are simply calling for trouble. Soon or later you'll get it.

It was many times pointed out in this forum what you should do if you want to have several versions of Celestia on your harddisk and use them interchangably...

I am only wondering if a script is more hardware intensive than the still images and how much.
...

You are not a newbie. Just take your common sense and use it!

In order for an outsider to really estimate the load on your hardware, he/she would have to know all the image sizes and add-ons you are loading when executing your script. This only you know, so you also got to find the answer for yourself!

Bye Fridger