Question: Change in the display priority of sprites in relation to Scroll Screens (VDP2) (SOLUTION)
@seven-shades is already working on this.
Since Sep 1, 2026.
Assessment
This issue has not been assessed yet.
Description
It seems that after some recent updates (Aug 13th/Aug 15th) regarding VDP2 and/or Scene2D, the display priority between sprites and Scroll Screens - which can be arranged in different Layers using SetPriority() - has changed.
Up until now the behavior I observed was that the sprites had higher display priority than VDP2::Layer6, thus were drawn on top:
... VDP2::Layer4 < VDP2::Layer5 < VDP2::Layer6 < SPRITES
After updating my local library files to the current repository version, and without having altered my test samples, the display order has changed to this:
... VDP2::Layer4 < SPRITES < VDP2::Layer5 < VDP2::Layer6
The sprites are now hidden by the Scroll Screens assigned to Layer5 or above.
I've created this issue only because I don't know whether this is an intended behavior which has to be taken into account from now on regarding display priorities, or it's an indirect (maybe unintentional) consequence of having modified something else.
Thank you!
- Dominant language
- C++
- Stars
- 90
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ReyeMe/SaturnRingLib
-
bug required hardware test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ReyeMe/SaturnRingLib#148 ·
-
bug required hardware test
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ReyeMe/SaturnRingLib#147 ·
-
bug required hardware test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ReyeMe/SaturnRingLib#146 ·
-
bug required hardware test
Difficulty 1/5 Under an hour Newbie friendliness 82/100
ReyeMe/SaturnRingLib#145 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ReyeMe/SaturnRingLib#144 ·
All issues in ReyeMe/SaturnRingLib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/tensorstore#306 ·
-
comp-formats
Difficulty 2/5 Half a day Newbie friendliness 64/100
ClickHouse/ClickHouse#131694 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ETSInitiative/PETSIRD#243 ·
Maintainers usually reply within 1 day
-
[BUG][Ascend][AscendC] Scalar FP8 arithmetic stored to UB emits ".data" on a float and fails deviceOpenascend bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day