Fonts unreadable in 0.10.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Stellarium |
Fix Released
|
High
|
Unassigned |
Bug Description
My graphics card is an older Radeon 9600 TX card with new drivers. Star labels and the labels in the main menu bars are virtually unreadable.
http://
http://
Other operations are nominal.
This is new since I installed Stellarium 0.10.4.
Hartwig
2010-02-22T21:21:26
Windows XP
Compiled with GCC 4.4.0
Qt runtime version: 4.6.2
Qt compilation version: 4.6.2
Addressing mode: 32-bit
Total memory: 1535 MB (unreliable)
Total virtual memory: 2047 MB (unreliable)
Physical memory in use: 36%
Processor speed: 2605 MHz
Processor name: Intel(R) Pentium(R) 4 CPU 2.60GHz
C:\Programme\
------
[ This is Stellarium 0.10.4 - http://
[ Copyright (C) 2000-2010 Fabien Chereau et al ]
------
Writing log file to: "C:/Dokumente und Einstellungen/
File search paths:
0 . "C:\Dokumente und Einstellungen\
1 . "."
Attempting to use an existing older config file.
Config file is: "C:\Dokumente und Einstellungen\
Qt GL paint engine is: "OpenGL2"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
Cache directory is: "C:\Dokumente und Einstellungen\
Sky language is "de"
Application language is "de"
Loading Solar System data ...
Loaded 38 / 38 planet orbits
Loading star data ...
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
Finished loading star catalogue data, max_geodesic_level: 3
navigation/
Loaded 10051 NGC records
Loading NGC name data ...
Loaded 222 / 222 NGC name records successfully
Loaded 88 / 88 constellation records successfully for culture "western"
Loaded 85 / 85 constellation art records successfully for culture "western"
Loaded 89 / 89 constellation names
Loading constellation boundary data ...
Loaded 782 constellation boundary segments
Loading star names from "./skycultures/
Loaded 230 / 230 common star names
Loading star names from "./stars/
Loaded 3215 / 4359 scientific star names
Creating GUI ...
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
Downloaded 0 files (0 kbytes) in a session of 11.828 sec (average of 0 kB/s + 0 files from cache (0 kB)).
drasnor (drew-beckett) wrote : | #1 |
Bogdan Marinov (daggerstab) wrote : | #2 |
Could you please try adding to the configuration file, under "[main]", "use_qpaintengi
(On Windows, Stellarium's configuration file, config.ini, is accessible through a shortcut in Stellarium's Start menu folder.)
astrohardy (fb4a042) wrote : | #3 |
Great improvement.
On the startup screen, on the star display itself and in the left menu bar all symptoms are gone and all labels are clearly readable.
On the bottom menu bar the fonts are still nearly unreadable. This, however, was also the case in Stellarium 0.10.3, may be a different problem and is not so problematic,
Thanx a lot
Hartwig
drasnor (drew-beckett) wrote : | #4 |
I have the same result; the star display and startup screen now look fine but the bottom menu bar is still illegible.
Lew (lwakeman) wrote : Re: [Bug 525995] Re: Fonts unreadable in 0.10.4 | #5 |
- stellarium_screen_cap.png Edit (313.6 KiB, image/png; name="stellarium_screen_cap.png")
- stellarium_screen_cap.jpg Edit (74.7 KiB, image/jpeg; name="stellarium_screen_cap.jpg")
Thank you for your quick response. This helped tremendously! Almost!
But, like the previous user, all the labels within the application seem to
be fine now, but the bottom menu fonts are still garbled.
I have attached a screen shot for your review to see if that helps. I have
included a couple different formats.
Thanks again.
Lew.
On Tue, Feb 23, 2010 at 12:33 AM, Bogdan Marinov <email address hidden>wrote:
> Could you please try adding to the configuration file, under "[main]",
> "use_qpaintengi
>
> (On Windows, Stellarium's configuration file, config.ini, is accessible
> through a shortcut in Stellarium's Start menu folder.)
>
> --
> Fonts unreadable in 0.10.4
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Stellarium: New
>
> Bug description:
> My graphics card is an older Radeon 9600 TX card with new drivers. Star
> labels and the labels in the main menu bars are virtually unreadable.
> http://
> http://
>
> Other operations are nominal.
>
>
> This is new since I installed Stellarium 0.10.4.
>
> Hartwig
>
>
>
> 2010-02-22T21:21:26
> Windows XP
> Compiled with GCC 4.4.0
> Qt runtime version: 4.6.2
> Qt compilation version: 4.6.2
> Addressing mode: 32-bit
> Total memory: 1535 MB (unreliable)
> Total virtual memory: 2047 MB (unreliable)
> Physical memory in use: 36%
> Processor speed: 2605 MHz
> Processor name: Intel(R) Pentium(R) 4 CPU 2.60GHz
> C:\Programme\
> -------
> [ This is Stellarium 0.10.4 - http://
> [ Copyright (C) 2000-2010 Fabien Chereau et al ]
> -------
> Writing log file to: "C:/Dokumente und Einstellungen/
> Brorsen/
> File search paths:
> 0 . "C:\Dokumente und Einstellungen\
> Brorsen\
> 1 . "."
> Attempting to use an existing older config file.
> Config file is: "C:\Dokumente und Einstellungen\
> Brorsen\
> Qt GL paint engine is: "OpenGL2"
> QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
> "
> QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
> "
> Cache directory is: "C:\Dokumente und Einstellungen\
> Einstellungen\
> Sky language is "de"
> Application language is "de"
> Loading Solar System data ...
> Loaded 38 / 38 planet orbits
> Loading star data ...
> QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
> "
> "Loading "./stars/
> "Loading "./stars/
> "Loading "./stars/
> "Loading "./stars/
> Finished loading star catalogue data, max_geodesic_level: 3
> navigation/
> Loa...
Lew (lwakeman) wrote : | #6 |
Thank you for your quick response. This helped tremendously! Almost! All
the labels within the application seem to be fine now, but the menu at the
bottom is still garbled.
I have attached a screen shot for your review to see if that helps.
Thanks again.
Lance.
On Tue, Feb 23, 2010 at 12:33 AM, Bogdan Marinov <email address hidden>wrote:
> Could you please try adding to the configuration file, under "[main]",
> "use_qpaintengi
>
> (On Windows, Stellarium's configuration file, config.ini, is accessible
> through a shortcut in Stellarium's Start menu folder.)
>
> --
> Fonts unreadable in 0.10.4
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Stellarium: New
>
> Bug description:
> My graphics card is an older Radeon 9600 TX card with new drivers. Star
> labels and the labels in the main menu bars are virtually unreadable.
> http://
> http://
>
> Other operations are nominal.
>
>
> This is new since I installed Stellarium 0.10.4.
>
> Hartwig
>
>
>
> 2010-02-22T21:21:26
> Windows XP
> Compiled with GCC 4.4.0
> Qt runtime version: 4.6.2
> Qt compilation version: 4.6.2
> Addressing mode: 32-bit
> Total memory: 1535 MB (unreliable)
> Total virtual memory: 2047 MB (unreliable)
> Physical memory in use: 36%
> Processor speed: 2605 MHz
> Processor name: Intel(R) Pentium(R) 4 CPU 2.60GHz
> C:\Programme\
> -------
> [ This is Stellarium 0.10.4 - http://
> [ Copyright (C) 2000-2010 Fabien Chereau et al ]
> -------
> Writing log file to: "C:/Dokumente und Einstellungen/
> Brorsen/
> File search paths:
> 0 . "C:\Dokumente und Einstellungen\
> Brorsen\
> 1 . "."
> Attempting to use an existing older config file.
> Config file is: "C:\Dokumente und Einstellungen\
> Brorsen\
> Qt GL paint engine is: "OpenGL2"
> QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
> "
> QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
> "
> Cache directory is: "C:\Dokumente und Einstellungen\
> Einstellungen\
> Sky language is "de"
> Application language is "de"
> Loading Solar System data ...
> Loaded 38 / 38 planet orbits
> Loading star data ...
> QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
> "
> "Loading "./stars/
> "Loading "./stars/
> "Loading "./stars/
> "Loading "./stars/
> Finished loading star catalogue data, max_geodesic_level: 3
> navigation/
> Loaded 10051 NGC records
> Loading NGC name data ...
> Loaded 222 / 222 N...
m kroeger (mkkroeger) wrote : | #7 |
Same for me. This also fixed nearly immediate crashing. The bottom menu fonts are unreadable.
This is two releases in a row that have introduced profound display problems affecting a large portion of the user-base. The solution to both has been "false-ing" out various things, which is quite different than actually addressing the problem. Just as an expression of user-frustration: it would be nice if there was some testing done before release. I am hoping for a quick update that introduces no further headaches.
tochiro (bertrand-brebis) wrote : | #9 |
Same problem here and I fully agree with cm above. Stellarium is a wonderful program and it's a pity it suffers such obvious problems.
Bogdan Marinov (daggerstab) wrote : | #10 |
"(...) it would be nice if there was some testing done before release."
There was. Unfortunately, few people volunteer to be testers, so any testing is limited to the not-so-great variety of hardware available to the developers.
The reason for the "two releases in a row" is the varying level of support for OpenGL shaders and the fact that the last release of Qt uses implicitly shaders for some things by default.
drasnor (drew-beckett) wrote : | #11 |
Bogdan Marinov said,
"The reason for the "two releases in a row" is the varying level of support for OpenGL shaders and the fact that the last release of Qt uses implicitly shaders for some things by default."
Is this a Qt issue? What would be a good way to start working the problem from that direction?
Fabien Chéreau (xalioth) wrote : | #12 |
"(...) it would be nice if there was some testing done before release."
For this release, we had to do a compromise for the default value for the flags. Each combination of flags causes trouble on various hardware usually because of buggy openGL drivers.
crn, tochiro: we are not paid for this tedious work which consist in testing as many configurations as possible and trying to find out what goes wrong in each cases. So until you offer us a machine on which the bug can be reproduced we cannot do much. Another better solution is that you fix the bug yourself and send us the patch, or at least provide useful constructive comments to help us tracking it down.
Fabien
tochiro (bertrand-brebis) wrote : | #13 |
I do agree with cm and some testing should have been done because the bug we are dealing now is very basic.
But I see you only want to be praised and thanked for your hard unpaid work. You do not like when users are dissatisfied.
I should remember you that YOU have decided to do this software as unpaid work (well, as far as I know) and I did not force you.
And now I can decide to not use your software anymore and not spend my time here. Life is too short... And you are constructive yourself...
Good luck!
drasnor (drew-beckett) wrote : | #14 |
Bogdan Marinov, you mentioned that the problem may have something to do with the default shader level Qt uses. Where would I look to change Qt's behavior to something other than default?
SteveTuttle (seeker052) wrote : | #15 |
Fabien, thanks for all of your work. It is unfortunate that some people do not understand the difficulties of testing in an environment with so many variations. As far as some of these comments, "they" did not force you to work on this, but no one has forced "them" to use it. These kinds of issues will continue to crop up on such a complicated piece of software, attempting to stitch together multilple libraries such as Qt and Open/Gl. I am using 0.10.2 with no issues (Vista) and I have been testing 0.10.3 also working with no problems. I suggest that if people want to complain, they should instead volunteer to be beta testers.
I am not in a good position to complie a build from scratch, but I will gladly test any build on my setup once it is compliled. Keep up the excellent work.
Steve T.
REWard (reward) wrote : | #16 |
Amen Steve T.!!!
Love the program and the people (like Fabien) who take the time (their time) to give us such great and wonderful things to enjoy in our lives... Anyhow the programs we overpay for give us as much, if not more problems/issues! I am glad to do what I can to help when these issues arise, and these forums where we all work together is the way it gets done!
As far as tochiro goes, they can't even tell the difference between cm & crn!!!
Bogdan Marinov (daggerstab) wrote : | #17 |
To everyone: Please limit the discussion to the bug. This is not the place for this kind of flaming. Thank you.
"Where would I look to change Qt's behavior to something other than default?"
It can be done only by the program itself. See QPaintEngine's documentation:
http://
The "use_qpaintengi
Again, sufficient testing requires testers - people who volunteer to test pre-release builds of Stellarium on various kinds of hardware. Stellarium's team is only a handful of people who contribute in various directions, the OpenGL stuff is handled mainly by Fabien.
Tom (tom-mills9) wrote : | #18 |
After updating from 0.10.2 to 0.10.4 stellarium would crash on start up but adding "use_qpaintengi
Graphics card is ATI Radeon x600
Windows XP
Compiled with GCC 4.4.0
Qt runtime version: 4.6.2
Qt compilation version: 4.6.2
Addressing mode: 32-bit
Total memory: 2046 MB (unreliable)
Total virtual memory: 2047 MB (unreliable)
Physical memory in use: 45%
Processor speed: 3391 MHz
Processor name: Intel(R) Pentium(R) 4 CPU 3.40GHz
Processor speed: 3391 MHz
Processor name: Intel(R) Pentium(R) 4 CPU 3.40GHz
C:\Program Files\Stellariu
------
[ This is Stellarium 0.10.4 - http://
[ Copyright (C) 2000-2010 Fabien Chereau et al ]
------
Writing log file to: "C:/Documents and Settings/
File search paths:
0 . "C:\Documents and Settings\
1 . "."
Attempting to use an existing older config file.
Config file is: "C:\Documents and Settings\
Qt GL paint engine is: "OpenGL"
Cache directory is: "C:\Documents and Settings\user\Local Settings\
Sky language is "en"
Application language is "en"
Loading Solar System data ...
Loaded 38 / 38 planet orbits
Loading star data ...
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
"Loading "C:\Documents and Settings\
"Loading "C:\Documents and Settings\
"Loading "C:\Documents and Settings\
"Loading "C:\Documents and Settings\
ERROR: SpecialZoneArray( 8 )::SpecialZoneA
"Loading "C:\Documents and Settings\
Finished loading star catalogue data, max_geodesic_level: 7
navigation/
Loaded 10051 NGC records
Loading NG...
chue85 (chue85) wrote : | #19 |
i added "use_qpaintengi
Argentinian guy (sinapsis564-nospam) wrote : | #20 |
Same problem goning on here... It seems the problem is with ATI cards, I've got an integrated ATI radeon X1250 and my stellarium looks exactly like in the caps. One thing that improved the readability a little is turning off ClearType on WinXP.
faluco (borja-ferav) wrote : | #21 |
- stel_patched.rar Edit (4.2 MiB, application/rar)
Hello, there has been two patches fixing blurry fonts and menus in SVN. I'm attaching here a rar file with a patched version with these fixes to see if they fix all your font issues or otherwise this needs further investigation.
Just replace both files in the stellarium directory (only valid for 0.10.4). See if setting use_qpaintenginegl2 to true again is messed, and if setting it to false fixes the menu issues.
I hope this helps.
Argentinian guy (sinapsis564-nospam) wrote : | #22 |
Thanks Faluco!!! with the patch and use_qpaintenginegl2 = true there's no difference, but with use_qpaintenginegl2 = false all problems are gone!!!
Now Stellarium is working fine, all fonts are prefectly rendered.
Great job guys!!!
Thanks for maintaining this great software for free, and still spend lots of your precious hours into developing and debugging it!!
Greetings from Argentina
astrohardy (fb4a042) wrote : | #23 |
great, now my problem is completely solved. Thanks Faluco!
Hartwig
Orion105 (orion105) wrote : | #24 |
yes, this is true the fonts are hard to read and the "fps" is hovering around 5 to 8 fps!,
this a major catastrophe!
i installed the patch, it did not work! at all, STILL the same problem, what else can go wrong!:(
chue85 (chue85) wrote : | #25 |
thanks faluco, totally readable but only with use_qpaintenginegl2 = false, do not work with use_qpaintenginegl2 = true, here some images:
http://
http://
im running windows xp sp3, my graphic card is ATi radeon x1300 latest driver (10.2)
Orion105
did u add the line: use_qpaintenginegl2 = false
to the [main] section of the config.ini file????
Changed in stellarium: | |
status: | New → Fix Committed |
faluco (borja-ferav) wrote : | #26 |
Great news then. Everybody just set use_qpaintenginegl2 to false, it seems some ATI cards (probably oldest ones) have some rendering issues with opengl2 thats why you need to set it back to false to use opengl1 to get sharp fonts.
I guess this can be closed now since it's fixed in SVN and will get released in next version.
Fabien Chéreau (xalioth) wrote : | #27 |
Hi guys,
Thanks for the help everyone. I would need some more help from someone who experiences the problem with use_qpaintenginegl2 = true (or no value by default) and who is willing to compile and test some changes in the code.
In the future OpenGL2 engine will be the norm, so I would like to fix this bug as well.
Could someone try to change some parameters in the constructor of StelMainGraphic
Fabien
AB. (artem-bzr) wrote : | #28 |
Hello :)
I got all this problems with bad rendering even with use_qpaintenginegl2 = true (menu problem). That freaky problems on my Ati R9600 since 0.10.*. And I can help to test all new versions if someone will compile it for me because i don't have needed apps.
Thanks
Graham (tograhamr) wrote : | #29 |
Faluco your a star!!
Thanks a million!! :-)
Graham
joebot94 (joebot94) wrote : | #30 |
this may sound like a stupid question but where do u put the patch exactly i am running xp thanks for your help
AB. (artem-bzr) wrote : | #31 |
I've tried stel_patched.rar with that options:
use_glshaders = false
use_qpaintenginegl2 = false
And it resolved the problem. But without that lines - problem persists.
joebot94 (joebot94) wrote : | #32 |
ok but where do i put the rar file i dont know how to put it in the folder or which one i should put it in
Bogdan Marinov (daggerstab) wrote : | #33 |
joebot94,
That .rar file is an archive. You need to open it first and extract the files in it. It contains patched versions of the Stellarium .exe and .dll files. Just put them in Stellarium's folder in Program Files, so that they overwrite the installed .exe and .dll files.
joebot94 (joebot94) wrote : | #34 |
thank you how do i open it do i need a program sorry if i am a pain
joebot94 (joebot94) wrote : | #35 |
omg thank you so much this program if i find out a way to control my telescope with it will become the coolest program ever can anyone tell me how i can control my telescope with this program it says i can but it doesnt say how thanks
YuriG (lapizarradeyurigagarin) wrote : | #36 |
I am sorry but not working. :(
I have applied the patch to my installation folder, and added the lines
use_glshaders = false
use_qpaintenginegl2 = false
to the config file. But the strange fonts are still there.
Video card:
Radeon X850 series.
Log file:
2010-03-16T18:32:36
Windows XP
Compiled with GCC 4.4.0
Qt runtime version: 4.6.2
Qt compilation version: 4.6.2
Addressing mode: 32-bit
Total memory: 2047 MB (unreliable)
Total virtual memory: 2047 MB (unreliable)
Physical memory in use: 43%
Processor speed: 2607 MHz
Processor name: Dual Core AMD Opteron(tm) Processor 185
Processor speed: 2607 MHz
Processor name: Dual Core AMD Opteron(tm) Processor 185
C:\Archivos de programa\
------
[ This is Stellarium 0.10.4 - http://
[ Copyright (C) 2000-2010 Fabien Chereau et al ]
------
Writing log file to: "C:/Documents and Settings/
File search paths:
0 . "C:\Documents and Settings\
1 . "."
Attempting to use an existing older config file.
Config file is: "C:\Documents and Settings\User\Datos de programa\
Qt GL paint engine is: "OpenGL2"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
Cache directory is: "C:\Documents and Settings\
Sky language is "es"
Application language is "es"
Loading Solar System data ...
Loaded 38 / 38 planet orbits
Loading star data ...
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
"Loading "C:\Documents and Settings\
Finished loading star catalogue data, max_geodesic_level: 4
navigation/
Loaded 10051 NGC records
Loading NGC name data ...
Loaded 222 / 222 NGC name records successfully
Loaded 88 / 88 constellation records successfully for culture "western"
Loaded 85 / 85 constellation art records successfully for culture "western"
Loaded 89 / 89 constellation names
Loading constellation boundary data ...
Loaded 782 constellation boundary segments
Loading star names from "./skycultures/
Loaded 230 / 230 common star names
Loading star names from "./stars/
Loaded 3215 / 4359 scientific star names
Creating GUI ...
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
Downloaded 0 files (0 kbytes) in a session of 10.984 sec (average of 0 kB/s + 0 files from cache (0 kB)).
Thank you in advance!
Bogdan Marinov (daggerstab) wrote : | #37 |
YuriG, are you sure you have put the lines in the configuration file in the right place (under [main])? Your log file shows that your Stellarium is still using OpenGL2.
Fabien Chéreau (xalioth) wrote : | #38 |
You have to edit the C:\Documents and Settings\User\Datos de programa\
Fabien
Changed in stellarium: | |
assignee: | nobody → tom (gcrimi30) |
Changed in stellarium: | |
assignee: | tom (gcrimi30) → nobody |
Bernardo Pombo (bpombo) wrote : | #39 |
I am sorry but not working. :(
I have applied the patch to my installation folder, and added the lines
use_glshaders = false
use_qpaintenginegl2 = false
to the config file. But the strange fonts are still there.
Video Card:
Intel GMA3000
2010-03-23T22:33:59
Windows XP
Compiled with GCC 4.4.0
Qt runtime version: 4.6.2
Qt compilation version: 4.6.2
Addressing mode: 32-bit
Total memory: 2047 MB (unreliable)
Total virtual memory: 2047 MB (unreliable)
Physical memory in use: 33%
Processor speed: 2991 MHz
Processor name: Intel(R) Pentium(R) 4 CPU 3.00GHz
Processor speed: 2991 MHz
Processor name: Intel(R) Pentium(R) 4 CPU 3.00GHz
C:\Archivos de programa\
------
[ This is Stellarium 0.10.4 - http://
[ Copyright (C) 2000-2010 Fabien Chereau et al ]
------
Writing log file to: "C:/Documents and Settings/
File search paths:
0 . "C:\Documents and Settings\
1 . "."
Attempting to use an existing older config file.
Config file is: "C:\Documents and Settings\
WARNING StelFileMgr:
WARNING: problem while setting screenshot from config file setting: NOT_VALID
Qt GL paint engine is: "OpenGL"
Cache directory is: "C:\Documents and Settings\
Sky language is "es"
Application language is "es"
Loading Solar System data ...
Loaded 38 / 38 planet orbits
Loading star data ...
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
Finished loading star catalogue data, max_geodesic_level: 3
navigation/
Loaded 10051 NGC records
Loading NGC name data ...
Loaded 222 / 222 NGC name records successfully
Loaded 88 / 88 constellation records successfully for culture "western"
Loaded 85 / 85 constellation art records successfully for culture "western"
Loaded 89 / 89 constellation names
Loading constellation boundary data ...
Loaded 782 constellation boundary segments
Loading star names from "./skycultures/
Loaded 230 / 230 common star names
Loading star names from "./stars/
Loaded 3215 / 4359 scientific star names
Creating GUI ...
Loaded plugin "AngleMeasure" .
AngleMeasure plugin - press control-A to toggle angle measure mode
Loaded plugin "CompassMarks" .
CompassMarks plugin - press control-C to toggle compass marks
Loaded plugin "Oculars" .
Ocular plugin - press Command-o to toggle eyepiece view mode. Press ALT-o for configuration.
Oculars:
Changed in stellarium: | |
status: | Fix Committed → Incomplete |
Bogdan Marinov (daggerstab) wrote : | #40 |
The "Incomplete" status is used when the user reporting the bug has not provided enough information.
Bernardo Pombo,
could you please attach a screenshot? (From the "Add attachment or patch" link below the comment field.)
Also, could you please try downloading this file:
http://
and replacing with it the "xyYToRGB.glsl" file that is in "shaders" in "data" in your installation directory.
Changed in stellarium: | |
importance: | Undecided → High |
status: | Incomplete → Confirmed |
Bogdan Marinov (daggerstab) wrote : | #41 |
To the people who still have problems after the patch: There's a test build for the next version here:
https:/
Could you please try it and report the results? It is recommended to delete your old configuration file first.
Juzer (kontofgh) wrote : | #42 |
Almost good, remain only two small problem: http://
faluco (borja-ferav) wrote : | #43 |
Tested in my netbook which can only run OpengGL1 (integrated Intel card) and worked without any problems, all fonts are sharp and clear.
Jarda Kristen (kristen-volny) wrote : | #44 |
I am experiencing an identical problem when upgrading from 0.10.2 to 0.10.4. I am using Windows XP Pro 32-bit and have an old Albatron's FX5200LP graphics card. In 0.10.2 was everything OK. I reinstaled 0.10.4 back to 0.10.2. and evetything is OK like was.
Bogdan Marinov (daggerstab) wrote : | #45 |
Jarda Kristen, could you please download the test build from here:
https:/
And report if there is a difference?
If some of the text in the test build is unreadable, try the following: in Stellarium's configuration file (config.ini), under "[main]", add the following line:
use_qpaintenginegl2 = false
Then save the file and restart Stellarium.
(On Windows, Stellarium's configuration file is accessible through Stellarium's folder in the Start menu - just look for "config.ini".)
Dr. Christof Lehmann (dr-christof-lehmann) wrote : | #46 |
Hello.
Wonderful program, but the bug renders the program more or less useless. I would like NOT to delete the program and forget about it - that is, if someone could provide a step by step " understandable " way of fixing it, that does not require programming skills which I do not have. Neither do I want to waste my time at acquiring them. I have other specialties and interests.
Maybe the solutions above work out fine, and thank´s for those who provided them, but it really isn´t helpful unless one has the time and skills to learn programming first.
A simple - do this, type that - then paste this "there " press this would be helpful.
Thank YOU. :)
Christof
Bogdan Marinov (daggerstab) wrote : | #47 |
Dr. Christof Lehmann,
If your operating system is Windows, please read the previous comment
for instructions:
https:/
If you have any problems with the instructions, you can ask here:
https:/
If your operating system is not Windows, you have no choice but to
wait for the next release (0.10.5).
Matthew Gates (matthew-porpoisehead) wrote : | #48 |
I added a command line option --safe-mode which disables GL shaders and the GL Engine 2 for one run only (nothing is changed in the config.ini file).
Jarda Kristen (kristen-volny) wrote : | #49 |
Hi,
thank you for your advise. I used advices from your pages. Everything
is OK now. Thank you very much for your help.
Best regards... :o))
Jaroslav
----- PŮVODNÍ ZPRÁVA -----
Od: "Bogdan Marinov" <email address hidden>
Komu: <email address hidden>
Předmět: Re: [Bug 525995] Re: Fonts unreadable in 0.10.4
Datum: 17.4.2010 - 14:59:34
> Dr. Christof Lehmann,
>
> If your operating system is Windows, please read the
> previous comment
> for instructions:
> https:/
>
> If you have any problems with the instructions, you
> can ask here:
> https:/
>
> If your operating system is not Windows, you have no
> choice but to
> wait for the next release (0.10.5).
>
> --
> Fonts unreadable in 0.10.4
> https:/
> You received this bug notification because you are
> a direct subscriber
> of the bug.
>
> Status in Stellarium: Confirmed
>
> Bug description:
> My graphics card is an older Radeon 9600 TX card with
> new drivers. Star labels and the labels in the main
> menu bars are virtually unreadable.
> http://
> http://
>
> Other operations are nominal.
>
>
> This is new since I installed Stellarium 0.10.4.
>
> Hartwig
>
>
>
> 2010-02-22T21:21:26
> Windows XP
> Compiled with GCC 4.4.0
> Qt runtime version: 4.6.2
> Qt compilation version: 4.6.2
> Addressing mode: 32-bit
> Total memory: 1535 MB (unreliable)
> Total virtual memory: 2047 MB (unreliable)
> Physical memory in use: 36%
> Processor speed: 2605 MHz
> Processor name: Intel(R) Pentium(R) 4
> CPU 2.60GHz
> C:\Programme\
> -------
>
> [ This is Stellarium 0.10.4 - http://
> ]
> [ Copyright (C) 2000-2010 Fabien Chereau et al
> ]
> -------
>
> Writing log file to: "C:/Dokumente und Einstellungen/
> Brorsen/
> File search paths:
> 0 . "C:\Dokumente und Einstellungen\
> >
> 1 . "."
> Attempting to use an existing older config file.
> Config file is: "C:\Dokumente und Einstellungen\
> Brorsen\
> Qt GL paint engine is: "OpenGL2"
> QGLShader::link: "Fragment shader(s) linked, vertex
> shader(s) linked.
> "
> QGLShader::link: "Fragment shader(s) linked, vertex
> shader(s) linked.
> "
> Cache directory is: "C:\Dokumente und Einstellungen\
> Brorsen\Lokale Einstellungen\
> >
> Sky language is "de"
> Application language is "de"
> Loading Solar System data ...
> Loaded 38 / 38 planet orbits
> Loading star data ...
> QGLShader::link: "Fragment shader(s) linked, vertex
> shader(s) linked.
> "
> "Loading "./stars/
> 5013"
> "Loading "./stars/
> 21999"
> "Loading "./stars/
> 151416"
> "Loading "./stars/
> ...
Paolo N (paolo-paola) wrote : | #50 |
Thanks for the wonderful program. The greek labels for stars were not properly shown (looked as "box" characters) using the released 0.10.4 version. My graphic card is a GeForce Go 6200. Adding use_glshaders = false and use_qpaintenginegl2 = false lines in config.ini made no difference. With the new test version everything got fine setting use_qpaintenginegl2 = false.
SteveTuttle (seeker052) wrote : | #51 |
I have just uninstalled stellarium-
Under r6054, i have noticed no problems with fonts, or any other problems, runs great.
In 6155, the fonts are garbled (some characters ok, some not and all are difficult to read) for the information for the selected object (printed inthe upper left corner of the screen) and for the short descriptions for the GUI buttons when hovering over the buttons. The HIP stars were preceded by some extraneous characters, but not other objects. All other functions/
My setup is Vista, Dell Inspron 1525, Intel Mobile 965 Express graphics card (integrated).
I tried various combinations of the use_glshaders = false/true and use_qpaintenginegl2 = false/true in the [main] section of the config.ini, all with no effect on the issues for 6155. I have reinstalled 6054, all is working well.
I hope this helps, Steve T.
Fabien Chéreau (xalioth) wrote : | #52 |
The line causing the troubles have been reverted in rev 6156.
Thanks,
Fabien
SteveTuttle (seeker052) wrote : | #53 |
I have just tested the test-build r6184. All of the text looks great and all of my scripts run properly with no problems. I will continue to test, but so far it looks great.
My setup is Vista, Dell Inspron 1525, Intel Mobile 965 Express graphics card (integrated).
Thanks, Steve T.
SteveTuttle (seeker052) wrote : | #54 |
I have now had time to test r6184 on my older Dell 6000, with 2GB mem, WinXP SP3, and an ATI Mobility Radeon X300. So far I have noticed no problems with text or anything else, all seems well. I have also tested this version on Older Dells at work, with 1GB mem, Intel video cards and XP SP3. That also seems to work well. I will keep testing and let you know how it goes.
Steve T.
pedemoz (pedemoz) wrote : | #55 |
I've been testing r6268 on WinXP SP3 with a GeForce Go 6800.
Since 0.10.3 I've had major problems with the fonts and some other OpenGL related issues, and so have stuck with 0.10.2 until now. I was able to get 0.10.4 working with a r6175 patch and, crucially, using 'use_qpaintengi
I've run a clean install of r6268 30+ times to try and get some repeatability. To produce the font problems, I only have to run and then turn off the atmosphere - as soon as I then pan around there is a 2-3 second pause and the fonts are stuffed. However, if I mouse over the tool bars and click on a star, I don't get the font problems. If I only mouse over the toolbar OR only select a star, I usually get font problems. (The 'Angle Measurement' plugin fonts are always messed up under GL2, but that's a separate issue.)
My guess is that buffers are not being properly allocated or initialised or there is memory corruption if the text of the toolbars and info display aren't invoked first. But I'm also suspicious about problems due to delayed loading of textures, etc. Is there any cmd line switch or config file parameter to force loading of all catalogues, textures, etc., at start-up as per v0.10.2?
Keep up the great work and try to keep the community involved.
P.
Fabien Chéreau (xalioth) wrote : | #56 |
Hi pedemoz,
Thanks for the useful comments. It's interesting that the AngleMeasure plugin has always messed up fonts. Do you know how to compile the code? If yes it would be very helpful to make some test changing some openGL states in the AngleMeasure:
Fabien
pedemoz (pedemoz) wrote : | #57 |
On Linux yes, Windows no. But I'll set something up and get back to you. In the mean time, if you have any specific ideas, please forward them to me.
P.
SteveTuttle (seeker052) wrote : | #58 |
I have tested r6326 by hand and using scripts.
My setups are both laptops:
1) Vista, Dell Inspiron 1525, 3GB mem, and an Intel Mobile 965 Express graphics card.
- No problems, fonts all good, other functions appear normal.
2) WinXp SP3, Dell 6000, with 2GB mem, and an ATI Mobility Radeon X300 graphics card.
- Fonts all good.
- Two minor issues (not noticed in previous test versions):
- ONE, typing into the Search Tool (for example), the text lags the actual typing by up to two seconds.
By the time I type "Jupiter", the display in the Search tool only contains "Ju" and takes another one to two seconds to
complete and then perform the search.
- TWO, when I select a planet and zoom in, the planet's png texture is not visible. If I wait about two to three seconds,
the texture appears. Once the texture appears for an object, if I leave that object and return later, the texture
appears immediately, as expected.
Hope this helps, keep up the great work,
Steve T.
SteveTuttle (seeker052) wrote : | #59 |
I have been testing build 6364 on Vista and XP laptops. In both cases and at random, I can open Stellarium and click on a star. The information block in the upper left is all ok and readable. I then exit Stellarium, restart it, click on the same star and the information block is unreadable with garbbled text. I have repeated this process with random results of readable and unreadable text.
If there is anything else you want me to try and test, let me know.
Steve T.
faluco (borja-ferav) wrote : | #60 |
Hello Steve, let me ask you two things:
1) Is this only happening when using OpenGL1?
2) Do you have a rough estimate of since what revision or test build is this happening?
I'm able to reproduce the issue only in opengl1 mode. Maybe the issue going on here is similar to what pedemoz mentioned above, although i cant reproduce the 2 second pause he mentions. Since this is happening on startup and depends on previous program launches it sounds as an opengl buffer problem. Fabien do you have any suggestions or tests we could make to test this out? (I'm able to compile code).
I've attached a screenshot showing the problem, it shows the object info, and the help labels.
pedemoz (pedemoz) wrote : | #61 |
I'm finally set up to compile under Windows (previously only Linux), so I can do some more Windows-based testing. There are some issues building under Windows but that's for another report.
Somewhat frustratingly, my font problems have disappeared - normally a good thing, but this time I really am annoyed as I wanted to investigate where the problems were coming from! Other than installing all the Qt-related stuff, the only changes were some Windows monthly updates that were installed at a reboot. I'm contemplating how to get back to where I was, pre-updates... (I should also add - fonts are working with all versions, using both OpenGL1 and 2, with 0.10.4 being the oldest tested.)
faluco- Have you tried the process I detailed? (run the mouse cursor over the toolbars and select a star before panning around) I really only had problems with OpenGL2 but perhaps the same process will work for you.
Steve - I do have the same problems as you, namely slow response to keyboard entry (there is a 1-3 second delay before Stellarium responds) and the planet textures are slow to display. What happens when you use the arrow keys to pan around? I get a delay and then it moves for much longer than I had the key pressed (as if there is a delay in processing the key-up event). With all of the 0.10.5 derivatives, I get this using OpenGL1 or 2 but panning with the mouse is perfectly smooth. Everything is more response under 0.10.4 and the frame rate is about 60 compared to 30 under 0.10.5. Limiting the FPS under 0.10.5 to about 20 FPS improves responsiveness, which again suggests too much time is being consumed by the graphics sub-routines or there are some timer problems.
Fabien - If you have an approximate idea which commit may have affected the frame rates and keyboard responsiveness, let me know and I'll work through to find the cause.
faluco (borja-ferav) wrote : | #62 |
Hello pedemoz, i've done what you described but i cant reproduce the pauses either with opengl1 or 2. So probably there's something different in my setup. As i mentioned in my previous post, i can only reproduce the font corruption problems in opengl1.
Two days ago i was able to reproduce the slow loading of planet textures like you mentioned, but i didnt test the keyboard response, i'll test it if im able to reproduce this again.
pedemoz (pedemoz) wrote : | #63 |
Just determined - low frame rate and slow keyboard response are due to grid lines (az/alt, etc.) and/or constellation boundary lines. I vaguely recall there being a patch to do with that but it's obviously still NQR. Turn all 'lines' off and FPS back to 60 at smooth(ish) panning (not quite as good as 0.10.2 but I only had 30 fps then). Also, no problems with textures when grid lines turned off, but we're getting way off topic here...
SteveTuttle (seeker052) wrote : | #64 |
Faluco and pedemoz
I have had slow typing and slow planet textures since r6326, on XP only. I have been using r6402 today on both machines, and I still get the random garbbled text on both machines. I think I am only using OpenGL1, the log says "OPEN/GL". Are there still switches to change to OpenGL2 ? I am happy to try that. I have not tried panning with the keys, will try shortly.
My setups:
1) Vista, Dell Inspiron 1525, 3GB mem, and an Intel Mobile 965 Express graphics card.
2) WinXp SP3, Dell 6000, with 2GB mem, and an ATI Mobility Radeon X300 graphics card.
Steve T.
faluco (borja-ferav) wrote : | #65 |
Hello Steve, opengl2 is used automatically if your card supports it unless you're forcing to use opengl1 by adding "use_qpaintengi
To see in which mode you're running inside stellarium go to Help->Log tab and look for the line "Qt GL paint engine is: "
My laptop uses an intel integrated card like yours, and it doesnt support opengl2, no idea about the ATI one.
About your issue getting garbled text with this revision: you should force using opengl1 adding "use_qpaintengi
Let me know if doing this fixes it.
faluco (borja-ferav) wrote : | #66 |
In fact, i think the safe mode shortcut is already added in this release candidate, it's called "Stellarium (no OpenGL2)". So better run the program from here instead of modifying your config.ini file as i mentioned before.
pedemoz (pedemoz) wrote : | #67 |
Steve,
Without realising it, you gave me an idea of how to reproduce the font problems - they're nowhere near as bad as I could produce two weeks ago but, nonetheless, I have something to test. Thanks.
All,
An issue was found with the DejaVu Sans font at a pixel size of 13 when using OpenGL1 under Windows. See:
https:/
It was found that changing the font to Verdana (a standard Windows font that looks almost identical to DejaVu Sans) fixed the problem. The code was then patched (svn r6393) to use Verdana, but only when using 'safemode' (i.e. when forcing OpenGL1, not when OpenGL1 is the only version supported by the GPU). Wondering if changing to Verdana may solve other font issues, I can confirm it seems to for me; the problem is intermittent/random but I have not been able to reproduce using Verdana, whereas I can often with DejaVu Sans.
Therefore...
Please 'force' it to use OpenGL1, even if that is already being used (i.e. if it is the only version supported). This can be done three possible ways:
1/ Use the "(safe mode)" or "(no OpenGL2)" selection in the Windows Start menu (only added in recent versions).
2/ Append '--safe-mode' at the command line, e.g.
"c:\program files\stellariu
3/ Add "use_qpaintengi
Hopefully this fixes the problem - let us know (and be sure to include the version number).
SteveTuttle (seeker052) wrote : | #68 |
All,
For me, the forcing of OpenGL1 instead of allowing it to default to GL1 seems to have solved the garbbled text issue on both of my setups. Until today, I could not start and stop VERSION "r6402" for more that about 5 or 10 cycles before it would go from good to bad, etc. I have now gone about an hour with no problems.
Steve T.
Fabien Chéreau (xalioth) wrote : | #69 |
Dear all,
Bogdan have uploaded a new release candidate package: http://
It uses Verdana font on windows in the hope of fixing the problems. We are currently finishing the release, so please report ASAP of any improvement/
Thanks,
Fab
m kroeger (mkkroeger) wrote : | #70 |
Just installed it. With use_qpaintenginegl2 = false, everything seems to work great: All fonts OK, movement OK. No crashes. Night sky looks great.
With use_qpaintenginegl2 = true, immediate crash. Obviously, I don't intend to use this setting.
Using XPSP3, ATI mobility Radeon X1400 (256MB), Resolution 1440X900 32-bit color
Thanks!
SteveTuttle (seeker052) wrote : | #71 |
All,
I have been using the r6435 on my two setups for about one hour. So far, no problems with fonts. All fonts (sky, menus, etc.) look great and the overall display looks great. I have also run some of my own scripts and they all run with no font problems.
I hope everyone else has positive results.
My setups:
1) Vista, Dell Inspiron 1525, 3GB mem, and an Intel Mobile 965 Express graphics card.
2) WinXp SP3, Dell 6000, with 2GB mem, and an ATI Mobility Radeon X300 graphics card.
Steve T.
Fabien Chéreau (xalioth) wrote : | #72 |
Dear all,
It seems that there is a similar bug report on the qt bug trackers: http://
If you could try to reproduce/add comments to this bug report, it could make things go faster on the Qt side to try to resolve the bug properly..
Fabien
Peter Mousley (scrupeus) wrote : | #73 |
On Tue, 2010-06-01 at 10:05 +0000, Fabien Chéreau wrote:
> Dear all,
> It seems that there is a similar bug report on the qt bug trackers: http://
> If you could try to reproduce/add comments to this bug report, it could make things go faster on the Qt side to try to resolve the bug properly..
> Fabien
>
I think there are multiple, possibly independent problems related to
fonts. The Qt bug is about the quality of rendering, which is an issue
(particularly with DejaVu Sans under OpenGL1). The 'unreadable' fonts
various people are getting are just that - they are totally corrupted
and not legible. Check my post some time ago that included some
attached images ("Issue with OpenGL font rendering and font size on
Windows", 29/5). It shows examples of corruption and poor quality
rendering.
Peter Mousley (scrupeus) wrote : | #74 |
I should have added... I managed to reproduce font corruption on an
ATI-based system today (previously only tried and produced on
nvidia-based systems). As before, it was when using OpenGL1 and it made
a lot of the info text unreadable.
Fabien Chéreau (xalioth) wrote : | #75 |
OK.. Maybe it's too much asking, but if someone could have a try with Qt 4.7 beta, I am curious to know if it's solved. From the qt trackers I saw several other text rendering issues fixed for 4.7. If it turns out that Qt 4.7 solve that, I could stop looking for problems in Stellarium's code itself (I am having nightmares with subtitles in garbled fonts)..
faluco (borja-ferav) wrote : | #76 |
Fabien i've executed stellarium under Qt4.7 and corrupt text is still there :\
faluco (borja-ferav) wrote : | #77 |
As with 4.6.3, j's are missing aswell if font is smaller than 13. All these issues happen with dejavusans+opengl1
Peter Mousley (scrupeus) wrote : | #78 |
On 2/06/2010 4:19, faluco wrote:
> As with 4.6.3, j's are missing aswell if font is smaller than 13. All
> these issues happen with dejavusans+opengl1
>
>
In fact, font size 12 and below works okay - it is only size 13 that is
problematic. This was the first hint to me that it is the font itself
which is causing problems (hence my encouragemnt for testing altenative
fonts).
faluco (borja-ferav) wrote : | #79 |
Yes Peter, exactly, i wanted to write that but wrote a different thing. This is going to need more testing. Fabien could you try writing a minimal app just printing text to reproduce the issue and for easier debugging?
Fabien Chéreau (xalioth) wrote : | #80 |
I just updated the dejavu font file on the SVN from http://
Please report any changes..
Fab
faluco (borja-ferav) wrote : | #81 |
Didnt fix it.
Fabien Chéreau (xalioth) wrote : | #82 |
- 2dpainting-bugfontgl.zip Edit (1.2 MiB, application/zip)
OK.. Thanks..
I just did a little test app to try to reproduce the bug, based on the Qt 2d painting example.
Please have a look. Normally just opening the .pro with qtcreator and runing it should be enough.
You can play with the GLEngine/font name/font size, parameters in main.cpp.
Fabien
faluco (borja-ferav) wrote : | #83 |
faluco (borja-ferav) wrote : | #84 |
Oh well i've removed the text rotation instruction aswell, since it makes text look horrible, but this is a different bug you reported to Qt Fabien.
Fabien Chéreau (xalioth) wrote : | #85 |
Great Faluco!
I would suggest you open an item in Qt bugs (if you can't find matching bugs) and let us informed of the bug status!
faluco (borja-ferav) wrote : | #86 |
The bug report is here: http://
Please feel free to include more information or support if needed. We'll see what happens here.
Changed in stellarium: | |
status: | Confirmed → Fix Committed |
milestone: | none → 0.10.5 |
Changed in stellarium: | |
status: | Fix Committed → Fix Released |
faluco (borja-ferav) wrote : | #87 |
The Qt bug report has been closed today, sigh. Reason is that they will only fix bad regressions for opengl1, so we'll have to find a way to reproduce the font corruption problem in a separate application.
I am experiencing an identical problem when upgrading from 0.10.2 to 0.10.4. I am using Windows 7 Pro 32-bit and have an ATI Mobility FireGL T2 graphics card (9600 XT-based.)
2010-02-22T16:52:52 m\stellarium. exe ------- ------- ------- ------- ------- ------- ------- www.stellarium. org ] ------- ------- ------- ------- ------- ------- ------- drasnor/ AppData/ Roaming/ Stellarium/ log.txt" drasnor\ AppData\ Roaming\ Stellarium" drasnor\ AppData\ Roaming\ Stellarium/ config. ini" does not exist. Copying the default file. drasnor\ AppData\ Roaming\ Stellarium/ config. ini" drasnor\ AppData\ Local\stellariu m\stellarium\ cache" drasnor/ AppData/ Roaming/ Stellarium/ stars/default" drasnor\ AppData\ Roaming\ Stellarium/ stars/default/ starsConfig. json" default/ stars_0_ 0v0_1.cat" : 0_0v0_1; 5013" default/ stars_1_ 0v0_1.cat" : 1_0v0_1; 21999" default/ stars_2_ 0v0_1.cat" : 2_0v0_1; 151416" default/ stars_3_ 1v0_0.cat" : 3_1v0_0; 434064" preset_ sky_time is a double - treating as jday: 2.45151e+06 western/ star_names. fab" default/ name.fab"
Unsupported Windows version
Compiled with GCC 4.4.0
Qt runtime version: 4.6.2
Qt compilation version: 4.6.2
Addressing mode: 32-bit
Total memory: 2046 MB (unreliable)
Total virtual memory: 2047 MB (unreliable)
Physical memory in use: 36%
Processor speed: 598 MHz
Processor name: Intel(R) Pentium(R) M processor 2.10GHz
C:\Program Files\Stellariu
------
[ This is Stellarium 0.10.4 - http://
[ Copyright (C) 2000-2010 Fabien Chereau et al ]
------
Writing log file to: "C:/Users/
File search paths:
0 . "C:\Users\
1 . "."
Config file "C:\Users\
Config file is: "C:\Users\
Qt GL paint engine is: "OpenGL2"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
Cache directory is: "C:\Users\
Sky language is "en"
Application language is "en"
Loading Solar System data ...
Loaded 38 / 38 planet orbits
Could not find the starsConfig.json file: will copy the default one.
Creates directory "C:/Users/
Creates file "C:\Users\
Loading star data ...
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
"Loading "./stars/
Finished loading star catalogue data, max_geodesic_level: 3
navigation/
Loaded 10051 NGC records
Loading NGC name data ...
Loaded 222 / 222 NGC name records successfully
Loaded 88 / 88 constellation records successfully for culture "western"
Loaded 85 / 85 constellation art records successfully for culture "western"
Loaded 89 / 89 constellation names
Loading constellation boundary data ...
Loaded 782 constellation boundary segments
Loading star names from "./skycultures/
Loaded 230 / 230 common star names
Loading star names from "./stars/
Loaded 3215 / 4359 scientific star names
Creating GUI ...
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
QGLShader::link: "Fragment shader(s) linked, vertex shader(s) linked.
"
Downloaded 0 files (0 kbytes) in a session of 12.098 sec (average of 0 kB/s + 0 files from cache (0 kB)).