Celestia 1.7.0 Development Thread

[FarGetaNik]

I don't have a GitHub account so I'm posting it here. The latest 1.7 version posted here seems to no longer support the change of ring segment resolution. In the config file,

Code: Select all

   RingSystemSections      256


controls how many sections Celestia uses to approxiamte a circle and the default value of 100 makes it look very choppy if you zoom into a ring moon like say Pan. Changing this value doesn't seem to do anything anymore.

[Markerz]

Changing this value doesn't seem to do anything anymore.

it seems to have been removed in this pr https://github.com/CelestiaProject/Celestia/pull/271/ . the value is always 180.

[Lafuente_Astronomy]

I don't have a GitHub account so I'm posting it here.

Actually, you can make a free Github Account. Your contributions to the discussions in the Github page will really be great

[FarGetaNik]

Why would they remove this option I can't remember a time when rings actually slowed down anything. I would appreachiate if there was an option still. As I demonstrated on the discord already, the restriction procudes obvious artifacts.

Hm that would just be another account to manage. Not sure, if I get more involved with actual developent I might make one.

[onetwothree]

1) RingSystemSections won't be restored because this is a) a workaround b) incorrect, global configuration option. Proper implementation a) should take into account ring size in pixels (like we have LOD for spheres, we should have LOD for rings) b) should draw almost perfect rings using glsl.

2) if somebody is unsatisfied with our changes and want to reject them, s/he can always join the team as a QA and intensively test every pull request, showing flows and problems in our changes.

[FarGetaNik]

If that's the case, I'm ok with it. I just find it odd that you would "break" something on purpose before implementing the update.

[onetwothree]

Now rings look better:

[FarGetaNik]

Looking great, can't wait for the next updated executables

[FarGetaNik]

On that note, are there also any changes done to the orbit path samples and shadow/eclipse texture sizes?

[onetwothree]

Nope.

Added after 23 minutes 3 seconds:
A new windows snapshot available, binary files only.

Changes since the previous one:
* Use bolometric luminosity to calculate comet's tail fading
* Startup logo is not hardcoded any more and can be specified in start.cel
* No more duplicated english body names (e.g. Earth / Earth)
* Splash screen in win32 frontend doesn't cover other (non-Celestia's) windows (will be 1.6.2 too)
* Star orbits are restored
* Dwarf planet orbits and labels are now purple
* In qt and gtk frontends dwarf planets and minor moons are shown in body's context menu
* Fix for markers drawn in multi-view mode (will be 1.6.2 too)
* A lot of internal changes making different part less dependent on each other.

[FarGetaNik]

Nope

Alright so I don't need to worry about these properties then.

Great to see another update on Celestia, keep up the good work

I don't want to bother you but I found a lot of bugs and issues in the 1.7 builds that aren't reported on github as far as I can tell. I was gonna ask if I can help with anything in terms of developement. As for now, where to report bugs, here or should I make a github account?

[Anthony_B_Russo10]

Make a github account

[Lafuente_Astronomy]

Make a github account

Yeah, just make a GitHub account. Anyway, you can make an account for free in GitHub, so it wouldn't be a problem

[Anthony_B_Russo10]

That's why I used github to make an archive for Celestia.

[Lafuente_Astronomy]

onetwothree

I got the new installation files that you presented, and downloaded the ZIP file of the latest version of Celestia with all is latest commits from Celestia's Github.

I used the 64x version of the celestia qt and celestia win files, and when I clicked either the qt or the win version to open it, this notif came:

I downloaded and added the libintl.dll file as instructed, and tried opening it again but then this notif came:

Once again, I downloaded the glew32.dll file as instructed and then tried once again opening it, but then this notif came:

Again, I used the 64x files, so I'm not sure what I did wrong here. And if so, is there something that should be done to solve this issue?

[onetwothree]

Use the full previous release celestia-win64_1.7.0~git20190903+3a56afb.7z and the unpack update celestia-update_1.7.0~git20190906+1776830.7z and then
celestia-update-1.7.0~git20191101+9e9541c.7z

I'm too lazy to build full releases.

[Lafuente_Astronomy]

Use the full previous release celestia-win64_1.7.0~git20190903+3a56afb.7z and the unpack update celestia-update_1.7.0~git20190906+1776830.7z and then
celestia-update-1.7.0~git20191101+9e9541c.7z

I'm too lazy to build full releases.

Where would they be located? Or did you make a directory for them?

[onetwothree]

unpack them anywhere you want

[Lafuente_Astronomy]

I'm too lazy to build full releases.

Alright I found them on Bintray. I had to look once I woke up. But when will you feel that you will release a full release for your latest upcoming update?

[onetwothree]

dunno

Added after 2 hours 50 minutes:
I've just added artifacts creation in our build server so I will not provide snapshots any more.

To download artifacts (exe files) do the following:
* go to https://ci.appveyor.com/project/375gnu/celestia/history
* select a build you want to test (builds with name like 1.7.0-dev-248 are for master branch, 1.7.0-dev-248-fagfajt are for pull requests and may be ignored)

* in the build page select "Artifacts"
* download files you want

Currently only 32bit versions are provided.