pouët.net

Here is the demo: https://imersiva.com/demos/eo

Full source-code will be released in the next days. I just want to bug-fix and do some clean up before putting it on github.

- WebGL 2 support;
- WebVR support;
- Gamepad support;
- Real-time streaming to mobile (with head-tracking!) so you can see it in VR even on an average mobile and Google Cardboard;
- (soon) Persistent fractal editor for inserting your own 3D fractals in space.

I kindly ask for some feedback:

- Your Operating System (if you don't mind, also your GPU);
- Does it run for you?
- Do you see a few fractals floating in space, and you can visit/enter them?
(there is polygonal collision detection but as fractals won't collide yet, i disable that)
- Does the planet show complete, with spherical terrain?
- Does it run in 60fps?
- Any other comments, critics and/or suggestions?

Thank you.

I will give a feedback myself:

- Ubuntu 16.04, AMD RX580;
- runs as expected;
- all fractals showing as expected;
- planet as expected;
- steady 60fps;

- Windows 10, AMD RX580;
- runs;
- all ractals;
- planet is just a sphere;
- 60fps.

oh sheet, how i wish i could edit posts! would be good to know what browser you tried as well. thanks!

That click for fullscreen is anoying as hell. Take it off.

- Arch/Parabola/Gentoo frankenstein monster, Intel 2330M, GeForce 410M (nouveau drivers, mesa 17.3.7)
- tried with (rebranded) Firefox 59.0.2, (rebranded and slightly modified) Firefox 52.6.0, and Qutebrowser 1.2.1
- "no WebGL 2 detected on your hardware" (in Brazilian), on all browsers, even though it's enabled in about:config (or its equivalent in ~/.config/qutebrowser/qutebrowser.conf).

Also, is a video preview really needed? It's not very low-bandwidth friendly (or for people with download caps).

having webgl2 enabled in the config doesn't necessarily mean your hardware(or driver) supports it

Fullscreen on click was removed now. You might need to CTRL+F5 to fully refresh the page. I can't edit the first post, but here is the direct link:

https://imersiva.com/demos/eo/game.php



That is right. You can also check your hardware on http://webglreport.com/

Thanks.

They're both supported (and it worked before). Mesa 17.3.7 is pretty much the latest (v18 was released a few days ago, haven't compiled it yet).

If every support thing was as fast as you the world would be a better place.

Just in case you still read this thread:




Did http://webglreport.com/ report WebGL2 support? That would be really strange, but please let me know.

Anyway, some demos out there will fall back to WebGL1 if WebGL2 support fails (in their case, they don't really *need* the wgl2 extra features). This demo here won't fall back, it will simply refuse to run, because it *does* need the extra features.




That result is from a single line which tries to get a WebGL2 context. If that fails, well, I would be 99% confident that your system is currently not WebGL2 capable -- not saying that your *hardware* is not capable, but the system (driver or something else) is most probably not.

You could maybe dual boot into Windows and check that with Windows drivers.

Thank you for the feedback!

Win10, Chrome, GTX 1060; I get cockpit + legend in the top left counting FPS (~120ish in 1080p) but nothing moves and I can't seem to control anything.

Did you click inside the window? =)

Yes. No change, and as I said, nothing is moving, there's no animation, nothing.

Think this might be the reason:

Oh, that is weird. If you have an extra minute, please CTRL+SHIFT+J (open console) then see if there is any error there?

Thanks!!!

(Posted before seeing)

Oh, you have a plugged gamepad? There is some time I don't test gamepads, will test right now, might be broken that!

I didn't, now I plugged in the Xbox One pad I have and it's still the same problem.

Any VR device (Oculus Rift with Touch for ex)? Something might be wrongly detected as gamepad.

Asking just so I can pinpoint the bug, thank you very much.

I do have a Rift plugged on, yes.

And a Steam Controller.

Oh and a driving wheel.

That is it. I should disable Gamepad then for now, will upload in a few minutes. Thanks for the help!

It looks like it's the wheel because you assume it has a lot more buttons than it actually has :)

Note: I just uploaded a version with Gamepad support disabled for now.

Gargaj: you are very right on this. As you probably know, the problem with usb controllers (gamepads, wheels etc) is that there is no standard, so the only way to really know them is by letting the user configure buttons (pressing and moving).

I confess I was naive on gamepad support, just assuming that people will be using a XBox controller or similar, and no wheels / touch etc. Then I forgot about that. =)

Okay now it seems to work fine except I can't seem to INCREASE ([) the FOV, only decrease it (]).