Please provide the details from the sticky so I can get this replicated and proceed with investigation. OGL team already previewed the post and says it's an unknown bug and agreed to look into it further.
Detailed infos except from Direct3D in DXDIAG.TXT, for some reason it crashed today.
EDIT: new DXDIAG.TXT attached, crash was caused by GeForce driver (nvwgf2um.dll)
EDIT 2: the demo fails now to compile on Shadertoy.com with any GPU, i guess they made some changes on server side.
Answers (N/A if not applicable)
Provide a detailed description of the issue AND 'does it fail every single time, or only sometimes?' If you can offer a % rate please do.
Demo "crystal skull" fails to compile in Shadertoy, after converting to GLSL hacker format it renders weird waves.
Demo renders correcty with NVIDIA or AMD GPUs
Brand and Model of the system.
Hybrid or switchable graphics system? ie Does it have AMD or NV graphics too?
Make and model of any Displays that are used to see the issue (see note2 below).
LFP = Local Flat Panel (Laptop panel)
EFP = External Flat Panel (Monitor you plug in)
How much memory [RAM] in the system (see note2 below).
Provide any other hardware needed to replicate the issue.
ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc
Hardware Stepping (see note1 below).
Operating System version (see note2 below).
Windows 10 Home Insider Preview 64-bit (10.0, Build 10547) (10547.th2_release.150913-1511)
VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.
Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).
SW/Apps version used to replicate the issue.
MadShaders 0.41 (render issue), FireFox 40 (compiler issue)
Single display, clone, or extended (see note2 below).
Display resolution & refresh rate setting of each display (see note2 below).
AC or DC mode, i.e. is power cable plugged in or not?
How to repro
Please provide steps to replicate the issue. These steps are very crucial to finding the root cause and fix.
A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.
1. With any browser goto Shadertoy BETA for compiler issue
2. download shader converted for GLSL Hacker from Crystal_skull_gl2.xml - Google Drive
3. download MadShders 0.41 from MadShaders - Best GLSL Pixel Shaders in an Unique App
4. copy XML file into demos folder (contains texture cube used in pixel shader)
5. run GLSLHacker.exe, make sure it reads Intel GPU on topbar if using an Optimus rig
6. load XML file, Intel GPU show a black waves/tornado thing
Issue's not present on SKL with latest driver. Back in Dev for BDW. I'll update when more info is made available, stay tuned...
The Dev was asking if you could try this. Let me know your thoughts. Thanks
In attachment you can find my proposal of slightly changed fragment shader from the “crystal skull” demo, extracted from Crystal_skull_gl2.xmlfrom communities thread: https://communities.intel.com/message/362076#362076
How to repro: 2. download shader converted for GLSL Hacker from Crystal_skull_gl2.xml - Google Drive
I marked my changes in glsl code with // AIL
Because shader is “unstable” I slightly changed the code and with my modifications it works OK both on Intel and NVIDIA (I have the NVIDIA Quadro NVS 290). I’m wondering if the submitter would like to use my version of this shader instead of the original.
The interesting thing is that the original shader does 8-9 FPS while mine does 14-15 FPS J, tested on NVIDIA Quadro NVS 290.