Celestia Forums

Hi,
I'm used to have the latest version of Celestia, compiled from the CVS files. But since I use a version from a few days ago a strange phenomena happens when I start up Celestia.

First of all my screen becomes dark for a few seconds during startup.

The second weird thing is that the FOV isn't 45 degrees but 19 degrees, so the screen doesn't show me a nice view of IO on a deacent distance but is almost completly filled with the surface of this moon. Why is that?
What can I do to get this FOV of 45 degrees back or to enlarge the distance of view?

My mousewheel seems to work less smooth than before.


I have a nVidia,32 MB mx400 graphics card, Pentium 3CPU, winXP and 512 Mb memory.

HB

HB wrote:Hi,
I'm used to have the latest version of Celestia, compiled from the CVS files. But since I use a version from a few days ago a strange phenomena happens when I start up Celestia.

First of all my screen becomes dark for a few seconds during startup.

Mine has been doing that for months -- for many versions of Celestia. I assumed it's some problem in the Nvidia drivers. I have a Ti 4200, with the v43.45 drivers.

Hopefully one of the developers can comment on this and the rest of your questions.

It's not a bug, it's a feature. Since a few days ago FoV does not default to 45° anymore.

The default FoV is now calculated to present the real angular sizes of objects, it depends on: your screen resolution (DPI), the size of the Celestia window, and your distance to the screen.

If you're using the KDE version you can change your distance to the screen in the configuration dialog, you can even lie about it if you prefer to have a wider than real field of view.

If you're using the Windows version I think Chris hasn't yet implemented the settings for it and they will default to 96dpi for the screen resolution and 40cm for the distance to screen. If you want to change these you can edit src/celestia/celestiacore.cpp on line 289 and 290.

This problem I assume is only appearing on the linux versions and not the win32 versions. I'm using the win32 1.3.1 prerelease version and haven't experienced any of these issues.

That wasn't in CVS when 1.3.1 pre was released. If you compile the CVS windows version as of today, you will get the same behaviour.