Celestia 1.7.0 Development Thread

[john71]

Thank you for the update. Unfortunately I got a VCRUNTIME140D.dll error.

[onetwothree]

Crap, sounds like luajit is a debug build. I'll update it later.

Added after 6 hours 23 minutes:
Crap #2. Luajit builds are debug only. I'll rebuild Celestia with usual Lua. But only on Thursday evening.

[Janus]

@Lafuente_Astronomy

This topic, Pg#22, #437, sorry about late reply, thought I had posted, but apparently I hit the wrong button.


Janus.

[Lafuente_Astronomy]

@Lafuente_Astronomy

This topic, Pg#22, #437, sorry about late reply, thought I had posted, but apparently I hit the wrong button.


Janus.

Thanks a lot, Janus. I'll download it soon

Crap, sounds like luajit is a debug build. I'll update it later.

Added after 6 hours 23 minutes:
Crap #2. Luajit builds are debug only. I'll rebuild Celestia with usual Lua. But only on Thursday evening.

Just a question, why is Luajit is a debug build and therefore, not applicable for Celestia development to the point you'll have to rebuild it with the usual Lua?

[onetwothree]

Just a question, why is Luajit is a debug build and therefore, not applicable for Celestia development to the point you'll have to rebuild it with the usual Lua?

Because it's vcpkg (that's the tool we use to work with dependencies on windows) build file is incorrect. It's file for development but bad for end-users as visual c runtime libraries are built in release mode, and debug libraries are not available unless you install a compiler suite.

[Lafuente_Astronomy]

Because it's vcpkg (that's the tool we use to work with dependencies on windows) build file is incorrect. It's file for development but bad for end-users as visual c runtime libraries are built in release mode, and debug libraries are not available unless you install a compiler suite.

Ahhh. Starting Thursday Night, how are you going to revert everything back to the usual Lua?

[onetwothree]

I will just remove luajit and recompile Celestia using lua5.3 library.

[onetwothree]

Fixed snapshot has been uploaded to https://dl.bintray.com/celestia/celestia-builds/c ... e-1.7.0~git20190710 7b095b8.7z replacing the old archive.

[Janus]

@onetwothree

Check your links.
The colon ':' before celestia-update breaks the link.

https://dl.bintray.com/celestia/celestia-builds/: ... e-1.7.0~git20190710 7b095b8.7z

Should be

https://dl.bintray.com/celestia/celestia-builds/c ... e-1.7.0~git20190710 7b095b8.7z

Thought you should know.


Janus.

EDIT:Spilling fix.

[onetwothree]

Thanks for pointing. But quite strange that it works from https://dl.bintray.com/celestia/celestia-builds/.

[Janus]

Internal vs external addressing filter for file host.
I have seen stuff like this many times.
Links from onsite are treated differently than links from offsite.
Stops spam and other bots from link or automated file harvesting for one thing.
It is likely they filter based on the referrer link of the header for the request.


Janus.

[john71]

Whoa, the win version works perfectly for the first time! Every moon and mesh is visible! Nice!

The fps rates are also good!

[onetwothree]

Whoa, the win version works perfectly for the first time!

1.7 now uses different registry path, so 1.6.1 and 1.7 can be used simultaneously without interfering each other.

[Lafuente_Astronomy]

1.7 now uses different registry path, so 1.6.1 and 1.7 can be used simultaneously without interfering each other.

That's great! What other issues aside from the AstroDB Branch do you think you can deal with on the next snapshot?

[pirogronian]

What other issues aside from the AstroDB Branch

Oh, I didn't realize that branch astrodb is an issue...

[onetwothree]

Basically I work with GL code modernizing it. Among other user-visible changes I might manage to implement TrueType fonts support and video encoding using FFMPEG library. These two are old branches I work from time to time. The 3rd feature that I once started to work with is shadows but it requires quite invasive changes to the current rendering code.

[john71]

I think you should make an official, downloadable release named Celestia 1.7 with an exe file.

This is an usable version and Celestia 1.6.1 is 32 bit only AND very old.

So please make it official.

It would be very nice to have a clean 1.7 installation with an exe file...

Added after 1 minute 50 seconds:
New rendering features can be released with the 1.8 or 1.7.1 version...

Added after 2 minutes 27 seconds:
I mean you should release the win version, the qt version has the same low fps problem as before.

[Lafuente_Astronomy]

Oh, I didn't realize that branch astrodb is an issue...

I didn't mean to say your AstroDB Branch is an issue. I just said that because the AstroDB Branch is your current development within Celestia 1.7.0. I asked Onetwothree regarding the issues of Celestia 1.7.0 that are not issues of the AstroDB Branch. I'm sorry if what I said kind of hurts you. I formally apologize

[pirogronian]

I formally apologize

Lafuente, I just joked! See an emoticon smile at the end of my post. I just like language humor...

Back on topic: I see nothing wrong to release 1.7 with current set of features and move AstroDb to 1.8 (or 2.0). It's going to be a realy big change, I cant estimate when it will pass all necesarry tests.

[john71]

Back on topic: I see nothing wrong to release 1.7 with current set of features

That would be nice.