Testers wanted for the model viewer

[GhostWolf]

I want to run a small test, to see how WebGL works on different computers, because I am getting weird inconsistencies.

The test is simple - it tries to draw more and more objects, until the FPS drops to about 55. It isn't exact, but it should become stable at some point.

Your job is to write how many draw calls you managed to achieve, the browser (preferably an updated Chrome, nothing beats V8), and your graphics card's model (preferably with updated drivers!).

The test is here.

Thanks.

 

[Dr Super Good]

The test is not working on Microsoft edge at all, just shows a black rectangle in the window.

SCRIPT5008: Invalid left-hand side in assignment
viewer.js (121,17)

Only error. I understand you would prefer Chrome but I thought I would try to post Edge results for comparison.

Could be due to my GPU drivers being a bit old. I will try to update them.

EDIT:
Even with updated drivers still just a black rectangle.

 

[Ralle]

Mine ended at 3418. GTX 970.

 

[GhostWolf]

Internet Explorer is not going to be supported anymore (ES6). Get on with the times. Spartan might support enough ES6 features, I am not sure.

Not only that, but I also plan to use features that are only somewhat supported also in current browsers (mostly shared memory), but those will have fallbacks.

 

[Dr Super Good]

Internet Explorer is not going to be supported anymore (ES6). Get on with the times. Spartan might support enough ES6 features, I am not sure.

I was using Spartan (Microsoft Edge).

Apparently there are some issues with the HTML5 conformance of Edge, scoring only 453/555 on the tests. Apparently the developer build scheduled for release in July is upping it to at least 479/555. Google chrome is a lot more conformant (526/555).

However that score is kind of meaningless by itself as it is unlikely you use many of the unsupported features (such as voice recognition lol). Here is a detailed comparison of the features currently supported.

Edge ES6 support is also kind of dicy although that is also something improving vastly in July.

 

[Chaosy]

3563 on chrome with a GTX 960

 

[Warseeker]

The test is not working on Microsoft edge at all, just shows a black rectangle in the window.

Got this as well ^^ but for Internet Explorer.

 

[General Frank]

3498 calls on GTX970, i7 4470K and 32GB of ram and firefox 46.0.1

 

[Dr Super Good]

The link now throws "Error 503 Backend fetch failed". I tried enabling experimental Java Script features for better compatibility but I have a feeling that is likely not related.

 

[GhostWolf]

The Hive was down for some reason, it's not related.

 

[Dr Super Good]

The Hive was down for some reason, it's not related.

Yet hive clearly is not down as I am replying to this and it is still throwing that error...

 

[GhostWolf]

Well, I don't know.

 

[Ralle]

Sorry guys, someone farted really loud and the servers shut off.

I would like to support Edge, but I have my own plan of using https://babeljs.io/ to convert GhostWolf's code to more backwards compatible code.

 

[KILLCIDE]

GIGABYTE 980	7,304 calls
ASUS 970 STRIX	6,494 calls
EVGA 680	4,521 calls

I had a friend of mine do the test as well, but the test kept stopping between 80-90 draw calls. He was on Chrome with an EVGA 970 FTW.

 

[GhostWolf]

Well, these results are about as arbitrary as I expected, seeing my own...

Can you people run also the old map version,, and see how fast it runs?
It doesn't have a built-in FPS meter, but you can both see if the animation runs smoothly, or if under Chrome (and probably other browsers have similar settings) you can open the console with F12, press on the three dots on the right-top corner of it, then More tools -> Rendering settings -> Show FPS meter.

 

[KILLCIDE]

Everything looks smooth for me. Took ~10 seconds to load everything.

 

[Cherrymage]

276 calls on Chrome, 2 GB ram using ATI Mobility Radeon HD 5400 Series.

EDT: About the old map version, I am stuck on one file still being loaded

 

[Rex.]

811 calls.

Geforce GT540 2GB. Google Chrome.

 

[A Void]

My results:

Results

Google Chrome, AMD Radeon R9 200 Series.

 

[Tleno]

I didn't get much, which is rather weird imo. Anyways it stopped growing quickly at about 560. It still grows but super slowly.

 

[Edge45]

I think mine is much more less, though I use a phone, it slowly grow to 243 and seem to stop.

 

[Emm-A-]

does not really seem to stop for me, but after 15 min it was 2252 at firefox, GTX 460

 

[DaneTheBeast]

1174 Chrome
GeForce GT440

 

[Ralle]

GhostWolf, what is the conclusion here?

 

[GhostWolf]

That WebGL is the least stable thing ever, and there are no conclusive conclusions whatsoever.
It seems random at best.

 

[Ralle]

But is the bar high enough for the product you have in mind to be stable?

 

[WhiteFang]

Your job is to write how many draw calls you managed to achieve, the browser (preferably an updated Chrome, nothing beats V8), and your graphics card's model (preferably with updated drivers!).

About 3300 with a R7 360 MSI OC 2GB edition on chrome,both my drivers and chrome are updated to the latest version.I was running a game in the background,not sure if that effected it

Edith sry,didn't see the second page

 

[A Void]

About 3300 with a R7 360 MSI OC 2GB edition on chrome,both my drivers and chrome are updated to the latest version.I was running a game in the background,not sure if that effected it

*affected

 

[WhiteFang]

 

[A Void]

Exactly.

 

[TriggerHappy]

Draw calls: 6457

GTX 1080