Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Some more description would be nice. Thanks.
Your 2016 image looks more like a driver issue but there is nothing I could do about that. Haven't seen it before though and had no reports ever since 2016 was supported. And I am sure that in now over a year this would definitely have popped up considering the user base.
The 2017 image I don't understand.
I'm sorry. Please just ignore the 2017 image. I would like to say everything works smoothly.
Thank you for your support. Now I can identify the cause of problem. I used DirectX11 as rendering engine for shader verification in 2016. This is the cause of issue. Changing to openGL, all functions work fine.
kenneth0083
