Bad Performance in Mac M2

pacastro commented 1 year ago

Expected Behaviour

Good performance in rendering everything (high fps)

Actual Behaviour

Bad performance in general, very low fps when moving view around (status bar displays 15 but movement is less than 5). Had same issue with version 1.1, NO issues at all with version 1.0 or previous (fps in the 80´s) runs buttery smooth.

Similar to issue #2836 but with boundaries not enabled (with them enabled it is a lot worse), more like issue #2778 but with a great decrease in displayed fps compared to v1.0 (15 vs 80).

Steps to reproduce

Run Stellarium version 1.2 or 1.1 in a MacBook Air M2

System

Stellarium version: Stellarium-1.2-macOS.zip
Operating system: macOS 13.1 M2
Graphics card: Apple M2
Screen type: 2048x1332 (same performance with default 1470x956 res)

Logfile

log.txt

gzotti commented 1 year ago

1) The graphics requirements were increased to make the new Skylight model available particularly for Macs. Is Metal 4.1 functionally equivalent to OpenGL 4.1?

2)

QGestureManager::deliverEvent: could not find the target for gesture

Looks like particular Mac/Qt-related touchpad issues again.

rayw000 commented 1 year ago

I ran into exactly the same issue with my M1 pro laptop.

alex-w commented 1 year ago

@pacastro @rayw000 please run Stellarium in Terminal.app as /Applications/Stellarium.app/Contents/MacOS/stellarium --opengl-compat, test the performance and show the logs

pacastro commented 1 year ago

Same low performance running as /Applications/Stellarium.app/Contents/MacOS/stellarium --opengl-compat from terminal.app. No noticiable difference (~15 fps).

log.txt

and this is the log from running v1.0 (~70-80 fps)

logv1.txt

Ruediger3 commented 1 year ago

Hi, I also suffer from severe performance issues under Windows 10 and Intel. version 1.2 consumes 4 times as much CPU as v1.1 did on a i7-9800X. Starting in any other mode gives the same result. After downgrading to 1.22.4-4450 qt6 it is back to approx 14% compared to 50% with v1.2 qt6.

Regards Ruediger

PoisonAstro commented 1 year ago

Same on M1 MacBook Pro Max.

gorante commented 1 year ago

Reporting the same problem with this specs:

MacBook Pro (14", 2021) Apple M1 Max 32 GB RAM

With v 1.2 it's slowing down to less than 1fps (even if keeps showing 10/15 fps on control bar). Looks like a rendering problem since it slows down as i add objects or grids, with stellarium reset to defaults (so just Guereins as landscape and the sun visible) it runs nicely.

No problems with previous versions (i came straight from 0.22.2)

gzotti commented 1 year ago

Wow, 1fps reads like "software rendering", equivalent to Mesa mode on Windows. As almost always, logfiles would be helpful. @10110111 Probably the same as #2836 ?

gorante commented 1 year ago

Wow, 1fps reads like "software rendering", equivalent to Mesa mode on Windows. As almost always, logfiles would be helpful. @10110111 Probably the same as #2836 ?

Looks like a rendering problem to me too, but if I read correctly the log file it's loading Metal, it's not going on software rendering.

What i noticed is that it runs pretty smooth if object (any kind of) are turned off, as soon as I add grids (equatorial and alt-az) it goes nut slowing down to less than 1fps (still showing 10/20 fps on status bar). If I add object as galaxyes, planets or nebulas, it slows down equally (but a little less). If i increase the number of objects it slows down until being totally unusable.

Number of objects and grids in the same amount were ok with the previous versions.

Log file attached:

log.txt

gorante commented 1 year ago

@gzotti just read https://github.com/Stellarium/stellarium/issues/2836 I can confirm that could be the same problem as you wrote there.

10110111 commented 1 year ago

There may be multiple issues interfering here.

Try disabling all lines, including boundaries, grids, orbits (anything else, @gzotti?), check how the frame rate compares to v1.0.
Try using a mouse instead of the touchpad, check how (and whether) the frame rate changes.

Does the combination of these two changes return performance with v1.0 (configured the same way)?

gzotti commented 1 year ago

Constellation/Asterism/RayHelper lines. Compass marks. Landscape gazetteer lines. Basically everything that looks like dots or short or long lines on the screen.

I agree this looks like two issues.

OpenGL lines now causing massive slowdowns, independent from platform, but best noted on non-Geforces. Is there a way to switch between old and new solution? We need the new solution for thick lines on modern OpenGL. But maybe fast thin-only lines (like we had on GLES/ANGLE) are better than too slow thick lines.
Touchpad issue (again) on Macs. I can only speculate here. This is a recurring issue.

gorante commented 1 year ago

There may be multiple issues interfering here.

Try disabling all lines, including boundaries, grids, orbits (anything else, @gzotti?), check how the frame rate compares to v1.0.

Try using a mouse instead of the touchpad, check how (and whether) the frame rate changes.

Does the combination of these two changes return performance with v1.0 (configured the same way)?

I can confirm that disabling everithing it runs smoothly.

I've tried also with a mouse (Apple magicmouse via bluetooth) and.. i runs smooth also with everything enabled. So, it's kind of two issues interacting: with lines activated if used with trackpad it slows down, but it runs good with external mouse. With everything disabled, runs smooth even with the trackpad.

pacastro commented 1 year ago

Also confirm that disabling everything make it run smooth (~80 fps), even with trackpad.

With mouse and nothing disabled it is different, it runs faster BUT fps displayed still is 15 fps, and it behaves like 15 fps. So the trackpad issue makes it behave like ~1 fps or less, but with the 15 fps displayed in status bar (with everything turned on).

Maybe with trackpad and everything turned off the fps displayed is 80 fps, but the actual movement can be lower because of the trackpad issue .... if it is around 40-50 for example, you actually can't notice the difference.

rayw000 commented 1 year ago

@pacastro @rayw000 please run Stellarium in Terminal.app as /Applications/Stellarium.app/Contents/MacOS/stellarium --opengl-compat, test the performance and show the logs

@alex-w

When running with --opengl-compat option, the fps goes up to about 70-110, which is much higher than 10-20 (or even lower) without --opengl-compat. Here is the output:

 ------------------------------------------------------------
[ This is Stellarium 1.2 (v1.22.5) - https://stellarium.org/ ]
[ Copyright (C) 2000-2022 Stellarium Developers              ]
 ------------------------------------------------------------
Writing log file to: "$HOME/Library/Application Support/Stellarium/log.txt"
File search paths:
  0 .  "$HOME/Library/Application Support/Stellarium"
  1 .  "/Applications/Stellarium.app/Contents/Resources"
Config file is:  "$HOME/Library/Application Support/Stellarium/config.ini"
Default surface format:  QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
OpenGL module type: 0
Setting OpenGL Compatibility profile from command line...
Default surface format:  QSurfaceFormat(version 3.3, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::CompatibilityProfile)
OpenGL module type: 0
Setting OpenGL Compatibility profile from command line...
StelGLWidget constructor
StelGraphicsScene constructor
initializeGL(windowWidth = 1024, windowHeight = 768)
OpenGL supported version:  "2.1 Metal - 76.3"
Current Format:  QSurfaceFormat(version 2.1, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 32, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize -1, stencilBufferSize 0, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
StelGLWidget context format version: 2 . 1
StelGLWidget has CompatibilityProfile: no ( QSurfaceFormat::NoProfile )
StelMainView::init
Luminance textures are supported
Maximum texture anisotropy: 16
Driver version string: "2.1 Metal - 76.3"
GL vendor is "Apple"
GL renderer is "Apple M1 Max"
GL Shading Language version is "1.20"
stel.OpenGLArray: Vertex Array Objects are supported
Detected a high resolution device! Device pixel ratio: 2
Sky language is  "zh_CN"
Planetary features language is  "zh_CN"
Application language is  "zh_CN"
Scripts language is  "zh_CN"
Cache directory is:  "$HOME/Library/Caches/stellarium/stellarium"
Using HTTP proxy: "" "" "localhost" "41091"
Loaded 252 countries
Loaded 193 regions
Loading Solar System data (1: planets and moons) ...
Loading from : "/Applications/Stellarium.app/Contents/Resources/data/ssystem_major.ini"
SolarSystem has  83 entries.
Loaded 83 Solar System bodies
Loading Solar System data (2: minor bodies)...
Loading from : "$HOME/Library/Application Support/Stellarium/data/ssystem_minor.ini"
SolarSystem has  186 entries.
Loaded 103 Solar System bodies
File ssystem_minor.ini is loaded successfully...
Loading nomenclature for Solar system bodies ...
Loaded 15801 / 15852 items of planetary surface nomenclature
WARNING - These planets to assign nomenclature items were not found: "Bennu, Dactyl, Ryugu"
Loading star data ...
"Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_0_0v0_8.cat: 0_0v0_8; 4979"
"Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_1_0v0_8.cat: 1_0v0_8; 21806"
"Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_2_0v0_8.cat: 2_0v0_8; 150826"
"Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_3_1v0_4.cat: 3_1v0_4; 425807"
"Loading $HOME/Library/Application Support/Stellarium/stars/default/stars_4_1v0_2.cat: 4_1v0_4; 1692779"
"Loading $HOME/Library/Application Support/Stellarium/stars/default/stars_5_2v0_1.cat: 5_2v0_1; 7083058"
"Loading $HOME/Library/Application Support/Stellarium/stars/default/stars_6_2v0_1.cat: 6_2v0_1; 24670782"
Finished loading star catalogue data, max_geodesic_level:  6
Loading scientific star names from /Applications/Stellarium.app/Contents/Resources/stars/default/name.fab
Loaded 4942 / 4942 scientific star names
Loading scientific star extra names from /Applications/Stellarium.app/Contents/Resources/stars/default/extra_name.fab
Loaded 26200 / 26200 scientific star extra names
Loading variable stars from /Applications/Stellarium.app/Contents/Resources/stars/default/gcvs_hip_part.dat
Loaded 6862 / 6862 variable stars
Loading double stars from /Applications/Stellarium.app/Contents/Resources/stars/default/wds_hip_part.dat
Loaded 22992 / 22992 double stars
Loading cross-identification data from /Applications/Stellarium.app/Contents/Resources/stars/default/cross-id.dat
Loaded 108378 / 108378 cross-identification data records for stars
Loading parallax errors data from /Applications/Stellarium.app/Contents/Resources/stars/default/hip_plx_err.dat
Loaded 117703 / 117703 parallax error data records for stars
Loading proper motion data from /Applications/Stellarium.app/Contents/Resources/stars/default/hip_pm.dat
Loaded 117955 / 117955 proper motion data records for stars
navigation/preset_sky_time is a double - treating as jday: "2451514.25001"
Loading DSO data ...
[...] Stellarium DSO Catalog, version 3.18 (standard edition)
Loaded 94661 DSO records
Loading DSO outline data ...
Loaded 98 DSO outline records successfully
LandscapeMgr: initialized Cache for 100 MB.
Loading star names from /Applications/Stellarium.app/Contents/Resources/skycultures/modern/star_names.fab
Loaded 1103 / 1103 common star names
Loading DSO name data ...
Loaded 1316 / 1342 DSO name records successfully
WARNING - No position data for 26 objects: NGC 1276, NGC 4173, PGC 2798, PGC 2907, PGC 23521, PGC 28759, PGC 29167, PGC 34658, PGC 42102, PGC 44750, PGC 54559, PGC 59117, PGC 59858, PGC 59953, PGC 69018, PGC 69877, PGC 73957, PGC 95597, PGC 100170, PGC 100170, PGC 119230, PGC 1000714, PGC 1694462, PGC 2822840, PGC 2826829, PGC 3098124
Loaded 88 / 88 constellation records successfully for culture "modern"
Loaded 85 / 85 constellation art records successfully for culture "modern"
Loaded 88 / 88 constellation names
Loading constellation boundary data ...
Loaded 782 constellation boundary segments
Loaded 84 / 84 asterism records successfully for culture "modern"
Loaded 74 / 74 asterism names
Initializing basic GL shaders...
Creating GUI ...
Loading Style file ":/graphicGui/normalStyle.css"
Loaded plugin "AngleMeasure"
Loaded plugin "EquationOfTime"
Loaded plugin "MeteorShowers"
[MeteorShowersMgr] Loading catalog file: "$HOME/Library/Application Support/Stellarium/modules/MeteorShowers/MeteorShowers.json"
[MeteorShowersMgr] Version of the format of the catalog: 2
Loaded plugin "NavStars"
Loaded plugin "Novae"
[Novae] version of the catalog: 1
[Novae] loading catalog file: "$HOME/Library/Application Support/Stellarium/modules/Novae/novae.json"
Loaded plugin "Observability"
Loaded plugin "Oculars"
Oculars::validateAndLoadIniFile() ocular.ini exists at:  "$HOME/Library/Application Support/Stellarium/modules/Oculars/ocular.ini" . Checking version...
Oculars::validateAndLoadIniFile() found existing ini file version  3.1
Loaded plugin "Pulsars"
[Pulsars] Version of the format of the catalog: 2
[Pulsars] Loading catalog file: "$HOME/Library/Application Support/Stellarium/modules/Pulsars/pulsars.json"
Loaded plugin "Satellites"
[Satellites] loading catalogue file: "$HOME/Library/Application Support/Stellarium/modules/Satellites/satellites.json"
Loaded plugin "Scenery3d"
Loaded 1 extensions for "Scenery3d"
stel.plugin.scenery3d: Scenery3d plugin - press KGA button to toggle 3D scenery, KGA tool button for settings
stel.plugin.scenery3d: Initializing Scenery3d renderer...
stel.plugin.scenery3d.renderer: Maximum texture size: 16384
stel.plugin.scenery3d.renderer: Maximum viewport dims: 16384 16384
stel.plugin.scenery3d.renderer: Maximum renderbuffer size: 16384
stel.plugin.scenery3d.renderer: Maximum framebuffer size: 16384
stel.plugin.scenery3d.renderer: Geometry shader not supported on this hardware
stel.plugin.scenery3d.renderer: GL_MAX_TEXTURE_IMAGE_UNITS: 16
stel.plugin.scenery3d.renderer: GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS: 16
stel.plugin.scenery3d.renderer: Seamless cubemap filtering enabled
stel.plugin.scenery3d: Initializing Scenery3d renderer...done
Loaded plugin "SolarSystemEditor"
Using the ssystem_minor.ini file that already exists in the user directory...
Loaded plugin "Supernovae"
[Supernovae] version of the catalog: 1
[Supernovae] loading catalog file: "$HOME/Library/Application Support/Stellarium/modules/Supernovae/supernovae.json"
Initializing planets GL shaders...
"StelPainter: Warnings while linking transformShaderProgram shader program:\nWARNING: Could not find vertex shader attribute 'texCoord' to match BindAttributeLocation request.\nWARNING: Could not find vertex shader attribute 'normalIn' to match BindAttributeLocation request.\n"
Dubious result: Landscape  "Guereins"  not calibrated. Opacity test represents mathematical horizon only.
Unloaded plugin "Supernovae"
Unloaded plugin "SolarSystemEditor"
stel.plugin.scenery3d.shadermgr: Clearing 0 shaders
Unloaded plugin "Scenery3d"
Unloaded plugin "Satellites"
Unloaded plugin "Pulsars"
Unloaded plugin "Oculars"
Unloaded plugin "Observability"
Unloaded plugin "Novae"
Unloaded plugin "NavStars"
Unloaded plugin "MeteorShowers"
Unloaded plugin "EquationOfTime"
Unloaded plugin "AngleMeasure"
Downloaded 0 files (0 kbytes) in a session of 17.56 sec (average of 0 kB/s + 0 files from cache (0 kB)).
LandscapeMgr: Clearing cache of 0 landscapes totalling about  0 MB.
StelGLWidget destroyed

firsttest12 commented 1 year ago

Same problem on M1 pro laptop. Had to uninstall 1.1 and revert to 1.0. Now will have to uninstall 1.2 and revert to 1.0. This is a serious bug.

Have noticed that will run smoothly when on a reasonably high level of zoom / only a small area of night sky visible. Say FOV 15-20degrees upper limit before becomes very jumpy and then unusable.

astro-moose commented 1 year ago

This problem persists in Stellarium 1.2 (25.12.2022) on MacOS 12.6.2 with a MacBook Pro 2015. Using the trackpad is a pain in the ass, stellarium nearly freezes. The same Application runs flawless on a hacked Mac Mini 2012 with 12.6.2.

Using a mouse on the Macbook helps a little bit...

I am not experienced with programming - i do not know how to log this issue...

Georg Zotti: Hallo Georg, ich kann dich ja mal mit dem Teil besuchen, damit du es "in Natura" sehen kannst - es scheint "wieder" das Touchpad-Problem zu sein. wenn man eine Maus verwendet, geht es um einiges besser. - viele liebe Grüsse, Gerhard Rehak, WAA

10110111 commented 1 year ago

The touchpad problem is tracked in #2778.

gzotti commented 1 year ago

Georg Zotti: Hallo Georg, ich kann dich ja mal mit dem Teil besuchen, damit du es "in Natura" sehen kannst - es scheint "wieder" das Touchpad-Problem zu sein. wenn man eine Maus verwendet, geht es um einiges besser. - viele liebe Grüsse, Gerhard Rehak, WAA

Ah, sieh an. Nein, Demo nützt nichts. Ich weiß nicht von Macs, außer daß die Mac-Touchpads mit fast jeder MacOS-Version wieder neue Probleme machen.

Flexximilian commented 1 year ago

Servus!

I don't think this is just a Mac issue.

I run Gentoo Linux on a i5-2400 @ 3.10GHz (with integrated HD 2000 Graphics), Stellarium used to run just fine, rarely below 10 honest fps. But Version 1.2 (0.22.5) runs way slower and makes the whole system lag and stutter. The regression is very drastic and clear compared to earlier versions.

What's quite odd is that the displayed FPS are not the real rendered FPS any longer. It shows ~6fps, when I actually get one frame per two seconds, so 0.5 fps when panning around using the mouse. When I open the sensors view, and select a star, the position numbers on the top left of the sensor frame update every other second, along with the object information and the selection markers, while the menu still shows some 5-6 fps. It's like the engine thinks it renders more frames than are actually displayed.

The performance (and impact on the whole system) I see is more consistent with software rendering than hardware rendering, really. Sometime I seem to get a couple frames with about 1/4 of a second in between before a long pause. OTOH, the laggy response of the whole Plasma UI seems like the CPU is stressed. Oddly enough, htop shows only up to 135% of 400% (4 cores) while panning. I guess the integrated GPU is severely overloaded, such that context switching to another desktop or windows from the fullscreen Stellarium, or switching tabs in the Konsole window open alongside on another screen (not really a complicated render) takes a few seconds to complete.

Removing everying but the UI (menus), milky way and planets helped a bit, but panning was still 0.75 actual fps, while the counter went up to 10fps, which was clearly not the frames actually rendered. Do you have any insight where that discrepancy between the shown fps and actual fps come from?

So whatever you changed with regard to rendering, older systems seem to need whatever was there before, so please put it back in as an option.

Let me know if you want me to try anything else, below are the logs (-d --single-buffer). BTW, --single-buffer didn't help, but it was worth a try.

Thanks for all the great work you've done over the years!

 ------------------------------------------------------------
[ This is Stellarium 1.2 (v0.22.5) - https://stellarium.org/ ]
[ Copyright (C) 2000-2023 Stellarium Developers              ]
 ------------------------------------------------------------
Writing log file to: "/home/user/.stellarium/log.txt"
File search paths:
  0 .  "/home/user/.stellarium"
  1 .  "/usr/share/stellarium"
Config file is:  "/home/user/.stellarium/config.ini"
Default surface format:  QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
OpenGL module type: 0
Default surface format:  QSurfaceFormat(version 3.3, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::CoreProfile)
OpenGL module type: 0
StelGLWidget constructor
StelGraphicsScene constructor
initializeGL(windowWidth = 1024, windowHeight = 768)
OpenGL supported version:  "3.3 (Core Profile) Mesa 23.0.0-rc4"
Current Format:  QSurfaceFormat(version 3.3, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 0, samples 0, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::CoreProfile)
StelMainView::init
Luminance textures are not supported
Maximum texture anisotropy: 16
Detected: OpenGL "3.3"
Driver version string: "3.3 (Core Profile) Mesa 23.0.0-rc4"
GL vendor is "Intel"
GL renderer is "Mesa Intel(R) HD Graphics 2000 (SNB GT1)"
GL Shading Language version is "3.30"
initializeOpenGLFunctions()...
OpenGL Features:
 - glActiveTexture() function is available.
 - Shader functions are available.
 - Vertex and index buffer functions are available.
 - Framebuffer object functions are available.
 - glBlendColor() is available.
 - glBlendEquation() is available.
 - glBlendEquationSeparate() is available.
 - glBlendFuncSeparate() is available.
 - Blend subtract mode is available.
 - Compressed texture functions are available.
 - glSampleCoverage() function is available.
 - Separate stencil functions are available.
 - Non power of two textures are available.
 - Non power of two textures can use GL_REPEAT as wrap parameter.
 - The fixed function pipeline is NOT available.
Line widths available from 1 to 7.375
OpenGL shader capabilities and details:
 - Vertex Shader: YES
 - Fragment Shader: YES
 - Geometry Shader: YES
 - TessellationControl Shader: NO
 - TessellationEvaluation Shader: NO
 - Compute Shader: NO
We have 173 OpenGL extensions:
 - "GL_3DFX_texture_compression_FXT1"
 - "GL_AMD_conservative_depth"
 - "GL_AMD_draw_buffers_blend"
 - "GL_AMD_performance_monitor"
 - "GL_AMD_pinned_memory"
 - "GL_AMD_seamless_cubemap_per_texture"
 - "GL_AMD_shader_trinary_minmax"
 - "GL_AMD_texture_texture4"
 - "GL_AMD_vertex_shader_layer"
 - "GL_AMD_vertex_shader_viewport_index"
 - "GL_ANGLE_texture_compression_dxt3"
 - "GL_ANGLE_texture_compression_dxt5"
 - "GL_ARB_ES2_compatibility"
 - "GL_ARB_ES3_compatibility"
 - "GL_ARB_arrays_of_arrays"
 - "GL_ARB_base_instance"
 - "GL_ARB_blend_func_extended"
 - "GL_ARB_buffer_storage"
 - "GL_ARB_clear_buffer_object"
 - "GL_ARB_clear_texture"
 - "GL_ARB_clip_control"
 - "GL_ARB_compressed_texture_pixel_storage"
 - "GL_ARB_conditional_render_inverted"
 - "GL_ARB_conservative_depth"
 - "GL_ARB_copy_buffer"
 - "GL_ARB_copy_image"
 - "GL_ARB_cull_distance"
 - "GL_ARB_debug_output"
 - "GL_ARB_depth_buffer_float"
 - "GL_ARB_depth_clamp"
 - "GL_ARB_direct_state_access"
 - "GL_ARB_draw_buffers"
 - "GL_ARB_draw_buffers_blend"
 - "GL_ARB_draw_elements_base_vertex"
 - "GL_ARB_draw_instanced"
 - "GL_ARB_enhanced_layouts"
 - "GL_ARB_explicit_attrib_location"
 - "GL_ARB_explicit_uniform_location"
 - "GL_ARB_fragment_coord_conventions"
 - "GL_ARB_fragment_layer_viewport"
 - "GL_ARB_fragment_shader"
 - "GL_ARB_framebuffer_object"
 - "GL_ARB_framebuffer_sRGB"
 - "GL_ARB_get_program_binary"
 - "GL_ARB_get_texture_sub_image"
 - "GL_ARB_half_float_pixel"
 - "GL_ARB_half_float_vertex"
 - "GL_ARB_instanced_arrays"
 - "GL_ARB_internalformat_query"
 - "GL_ARB_internalformat_query2"
 - "GL_ARB_invalidate_subdata"
 - "GL_ARB_map_buffer_alignment"
 - "GL_ARB_map_buffer_range"
 - "GL_ARB_multi_bind"
 - "GL_ARB_occlusion_query2"
 - "GL_ARB_parallel_shader_compile"
 - "GL_ARB_pipeline_statistics_query"
 - "GL_ARB_pixel_buffer_object"
 - "GL_ARB_point_sprite"
 - "GL_ARB_polygon_offset_clamp"
 - "GL_ARB_program_interface_query"
 - "GL_ARB_provoking_vertex"
 - "GL_ARB_robustness"
 - "GL_ARB_sample_shading"
 - "GL_ARB_sampler_objects"
 - "GL_ARB_seamless_cube_map"
 - "GL_ARB_seamless_cubemap_per_texture"
 - "GL_ARB_separate_shader_objects"
 - "GL_ARB_shader_bit_encoding"
 - "GL_ARB_shader_draw_parameters"
 - "GL_ARB_shader_group_vote"
 - "GL_ARB_shader_objects"
 - "GL_ARB_shader_subroutine"
 - "GL_ARB_shader_texture_lod"
 - "GL_ARB_shader_viewport_layer_array"
 - "GL_ARB_shading_language_420pack"
 - "GL_ARB_shading_language_include"
 - "GL_ARB_shading_language_packing"
 - "GL_ARB_sync"
 - "GL_ARB_texture_barrier"
 - "GL_ARB_texture_buffer_object"
 - "GL_ARB_texture_buffer_object_rgb32"
 - "GL_ARB_texture_buffer_range"
 - "GL_ARB_texture_compression_bptc"
 - "GL_ARB_texture_compression_rgtc"
 - "GL_ARB_texture_cube_map_array"
 - "GL_ARB_texture_filter_anisotropic"
 - "GL_ARB_texture_float"
 - "GL_ARB_texture_gather"
 - "GL_ARB_texture_mirror_clamp_to_edge"
 - "GL_ARB_texture_multisample"
 - "GL_ARB_texture_non_power_of_two"
 - "GL_ARB_texture_query_levels"
 - "GL_ARB_texture_query_lod"
 - "GL_ARB_texture_rectangle"
 - "GL_ARB_texture_rg"
 - "GL_ARB_texture_rgb10_a2ui"
 - "GL_ARB_texture_storage"
 - "GL_ARB_texture_storage_multisample"
 - "GL_ARB_texture_swizzle"
 - "GL_ARB_timer_query"
 - "GL_ARB_transform_feedback2"
 - "GL_ARB_transform_feedback_instanced"
 - "GL_ARB_transform_feedback_overflow_query"
 - "GL_ARB_uniform_buffer_object"
 - "GL_ARB_vertex_array_bgra"
 - "GL_ARB_vertex_array_object"
 - "GL_ARB_vertex_attrib_binding"
 - "GL_ARB_vertex_buffer_object"
 - "GL_ARB_vertex_shader"
 - "GL_ARB_vertex_type_10f_11f_11f_rev"
 - "GL_ARB_vertex_type_2_10_10_10_rev"
 - "GL_ARB_viewport_array"
 - "GL_ATI_blend_equation_separate"
 - "GL_ATI_texture_float"
 - "GL_EXT_EGL_image_storage"
 - "GL_EXT_EGL_sync"
 - "GL_EXT_abgr"
 - "GL_EXT_blend_equation_separate"
 - "GL_EXT_debug_label"
 - "GL_EXT_demote_to_helper_invocation"
 - "GL_EXT_draw_buffers2"
 - "GL_EXT_draw_instanced"
 - "GL_EXT_framebuffer_blit"
 - "GL_EXT_framebuffer_multisample"
 - "GL_EXT_framebuffer_multisample_blit_scaled"
 - "GL_EXT_framebuffer_object"
 - "GL_EXT_framebuffer_sRGB"
 - "GL_EXT_packed_depth_stencil"
 - "GL_EXT_packed_float"
 - "GL_EXT_pixel_buffer_object"
 - "GL_EXT_polygon_offset_clamp"
 - "GL_EXT_provoking_vertex"
 - "GL_EXT_semaphore"
 - "GL_EXT_semaphore_fd"
 - "GL_EXT_shader_framebuffer_fetch_non_coherent"
 - "GL_EXT_shader_integer_mix"
 - "GL_EXT_texture_array"
 - "GL_EXT_texture_compression_dxt1"
 - "GL_EXT_texture_compression_rgtc"
 - "GL_EXT_texture_compression_s3tc"
 - "GL_EXT_texture_filter_anisotropic"
 - "GL_EXT_texture_integer"
 - "GL_EXT_texture_sRGB"
 - "GL_EXT_texture_sRGB_R8"
 - "GL_EXT_texture_sRGB_decode"
 - "GL_EXT_texture_shadow_lod"
 - "GL_EXT_texture_shared_exponent"
 - "GL_EXT_texture_snorm"
 - "GL_EXT_texture_swizzle"
 - "GL_EXT_timer_query"
 - "GL_EXT_transform_feedback"
 - "GL_EXT_vertex_array_bgra"
 - "GL_IBM_multimode_draw_arrays"
 - "GL_INTEL_blackhole_render"
 - "GL_INTEL_performance_query"
 - "GL_KHR_blend_equation_advanced"
 - "GL_KHR_context_flush_control"
 - "GL_KHR_debug"
 - "GL_KHR_no_error"
 - "GL_KHR_parallel_shader_compile"
 - "GL_KHR_texture_compression_astc_ldr"
 - "GL_KHR_texture_compression_astc_sliced_3d"
 - "GL_MESA_pack_invert"
 - "GL_MESA_shader_integer_functions"
 - "GL_MESA_texture_signed_rgba"
 - "GL_NV_conditional_render"
 - "GL_NV_copy_image"
 - "GL_NV_depth_clamp"
 - "GL_NV_packed_depth_stencil"
 - "GL_NV_texture_barrier"
 - "GL_OES_EGL_image"
 - "GL_S3_s3tc"
EXT_gpu_shader4 MISSING!
MESA Version Number detected:  23
Mesa version is fine, we should not see a graphics problem.
GLSL Version Number detected:  3.3
GLSL version is fine, we should not see a graphics problem.
stel.OpenGLArray: Vertex Array Objects are supported
Sky language is  "de_AT"
Planetary features language is  "de_AT"
Application language is  "de_AT"
Scripts language is  "de_AT"
Cache directory is:  "/mnt/hdd/root/home/user/.cache/stellarium/stellarium"
Loaded 252 countries
Loaded 193 regions
Loading Solar System data (1: planets and moons) ...
Loading from : "/usr/share/stellarium/data/ssystem_major.ini"
SolarSystem has  83 entries.
Loaded 83 Solar System bodies
Loading Solar System data (2: minor bodies)...
Loading from : "/home/user/.stellarium/data/ssystem_minor.ini"
SolarSystem has  1569 entries.
Loaded 1486 Solar System bodies
File ssystem_minor.ini is loaded successfully...
Loading nomenclature for Solar system bodies ...
Loaded 15814 / 15852 items of planetary surface nomenclature
WARNING - These planets to assign nomenclature items were not found: "Bennu, Dactyl"
Loading star data ...
"Loading /usr/share/stellarium/stars/default/stars_0_0v0_8.cat: 0_0v0_8; 4979"
"Loading /usr/share/stellarium/stars/default/stars_1_0v0_8.cat: 1_0v0_8; 21806"
"Loading /usr/share/stellarium/stars/default/stars_2_0v0_8.cat: 2_0v0_8; 150826"
"Loading /usr/share/stellarium/stars/default/stars_3_1v0_4.cat: 3_1v0_4; 425807"
"Loading /home/user/.stellarium/stars/default/stars_4_1v0_2.cat: 4_1v0_4; 1692779"
"Loading /home/user/.stellarium/stars/default/stars_5_2v0_1.cat: 5_2v0_1; 7083058"
"Loading /home/user/.stellarium/stars/default/stars_6_2v0_1.cat: 6_2v0_1; 24670782"
"Loading /home/user/.stellarium/stars/default/stars_7_2v0_1.cat: 7_2v0_1; 50733321"
"Loading /home/user/.stellarium/stars/default/stars_8_2v0_1.cat: 8_2v0_1; 92304337"
Finished loading star catalogue data, max_geodesic_level:  8
Loading scientific star names from /usr/share/stellarium/stars/default/name.fab
Loaded 4942 / 4942 scientific star names
Loading scientific star extra names from /usr/share/stellarium/stars/default/extra_name.fab
Loaded 26200 / 26200 scientific star extra names
Loading variable stars from /usr/share/stellarium/stars/default/gcvs_hip_part.dat
Loaded 6862 / 6862 variable stars
Loading double stars from /usr/share/stellarium/stars/default/wds_hip_part.dat
Loaded 22992 / 22992 double stars
Loading cross-identification data from /usr/share/stellarium/stars/default/cross-id.dat
Loaded 108378 / 108378 cross-identification data records for stars
Loading parallax errors data from /usr/share/stellarium/stars/default/hip_plx_err.dat
Loaded 117703 / 117703 parallax error data records for stars
Loading proper motion data from /usr/share/stellarium/stars/default/hip_pm.dat
Loaded 117955 / 117955 proper motion data records for stars
navigation/preset_sky_time is a double - treating as jday: "2458023.73125"
Loading DSO data ...
[...] Stellarium DSO Catalog, version 3.18 (extended edition)
Loaded 1103362 DSO records
Loading DSO outline data ...
Loaded 98 DSO outline records successfully
LandscapeMgr: initialized Cache for 100 MB.
Loading star names from /usr/share/stellarium/skycultures/modern/star_names.fab
Loaded 1103 / 1103 common star names
Loading DSO name data ...
Loaded 1331 / 1342 DSO name records successfully
WARNING - No position data for 11 objects: NGC 1276, NGC 4173, PGC 59117, PGC 73957, PGC 100170, PGC 100170, PGC 119230, PGC 1694462, PGC 2822840, PGC 2826829, PGC 3098124
Loaded 88 / 88 constellation records successfully for culture "modern"
Loaded 85 / 85 constellation art records successfully for culture "modern"
Loaded 88 / 88 constellation names
Loading constellation boundary data ... 
Loaded 782 constellation boundary segments
Loaded 84 / 84 asterism records successfully for culture "modern"
Loaded 74 / 74 asterism names
Initializing basic GL shaders... 
Creating GUI ...
Loading Style file ":/graphicGui/normalStyle.css"
Loaded plugin "AngleMeasure"
Loaded plugin "ArchaeoLines"
Loaded plugin "EquationOfTime"
Loaded plugin "Exoplanets"
[Exoplanets] Version of the format of the catalog: 1
[Exoplanets] loading catalog file: "/home/user/.stellarium/modules/Exoplanets/exoplanets.json"
Loaded plugin "MeteorShowers"
[MeteorShowersMgr] Loading catalog file: "/home/user/.stellarium/modules/MeteorShowers/MeteorShowers.json"
[MeteorShowersMgr] Version of the format of the catalog: 2
Loaded plugin "NavStars"
Loaded plugin "Novae"
[Novae] version of the catalog: 1
[Novae] loading catalog file: "/home/user/.stellarium/modules/Novae/novae.json"
Loaded plugin "Observability"
Loaded plugin "Oculars"
Oculars::validateAndLoadIniFile() ocular.ini exists at:  "/home/user/.stellarium/modules/Oculars/ocular.ini" . Checking version...
Oculars::validateAndLoadIniFile() found existing ini file version  3.1
Loaded plugin "OnlineQueries"
Loaded plugin "PointerCoordinates"
Loaded plugin "Pulsars"
[Pulsars] Version of the format of the catalog: 2
[Pulsars] Loading catalog file: "/home/user/.stellarium/modules/Pulsars/pulsars.json"
Loaded plugin "Quasars"
[Quasars] Version of the format of the catalog: 1
[Quasars] Loading catalog file: "/home/user/.stellarium/modules/Quasars/quasars.json"
Loaded plugin "RemoteControl"
RemoteControl using QtWebApp version 1.6.4-stellarium
StaticFileController: docroot=/usr/share/stellarium/webroot, encoding=UTF-8, maxAge=60
StaticFileController: cache timeout=60000, size=1048576
Loaded plugin "RemoteSync"
stel.plugin.remoteSync: Plugin initialized
Loaded plugin "Satellites"
[Satellites] loading catalogue file: "/home/user/.stellarium/modules/Satellites/satellites.json"
Loaded plugin "Scenery3d"
Registering RemoteControl extension service: "scenery3d"
Loaded 1 extensions for "Scenery3d"
stel.plugin.scenery3d: Scenery3d plugin - press KGA button to toggle 3D scenery, KGA tool button for settings
stel.plugin.scenery3d: Initializing Scenery3d renderer...
stel.plugin.scenery3d.renderer: Maximum texture size: 8192
stel.plugin.scenery3d.renderer: Maximum viewport dims: 8192 8192
stel.plugin.scenery3d.renderer: Maximum renderbuffer size: 8192
stel.plugin.scenery3d.renderer: Maximum framebuffer size: 8192
stel.plugin.scenery3d.renderer: Geometry shader supported
stel.plugin.scenery3d.renderer: GL_MAX_TEXTURE_IMAGE_UNITS: 16
stel.plugin.scenery3d.renderer: GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS: 48
stel.plugin.scenery3d.renderer: Seamless cubemap filtering enabled
stel.plugin.scenery3d: Initializing Scenery3d renderer...done
Loaded plugin "SolarSystemEditor"
Using the ssystem_minor.ini file that already exists in the user directory...
Loaded plugin "Supernovae"
[Supernovae] version of the catalog: 1
[Supernovae] loading catalog file: "/home/user/.stellarium/modules/Supernovae/supernovae.json"
Loaded plugin "TelescopeControl"
[TelescopeControl] Only embedded telescope servers are available.
[TelescopeControl] Adding device model: "Meade AutoStar compatible" "Any telescope or telescope mount compatible with Meade's AutoStar controller." "TelescopeServerLx200" 500000
[TelescopeControl] Adding device model: "Meade LX200 (compatible)" "Any telescope or telescope mount compatible with Meade LX200." "TelescopeServerLx200" 500000
[TelescopeControl] Adding device model: "Meade ETX70 (#494 Autostar, #506 CCS)" "Meade's ETX70 with the #494 Autostar controller and the #506 Connector Cable Set." "TelescopeServerLx200" 1500000
[TelescopeControl] Adding device model: "Losmandy G-11" "Losmandy's G-11 telescope mount." "TelescopeServerLx200" 500000
[TelescopeControl] Adding device model: "Wildcard Innovations Argo Navis (Meade mode)" "Wildcard Innovations' Argo Navis DTC in Meade LX200 emulation mode." "TelescopeServerLx200" 500000
[TelescopeControl] Adding device model: "Celestron NexStar (compatible)" "Any telescope or telescope mount compatible with Celestron NexStar." "TelescopeServerNexStar" 500000
[TelescopeControl] Adding device model: "Sky-Watcher SynScan (version 3 or later)" "Any Sky-Watcher mount that uses version 3 or later of the SynScan hand controller." "TelescopeServerNexStar" 500000
[TelescopeControl] Adding device model: "Sky-Watcher SynScan AZ GOTO" "The Sky-Watcher SynScan AZ GOTO mount used in a number of telescope models." "TelescopeServerNexStar" 500000
[TelescopeControl] Loaded successfully 2 telescopes.
Loaded plugin "TextUserInterface"
Initializing planets GL shaders...

gzotti commented 1 year ago

This sounds like another issue. V1.2 forces OpenGL 3.3, and it's possible that the old HD2000 has issues with that. On Windows I would suggest running ANGLE mode, but I don't know what to do in this case. @10110111 ?

10110111 commented 1 year ago

What's quite odd is that the displayed FPS are not the real rendered FPS any longer. It shows ~6fps, when I actually get one frame per two seconds, so 0.5 fps when panning around using the mouse.

Konsole

You seem to be running on KDE. Do you have compositing enabled? If yes, try disabling it and running Stellarium in this state. Your GPU may be unable to handle such a multitasking load, or the driver is too poor (which won't surprise me with old Intel@Linux).

V1.2 forces OpenGL 3.3, and it's possible that the old HD2000 has issues with that.

In principle, the user can force Mesa to report lower OpenGL version via MESA_GL_VERSION_OVERRIDE environment variable. On Windows HD2000 seems to only support OpenGL 3.1, not 3.3, so it might be useful to try this with Mesa.

Flexximilian commented 1 year ago

Servus Georg,

hmm, that sucks... This says that Linux (MESA) and Mac should have 3.3 support, while Intel officially says just 3.1. So I guess it's "3.3, but slow" using MESA...

Is there a (good) reason to force 3.3 now? Unfortunately, my Windows 7 Laptop I use for astronomy also has a Sandy Bridge CPU... :(

gzotti commented 1 year ago

The good reason is the incredible new skylight model. If you don't use that, I think it should be possible to run on anything that has 2.1+ like before. A RaspberryPi3 has about 3.5 fps at your screen size.

gzotti commented 1 year ago

I have an old Vaio notebook from 2010 with Core-i7 of the first generation. Its Win10 Geforce support (patched Geforce driver) was lost in a second WIn10 update, but its cheesy Intel GPU runs good enough with ANGLE mode (old sky model only).

Flexximilian commented 1 year ago

Hi, thanks for answering so quickly! So... running MESA_GL_VERSION_OVERRIDE=3.1 stellarium -d made the rendering faster when panning, but the UI no longer renders at all. Also, there are no labels on stars / planets / DSO's. It's still choppy when panning but better (more like I am used to).

I'll try starting with 3.3 under a plain twm, to eliminate any KWin compositor influence, and report back momentarily.

Flexximilian commented 1 year ago

Hi again,

success! Turning off the compositor did the trick. I just tried it under xfce, I assume it's the same for KWin. Now I get the performance shown in the counter, a bit over 6fps, and fairly consistently. It's down a few from what I used to have in the pre-1.0 times, but usable. Oddly, the performance remained most stable under wayland/sway (and thus xwayland), but mouse cursor is choppy, but that's a wayland issue, of course.

Thanks very much for your quick responses! Amazing!

Maybe mention this in the release notes, I am probably not the only one having a compositor turned on, despite not having the muscle for it, really. Who needs a compositor when they can have Stellarium, right? ;)

Flexximilian commented 1 year ago

And I can confirm that turning off the compositor on KWin / Plasma works as well. Conveniently, KWin allows this to be done automatically per-application using the "Configure Special Application Settings..." menu.

10110111 commented 1 year ago

I am probably not the only one having a compositor turned on, despite not having the muscle for it, really. Who needs a compositor when they can have Stellarium, right? ;)

Well, I also run a compositor on Intel HD Graphics 620, but it works fine. The only problem in your case is that your combination of GPU and driver fails to properly synchronize the appearing frames from Stellarium and the redraw by KWin's compositor. I had something similar with Intel Atom from 2011, though its GPU (GMA 950) driver was even worse.

gzotti commented 1 year ago

Some users (me included) may need real instructions to "turn off the compositor" before writing them into the FAQ. But running a lightweight desktop is a reasonable recommendation for older devices. I have a little netbook (AMD APU-1200 from 2015) which meanwhile dual-boots with Ubuntu Mate. It is CPU-limited (2x1GHz), adding a SSD did not help! And it takes what feels a full work day to install a month of Win10 updates (and do the unavoidable telemetry feedback). The GPU delivers (IIRC) OpenGL4.2, so nothing to throw away easily. With Mate, this really delivers sufficient performance (and takes rather minutes to install its updates).

I once also had an Atom with GMA3150 (2010/11?). OpenGL1.4. Just not suited for Stellarium 0.12+.

10110111 commented 1 year ago

Some users (me included) may need real instructions to "turn off the compositor"

There's a large diversity of compositors and even window systems. One instruction for KWin, another for XFWM4 (which is also capable of XRender-based compositing), yet another for compiz etc. And I don't know if Wayland has any problems (it seems to always be composited).

So I think the users had better know how to configure their own DE. We can only hint that sometimes "disable compositor" is also called "disable desktop effects".

Flexximilian commented 1 year ago

So I think the users had better know how to configure their own DE. We can only hint that sometimes "disable compositor" is also called "disable desktop effects".

I agree, it'll be hard to give good instructions for every scenario or Desktop Environment, but I don't think it's really necessary, since (a) a lot of Linux users are quire proficient, and do know how to disable their compositor, and (b) DE's have documentation and a quick search will yield results. And it sure isn't your job to explain this in the first place.

But it was simply not quite obvious (until you mentioned it) that the compositor could have anything to do with it, since it works fine with any other OpenGL stuff I use, indeed earlier versions of Stellarium worked fine with the compositor on on my machine. That's why I said a release note or FAQ entry simply stating that some users on older integrated graphics may experience performance regressions relative to pre 1.2-Versions and that turning off compositing can restore performance to levels near what they were before.

OTOH, it's now documented here, anyway (but in an unrelated issue, though). ;)

Surendrajat commented 1 year ago

I'm on MBP M1 and using --opengl-compat makes a huge difference for me. It went from 20-40 fps to 70–80 fps(I'm building with most stuff disabled). Any idea if this can me made the default?

gzotti commented 1 year ago

See User Guide, 6.2.2, for the STEL_OPTS environment variable

Surendrajat commented 1 year ago

Thanks @gzotti it works.

gorante commented 1 year ago

Sorry, i saw that a fix has been found for mac, but i did not understand if it has been already applied to the current code.

Just for the records, i've downloaded the latest weekly snapshot and it still runs very slow as soon as I add overlays or just open a window (build v.23.0.78-1be40f4).

I made a video just for reference (running on a MacBook Pro M1 Max with 32GB of Ram):

https://user-images.githubusercontent.com/4375800/227715764-1d008975-7dc8-4d89-9e60-cb3f8091db88.mp4

I've tried to compile myself but I'm stuck on black screen after launching (still not checked really well all the compiling process), if there's some caveats for this or if there is some parameters to pass to improve performances, could someone point me to the right informations? Thanks.

Atque commented 1 year ago

Yes, there is no difference between the latest beta and 1.2.

alex-w commented 1 year ago

Please check https://github.com/Stellarium/stellarium-data/releases/download/weekly-snapshot/Stellarium-23.1-278d653-qt6-macOS.zip

astro-moose commented 1 year ago

Please check https://github.com/Stellarium/stellarium-data/releases/download/weekly-snapshot/Stellarium-23.1-278d653-qt6-macOS.zip

@alex-w i just tried it an a macbook pro. using the TouchPad is a pain in the neck - using a mouse works flawless. I deleted even all preference files and did a clean installation. The trackpad issue persists

regards, Gerhard

alex-w commented 1 year ago

Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot

astro-moose commented 1 year ago

now - i got the new build for a MacBook Pro 2015 with Monterey 12.6.2 - it worked fine. Even with the trackpad.

Then i did an update to 12.6.5 - an the use of the trackpad was quite impossible. It does not react anyway :-(

I hope this helps a little bit…

regards, Gerhard

Am 02.05.2023 um 15:51 schrieb Alexander V. Wolf @.***>:

Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot — Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/2947#issuecomment-1531516931, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUFWYF7KXDSBUCV3XAEH233XEEGPJANCNFSM6AAAAAATLWJZXU. You are receiving this because you commented.

alex-w commented 1 year ago

Please check the first release candidate to version 23.2 of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot

It's a bit better now IMHO

rayw000 commented 1 year ago

Please check the first release candidate to version 23.2 of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot

It's a bit better now IMHO

It works way much better on my Apple Silicon MacBook Pro, with 50-100 fps at most time.

gorante commented 1 year ago

@alex-w i've tested

Stellarium-23.1-f97cbe8-qt5-arm64.zip
Stellarium-23.1-f97cbe8-qt6-macOS.zip

Stellarium-23.1-f97cbe8-qt5-arm64.zip It's a no-way: poor performances with the trackpad yet with basically none to display (30/40fps in the status bar, probably 10/15 in the reality), as soon as I add a couple of markings it drops to less than 1FPS (still showing 15/17fps in the status bar)

https://github.com/Stellarium/stellarium/assets/4375800/e5347ef0-3315-4506-946b-8df02b4c2925

Stellarium-23.1-f97cbe8-qt6-macOS.zip Way better with no markings, shows in the status bar > 60FPS that seems real BUT it still have a big problem with markings: as soon as i add them, PFS drops to the lowest. It's a bit better than the ARM64 / qt5 version but still unusable.

https://github.com/Stellarium/stellarium/assets/4375800/dcd7bda8-11b2-4408-8e80-d9929c3e48a3

With external mouse it's way better, even if FPS displayed drops from 60 to 25 with just a couple of markings added (those in the video above).

My system is: MacOS 12.5.1, M1 Max, 32GB Ram @rayw000 on which system did you tested? How did you get 100FPS?

rayw000 commented 1 year ago

@gorante

Tested package: Stellarium-23.1-f97cbe8-qt5-arm64.zip System: MacBook Pro M1 Max, macOS Ventura 13.4, 32GB Ram.

When disabling deep-sky objects

Works well with more than 70+ fps, occasionally 90-100

When enabling deep-sky objects with standard deep-sky catalogs

The fps drops down to 30 in the status bar, but feels like 10-20 when displaying only areas near Sagittarius due to too many objects to render, noticeable lag, but still usable.

When enabling deep-sky objects with all deep-sky catalogs

The fps drops down to 20 in the status bar, but feels like less than 10, like moving slideshows.

In all the three situations above, it works better than before on my side, though could still be improved. I can hardly get smooth moving experience in current released 23.1 even in the daytime with atmosphere.

gzotti commented 1 year ago

Now it depends which DSO catalogs you have enabled, and what the magnitude threshold is.

alex-w commented 1 year ago

Now it depends which DSO catalogs you have enabled, and what the magnitude threshold is.

It may depends with number of DSO markers or labels.

@rayw000 please check qt6-macOS package

alex-w commented 1 year ago

@rayw000 @gorante please share screen size info (Settings -> Displays?)

rayw000 commented 1 year ago

@rayw000 please check qt6-macOS package

qt6-macOS shows a similar performance as qt5-arm64 on my laptop.

@rayw000 @gorante please share screen size info (Settings -> Displays?)

gorante commented 1 year ago

@alex-w

@rayw000 @gorante please share screen size info (Settings -> Displays?)

QT6/universal works better here than QT5/Arm64 and this is the amount of DSOs marker enabled (pretty low count, I was used to enable 80% of the catalogues and to bring "label" and "hints" sliders to 80% of the bar, more or less):

This is the res I'm using:

Still, the problem is with trackpad events as with external mouse (I use an Apple Magic Mouse) it works -way- better. Even if an FPS drop is clearly noticeable.

Stellarium / stellarium