Celestia 1.7.0 Development Thread
-
- Developer
- Posts: 274
- Joined: 29.01.2009
- Age: 29
- With us: 15 years 9 months
- Location: Suzhou, China
About hi-res saturn showing up black, it is related to texture size. The texture in hi-res folder is 2880 x 1440, an npot texture , which shows up black on iOS... So we will need to scale it down to 2048 x 1024....
Does the extras directory not work? I'm not sure, does Celestia scan the extra directories to find textures? @onetwothree
Does the extras directory not work? I'm not sure, does Celestia scan the extra directories to find textures? @onetwothree
-
Topic authoronetwothree
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 2 months
- Gurren Lagann
- Posts: 434
- Joined: 31.01.2018
- Age: 18
- With us: 6 years 9 months
- Location: State of Rio de Janeiro, Brazil
I have an idea to implement subclasses beyond 9:
The core of the star subclasses is at star.cpp - in it, there's this little snippet of code:
Or something like that, at lines 389-391. Sure, that's not the only thing we need to change here, but this is basically the key.
If we want to, say, extend it to 11, change "SubclassNames[11]" to "SubclassNames[13]", then add 10 and 11. We configure the parameters for subclasses 10 and 11, and we are set.
We can also do this for white dwarfs, if the devs want:
The core of the star subclasses is at star.cpp - in it, there's this little snippet of code:
Code: Select all
const char*
SubclassNames[11] = {
"0", "1", "2", "3", "4", "5", "6", "7", "8", "9", ""};
Or something like that, at lines 389-391. Sure, that's not the only thing we need to change here, but this is basically the key.
If we want to, say, extend it to 11, change "SubclassNames[11]" to "SubclassNames[13]", then add 10 and 11. We configure the parameters for subclasses 10 and 11, and we are set.
We can also do this for white dwarfs, if the devs want:
Code: Select all
const char*
WhiteDwarfSubclassNames[13] = {
"0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", ""};
"The tomorrow we're trying to reach is not a tomorrow you had decided on!"
- Simon the Digger
"Nothing is impossible for me, as long I'm determinated to keep moving forward!"
"If other people aren't going to do it, I'm going to do it myself!"
- Me (Gurren)
Current major projects:
- Aur Cir
- Cel+
- Project Sisyphus
- Populating the Local Group
- An galaxy generator
- Simon the Digger
"Nothing is impossible for me, as long I'm determinated to keep moving forward!"
"If other people aren't going to do it, I'm going to do it myself!"
- Me (Gurren)
Current major projects:
- Aur Cir
- Cel+
- Project Sisyphus
- Populating the Local Group
- An galaxy generator
- SevenSpheres
- Moderator
- Posts: 826
- Joined: 08.10.2019
- With us: 5 years 1 month
Some notes: For white dwarfs, the subclasses would need to go to 14. Also, white dwarf subclasses are calculated by dividing 50400 by the temperature, so that could be used in Celestia's code to determine a white dwarf's temperature from its subclass.
My Addons: viewtopic.php?f=23&t=19978 • Discord server admin
Celestia versions: 1.5.1, 1.6.1, 1.6.2, 1.7.0, and some unofficial versions like Celestia-ED
Celestia versions: 1.5.1, 1.6.1, 1.6.2, 1.7.0, and some unofficial versions like Celestia-ED
Thoughts: to retain backwards compatibility, would it be better to organize it like this:
where the "" entry comes before "10", etc.?
Of course I am not a developer by any means, so it would best for them to decide.
Code: Select all
const char*
WhiteDwarfSubclassNames[13] = {
"0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "", "10", "11"};
where the "" entry comes before "10", etc.?
Of course I am not a developer by any means, so it would best for them to decide.
Hi Markerz and Onetwothree,
the virtual textures are not used for AddOns either. They show only if I copy them in the program directory. That's why I think it would be good if there is a textures folder in the library.
An I have another question. I wonder if the go to modal keeps track of the last searched items? I think it would be cool when you click on the arrow button and it would display the last 10 or so targets you searched for, instead of suggestions (which I just found out a minute ago, lol).
the virtual textures are not used for AddOns either. They show only if I copy them in the program directory. That's why I think it would be good if there is a textures folder in the library.
An I have another question. I wonder if the go to modal keeps track of the last searched items? I think it would be cool when you click on the arrow button and it would display the last 10 or so targets you searched for, instead of suggestions (which I just found out a minute ago, lol).
-
- Developer
- Posts: 274
- Joined: 29.01.2009
- Age: 29
- With us: 15 years 9 months
- Location: Suzhou, China
I think I'm going to make a release in a couple of days. for iOS/Mac/Android. my plan is to use the non-metal version on iOS, and the non-metal version on Mac (not the Catalyst one). Since I tested on early 2013 MacBook Pro, The catalyst version (with MetalANGLE) has significant problem rendering texture. It is not due to it being built on Catalyst though, since the AppKit version also has it when I switched to MetalANGLE, it might be MetalANGLE's bug.
However I kinda of want to release the iOS version with MetalANGLE, since it is slightly faster, and might actually be more compatible (it can render npot textures without problem)... Celestia is targeting iOS 11+, so the earliest iPhone it supports will be iPhone 5s, which was also released in 2013, I don't know if the problem that exists on Mac also exists on iOS. I can only say that it runs well on iPhone 7 (since @Dimmi72 tested), iPhone X, iPhone SE (second generation).
For Android, the minimum requirement will remain Android 5.0, but I kinda of want to get rid of 32bit support.
Android/iOS version will be 1.0, the Mac will have version number of 1.7.0.
However I kinda of want to release the iOS version with MetalANGLE, since it is slightly faster, and might actually be more compatible (it can render npot textures without problem)... Celestia is targeting iOS 11+, so the earliest iPhone it supports will be iPhone 5s, which was also released in 2013, I don't know if the problem that exists on Mac also exists on iOS. I can only say that it runs well on iPhone 7 (since @Dimmi72 tested), iPhone X, iPhone SE (second generation).
For Android, the minimum requirement will remain Android 5.0, but I kinda of want to get rid of 32bit support.
Android/iOS version will be 1.0, the Mac will have version number of 1.7.0.
Hello,
Once I had translated .po files of Celestia to Japanese.
I have been away from Celestia for years, but the new version of Celestia is coming, so I want to update ja.po files for 1.7.0.
I attached the archive of ja.po files in /po/ and /po3/ (the one in /po2/ has nothing to do, so not contained).
I would be grateful if the files are added to Celestia sources.
Once I had translated .po files of Celestia to Japanese.
I have been away from Celestia for years, but the new version of Celestia is coming, so I want to update ja.po files for 1.7.0.
I attached the archive of ja.po files in /po/ and /po3/ (the one in /po2/ has nothing to do, so not contained).
I would be grateful if the files are added to Celestia sources.
- Attachments
-
- ja.po_files.zip
- (36.4 KiB) Downloaded 322 times
-Suι
-
- Developer
- Posts: 274
- Joined: 29.01.2009
- Age: 29
- With us: 15 years 9 months
- Location: Suzhou, China
Thanks, Sui! It is great help. I'll integrate it in my fork for now, since your translation is based on my fork. which has a little difference from the main repo. The specific differences are the new introduced strings of "Hong Kong" and "Nur-Sultan".
Added after 3 hours 30 minutes:
@Dimmi72, this is the hopefully last version before we make a release on AppStore, can you test it? https://install.appcenter.ms/orgs/celestiaproject ... ribution_groups/public testers
Also the iOS version is up on TestFlight, build 38.
Added after 3 hours 30 minutes:
@Dimmi72, this is the hopefully last version before we make a release on AppStore, can you test it? https://install.appcenter.ms/orgs/celestiaproject ... ribution_groups/public testers
Also the iOS version is up on TestFlight, build 38.
Hi Markerz,
I tested both versions. The both run very smooth.
The IOS Version runs the demo on my phone with around 60 fps most of the time. Dropping only to 57.5 sometimes, the lowest was 53.3 fps for a second. It seems to stutter when the star names are shown. Like I mentioned before, the distance in the demo is to close for the planets, the moons and the solar system, so it shows only a part of it, since its to close.. At least on my phone.
The MacApp runs great as the previous one. I really would appreciate if there would be a texture folder in the library, since you loose all the virtual textures added to the app, every time you update it. If there would be a textures folder that is scanned during start in the library, you only have to add the virtual textures once.
I tested both versions. The both run very smooth.
The IOS Version runs the demo on my phone with around 60 fps most of the time. Dropping only to 57.5 sometimes, the lowest was 53.3 fps for a second. It seems to stutter when the star names are shown. Like I mentioned before, the distance in the demo is to close for the planets, the moons and the solar system, so it shows only a part of it, since its to close.. At least on my phone.
The MacApp runs great as the previous one. I really would appreciate if there would be a texture folder in the library, since you loose all the virtual textures added to the app, every time you update it. If there would be a textures folder that is scanned during start in the library, you only have to add the virtual textures once.
Hello Markerz,
Thank you very much for committing the files.
Thank you very much for committing the files.
Yes, I chose your fork because I think it is better to use a version that has new strings.Markerz wrote:Thanks, Sui! It is great help. I'll integrate it in my fork for now, since your translation is based on my fork. which has a little difference from the main repo. The specific differences are the new introduced strings of "Hong Kong" and "Nur-Sultan".
-Suι
-
- Developer
- Posts: 274
- Joined: 29.01.2009
- Age: 29
- With us: 15 years 9 months
- Location: Suzhou, China
Thanks again, you should be able to see your work in the 1.0 release of Celestia on Android/iOS
Android: https://play.google.com/store/apps/details?id=space.celestia.mobilecelestia
iOS: https://apps.apple.com/us/app/id1500434829
Android: https://play.google.com/store/apps/details?id=space.celestia.mobilecelestia
iOS: https://apps.apple.com/us/app/id1500434829
Hi Markerz,
it is an option yes.
I know a little bit about how programs and the structure work on Mac. But I think there are people who are not very good at that or are afraid of messing with program files, therefore I think it would be convenient to just place the virtual textures in a folder in the library. Just a thought.
it is an option yes.
I know a little bit about how programs and the structure work on Mac. But I think there are people who are not very good at that or are afraid of messing with program files, therefore I think it would be convenient to just place the virtual textures in a folder in the library. Just a thought.
-
Topic authoronetwothree
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 2 months
Since today and build 1.7.0-dev-400 users using appveyor builds should download an additional archive celestia-dep.x86.7z. This archive contains all required dll and especially celestia.dll extracted from exe files. So, to run native windows exe, one needs celestia-win.x86.7z + celestia-dep.x86.7z, to use qt exe celestia-qt.x86.7z + celestia-dep.x86.7z.
-
Topic authoronetwothree
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 2 months