I set up a scrolling platformer module project using many of the new tutorial platformer assets and made 3 test screens, setting them all to scroll in both directions without edge blocking, and using gravity. Movement and scrolling etc seemed to work normally at first, but if you add elements of any kind that are solid towards the edge of each screen in the editor (like a 1 tile high wall on top of the floor, for instance), these attributes will invisibly apply to the edge of the screen before it, and sometimes going back and forth between the areas will lead to a column of tiles disappearing or palette swapping in a weird way.
This all being said, is two-way scrolling (just left and right) for sure supported in 4.1? I saw a video preview of it on the facebook group but it was brief and lacked an explanation, so I didn't know if these things I was attempting out of the box were even supposed to be working.
EDIT: Dur, I didn't look at their site close enough. In the unlisted youtube video for the scrolling tutorial, Joe states that two-way / bidirectional scrolling is not fully functional at present, and will likely exhibit bugs and strange things if used.
Thus far the only bugs I have found (if other people want to mess with it), apart from some odd palette stuff here and there sometimes, is that going back and forth, as mentioned above, changes the edges of the screens to include collision data from the opposite side. You can get around this in level design no problem so long as tall things are not on the edges of each screen boundary, but if you have changing attributes or other custom stuff it might not work out.
This all being said, is two-way scrolling (just left and right) for sure supported in 4.1? I saw a video preview of it on the facebook group but it was brief and lacked an explanation, so I didn't know if these things I was attempting out of the box were even supposed to be working.
EDIT: Dur, I didn't look at their site close enough. In the unlisted youtube video for the scrolling tutorial, Joe states that two-way / bidirectional scrolling is not fully functional at present, and will likely exhibit bugs and strange things if used.
Thus far the only bugs I have found (if other people want to mess with it), apart from some odd palette stuff here and there sometimes, is that going back and forth, as mentioned above, changes the edges of the screens to include collision data from the opposite side. You can get around this in level design no problem so long as tall things are not on the edges of each screen boundary, but if you have changing attributes or other custom stuff it might not work out.