Celestia 1.7.0 Development Thread

[trappistplanets]

I did not rebuild another commit. It is the same build. I edited the celestia.iss file only.

installed, and try to run celestia-win.exe and celestia-qt.exe but nothing is opening even with a batch script

[cartrite]

What operating system are you using? Did you create a desktop icon? How are you trying to start the programs?

[trappistplanets]

What operating system are you using? Did you create a desktop icon? How are you trying to start the programs?

i am using Windows 7 32 bit, and yes i do have desktop icon, and i tried to start it the normal way and with a batch script (talk to seven about batch scrips that can force open EXEs)

[cartrite]

This a 64 bit program. It will not run on your system.

I didn't build a 32 bit version. I'll look into the difficulty I will have to endure to build a 32 bit app. I may need to download too much. If my version of Visual Studio will build 32 bit, I'll look into installing vcpkg 32 bit packages.

[trappistplanets]

I didn't build a 32 bit version. I'll look into the difficulty I will have to endure to build a 32 bit app. I may need to download too much. If my version of Visual Studio will build 32 bit, I'll look into installing vcpkg 32 bit packages.

it would be a good idea to put a 64 bit warning on the original post

Added after 1 minute 7 seconds:
so others don't run into this problem (and know to wait until you build a 32 bit one if its possible on your end)

Added after 48 seconds:
celestia is made to run on most systems (only systems it can't run on is really really really bad PCs, ones way worse than mine)

[SevenSpheres]

5 posts moved from cartrite's thread. Trappist, please read the OP in which cartrite asks people to report any problems in this thread to not clutter the installer thread.

GitHub Actions generates both 64-bit and 32-bit binaries, which can replace the ones in the installed program. You need a GitHub account to download them.

[cartrite]

Thank You SevenSpheres.

Added after 3 minutes 41 seconds:

I didn't build a 32 bit version. I'll look into the difficulty I will have to endure to build a 32 bit app. I may need to download too much. If my version of Visual Studio will build 32 bit, I'll look into installing vcpkg 32 bit packages.

it would be a good idea to put a 64 bit warning on the original post

so others don't run into this problem (and know to wait until you build a 32 bit one if its possible on your end)

celestia is made to run on most systems (only systems it can't run on is really really really bad PCs, ones way worse than mine)

I didn't realize that people were still using 32 bit operating systems. You must have a 32 bit machine and it must be very old. But I'll look into getting 32 bit libs for celestia. I will not get the qt5 32bit libs though. It's too big and it will take too much time to build, so celestia-qt 32 bit will not be built.

[Art Blos]

I didn't realize that people were still using 32 bit operating systems. ou must have a 32 bit machine and it must be very old.

Although such systems are already considered obsolete, they are still quite widespread. And computers with such systems do not have to be very old. 5-7 years is not such a long time.

[cartrite]

I bought a Toshiba laptop about 10 years ago and that came with windows 7 64 bit.

With Linux things would be easy. Every lib comes with a 32 bit version. I simply install them with yast. With windows the vcpkg system that celestia is currently using downloads source and must be built. So that can take me a few days.

[john71]

This "instead of numbers, there are rectangles" bug still persists. I installed all available fonts, tried every Windows compatibility method, but nothing is working.

This bug only resurfaces in the screen information data, not in the menus or other texts.

Is there a special font type for the screen information data, especially for numbers?

Added after 8 minutes 53 seconds:
Maybe there was an accidental change in the screen font types?

[onetwothree]

No, fonts were not changed. And the only place where we replace invalid chars with that square is in tokenizer (the part of code which reads config file and catalogs). The only way to find the root cause is to use git bisect to find the commit which introduced the bug. But this is not reproducible in GLU/Linux nor macOS so we can't do this.

[SevenSpheres]

But this is not reproducible in GNU/Linux nor macOS so we can't do this.

Doesn't ajtribick use both Windows and Linux? Anyway, I'm not seeing this issue on Windows and neither is anyone except john71, apparently. I tried changing language using "set LC_MESSAGES" but that doesn't seem to work on 1.7.

[cartrite]

When he first reported he posted a link to a similar problem with windows. On that link it was corrupted fonts. He probably has corrupted fonts that are part of his windows OS.

[john71]

No, fonts were not changed. And the only place where we replace invalid chars with that square is in tokenizer (the part of code which reads config file and catalogs). The only way to find the root cause is to use git bisect to find the commit which introduced the bug. But this is not reproducible in GLU/Linux nor macOS so we can't do this.

Maybe I have another clue.

I downloaded the "Post #1052by cartrite » 20.07.2021, 22:09" version setup, and this has not produced the "rectangular numbers" bug.

So it must have been a change between 2021.07.20 and the last version a few weeks ago.

[cartrite]

Strange thing is why is it only happening to you? That probably dismisses what I just posted above.

[john71]

I think it is not so strange, you should have only a few dozens of installations worldwide considering the latest builds.

[trappistplanets]

I didn't realize that people were still using 32 bit operating systems. You must have a 32 bit machine and it must be very old. But I'll look into getting 32 bit libs for celestia. I will not get the qt5 32bit libs though. It's too big and it will take too much time to build, so celestia-qt 32 bit will not be built.

seven helped me get celestia 1.7.0 to run but there is this problem on my end, how do i fix, star rendering is on?

areas above terminator marker should be daylight

Added after 10 minutes 40 seconds:
everything is affected with this bug other than the irregular moons of the jovian and ice planets that have meshes and planets with more than one star

[onetwothree]

Provide celestia-shaders.log please

[trappistplanets]

here

[john71]

OK. I found another strange bug while I wanted to document the "rectangles instead of numbers" bug.

The captured screen video (from inside of Celestia) is obviously wrong, it is transformed or flipped.

Here is the video (you can see the rectangles at the lower left corner!):

celestia video errors.zip