I was getting the same error (looked more like z-fighting to me), but it seems to be fixed in this test.
Specs:
i7 3770
Gtx 660
16GB RAM
Windows 7
GPU is updated to latest drivers.
Fixed here too now with the latest update.
Thanks guys, pushed the commits for the new simple physics and graphical fix.
Also added a new video to the main post, wandering around with physics.
That last patch is working now (I just updated to Windows 10 but I’m sure it would have worked on Windows 8.1 as well).
My pc:
Amd fx-4100
Nvidia Gtx 660
4gb RAM
Windows 10
Just pushed an update eliminating that pop in when you turn.
Thought I’d take a minute to explain what I figured out the cause of the graphical glitch was on certain GPUs.
Jrenner was partially right, it turned out to be due to my unique shader packing, but more correctly due to my varying float vs int passed to the fragment shader for GLES compatibility. When checking if a value matched an int for which texture to use, some GPUs it seems were taking the floor of the value so on my own PC 1.999999997 was being equated to true for equals 2 by the shader but for some true for equals 1.
Looks and performs great on my i5/R9 290 setup, FPS is fine but walking speed is a bit slow. To echo Icecore and cylab, get some gameplay in this thing, stat! I want to play it!