Posted by interdpth

---

release date april 7.

---

Posted by interdpth

---

Let me show you

Public Type ScrollType
xStart As Byte
xEnd As Byte
yStart As Byte
yEnd As Byte
End Type

Private Type Scroller
Filler As Byte
Number As Byte
Scrolls() As ScrollType
End Type


That's how scroll data is defined.

Sample structure from first room.

00
03
--scroll zero
02-xStart
4C-xEnd
16-yStart
1F-yEnd
--End scrollone
FFFFFFFF
-Scroll 2
20-xStart
2E-xEnd
02-yStart
17-yEnd
-
FFFFFFFF202E1F29FFFFFFFF
Now using scroll one
For width

xEnd - xStart

Width = 4C - 02 = Width of 4A or 74 multiply that by 16 to get total Width in pixels
Height = 1F - 16 = Height of 9 multiply that by 16 to get total height in pixels


lblScroll(0).Height = Height
lblScroll(0).Width = Width


Next Scroll is a FF'd one

So move on to next one

Width = 2E - 20 = Width of E or 14 multiply that by 16 to get total Width in pixels
Height = 17 - 02 = Height of 15 or 21 multiply that by 16 to get total height in pixels

lblScroll(2).Height = Height
lblScroll(2).Width = Width

Ok so find their pointer of intersection

Slope formula?

(21 - 9)/(14-74)
12/-60=-.02
So yeah they cross =P

I think that was the right formula.

---

Posted by Kyoufu Kawa

---

Let me rephrase.

What you see in the editor is how it, by your code, reads the data. The data -seems- to say that the scrolls in the starting room overlap by one tile like in that screenshot.

What I say is that your editor might be misinterpreting and needs to shrink the scrolls by one tile, sixteen pixels.

Cos there's no good reason for them to overlap like that.

---