Thank you very much for sharing your issue with the Intel® Communities Team.
I understand you are not able to start your project with Qr5.10.10 / QtQucick 2.0 since you receive an error. Allow me to help you regarding this issue you are facing.
Let me share with you that the latest Graphics version for your system will be the 4901.
In the case you need to complete an installation for the drivers please follow the instructions of this YouTube video.
Thank you for your response also for the information provided, keep checking for any response on the other forum; let me share with you this following information:
Looking into the information of the processor that you have, I see that it supports OpenGL 4.4, please verify that the software is compatible with this specification, this information is on the link that you share:
I also find some assistance information form Qt Documentation that could be helpful for you
Please be aware that the content on that site is not controlled by Intel*. This information is offered for your convenience and should not be viewed as an endorsement by Intel* for the merchants or services offered there.
In my first post:
This is a verbatim quote from Qt Support:
"This seems to be crashing inside your GPU driver on buffer swap. This
example needs OpenGL 4.3 to work"
This is taken directly from the requirements page you just directed me to.
For Qt Quick 2 to work, a graphics driver that provides OpenGL 2.1 or higher is required. The default driver from Windows is OpenGL 1.1. Qt includes a version of the ANGLE project which is included from the Windows Qt installers. ANGLE implements the OpenGL ES 2.0 API on top of DirectX 11 or DirectX 9. ANGLE requires that the DirectX SDK is installed when building Qt.
Thanks. I'm well aware of the requirements, it's been working fine until the latest driver updates.
Let me know if I can provide any NEW information or further assistance but also please beware I'm trying to develop around your hardware and software now - the support has been truly horrible. Sorry, it has.
Perceptions matter and I'd love to suddenly have someone actually, you know, first up a OpenGL program on a i5 6400 on windows and actually prove it's broken to themselves, but I won't hold my breath.weve
I will however be seriously considering changing my stance on using Intel for my released product.
It's been horrible trying to get support, having posts closed without resolution (what's with that). Then I raised another thread over in Developing Games & Graphics on Intel as suggested which hasn't even had an acknowledgement.
I then raised an actual ticket through that horrible site and you know what they replied with:
Greetings from Intel® Customer Support!
Thank you for raising your concern to us.
As we have checked, you have an existing case with Antony about Graphics Driver, kindly focus on this case with regards to your concern. With that said, we will be closing this case now as duplicate.
Thank you and have a nice day!
Intel Customer Support
Thanks Paula for being a colossal help. I'll ask for you next time /s
Antony. It seems I am to go to you for patching this defective driver, getting OpenGL to not throw a fatal exception for me? What do you need from me?
It appears the actual graphics support team don't want to hear about it. I don't have faith a community member support is going to fix my driver.
In your expert capacity: Do you think perhaps I should ask Radeon Technologies Group if they can help me develop an embedded product with semi-decent 3d capabilities?
Seriously. Intel. What a horrible response and experience to a developer.
If I was in the room with any of you I'd be walking out shaking my head or if it was my room - forcing you clowns out. It's your product, we're trying to get it just to work as advertised, what is wrong with you people and processes?
First of all I would like to step in and offer our apologies for how this situation has been handled so far.
Intel takes these reports seriously, and it is within our interest that you maintain using our products for your different solutions.
I can confirm that given the nature of this issue, it is best suited for the Intel Developer Zone (IDZ) since you are after all, developing an application on Intel Graphics. Thus I wish to thank you for already submitting MSVC17 Intel Graphics: reproducible OpenGL fatal.
I have escalated this internally so you get a reply as soon as possible in the aforementioned IDZ thread, and I'll continue to monitor it until you get one.
Thank you Ronald, for your reply and escalating is appreciated. I might have been a bit upset, I'm sorry, I do appreciate the support.
I don't want Intel to stop the world for my issue - I just need drivers that work and they were before.
Sadly with Windows automatically pushing updates, after a time you get forced onto new drivers regardless (it appears).
Running older drivers is less than ideal but we were hoping we could ride it out until another set that work again. Now we cannot and a whole compiler binary option is nullified, ironic we cannot ship a Windows binary using the native Microsoft tooling...
I know it is just onboard / ondie graphics and just one developer - these are just capable enough for our graphics needs.
Using this we can drive our solution with something small like a NUC.
I'd like smaller but this is the first release... I just found Intel® NUC Kit NUC6i7KYK Features and Configurations - man, that thing has a nice physical footprint! I'd like that...
Anyhow, the drivers used to work so - as it's a regression and we are currently developing our product with this as a base it's really important to us.
At the moment MSVC17 builds are forced to use Angle/OpenGLES which has no antialiasing etc, it's ugly as but at least it works. We'd never ship with a MSVC release looking like that though.
The hardware isn't a problem (likely) as different compilers execute the same code making OpenGL calls just fine. Do let me know if I can provide detailed information. Videos etc.