Closed stooge75 closed 1 year ago
The question may seem strange, but is the mount connected to the computer at startup of the planetarium?
Yes it is. I just tried again and again crashed. Here’s the thing and I don’t know if this is having anything to do with it. After I open stellarium, I goto ‘atmosphere’ and click it so I can see the stars. Then I goto configuration spanner on left side and just as I click on spanner,sometimes the eqmod panel will appear and then it crashes. But sometimes it won’t. Frustrating
Sorry I didn’t mean to close this
Could you for the experiment disable autoconnect to the mount in the Telescope Control plugin?
You mean at load at startup tick box ? I’ll try it now
Well I just unticked the load at startup and it no longer crashes. Just tried starting stellarium 3 times and no crash. Plus no eqmod appearance as I click on spanner
Did you disable the plugin or automatic connect to the mount within plugin?
I just unticked the box for load at startup in telescope control. My eq6-r mount isn’t on the screen at Polaris so not connected. But if I go back to plugin and telescope control and tick the box to load at startup,then restart stellarium it crashes again
I cannot click on configure in telescope control as it is not available,it’s greyed out. Unless load at startup is ticked
If you need to connect to this computer to check anything just let me know,no problem
Could you find and send me to email file telescopes.json
?
P.S. Hint: please try C:\Users\ACER\AppData\Roaming\Stellarium\modules\TelescopeControl\telescopes.json
{ "1": { "ascom_device_id": "EQMOD.Telescope", "ascom_use_device_eq_coord_type": true, "connect_at_startup": true, "connection": "ASCOM", "delay": 500000, "equinox": "J2000", "name": "EQ6R-PRO", "tcp_port": 10001 }, "version": "0.4.1" }
On Tue, 1 Nov 2022 at 15:19, Alexander V. Wolf @.***> wrote:
Could you find and send me to email file telescopes.json?
— Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/2804#issuecomment-1298692001, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANJ73CMCXBU5ITFNOSYCSPTWGEYJVANCNFSM6AAAAAARUCBWNM . You are receiving this because you modified the open/close state.Message ID: @.***>
Just in case it makes any difference,my mount has the new chipset! I just thought I would mention it because when I use asiair I had to load a special operating system onto the asiair because it would not detect my mount if left to ordinary OS.
Please try do next steps: 1) Update telescopes.json file as here:
{
"1": {
"ascom_device_id": "EQMOD.Telescope",
"ascom_use_device_eq_coord_type": true,
"connect_at_startup": false,
"connection": "ASCOM",
"delay": 500000,
"equinox": "J2000",
"name": "EQ6R-PRO",
"tcp_port": 10001
},
"version": "0.4.1"
}
2) Run Stellarium and tick "Load at startup" checkbox for Telescope Control plugin 3) Restart Stellarium
That doesn’t work. After I do that and restart stellarium mount is not connected. So I have to go to telescope control and manually connect. And once that’s done it crashes soon after
That doesn’t work. After I do that and restart stellarium mount is not connected. So I have to go to telescope control and manually connect. And once that’s done it crashes soon after
But we found the source of crash - ASCOM client in Telescope Control plugin
Could any of this be due to my mount having the new chipset?
Could any of this be due to my mount having the new chipset?
I don't know, sorry.
Can you sort the issue? Or is it an ASCOM issue?
I’ve installed an older version. It doesn’t crash,but I still have a tiny issue that when I go to click on configuration spanner at left of screen,sometimes eqmod (or ascom,I get confused. The panel that has north south east etc) panel will appear just as I click on the spanner,and this means I often click on something on the eqmod panel ie east button. By now I can tell when this will happen because normally when the cursor is hovering above the spanner,the outside of the button will light up(a thin lit line!),and when the eqmod thing happens there’s never the lit-up line around the spanner button beforehand.
Please try use windowed mode (F11)
Can you sort the issue? Or is it an ASCOM issue?
I don't have hardware for testing - maybe ASCOM Simulator can help sort the issue
I’m at the end of my patience with it. I’m a bit lucky in that I also have asiair that works ok so can use that just now but I feel bad for people who only have stellarium/nina etc. something is telling me that my issue is something that entails this new chipset in the eq6-r pro mount. I’ve got in touch with synta(skywatcher), to ask them if in their opinion,this new chipset can have a negative effect on using stellarium and in particular the ascom client. I don’t know what else to say
I have the same issue as stooge75 but i have a older eq6 atlas...1.0 crashed...i updated to 1.1 it crashed also about 5 secs after start up..i disabled telescope plug in and it ran until i ran it again at start up...i went back and downloaded the 1.1 QT5 stellaruim and all is well now and no crashes...QT6 framework seems to crash my win 10 machine with AMD
@stooge75 could you test your mount with version 1.1-qt5?
It no longer crashes. But I’ve maybe stumbled onto something that was also happening. Remember when I said I clicked on spanner the eqmod panel would appear,I just switched on pc and started stellarium and went to click on spanner on left and it never lit up(if I clicked on it I just knew the eqmod panel would appear!), so I went back to desktop and changed resolution (my pc is always telling me at switch on to check resolution), and came back to stellarium and hovered over the spanner and it lit up. I clicked on it and NO eqmod panel! So maybe resolution has something to do with the problem? Because I see somewhere that it says 95% of problems are due to graphics!! Anyway I have to go out I will see more later when I’m back home
Well Alex, QT5 seems to be working without crashing so far,with my eq6-r mount connected as well! Since I changed my resolution the spanner problem has not reappeared. Fingers crossed
argh it doesnt crash but every time i go to click on the spanner at the beginning it opens the eqmod panel ie north south east west thing,and it says 'runtime error 9' subscript out of range. driving me mad!!!!
Please attach the log
Writing log file to: "C:\Users\martin thomson\AppData\Roaming\Stellarium\log.txt"
File search paths:
0 . "C:\Users\martin thomson\AppData\Roaming\Stellarium"
1 . "."
Config file is: "C:\Users\martin thomson\AppData\Roaming\Stellarium\config.ini"
Default surface format: QSurfaceFormat(version 2.0, options QFlags
i am not with mount so it is not connected,but i used to get this regardless of whether mount is connected or not
this is a brand new fresh set up and installation of stellarium on fresh windows install(with updates done etc). this is the same problem i was telling you alex about,when i go to click on spanner on left side for configuration. one thing though,maybe its nothing maybe its something. i never had the spanner/runtime error before i changed the remote control setting in plugin. i clicked on the box for allow at startup,then have to shut down stellarium so i could reopen to configure remote control. as soon as it opens again and i go to spanner,it does not light up and that is when i click on it ,eqmod panel appears and runtime error!
oh i just changed my resolution on display and i dont think its giving me error anymore
Writing log file to: "C:\Users\martin thomson\AppData\Roaming\Stellarium\log.txt"
File search paths:
0 . "C:\Users\martin thomson\AppData\Roaming\Stellarium"
1 . "."
Config file is: "C:\Users\martin thomson\AppData\Roaming\Stellarium\config.ini"
Default surface format: QSurfaceFormat(version 2.0, options QFlags
This is a good task for the community to participate in the contribution into Stellarium. Who wants to help us?
Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot
Several Qt6/TelescopeControl issues have been solved before 23.3. We tentatively close this as member of a large group of related issue reports for now. In case of re-occurrence of this issue in V23.3, please create a new report with very clear description of circumstances.
Win 10. Intel graphics 64bit Fresh install of stellarium qt6 and ascom eqmod and stellarium still crashes at about the start. Here is last run log Writing log file to: "C:\Users\ACER\AppData\Roaming\Stellarium\log.txt" File search paths: 0 . "C:\Users\ACER\AppData\Roaming\Stellarium" 1 . "." Config file is: "C:\Users\ACER\AppData\Roaming\Stellarium\config.ini" Default surface format: QSurfaceFormat(version 2.0, options QFlags(), 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
Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing.
Default surface format: QSurfaceFormat(version 3.3, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QColorSpace(), profile QSurfaceFormat::CoreProfile)
OpenGL module type: 0
StelGLWidget constructor
StelGraphicsScene constructor
initializeGL
OpenGL supported version: "3.3.0 - Build 20.19.15.5126"
Current Format: QSurfaceFormat(version 3.3, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QColorSpace(), profile QSurfaceFormat::CoreProfile)
StelMainView::init
Luminance textures are not supported
Detected: OpenGL "3.3"
Driver version string: "3.3.0 - Build 20.19.15.5126"
GL vendor is "Intel"
GL renderer is "Intel(R) HD Graphics 4400"
GL Shading Language version is "3.30 - Build 20.19.15.5126"
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 "en_GB"
Empty translation file for language "en_GB" in section "stellarium-planetary-features"
Planetary features language is "en_GB"
Application language is "en_GB"
Scripts language is "en_GB"
Cache directory is: "C:\Users\ACER\AppData\Local\stellarium\stellarium\cache"
Loaded 252 countries
Loaded 193 regions
Loading Solar System data (1: planets and moons) ...
Loading from : "./data/ssystem_major.ini"
SolarSystem has 83 entries.
Loaded 83 Solar System bodies
Loading Solar System data (2: minor bodies)...
Loading from : "C:\Users\ACER\AppData\Roaming\Stellarium/data/ssystem_minor.ini"
SolarSystem has 190 entries.
Loaded 107 Solar System bodies
File ssystem_minor.ini is loaded successfully...
Loading nomenclature for Solar system bodies ...
Loaded 15833 / 15835 items of planetary surface nomenclature
WARNING - These planets to assign nomenclature items were not found: "Dactyl"
Loading star data ...
"Loading .\stars\default\stars_0_0v0_8.cat: 0_0v0_8; 4979"
"Loading .\stars\default\stars_1_0v0_8.cat: 1_0v0_8; 21806"
"Loading .\stars\default\stars_2_0v0_8.cat: 2_0v0_8; 150826"
"Loading .\stars\default\stars_3_1v0_4.cat: 3_1v0_4; 425807"
Finished loading star catalogue data, max_geodesic_level: 3
Loading scientific star names from ".\stars\default\name.fab"
Loaded 4942 / 4942 scientific star names
Loading scientific star extra names from ".\stars\default\extra_name.fab"
Loaded 26200 / 26200 scientific star extra names
Loading variable stars from ".\stars\default\gcvs_hip_part.dat"
Loaded 6862 / 6862 variable stars
Loading double stars from ".\stars\default\wds_hip_part.dat"
Loaded 22992 / 22992 double stars
Loading cross-identification data from ".\stars\default\cross-id.dat"
Loaded 108378 / 108378 cross-identification data records for stars
Loading parallax errors data from ".\stars\default\hip_plx_err.dat"
Loaded 117703 / 117703 parallax error data records for stars
Loading proper motion data from ".\stars\default\hip_pm.dat"
Loaded 117955 / 117955 proper motion data records for stars
StelCore: Invalid timezone name: "" -- not setting timezone.
navigation/preset_sky_time is a double - treating as jday: "2451514.25001"
Loading DSO data ...
[...] "Stellarium DSO Catalog, version 3.17 (standard edition)"
Loaded 94663 DSO records
Loading DSO outline data ...
Loaded 98 DSO outline records successfully
Got location ", , United Kingdom (51.4964, -0.1224; Europe/London)" for IP "51.198.13.11"
LandscapeMgr: initialized Cache for 100 MB.
Loading star names from ".\skycultures\western\star_names.fab"
Loaded 1102 / 1102 common star names
Loading DSO name data ...
Loaded 1212 / 1236 DSO name records successfully
WARNING - No position data for 24 objects: "NGC 4173, 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 "western"
Loaded 85 / 85 constellation art records successfully for culture "western"
Loaded 88 / 88 constellation names
Loading constellation boundary data ...
Loaded 782 constellation boundary segments
Error in Asterism "TA6" : can't find star with coordinates 2.14697 / 8.55097
ERROR reading asterism lines record at line 88 for culture "western"
Loaded 83 / 84 asterism records successfully for culture "western"
WARNING - asterism abbreviation "TA6" not found when loading asterism names
Loaded 73 / 74 asterism names
Initializing basic GL shaders...
Creating GUI ...
Loading Style file ":/graphicGui/normalStyle.css"
C:\stellarium\src\StelMainView.cpp:940: OpenGL context changed, fixing!
Loaded plugin "Exoplanets"
[Exoplanets] Version of the format of the catalog: 1
[Exoplanets] loading catalog file: "C:\Users\ACER\AppData\Roaming\Stellarium\modules\Exoplanets\exoplanets.json"
Loaded plugin "MeteorShowers"
[MeteorShowersMgr] Loading catalog file: "C:\Users\ACER\AppData\Roaming\Stellarium\modules\MeteorShowers\MeteorShowers.json"
[MeteorShowersMgr] Version of the format of the catalog: 2
Loaded plugin "Novae"
[Novae] version of the catalog: 1
[Novae] loading catalog file: "C:\Users\ACER\AppData\Roaming\Stellarium\modules\Novae\novae.json"
Loaded plugin "Oculars"
Oculars::validateAndLoadIniFile() ocular.ini exists at: "C:\Users\ACER\AppData\Roaming\Stellarium\modules\Oculars\ocular.ini" . Checking version...
Oculars::validateAndLoadIniFile() found existing ini file version 3.1
Loaded plugin "RemoteControl"
RemoteControl using QtWebApp version 1.6.4-stellarium
StaticFileController: docroot=C:/Program Files/Stellarium/webroot, encoding=UTF-8, maxAge=60
StaticFileController: cache timeout=60000, size=1048576
RemoteControl enabled
HttpListener: Listening on port 8090
Loaded plugin "Satellites"
[Satellites] loading catalogue file: "C:\Users\ACER\AppData\Roaming\Stellarium\modules\Satellites\satellites.json"
Satellite has invalid orbit: "SIMPL" "42983"
Satellite has invalid orbit: "AEROCUBE 7B (OCSD B)" "43042"
Satellite has invalid orbit: "AEROCUBE 7C (OCSD C)" "43043"
Satellite has invalid orbit: "ASGARDIA 1" "43049"
Satellite has invalid orbit: "PROPCUBE 2 (FAUNA)" "43052"
Satellite has invalid orbit: "SPACEBEE-1" "43142"
Satellite has invalid orbit: "ELFIN-A" "43617"
Satellite has invalid orbit: "STARLINK-61" "44249"
Satellite has invalid orbit: "ISS DEB" "44303"
Satellite has invalid orbit: "ISS DEB" "44306"
Satellite has invalid orbit: "ARMADILLO" "44352"
Satellite has invalid orbit: "RED-EYE 1 (PINOT)" "44364"
Satellite has invalid orbit: "ACRUX 1" "44369"
Satellite has invalid orbit: "PHOENIX" "45258"
Satellite has invalid orbit: "STARLINK-1501" "45763"
Satellite has invalid orbit: "STARLINK-1514" "46046"
Satellite has invalid orbit: "STARLINK-1531" "46572"
Satellite has invalid orbit: "STARLINK-1781" "46685"
Satellite has invalid orbit: "STARLINK-1810" "46709"
Satellite has invalid orbit: "STARLINK-1821" "46718"
Satellite has invalid orbit: "SPOC" "46921"
Satellite has invalid orbit: "NEUTRON-1" "46923"
Satellite has invalid orbit: "DESCENT" "46927"
Satellite has invalid orbit: "STARLINK-1874" "47159"
Satellite has invalid orbit: "STARLINK-2080" "47365"
Satellite has invalid orbit: "STARLINK-2023" "47605"
Satellite has invalid orbit: "STARLINK-1704" "47625"
Satellite has invalid orbit: "STARLINK-2067" "47674"
Satellite has invalid orbit: "STARLINK-2401" "47818"
Satellite has invalid orbit: "TSURU" "47927"
Satellite has invalid orbit: "MAYA-2" "47929"
Satellite has invalid orbit: "GUARANISAT-1" "47931"
Satellite has invalid orbit: "STARLINK-2239" "48017"
Satellite has invalid orbit: "ONEWEB-0251" "48969"
Satellite has invalid orbit: "MAYA-3" "49273"
Satellite has invalid orbit: "MAYA-4" "49274"
Satellite has invalid orbit: "PR-CUNAR 2" "49277"
Satellite has invalid orbit: "ONEWEB-0349" "49281"
Satellite has invalid orbit: "ONEWEB-0356" "49283"
Satellite has invalid orbit: "ONEWEB-0360" "49286"
Satellite has invalid orbit: "ONEWEB-0361" "49287"
Satellite has invalid orbit: "ONEWEB-0363" "49289"
Satellite has invalid orbit: "ONEWEB-0367" "49293"
Satellite has invalid orbit: "ONEWEB-0370" "49296"
Satellite has invalid orbit: "ONEWEB-0372" "49298"
Satellite has invalid orbit: "ONEWEB-0378" "49304"
Satellite has invalid orbit: "ONEWEB-0381" "49307"
Satellite has invalid orbit: "ONEWEB-0382" "49308"
Satellite has invalid orbit: "ONEWEB-0384" "49310"
Satellite has invalid orbit: "ONEWEB-0385" "49311"
Satellite has invalid orbit: "ONEWEB-0386" "49312"
Satellite has invalid orbit: "ONEWEB-0387" "49313"
Satellite has invalid orbit: "STARLINK-3307" "50164"
Satellite has invalid orbit: "ONEWEB-0389" "50469"
Satellite has invalid orbit: "ONEWEB-0390" "50470"
Satellite has invalid orbit: "ONEWEB-0391" "50471"
Satellite has invalid orbit: "ONEWEB-0392" "50472"
Satellite has invalid orbit: "ONEWEB-0393" "50473"
Satellite has invalid orbit: "DAILI" "51443"
Satellite has invalid orbit: "GT-1" "51510"
Satellite has invalid orbit: "STARLINK-3613" "51810"
Satellite has invalid orbit: "STARLINK-3556" "51877"
Satellite has invalid orbit: "STARLINK-3572" "51879"
Satellite has invalid orbit: "STARLINK-3570" "51882"
Satellite has invalid orbit: "STARLINK-3576" "51883"
Satellite has invalid orbit: "STARLINK-3577" "51884"
Satellite has invalid orbit: "STARLINK-3565" "51886"
Satellite has invalid orbit: "STARLINK-3536" "51888"
Satellite has invalid orbit: "STARLINK-3519" "51890"
Satellite has invalid orbit: "STARLINK-3667" "51999"
Satellite has invalid orbit: "ISS DEB" "52329"
Satellite has invalid orbit: "STARLINK-3785" "52375"
Satellite has invalid orbit: "STARLINK-3806" "52378"
Satellite has invalid orbit: "STARLINK-3840" "52466"
Satellite has invalid orbit: "STARLINK-3859" "52470"
Satellite has invalid orbit: "STARLINK-3839" "52480"
Satellite has invalid orbit: "STARLINK-3907" "52501"
Satellite has invalid orbit: "FALCON 9 DEB" "52504"
Satellite has invalid orbit: "FALCON 9 DEB" "52505"
Satellite has invalid orbit: "FALCON 9 DEB" "52506"
Satellite has invalid orbit: "FALCON 9 DEB" "52507"
Satellite has invalid orbit: "STARLINK-3897" "52537"
Satellite has invalid orbit: "STARLINK-3933" "52538"
Satellite has invalid orbit: "STARLINK-3757" "52539"
Satellite has invalid orbit: "STARLINK-3940" "52540"
Satellite has invalid orbit: "STARLINK-3926" "52543"
Satellite has invalid orbit: "STARLINK-3939" "52545"
Satellite has invalid orbit: "STARLINK-3935" "52549"
Satellite has invalid orbit: "FALCON 9 DEB" "52589"
Satellite has invalid orbit: "FALCON 9 DEB" "52595"
Satellite has invalid orbit: "FALCON 9 DEB" "52596"
Satellite has invalid orbit: "FALCON 9 DEB" "52597"
Satellite has invalid orbit: "STARLINK-4009" "52624"
Satellite has invalid orbit: "STARLINK-3992" "52627"
Satellite has invalid orbit: "FALCON 9 DEB" "52651"
Satellite has invalid orbit: "FALCON 9 DEB" "52652"
Satellite has invalid orbit: "FALCON 9 DEB" "52653"
Satellite has invalid orbit: "FALCON 9 DEB" "52654"
Satellite has invalid orbit: "FALCON 9 DEB" "52709"
Satellite has invalid orbit: "FALCON 9 DEB" "52710"
Satellite has invalid orbit: "FALCON 9 DEB" "52711"
Satellite has invalid orbit: "FALCON 9 DEB" "52712"
Satellite has invalid orbit: "OBJECT B" "52798"
Loaded plugin "SolarSystemEditor"
Using the ssystem_minor.ini file that already exists in the user directory...
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
connectionType: TelescopeControl::ConnectionASCOM initString: "EQ6R-PRO:ASCOM:J2000:EQMOD.Telescope:true"
Creating telescope "EQ6R-PRO:ASCOM:J2000:EQMOD.Telescope:true" ; name/type/equinox/params: "EQ6R-PRO" "ASCOM" J2000 "EQMOD.Telescope:true"
TelescopeClientASCOM::TelescopeClientASCOM with telescope name "EQ6R-PRO" and ascomDeviceId "EQMOD.Telescope"
OleInvoke: Exception [scode: -2147220480 wcode: 0 puArgErr: 0 ] GLE: 0
Could not get DoesRefraction for device: "EQMOD.Telescope"
[TelescopeControl] Loaded successfully 1 telescopes.