Donovan Patrick 1327883

So, I've started using "override high dpi scaling" on all of my programs that use OpenGL on my laptop. Before I did this, everything appeared blurry and overly zoomed on programs like VRC and vSTARS. For some reason, vERAM can't do this and I'm not sure why. It says "Can not activate GL Rendering Context," but VRC and vSTARs are able to function just fine when I enable that in compatibility settings. The resolution on my laptop is 1980 x 1080 but the screen is 14 inches. If I want to run vERAM with HD resolution, I have to change the scaling from 150% (recommended) to 100% which makes ever

Hello, I have AUTOCAD, but I'm stuck on what the steps are for creating an ASDE-X sector file for an airport. Anyone able to help me out? Thanks.

Hello, In the real ERAM system, it shows you an Aircraft List, a list of aircraft that are about to enter your sector. Why does the current version of vERAM not have this? It would make it easier to identify aircraft and plan ahead, instead of having to just "remember" callsigns when they call up. Just food for thought.

The Charlotte runways are the only runways in the [RUNWAY] section. There's no runway for 2NC5. This is primarily the reason why I am having all these issues - none of the runways are actually defined in our sector files, so I have to define them myself. EDIT: Problem solved. Deleted 2NC5 from the airport list. It seemed like ACSIM kept on "seeing" runway 23 and 5 as that helipad so I had to delete it. I corrected the headings for magnetic variation (2 degrees) on the runways and the planes stay on the centerline. They also capture the glideslope.

Okay, I put "23" in the LOC box for runway 23 and it displays "2NC5" above without an error message. I'm not sure what that means, but the aircraft still can't seem to capture the localizer (yes, they are on a 30 degree or less intercept heading). For 18C, it shows "KCLT" at the top. The GS seems to work as well. However, the lateral path for the runway is off. The plane flies in between runway 18C and 18L instead of on the centerline, so the coordinates may need some tweaking. I also got a "no elevation data for airport" error when typing "GS" for runway 23. So it seems like with run

Don't wanna shoot ya, so I'll post the runways for Charlotte [RUNWAY] 36L 18R 002 182 35.20059 -80.96529 35.22525 -80.96739 36C 18C 002 182 35.19998 -80.95079 35.22736 -80.95314 36R 18L 002 182 35.20097 -80.93407 35.22468 -80.93608 05 23 055 235 35.20896 -80.94986 35.22259 -80.93112 02 20 016 196 35.37776 -80.71137 35.39775 -80.70686

This is for ACSIM, not Euroscope.

I've been writing some ACSIM files and I am having trouble getting the planes to join the localizer and glideslope for the runways. I defined the runways in the [RUNWAY] section of the .sct file, but for some reason ACSIM doesn't see it when i type in the runway in the heading/fix field. There's probably something that I'm missing but I don't know what it is. Any suggestions? Thanks.

During a recent session I had, I would type the SR command and , and it would say "flight strip request approved" but I wouldn't see the flight plan on any of my monitors. I want to know if any others had similar issues. Thanks.

Everytime I connect .air file to sweatbox, they show up in Tower trainer, but several aircraft do not show up in VRC on the Sweatbox server. Eventually, they start disappearing and reappearing without giving me any error messages. Then it gives me "socket closed" messages. It's a simple S1 local training scenario with about 10 or 15 aircraft loaded. Anyone had this issue before? How do I fix this?

Hey guys, so recently vPilot just decided to stop launching. I have Windows 10, but last week vPilot was working just fine. I have no idea what I did in that time period that could've made it stop working! Windows 10 already has .NET framework 4.5 installed on it. I have tried reinstalling vPilot and it won't launch. Every now and then it comes up with an error related to .NET framework. http://postimg.org/image/kd9fu0491/