[pull] master from CelestiaProject:master#62
Open
pull[bot] wants to merge 1232 commits intohttpsgithu:masterfrom
Open
[pull] master from CelestiaProject:master#62pull[bot] wants to merge 1232 commits intohttpsgithu:masterfrom
pull[bot] wants to merge 1232 commits intohttpsgithu:masterfrom
Conversation
375gnu
force-pushed
the
master
branch
3 times, most recently
from
690ab56 to
2f8f3b0
Compare
- Remove models with unclear license - Use test CMOD file with a wider selection of attributes - Use simple icosphere model to test 3DS loader
- Move StarDBBuilder to separate files - Move cross-index catalogs into StarNameDatabase - Use indices instead of pointers in catalogNumberIndex
- Fix handling of modification of individual RA/Dec coordinates - Detect cyclic OrbitBarycenter references - Detect missing magnitude, spectral type when converting Barycenter back to Star - Fix line number handling in Tokenizer - Allow Modify to remove OrbitBarycenter if RA/Dec/Position are specified
Update openSUSE Leap and Ubuntu.
In Debian Bookworm for ARM64 it's resolved to C version for integers. Closes: #2208
- Use unique_ptr to hold DSOs - Use default growth strategy for DSO vector, as binary DSO files were never implemented
- Use vcpkg manifest mode to automatically install dependencies - Default all front-ends to OFF - Disable Qt5 on Windows - Update build instructions
This reverts commit 3bb3d12.
- Update to latest vcpkg - Default all front-ends to OFF - Use the OpenGL_GL_PREFERENCE variable instead of switching CMP0072 - Set CMP0167 to NEW (use Boost-provided find module) - Make use of meshoptimizer configurable instead of relying on find result
The current colour of comet tails (pale blue, with R = 0.5, G = 0.5, B = 0.75) has been noted by arbodox (n3), our resident small bodies guru, to be unrealistic. Therefore, I decided to change its colour to white, which is created by Mie scattering off the dust particles in the dust tail (gas tail is not always visible; it is only visible if it is ionized).
cubic pointed out in Discord that if there a star has any object in .ssc file orbiting it, the "Planetary companions present" text shows up. People pointed out that this is inaccurate since such an object can be an asteroid or a debris disc. As such, I propose we reword this text to "Planetary system present", as a planetary system contains everything from the most massive giant planets to asteroids and dust particles in debris discs, and hence is more accurate.
1. Use scaling factor from drawable height / window height, instead of `SDL_GetDisplayDPI` 2. Multiply by scaling factor in safe area 3. Reset font on DPI change
The ambiguously-named star files are given a prefix "stars-" to 1) inform viewers that they are star files, and 2) group them alphabetically, making them easier to find. The loading order of the files are also rearranged so that the bulk-generated files such as charm2 or whitedwarfs are loaded first, and then manually-created files (like stars-near) are loaded afterwards so that manually curated values supersede rather than being overridden. This PR is accompanied by this PR CelestiaProject/CelestiaContent#310 in CelestiaContent, and MUST be approved alongside it, else the program would break.
The following localization files have been updated: Parameter | Value ---- | ---- Source File | po/celestia.pot Translation File | po/bg.po Language Code | bg Transifex Project | [Celestia](https://app.transifex.com/celestia/celestia/) Transifex Resource | [celestia.pot](https://app.transifex.com/celestia/celestia/po-celestia-pot--master/) Transifex Event | translated Mode | default --------- Co-authored-by: transifex-integration[bot] <43880903+transifex-integration[bot]@users.noreply.github.com>
The following localization files have been updated: Parameter | Value ---- | ---- Source File | po/celestia.pot Translation File | po/pt_BR.po Language Code | pt_BR Transifex Project | [Celestia](https://app.transifex.com/celestia/celestia/) Transifex Resource | [celestia.pot](https://app.transifex.com/celestia/celestia/po-celestia-pot--master/) Transifex Event | translated Mode | default --------- Co-authored-by: transifex-integration[bot] <43880903+transifex-integration[bot]@users.noreply.github.com>
Includes Qt 6.10.2
we might need to use viewport effect for software sRGB, but we still need other viewport effects to work alongside it.
- Update to latest tag - Update to Codeberg URL
Co-authored-by: Andrew Tribick <ajtribick@googlemail.com>
1. Fix crash on exit 2. Break properly in Binder::unbind
Mainly to update to the latest libpng
Taken from #2483 no behavior change yet Fix a bug that iOS ES2 has OES_depth24 extension and will try to call this. GL_DEPTH_COMPONENT24 is not valid for ES2. ``` glTexImage2D(GL_TEXTURE_2D, 0, GL_DEPTH_COMPONENT24, m_width, m_height, 0, GL_DEPTH_COMPONENT, GL_UNSIGNED_INT, nullptr); ``` I've tested viewport effects with: iOS (ES2, ES3) and macOS (desktop GL), with MSAA on/off (ES2 FBO's MSAA is always off), with float or non-float storage.
1. create a struct holding label/line/etc colors used in renderer 2. add check for GL_EXT_sRGB/GL_EXT_sRGB_write_control (not used for now) 3. make shader name and needsFloatSource configuration in passthroughviewporteffect's constructor so we don't have to create a new class for future sRGB effect
No texture is read in sRGB format yet, so this PR doesn't change behavior. ES3 + Needs to generate mipmap: sRGBA is natively supported. Other sRGB formats are all expanded to sRGBA ES3 + No need to generate mipmap: sRGBA/sRGB are natively supported. Other sRGB formats are all expanded to sRGBA ES2 with EXT_sRGB: sRGBA/sRGB are natively supported. Other sRGB formats are all expanded to sRGBA There is no mipmap support, `glTexParameteri(GL_TEXTURE_CUBE_MAP, GL_TEXTURE_MIN_FILTER, GL_LINEAR)` is used instead ES2 with no EXT_sRGB: sRGB formats are treated as the non-sRGB formats. In this case we should probably not try to create sRGB texture in code
Pick up fixes in libpng-1.6.58
The calculation of the centre of the textures was half a pixel off for even sizes (i.e. everything larger than the 1x1 mipmap)
Given how prevalent cgs is in astronomy, this may be very useful. I know it'd be useful for one of my works right now.
Use a dummy OpenGL context for querying WGL capabilities, otherwise the extension queries will return false, and the `wglChoosePixelFormatARB` function pointer will be NULL. The dummy context thing seems to be the standard way to handle this problem. I am getting more and more tempted to just delete the win32 front-end though.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )