Earlier quoted context omitted.
> I assume that means it is rendering an entirely new image each frame... which is a tad wild. What's wild about that? That's exactly what it's doing and what most uses of canvas/WebGL do.
It's wild if it's running at 400 fps because nobody has a screen that refreshes at 400Hz. Every frame rendered past the screen refresh rate is wasted compute. Easily solved by limiting the frame rate.
A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese
81–86 of 86 posts
Re: A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese
#82Earlier quoted context omitted.
For me it showed 400 fps in the top left corner and my laptop fans spun up immediately as well. Seems to render frames continuously rather than waiting for the screen to refresh. Would probably be much less load when limited to 60 fps.
You need to click the "fps" text for it to actually show the FPS value (it'll be green). The 400 you saw was something else.
Re: A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese
#83Earlier quoted context omitted.
I think it's called learning to speak.
Don't be smartass. My question was how to change pitch? Most people can't change their pitch unless they have been trained. I can't speak with the pitch of child or woman. Neither are most people.
Re: A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese
#84Re: A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese
#85Earlier quoted context omitted.
I don't know, I don't live or am from US.
Well, rephrased then in more literal speak: being less dismissively-judgmental and more observational will go a long way in this community.
Re: A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese
#86Earlier quoted context omitted.
> I assume that means it is rendering an entirely new image each frame... which is a tad wild. What's wild about that? That's exactly what it's doing and what most uses of canvas/WebGL do.
It's wild if it's running at 400 fps because nobody has a screen that refreshes at 400Hz. Every frame rendered past the screen refresh rate is wasted compute. Easily solved by limiting the frame rate.
Annoyingly, on Firefox this is locked to 60fps on my 120hz display.