- October 26, 2016 at 3:00 pm #54736
I have the following problem. I was given a new laptop DELL Precision M4800 which uses NVIDIA Quadro K2100M and Intel HD Graphics 4600 display adapters in my work place. In my previous computer, I have written one OpenGL ES 2.0 application and I was able to run it with the PowerVR SDK and simulation (not sure what version was I using there). I installed the latest PowerVR SDK (2016_R1.2) on my new laptop and I tried to run that application. This time it failed with Access Violation Error. I decide to run the example applications, provided with the SDK (01_HelloAPI). Again, it crashed with Access Violation Error. I tried in both Release and Debug configuration but no luck. I am using Visual Studio 2013 Express. When I added some breakpoints and debugged, I saw that the application crashes when it executes this line of code
eglContext = eglCreateContext(eglDisplay, eglConfig, NULL, contextAttributes) – line 330;
Also tried to run some other examples and I saw that the following Warning is printed in PVRVFrame
I tried to change the Context Creation Mode to Loose and this time it passed executing of eglCreateContext() but this time it failed in the next statement – eglMakeCurrent()
Here is the Call Stack from Visual Studio, when I run the app in Strict mode
Please, let me know if you need any additional information or if there is same thread in the forum already
Best RegardsOctober 28, 2016 at 12:44 pm #54771
Are you using the integrated chipset or your dedicated NVIDIA card to run these applications?
Could you please provide your NVIDIA card driver version?
TheoOctober 28, 2016 at 2:57 pm #54792
Thanks for your reply. Honestly, I am not sure which one of both display adapters is used to run the applications. Is there any way to find out? All I see in the Device Manager of my computer is this:
The driver version of the Intel Graphics card is 126.96.36.19957
The driver version of the NVIDIA card is 188.8.131.523
Let me know if you need any additional information.
Ahmed K.October 28, 2016 at 3:51 pm #54801
hello ahmed since your laptop support two graphics card there should be a way to force to a particular card. Have you tried this before running the example?
also when you get past the eglCreateContext you application should out put a log.txt file it is normally in the same folder where your visual studio project file. could you send that to us please
also is this the only example you have tried? have you tried running on any other systems?October 31, 2016 at 8:24 am #54832
First I tried to force a particular graphics card to be used from the NVIDIA Control Panel. I tried with both Integrated and NVIDIA card but the problem remained the same.
Second, when I run the HelloApi example it does not create any log.txt file. However, with the other examples it does, I have taken two logs – one when the Context creation mode is set to Strict and one for the Loose mode. They are taken when I ran the Skinning example in the Advanced section.
I have tried other examples like “Skinning” and “Glass” and all of them failed.
AhmedOctober 31, 2016 at 10:45 am #54837
this is strange..
could you run introducingPVRShell with this following code in the initApplication function
so your initApplication function should look like this. This will force opengles2. This one should be supported. if not then your installation went bad,
// what ever
}October 31, 2016 at 12:08 pm #54840
I added that line of code, but the result is still the same 🙁 I have installed and unistalled the API like 5 times already. No errors or some other problems are introduced during the installation. Wondering if I have a problem with my display card’s drivers
AhmedOctober 31, 2016 at 12:18 pm #54841
I also think the driver is worth investigating.
Can I ask you what Opengl version is shown in the Host section of PVRFrameGUI when running introducingPVRShell? (Context info tab)October 31, 2016 at 12:56 pm #54843
Actually nothing is printed in the Context Info tab. I tried in both Strict and Loose modes. In case of the Loose mode, I see the following thing printed in the PVRVFrame GUI Console window (not sure if this is helpful):
Hardware profile: None
PVRVFrame version 10.3
AhmedOctober 31, 2016 at 2:28 pm #54844
Investigating further could you please:
1) Try an older version of the sdk (available from the github repository – checkout branch 3.5):
2) Send me the binary, (generated with SDK R1.2) for introducingPVRShell.
TheoOctober 31, 2016 at 3:49 pm #54847
I have attached the binary file. I downloaded the Native SDK 3.5 version, but I uninstalled the PVRVFrame, together with everything, that was installed previously. Then I realised, that no PVRVFrame was included in the files, I downloaded and I was not able to run the example. Do I have to use the PVRVFrame from the latest release or is there any other, which is related to versiopn 3.5?
AhmedNovember 1, 2016 at 9:17 am #54855
The native SDK 3.5 includes all the necessary to build and run the examples.
More precisely, the library required are located in:
As a curiosity could you check the opengl version supported by your NVIDIA card?
This tool can do that for you: http://www.realtech-vr.com/glview/
The binary you sent me runs just fine on my computer.
Please could you try the sdk R1.2 on another machine?
TheoNovember 1, 2016 at 11:41 am #54860
I tried to run with SDK 3.5 but I still have the same problem 🙁 I checked the supported OpenGL version and it is 4.3. See below
I see that there is a newer driver for this card so I can try to install it. It is my last hope.
AhmedNovember 1, 2016 at 11:48 am #54863
Let me know if updating the driver changes anything.
TheoNovember 2, 2016 at 9:40 am #54866
Today I figured out what was wrong. It is really strange or at least strange to me. Usually I keep my laptop on a docking station and I have connected to extern monitors to it. Somehow this setup messes with the OpenGL or does something else happens. When I took my laptop of the station and everything started to work just fine. My only concern now is that I will have to present some OpenGL examples using beamer and connecting it to my laptop my cause the same problem. If you have any idea why connecting to a docking station and external monitors causes problems, I will be glad to hear it.