i found this one when i made a teleporter that transports you from the land level with light greyblue shading to the forest level with black shading.
i made a grass flooritem that is used into both levels.
when i teleport into the forest, the grass keep the light greyblue shading color.
then i tried with a rock flooritem. if i "see" it in the land, and then go to the forest, it keeps the light greyblue shading too.
other flooritems in the forest have a black shading, because they weren't seen in the land...
[Not a bug] flooritem (and probably other stuff) shading
Moderator: George Gilbert
Forum rules
Please read the Forum rules and policies before posting. You may
to help finance the hosting costs of this forum.
Please read the Forum rules and policies before posting. You may

- George Gilbert
- Dungeon Master
- Posts: 3022
- Joined: Mon Sep 25, 2000 11:04 am
- Location: London, England
- Contact:
Hmmm - that is actually working as intended.
The issue is that flooritems are specified by *actual* bitmaps for each scaling (as opposed to, say monsters, which only have a single bitmap and the engine scales and shades it).
Your flooritem is (presumably) making use of the auto-scaling feature for floor bitmaps. When the bitmap is scaled then it becomes an *actual* bitmap (which is logically completely independent of the original). The problem comes when you change areas to a differently shaded one at which point the engine *shouldn't* re-shade your bitmap (because it is a bitmap that you've specified).
The way to get around this is simply to have two different objects, one for use in each shading area - BTW this is what DM-II does for things like the stone table and mud in the graveyard / thicket areas...
The issue is that flooritems are specified by *actual* bitmaps for each scaling (as opposed to, say monsters, which only have a single bitmap and the engine scales and shades it).
Your flooritem is (presumably) making use of the auto-scaling feature for floor bitmaps. When the bitmap is scaled then it becomes an *actual* bitmap (which is logically completely independent of the original). The problem comes when you change areas to a differently shaded one at which point the engine *shouldn't* re-shade your bitmap (because it is a bitmap that you've specified).
The way to get around this is simply to have two different objects, one for use in each shading area - BTW this is what DM-II does for things like the stone table and mud in the graveyard / thicket areas...