Futuremark 3DMark 2016 Beta with VRMark Preview

Published by

Click here to post a comment for Futuremark 3DMark 2016 Beta with VRMark Preview on our message forum
I'll have some results up in about 30 min 😀
I guess we should just give up on sli and crossfire as devs seem to be having issues making it work now. seems like everything that is being released now doesnt work with it. which Im fine with it has long as single gpu can push out great performance.
Pretty cool, shame they didn't have as many particle effects in the firestrike demo and would be nice you could walk around the room a bit more, atm it's all very boxed in, needs gamepad support as well, wasd is a bit too sensitive, analog sticks would be much better, it's still in development tho so I'm sure they'll add more to it, and I agree installing the benchmarks as DLC is a great idea especially when space is still quite limited when it comes to SSD's, it's nice to be able to choose what you want to install.
The BETA gives me 'Time measuring inaccurate' invalid result. Strange never saw that before, I'll chalk it down to being a BETA, but it has me wondering if it is GPU drivers.
Some screen shots of the new menu and all. The new UI is nice, the testing in the beta version seems messed up for for different reasons for both AMD and Nvidia cards for different reasons. However todays version has been patched for Nvidia, the not enough memory just ignore and click okay. AMD (like me) get an error after the test is done about the timer. Also I lose roughly 1000 in graphics scores at same clocks, same that other reported this is for both AMD and Nvidia, they are checking on it. /edit removed embeded images...too large http://i.imgur.com/eSVOrye.jpg http://i.imgur.com/SNwIOk5.jpg http://i.imgur.com/kxRZegd.jpg http://i.imgur.com/0chm27s.jpg http://i.imgur.com/mRuwIBu.jpg
Also 3dmark is onsale on Steam for 4.99 ( 80%) off
Well I'm on Nvidia and get the timer error, but I also noticed my card only boosts to 1300MHz instead of my 1550MHZ overclock, makes me wonder if that is where the timing error is coming from.
No-one cares about VR, wheres the new DX12 benchmark!
No-one cares about VR, wheres the new DX12 benchmark!
They released the new updated UI early, instead of releasing both the new UI and DX12 test in January. Reason they stated was to try and make sure the kinks in the new UI were worked out, instead of releasing two new big changes at once. They stated it would be easier to handle issue with each piece at separate time then not knowing which part was causing the issues. Over the the 3dmark beta forum thread, they said expect the DX12 test in January. Kind of makes sense to me.