Here's a bug report for you after playing last night.
Here's a bug report for you after playing last night. I'll give as much detail as I can, but I was GMing and most things worked for me.
I use Win7 and Chrome
Player 1 used Win7 and Chrome
Player 2 used OS Lion and Chrome, Firefox, and Safari to see which would work best
Bug 1: Player 2 didn't see anything in the app but a big black or white box where the map should be when using Firefox and Chrome. Is there maybe something weird about the Mac versions of those browsers that is screwy? I'm not a tech guy, so I don't know. In safari she could see the map and tokens, but not move tokens or interact with the map. No right clicking on tokens or the map either.
Bug 2: /localload worked for me, I was the one doing it, but it did not push anything to anyone else's session. So neither could see the map or tokens after I used /localload. When I right clicked a token and copied it, they could see the copy. I also tested saving to the TTF server and then loading, but that only worked for me as well.
Bug 3: Changing labels for tokens when right clicking only changed the label for whoever made the change, not for everyone else. Tokens added after changing aliases worked normally. Also, if you deleted a token, as I did many times after copying my locally loaded tokens, their label persisted if you moused over the spot they were when you deleted them. We called these "ghost tokens." Spoooooky.
Jason Beighel, if I missed anything, please chime in. You're way more a tech guy than I am.
I use Win7 and Chrome
Player 1 used Win7 and Chrome
Player 2 used OS Lion and Chrome, Firefox, and Safari to see which would work best
Bug 1: Player 2 didn't see anything in the app but a big black or white box where the map should be when using Firefox and Chrome. Is there maybe something weird about the Mac versions of those browsers that is screwy? I'm not a tech guy, so I don't know. In safari she could see the map and tokens, but not move tokens or interact with the map. No right clicking on tokens or the map either.
Bug 2: /localload worked for me, I was the one doing it, but it did not push anything to anyone else's session. So neither could see the map or tokens after I used /localload. When I right clicked a token and copied it, they could see the copy. I also tested saving to the TTF server and then loading, but that only worked for me as well.
Bug 3: Changing labels for tokens when right clicking only changed the label for whoever made the change, not for everyone else. Tokens added after changing aliases worked normally. Also, if you deleted a token, as I did many times after copying my locally loaded tokens, their label persisted if you moused over the spot they were when you deleted them. We called these "ghost tokens." Spoooooky.
Jason Beighel, if I missed anything, please chime in. You're way more a tech guy than I am.
Joshuha Owen Tabletop Forge just in case only making the post limited doesn't give a notification.
ReplyDeleteThanks.
Player 1 (me) was using Win XP and chrome, I'm not sure that makes a difference.
ReplyDeleteFor Bug 1, Player 2 was also having trouble with the video portion as well. If I recall she didn't see our video feeds part of the time. Its possible that the G+ plugin wasn't working properly. I don't know if TableTop Forges uses anything through that plugin, so that detail might not be relevant either.
Maybe this is bug 3, or perhaps an addition to Bug 1, but or OS X using Player 1 was unable to move any of the tokens on the map as well. Also the right click menu wouldn't work, the standard safari right click menu would show up. Basically the map was non-interactive even when it was visible.
Safari has issues with the pointer-events:none that is a known issue with Safari.
ReplyDeleteThe ghost tokens is a known issue and I think I will be able to fix it after I recover from my wisdom teeth being removed.
As far as the maps not syncing with a localload or in general, the next time that happens can you have the affected person bring up the javascript console on the browser. For Chrome that is ctrl+shift+j and let me know if any errors are spotted. Any javascript errors when loading the app would prevent the rest of the code from loading correctly.
Jason and I can probably test the javascript thing soon. We will let you know how it goes.
ReplyDeleteHow cruel of me to send you a bug report right after you got your wisdom teeth out. I suggest numbing your mouth with vodka.
On Vicodin now =).
ReplyDeleteOk ghost tokens should be fixed now.
ReplyDeleteSweet. We'll test soon.
ReplyDelete