Page 48 of 69

Posted: 25.10.2020, 20:40
by Anthony_B_Russo10
The builds have failed recently, thats why we haven't had any new releases on Bintray.

Posted: 25.10.2020, 21:53
by SevenSpheres
Georgi wrote:I'm curious what happened with the Bintray releases recently? Can we have newer test releases again? I don't really know which is the latest version currently, there are a bunch of newer exe files in this topic.
Anthony_B_Russo10 wrote:The builds have failed recently, thats why we haven't had any new releases on Bintray.

The Appveyor builds are working. AFAIK the only reason there haven't been Bintray releases is because there are now Appveyor builds; although those are just binaries and not full builds.

Posted: 26.10.2020, 10:37
by Markerz
Bintray builds are just appveyor builds distributed on Bintray. distributing to Bintray has been removed since last year as I know, so just just appveyor builds.

Posted: 26.10.2020, 17:19
by Georgi
SevenSpheres wrote:
Georgi wrote:I'm curious what happened with the Bintray releases recently? Can we have newer test releases again? I don't really know which is the latest version currently, there are a bunch of newer exe files in this topic.
Anthony_B_Russo10 wrote:The builds have failed recently, thats why we haven't had any new releases on Bintray.

The Appveyor builds are working. AFAIK the only reason there haven't been Bintray releases is because there are now Appveyor builds; although those are just binaries and not full builds.

I believe that the "Artifacts" are the binaries for the current release? Then I guess that the last full release was on Bintray and I should apply the exe updates to it?

Posted: 29.10.2020, 12:40
by Markerz
Georgi wrote:I believe that the "Artifacts" are the binaries for the current release?
The artifacts are the output binary for the commit it builds against. It's not an actual release, it is just that for every commit in the repo, appveyor will run and build a new binary. Usually you just need to replace the .exe, but sometimes like the latest halo fix, you also need to download the latest shaders.

Posted: 15.11.2020, 16:12
by Art Blos
Let somebody post the latest 1.7.0 beta for Windows (32 & 64 bit). It is highly desirable as a single installer. Thanks in advance.

Posted: 16.11.2020, 08:24
by Art Blos
What, no one has an installer? Or does it not exist in the Universe?
Then Origin will not switch to a new basis until at least one stable link appears on GitHub. :smoke:

Posted: 14.01.2021, 15:13
by onetwothree
Since today one can pass option -l or --log with a file name and messages written to console (`) will be duplicated to the specified file.

Please note that 1) only Qt-based interface supports this feature 2) file content will be overwritten on every invocation, appending is not supported.

Example:

celestia-qt --log celestia.log

Windows executable files can be downloaded from https://ci.appveyor.com/project/375gnu/celestia/builds/37265607

Posted: 18.01.2021, 20:50
by StarTrekking
Hi I am Gianluca from Italy. I have a dome of 7 meter. Celestia work in fisheye mode like Stellarium ?
If Yes how can i download the software ?
My best regards and sorry for my bad english.

Posted: 18.01.2021, 21:02
by SevenSpheres
StarTrekking wrote:Hi I am Gianluca from Italy. I have a dome of 7 meter. Celestia work in fisheye mode like Stellarium ?
If Yes how can i download the software ?
My best regards and sorry for my bad english.

Yes, see this thread and the corresponding GitHub thread.

Posted: 18.01.2021, 21:08
by StarTrekking
But is for spherical mirror i need for fisheye like stellarium.
The questions are:
1) How can i download Celestia 1.7 for windows 10 ?
2) Celestia 1.7 support the fisheye mode ?

Posted: 18.01.2021, 21:41
by Anthony_B_Russo10
For 1.7.0 you have to use Bintree releases and it does not support fisheye projection.

Posted: 18.01.2021, 21:50
by SevenSpheres
Anthony_B_Russo10 wrote:For 1.7.0 you have to use Bintree releases and it does not support fisheye projection.

It does support fisheye projection, as stated in the threads I linked.

onetwothree wrote:
Just a few minutes ago @markerz merged his branch to master. Now we have support for fish eye projection and some other distortions. Some work is still to be done but the most important part is finished. All hail to @markerz!

Posted: 19.01.2021, 04:34
by Anthony_B_Russo10
I keep forgetting.

Posted: 01.02.2021, 18:29
by john71
Can we get a preview exe file to test it?

Posted: 01.02.2021, 21:32
by Gurren Lagann
We already have preview exe files from Appveyor. They are more like compiled builds, but eh...

Posted: 22.02.2021, 02:03
by John Van Vliet
i just tested your git code ( 1.7 ) and it takes a fair amount of hacking using " ccmake" , the cmake GUI , to get it to build with spice enabled

but it dose finally build on OpenSUSE 15.2

but there are some annoying crashes and it is NOT stable

Posted: 22.02.2021, 10:10
by onetwothree
John Van Vliet wrote:i just tested your git code ( 1.7 ) and it takes a fair amount of hacking using " ccmake" , the cmake GUI , to get it to build with spice enabled

You just need to do a full clone with submodules and then to pass -DENABLE_SPICE=ON to cmake. But on OpenSUSE everything is much easier as our friend munix9 provides packages: https://build.opensuse.org/package/binaries/home: ... le/celestia/openSUSE_Leap_15.2.

John Van Vliet wrote:but there are some annoying crashes and it is NOT stable

I would like to see gdb output for them or at least test data which causes crashes.

Posted: 22.02.2021, 13:30
by John Van Vliet
i did enable spice ( -DENABLE_SPICE=ON )
but cmake fails at finding libSpice.so or cspice.a , depending on the spice build

i needed to give the full path including the lib mame
/usr/lib64/libSpice.so



as for gdb that is my next thing to do

Posted: 23.02.2021, 23:25
by John Van Vliet
gdb not much help

using SOHO and spice orbit i some times have a crash
( soho and 67p are the only addons i have installed other than the planets and moons using spice )

gdb is of little help
this is the error

Code: Select all

Thread 1 "celestia-qt" received signal SIGSEGV, Segmentation fault.
0x00007ffff2363669 in glBindBuffer () from /usr/lib64/libGLdispatch.so.0
(gdb)