Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Ross Carlson

Pages: [1]
The more I think about it, the more I realize that landline stuff (really ALL comms stuff) should be handled by AFV, primarily because FEs are already managing a database of facility-specific configuration data for AFV, and it would be good to keep that all in one place. We'll just need to have some inter-app communication happening between the controller clients and the AFV client to keep the text frequencies in sync, since all text comms will still flow through the controller client.

Hi all,

As most of you have probably seen, I am beginning to plan for retiring VRC, and enhancing vSTARS and vERAM to be more suitable for top-down controlling and for controlling tower cab positions. I'm currently working on restructuring the vSTARS code in preparation for this future update, and I'm running into a problem with the old voice system code library, which is known as VVL.

VVL is no longer used for air-to-ground VHF comms, since we all use AFV for that, but you can still use the VVL system for landline calls. As I was running into these issues, I realized that I'm probably wasting my time, since I assume most facilities use TeamSpeak or Discord for their coordination, rather than using the override and intercom calls built into vSTARS and vERAM. They generally don't even work properly if you don't have port forwarding set up in your router anyway.

So, my inclination is to remove all remnants of VVL from vSTARS and vERAM, and let everyone use TS or Discord for landline calls, and/or use AFV for landlines if that functionality is added to AFV in the future. However, I wanted to make sure my assumption is correct, and nobody is using (or very few people are using) VVL for landline calls.

Please let me know your thoughts, especially FEs.


General Discussion / Re: vPilot saying incorrect CID/Password - Help!
« on: September 03, 2020, 11:39:45 PM »
I suspect that there's more to this story ... if you correctly type your new password into the vPilot settings, it will update the XML. That code is untouched since the very first version of vPilot, and if there was a problem with it, I would have known about it years ago.

If you edit the vPilotConfig.xml file and put your password in there in plain text (normally it is encrypted, which is what John Combs described as "a mix of characters pulled out of the air somewhere") then vPilot will encrypt it and re-save the XML. This is exactly what happens if you type the password correctly into the vPilot settings window.

Events / Re: Charlotte-Orlando Xfire FNO
« on: February 09, 2018, 06:34:34 PM »
Will default scenery be OK for the FNO ??  I am on a new sim build with P3DV4 and having problems with the KCLT scenery update load from FSDT..

Mike, did you get this straightened out? I had a problem with the FSDT CLT scenery in P3D v4 where none of the buildings or surfaces would appear. It turned out it was because the scenery relied on functionality from GSX. Once I installed the free version of GSX, the scenery worked fine.

Pages: [1]