Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Stacked objects not keeping their order

Ok, I searched, but didn't find anything, so sorry if I double post this. Stacked background items are not keeping their order, when I quit and come back, or will be in a different order for players. I find that if I use the "Send to Front/Send to Back" menus it's much more reliable, but still not 100% effective, especially if I have multiple overlapping items. This screenshot shows a segment of arched alcoves which drops under one of the tiles. I used the "Send to front" command in the right click menu, then connected as a player, and it's still under the tile. I suspect, but I'm not sure that it relates to using the "send to front" and "send to back" commands on multiple overlapping objects, since I also sent the piece of floor to the front, so it would overlap one of the adjacent floor tiles (the tiles come with included walls, and previously I had a rogue wall just hanging out in the middle of the room) That series of ordering seemed to have stuck, but it appears when two objects "In front" collide, it's anyone's guess who gets to be the front one. Of course, this is just all my best guess at what's going wrong. I also haven't had any coffee this morning, so it's entirely possible that I sound like the guy who tells the computer tech "My printer won't print, so I tried deleting some stuff from My Documents to speed up the internet" TL;DR Z-axis ordering is not persistent when I quit, and will also display differently for players.
Update: I just re-arranged the order of the objects by using "send to back" on the other two overlapping items, and then my alcoves stayed in the right place when I exited and went back in, so my Scooby Doo detective senses about it being related to multiple overlapping items being "sent to front" seem to be right.
1336400336
Mike
KS Backer
This issue has been making my brain hurt for a while .. Spent ages creating a campaign and several pages have this issue. You're much clever than I am, I gave up and took a screen shot of what I created, then just copied it to photoshop and saved it as an image. I then deleted what I created in roll20, then just replaced it with that picture. However, if it works with "Send to back" and keeps its order .. I may just do that from now on.
Where is this "Send to front/Send to back" menu of which you speak? It sounds handy.
Where is this "Send to front/Send to back" menu of which you speak? It sounds handy. right click any object on the map and it's in the context menu
"Right click"? That's option-click, right?
Oh, your operating system's named after a large feline, isn't it? ;) Um... Two finger click/tap on a touchpad, or ctrl+click for mouseusers (according to the first page Google gave me, and I have no way to actually verify this) Option-click sounds like something I've heard in the past too though.
Actaullay, Apple stopped producing pointer devices that don't support right-click a couple of years ago. But, you have to enable the right-click in the device settings for all devices that don't have a physical second button.
That series of ordering seemed to have stuck, but it appears when two objects "In front" collide, it's anyone's guess who gets to be the front one. TL;DR Z-axis ordering is not persistent when I quit, and will also display differently for players. You nailed it. The problem is that technically when you move one thing to the front or back the z-index of all objects changes. As you can imagine this is an expensive save operation when you're dealing with hundreds of objects (not to mention all of your players needing to receive hundreds of updates). So I'm trying to figure the most "lightweight" way to do this that still gives consistent results. Obviously it's not there yet, but it's definitely something we're active working on. Thanks.
Glad to hear that this problem is being worked on. The opening to my campaign consisted of: Me- " Blah, blah blah(room description)... and in the southeast corner of the room sits a chest fastened with a heavy lock." Players in unison- "WHAT CHEST?!" Oh, what a way to start. :D
My problems have completely gone away since I stopped using "to front" As long as I stack everything by successively sending things down instead of up, it works like a charm. So, at least I have a functional, and easy, workaround.
Been having the same problem will give your work round a go and see if this works for me.