Eric Steiner Posted December 24, 2020 Share Posted December 24, 2020 Hello All, When ever controlling or event observing with vERAM I keep getting a OpenGL out of memory error. Has anyone ever had this, if so how do i go about fixing it? If not, who should I contact for this issue? Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 25, 2020 Share Posted December 25, 2020 How much video RAM do you have? Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 25, 2020 Author Share Posted December 25, 2020 3 hours ago, Ross Carlson said: How much video RAM do you have? I have 6GB of Video Ram. i have a RTX 2060 and vSTARS and VRC work just fine. i have 16GB of Ram in my system. Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 25, 2020 Share Posted December 25, 2020 I'm afraid I have no idea why you would be getting that error. The only thing I can suggest is try updating your video driver, or even downgrading it if it's already on the latest version. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 25, 2020 Author Share Posted December 25, 2020 37 minutes ago, Ross Carlson said: I'm afraid I have no idea why you would be getting that error. The only thing I can suggest is try updating your video driver, or even downgrading it if it's already on the latest version. I have even tried that but nothing seems to work. Is there anyway i can go into computer and allocate enough Vram for it? otherwise I am unable to use vERAM at all because it will crash Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 25, 2020 Share Posted December 25, 2020 It should make use of all that you have, and you have more than enough. vERAM doesn't use very much memory at all. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 25, 2020 Author Share Posted December 25, 2020 41 minutes ago, Ross Carlson said: I'm afraid I have no idea why you would be getting that error. The only thing I can suggest is try updating your video driver, or even downgrading it if it's already on the latest version. Could it also be, I am using 2 USB monitors that were at different resolution then the other 2. could that have anything to do with it? vERAM trying to use 2 different resolutions. i have since changed them so they are all the same. (I have 4 montiors in total) Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 25, 2020 Share Posted December 25, 2020 Usually that's not a problem, but I have no idea what's causing the issue, so I can't rule it out. Does vERAM work if you run it only on your primary monitor? Other users have reported issues running vERAM on a secondary monitor. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 25, 2020 Author Share Posted December 25, 2020 28 minutes ago, Ross Carlson said: Usually that's not a problem, but I have no idea what's causing the issue, so I can't rule it out. Does vERAM work if you run it only on your primary monitor? Other users have reported issues running vERAM on a secondary monitor. so this issue still happens even with me running it on one monitor. i just tested my theory and it failed again. i will post a screenshot of the error i get Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 25, 2020 Share Posted December 25, 2020 I would try uninstalling then reinstalling your video driver. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 25, 2020 Author Share Posted December 25, 2020 2 hours ago, Ross Carlson said: I would try uninstalling then reinstalling your video driver. I may try that and see what happens. Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 25, 2020 Share Posted December 25, 2020 1 hour ago, Eric Steiner said: I may try that and see what happens. Okay, and if you do, please report back with the result, good or bad. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 25, 2020 Author Share Posted December 25, 2020 8 minutes ago, Ross Carlson said: Okay, and if you do, please report back with the result, good or bad. So uninstalled my graphics driver and did a clean install of the most up to date and after an hour (almost on the dot) it gave me the error again 😞 Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 25, 2020 Share Posted December 25, 2020 I'm afraid I'm out of ideas. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 25, 2020 Author Share Posted December 25, 2020 24 minutes ago, Ross Carlson said: I'm afraid I'm out of ideas. With the fact I can use vSTARS and VRC just fine (dont know why that is) i am going to get into contact with NVIDIA and see if they know the problem. and see if they have any fixes. Link to comment Share on other sites More sharing options...
Dhruv Kalra Posted December 26, 2020 Share Posted December 26, 2020 Are any of your displays using Windows interface scaling? Try setting Windows scaling to 100% on all your monitors and try again. Dhruv Kalra VATUSA ZMP ATM | Instructor | VATSIM Network Supervisor Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 26, 2020 Author Share Posted December 26, 2020 29 minutes ago, Dhruv Kalra said: Are any of your displays using Windows interface scaling? Try setting Windows scaling to 100% on all your monitors and try again. So I tried that and all are set to 100 percent and that changed nothing. I still got the error Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 26, 2020 Author Share Posted December 26, 2020 (edited) so we have kind of narrowed it down to a memory leak in my VRAM during the use of vERAM. it will pop this error at 45 almost on the dot. i dont know how much anyone knows about computers but that something at least. how i can tell it is failing is my on screen display will go all block like (pictured below). it also will close out completely with no warning after about 10-15 min. Edited December 26, 2020 by Eric Steiner Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 26, 2020 Author Share Posted December 26, 2020 I Also have the crash reports from 2 different instances if you would like to look at those. Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 26, 2020 Author Share Posted December 26, 2020 UPDATE: i have found that my system had over 9000 MB (9GB) in standby memory. After downloading RAMMAP (https://docs.microsoft.com/en-us/sysinternals/downloads/rammap) in the drop down you can clear then standby. after doing that it opened up the memory i needed to use vERAM. now i have not tested this in the long term, but from the looks of it, this was the fix 🙂 Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 26, 2020 Share Posted December 26, 2020 (edited) The O/S should automatically release standby memory if more memory is needed by an application, so I'm skeptical that this is the actual fix, but please let me know what you find out. Note that it could be that some other program that you have running is not releasing its memory properly. I don't think that vERAM has such a nasty memory leak, because others would have reported it by now, but it's possible. Edited December 26, 2020 by Ross Carlson Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 27, 2020 Author Share Posted December 27, 2020 so one thing i have noticed is that if i use the two monitors that i have connected to USB's i will get the error, however, if i just use the GPU it runs fairly well. still testing and will let you know Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 27, 2020 Author Share Posted December 27, 2020 Question. how much ram does vERAM use on avarage in the working set? Link to comment Share on other sites More sharing options...
Ross Carlson Posted December 27, 2020 Share Posted December 27, 2020 40 minutes ago, Eric Steiner said: so one thing i have noticed is that if i use the two monitors that i have connected to USB's i will get the error, however, if i just use the GPU it runs fairly well. still testing and will let you know Earlier in this thread you said it still crashed if you just use the primary monitor. What's different this time? 27 minutes ago, Eric Steiner said: Question. how much ram does vERAM use on avarage in the working set? It will vary a little depending on how many aircraft and other controllers are in range, and how many displays you have open, but a reasonable average is around 85 megs. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Eric Steiner Posted December 27, 2020 Author Share Posted December 27, 2020 (edited) so i am running it in windows 8 compatibility mode, turned on triple buffering for OpenGL and just running on the GPU. also with clearing the standby memory. i think with the combo of those it may have fixed it but still to early to tell. EDIT: After some time controlling on CTR, clearing the standby, with only using the monitors that are on the GPU and everything, it still happens. I don't know what the issue is but all i did was prolong the issue. Edited December 27, 2020 by Eric Steiner update 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