Earlier quoted context omitted.
Not a great part of the experience, certainly. Needs WASD key support if nothing else. It's almost unusable with a mouse. If you're going to make it look like a first-person perspective game, it needs to act that way.
I wonder when the first crack comes out for WASD + free movement.
Persepolis of ancient Persia rendered in WebGL
191–200 of 215 posts
Re: Persepolis of ancient Persia rendered in WebGL
#192Earlier quoted context omitted.
Then just record a video. Presenting an interactive experience and then taking away all control from the user and replacing it with an extremely frustrating navigation mode (hint, not everyone is using a phone/tablet or laptop touchpad - try to scroll that much with a mouse!) is just stupid and completely wasting the potential of the medium.
Good lord. Have you ever made anything that explored "the potential of the medium" as much as this? What makes you feel equipped to call its creators "stupid"?
Yes. Does that matter? This particular work has terrible, user-hostile navigation controls, and needs to support free movement.
We could play Quake 2 in the browser several years ago, so it's not an unreasonable thing to ask for.
Re: Persepolis of ancient Persia rendered in WebGL
#193Where are our modern equivalent of marvels like Persians from ~500 B.C !
Re: Persepolis of ancient Persia rendered in WebGL
#194Earlier quoted context omitted.
> In this website you need to keep scrolling, which is pretty monotonous, it would be equivalent of spamming "next" on an overly complicated late 2000s Windows software installer. Or watching a Youtube video by spamming the frame skip shortcut. Or scrolling through a long document, as the scroll wheel is designed to do? You're not supposed to scroll straight through, there's stuff to see and read! If you want to skip…
> Or scrolling through a long document, as the scroll wheel is designed to do? And it does with a reasonable speed configurable by the user, which is easily mentally mapped to how much it will move since it's just a 2D surface. For example, I have mine set so each full scroll gesture (as you see in the video) is mapped to a whole screenful of movement. So I know that a complete scroll will show me all new information…
> I can't look around, so it's just a video that wastes more GPU power.
Fwiw, you can drag to look around most scenes. (Although I actually don't think this added much and agree that using WebGL was probably wasteful: https://news.ycombinator.com/item?id=30965352)
Re: Persepolis of ancient Persia rendered in WebGL
#195Re: Persepolis of ancient Persia rendered in WebGL
#196Just explored it with my 4 year old son. He insisted on a second tour and on clicking all of the interactive exhibits. Amazing design and execution!
What a great experience for a curious child! I was lucky enough to have grown up in the 2000s, when History / Science / Discovery channels still aired proper documentaries instead of reality TV. But I would have killed to have access to presentations like these.
I think if it were alive today, presentations like this Getty one would be common. As much information as Wikipedia has, it's presented in a very static way, which is a shame. There's huge potential of making the information there interactive, and thus more appealing to younger generations (and everyone, really) who otherwise wouldn't read an article with thousands of words and some pictures and audio.
Re: Persepolis of ancient Persia rendered in WebGL
#197Horrible UI but would be cool otherwise. On an Android and the performance was fine but way too much finger swiping.
But I had to keep clicking every time a new scene loaded, which I consider an unforced error. I'm always so impressed with the level of effort that goes into these types of projects, but so baffled that so many obvious issues always seem to slip by somehow! My guess is that some issue with the scroll hijacking made this difficult to fix, like maybe a loader framework resets the focus and they didn't have an easy way to modify its code or something.
Re: Persepolis of ancient Persia rendered in WebGL
#198Earlier quoted context omitted.
It's nice because scrolling is a 1d interaction, and the path you're navigating is 1d. It's superior to a movie because this scheme makes it super simple to control how long you spend at various points, and they open up optional interactions at various points. I don't understand why a lot of scrolling would be problematic, doesn't seem different then e.g. pushing arrow keys over and over when playing a video game.
A single repeated movement is very tiring. You compare to games, but games have you press different buttons, and there is usually either some rythm and variety to it, or at least hold the button (e.g. in a racing game you usually hold the acceleration button) In this website you need to keep scrolling, which is pretty monotonous, it would be equivalent of spamming "next" on an overly complicated late 2000s Windows so…
I tried with trackpad and mouse on my end, and the app is well-configured for both of my devices at least: I'm able to have fine-grained control over my location by making small adjustments to scroll position.
Re: Persepolis of ancient Persia rendered in WebGL
#199Extremely well done (at least for desktop). Many seem to dislike that it's scroll-controlled, but tbh I would've given up immediately if it were free navigation—I didn't feel like wandering around looking for things, just wanted to observe the sights. And since the core structure is a sequential list of sights, the scroll interface is a nice way of keeping that linear structure in place while automatically choosing n…
Re: Persepolis of ancient Persia rendered in WebGL
#200Extremely well done (at least for desktop). Many seem to dislike that it's scroll-controlled, but tbh I would've given up immediately if it were free navigation—I didn't feel like wandering around looking for things, just wanted to observe the sights. And since the core structure is a sequential list of sights, the scroll interface is a nice way of keeping that linear structure in place while automatically choosing n…
How about just clicking on the next area? How could scrolling possibly be better.