Can not activate the GL rendering context

[Ben Anello 811680 0]

Well. Thought I'd "test drive" by creating a new Facility file. When I double-click on the newly-created facility file, I get a fatal error: Can not activate the GL rendering context. I am using a NVidia GeForce GTX 970 card with the newest driver (10.18.13.619) and OpenGL version 4.4 on Windows 7 Home Premium with service pack 1.

 

Any clue on where to go from here?

 

Thanks

[Michael Roach 1304415 0]

I am having the exact same problem. I have a GTX 980.

[Ross Carlson 156]

I'm betting there's some incompatibility between the OpenGL library used in vERAM and the OpenGL support in the latest nVidia drivers. I'll see if I can find a machine where I can reproduce the issue.

 

If anyone reads this and is using the latest nVidia driver without a problem, please post a reply.

[Dhruv Kalra 16]

Been working on mine without issue. Win 7 Pro, GTX 980.

[Ryan Geckler 3]

This is the same issue I emailed you about.

 

It took a full on driver reinstall and some tweaks to get it to work; be advised though, if you restart your computer, you have to go through the whole process again.

[Ben Anello 811680 0]

I should point out that I am trying to create a new facilities file. I'm wondering if it would work with an existing one (which I don't have access to at the moment; hence creating one to test with.) I should also note that I do have vSTARS that I can bring up an existing facilities file without issue. Are there differences between the implementation of OpenGL commands between vSTARS and vERAM? Does vSTARS use OpenGL the same way?

[Ryan Geckler 3]

I should point out that I am trying to create a new facilities file. I'm wondering if it would work with an existing one (which I don't have access to at the moment; hence creating one to test with.) I should also note that I do have vSTARS that I can bring up an existing facilities file without issue. Are there differences between the implementation of OpenGL commands between vSTARS and vERAM? Does vSTARS use OpenGL the same way?

 

Try it, but when I tried doing that, it failed to make a difference.

[Ross Carlson 156]

Yeah, the facility file shouldn't make a difference ... though it could have something to do with the fact that a new facility file wouldn't have any GeoMaps set up yet.

 

Ryan, what tweaks are you referring to?

 

vSTARS uses similar OpenGL rendering code, but there are subtle differences in how the rendering context is set up.

[Ryan Geckler 3]

nVidia control panel tweaks.

[Ross Carlson 156]

nVidia control panel tweaks.

 

Any tweaks in particular??

[Ryan Geckler 3]

In the control panel, managed 3D settings:

 

http://puu.sh/nnKHt/f2e39cc3a9.png

 

http://puu.sh/nnKJi/525a1f5ae6.png

[Ross Carlson 156]

Ryan, I'm trying to understand what tweaks you made that fixed this issue for you. Which settings in those screenshots are relevant to this issue? I.e. what changes did you make that fixed the issue for you?

[Ryan Geckler 3]

Once I used those settings, the program stopped giving me errors. It was trial and error to get it to that point.

 

I'm not sure how else to describe the problem...

[Ben Anello 811680 0]

I tried the 3D settings that Ryan mentioned in his post. Still having the same error although I did not reinstall the driver before changing the values. GeForce Game Ready Driver release date: 2/15/2016 Version: 361.91.

[Michael Roach 1304415 0]

I reinstalled all Drivers and it still had issues. I searched up some issues online and they said it was a resolution problem. But I forced the "resolute?" to 1600x1200 and still had the same problem.

 

I also used your settings RG and still didn't work. I just bought a laptop and it came today so I am going to see if the problem is resolved there.

 

*EDIT*

Works with my laptop but not the PC. Laptop uses AMD.

Edited February 27, 2016 by Guest

[Ross Carlson 156]

Once I used those settings, the program stopped giving me errors. It was trial and error to get it to that point.

 

I was hoping you did a trial-and-error between each change so that you knew which change or changes had an effect ... I guess that's the meticulous (read: anal-retentive) developer in me.

[Ross Carlson 156]

Have either of you tried tweaking the Windows DPI setting?

[Ryan Geckler 3]

I have not tweaked the DPI, and yes, I did a proper troubleshoot

[Ross Carlson 156]

I have not tweaked the DPI, and yes, I did a proper troubleshoot

 

If that were true, then you'd know which setting or settings did the trick.

[Michael Roach 1304415 0]

Just checked with DPI. Still, Nada.

[Ross Carlson 156]

Michael, you mentioned it works on your laptop. Can you try exporting your facility file from the laptop and importing it into the other machine to see if loading a pre-made facility file prevents the error?

[Michael Roach 1304415 0]

Sorry Ross,

Still nothing.

[Ben Anello 811680 0]

Upgraded my NVidia drivers to the newest (released: March 1, 2016) at version 362.00. Still the same issue. I too installed the software package on my laptop with AMD and it worked fine. Must be an issue with OpenGL on the newer NVidia drivers. Will await word from Ross after he gets access to a newer NVidia graphics card to test the software on.

 

Edit: Oops. Missed page 2 for this thread. Guess I have some catching up to do. Tried export/import of the facility file as well from my laptop and yes, importing the working facility file has no effect on the error.