Ben Anello Posted February 27, 2016 Share Posted February 27, 2016 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 Ben Anello ZLA Senior Controller Link to comment Share on other sites More sharing options...
Michael Roach 1304415 Posted February 27, 2016 Share Posted February 27, 2016 I am having the exact same problem. I have a GTX 980. Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 27, 2016 Share Posted February 27, 2016 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. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Dhruv Kalra Posted February 27, 2016 Share Posted February 27, 2016 Been working on mine without issue. Win 7 Pro, GTX 980. Dhruv Kalra VATUSA ZMP ATM | Instructor | VATSIM Network Supervisor Link to comment Share on other sites More sharing options...
Ryan Geckler Posted February 27, 2016 Share Posted February 27, 2016 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. Ryan Geckler - GK | Former VATUSA3 - Division Training Manager VATSIM Minneapolis ARTCC | FAA Miami ARTCC Cross the Pond Planning Team Link to comment Share on other sites More sharing options...
Ben Anello Posted February 27, 2016 Author Share Posted February 27, 2016 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? Ben Anello ZLA Senior Controller Link to comment Share on other sites More sharing options...
Ryan Geckler Posted February 27, 2016 Share Posted February 27, 2016 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. Ryan Geckler - GK | Former VATUSA3 - Division Training Manager VATSIM Minneapolis ARTCC | FAA Miami ARTCC Cross the Pond Planning Team Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 27, 2016 Share Posted February 27, 2016 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. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ryan Geckler Posted February 27, 2016 Share Posted February 27, 2016 nVidia control panel tweaks. Ryan Geckler - GK | Former VATUSA3 - Division Training Manager VATSIM Minneapolis ARTCC | FAA Miami ARTCC Cross the Pond Planning Team Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 27, 2016 Share Posted February 27, 2016 nVidia control panel tweaks. Any tweaks in particular?? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ryan Geckler Posted February 27, 2016 Share Posted February 27, 2016 In the control panel, managed 3D settings: http://puu.sh/nnKHt/f2e39cc3a9.png http://puu.sh/nnKJi/525a1f5ae6.png Ryan Geckler - GK | Former VATUSA3 - Division Training Manager VATSIM Minneapolis ARTCC | FAA Miami ARTCC Cross the Pond Planning Team Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 27, 2016 Share Posted February 27, 2016 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? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ryan Geckler Posted February 27, 2016 Share Posted February 27, 2016 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... Ryan Geckler - GK | Former VATUSA3 - Division Training Manager VATSIM Minneapolis ARTCC | FAA Miami ARTCC Cross the Pond Planning Team Link to comment Share on other sites More sharing options...
Ben Anello Posted February 27, 2016 Author Share Posted February 27, 2016 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. Ben Anello ZLA Senior Controller Link to comment Share on other sites More sharing options...
Michael Roach 1304415 Posted February 27, 2016 Share Posted February 27, 2016 (edited) 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 Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 27, 2016 Share Posted February 27, 2016 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. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 27, 2016 Share Posted February 27, 2016 Have either of you tried tweaking the Windows DPI setting? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Ryan Geckler Posted February 28, 2016 Share Posted February 28, 2016 I have not tweaked the DPI, and yes, I did a proper troubleshoot Ryan Geckler - GK | Former VATUSA3 - Division Training Manager VATSIM Minneapolis ARTCC | FAA Miami ARTCC Cross the Pond Planning Team Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 28, 2016 Share Posted February 28, 2016 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. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Michael Roach 1304415 Posted February 28, 2016 Share Posted February 28, 2016 Just checked with DPI. Still, Nada. Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 28, 2016 Share Posted February 28, 2016 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? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Michael Roach 1304415 Posted February 28, 2016 Share Posted February 28, 2016 Sorry Ross, Still nothing. Link to comment Share on other sites More sharing options...
Ben Anello Posted March 2, 2016 Author Share Posted March 2, 2016 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. Ben Anello ZLA Senior Controller Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now