Editing Talk:1608: Hoverboard
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 106: | Line 106: | ||
I thought Atreyu's horse was Artax, not Artex. [[Special:Contributions/198.41.238.32|198.41.238.32]] 05:27, 26 November 2015 (UTC) | I thought Atreyu's horse was Artax, not Artex. [[Special:Contributions/198.41.238.32|198.41.238.32]] 05:27, 26 November 2015 (UTC) | ||
− | The beret guy riding a torpedo (/explosive device of some sort) looks like a Dr. Strangeloe tribute to me. | + | The beret guy riding a torpedo (/explosive device of some sort) looks like a Dr. Strangeloe tribute to me. |
Just added in the 'collision detection' section the text "On a slow connection, it's possible to move into an 'open' area and then the black image loads in and (probably permanently, without tricks) traps you immobile." To expand upon this, if this is a risk to anyone else (I'm reliant on mobile internet, being away from any comparable landline capability) then you need to look out for perfectly horizontal/vertical edges. For example, hovering up the side of the Washington monument and encountering (typically above the 'bricks' line) a completely flat top. Drifting onto that soon gets you embedded in the remaining Monument, somewhere well below the eventual tip. Alternately, drifting sideways over the landscape and discovering a perfectly vertical cliff downwards (just past the bowling pins is a prime location) tempts you to drift down it and then suddenly the solid land 'happens' around you, forcing a page-refresh and restart (though doubtless there's also various console tricks that could be used). The well, also 'opens out', but it's a lie. I've ended up trapped 'in white' below the now closed black blocks that surround the well bottom (and not found any way back up). But if there a 'texture' (like other cliffs) or 'slope' (like the real Monument edge) to the surface, you're probably Ok. It's a genuine surface or wall that you can generally navigate around without fear of being misled. (Or so is my experience.) [[Special:Contributions/162.158.152.227|162.158.152.227]] 09:12, 26 November 2015 (UTC) | Just added in the 'collision detection' section the text "On a slow connection, it's possible to move into an 'open' area and then the black image loads in and (probably permanently, without tricks) traps you immobile." To expand upon this, if this is a risk to anyone else (I'm reliant on mobile internet, being away from any comparable landline capability) then you need to look out for perfectly horizontal/vertical edges. For example, hovering up the side of the Washington monument and encountering (typically above the 'bricks' line) a completely flat top. Drifting onto that soon gets you embedded in the remaining Monument, somewhere well below the eventual tip. Alternately, drifting sideways over the landscape and discovering a perfectly vertical cliff downwards (just past the bowling pins is a prime location) tempts you to drift down it and then suddenly the solid land 'happens' around you, forcing a page-refresh and restart (though doubtless there's also various console tricks that could be used). The well, also 'opens out', but it's a lie. I've ended up trapped 'in white' below the now closed black blocks that surround the well bottom (and not found any way back up). But if there a 'texture' (like other cliffs) or 'slope' (like the real Monument edge) to the surface, you're probably Ok. It's a genuine surface or wall that you can generally navigate around without fear of being misled. (Or so is my experience.) [[Special:Contributions/162.158.152.227|162.158.152.227]] 09:12, 26 November 2015 (UTC) |