Jump to content
Sign in to follow this  
zedblk

PTT and response lag

Recommended Posts

Good day all, I hope everyone is good.

I have been using VOXATC  For sometime, and I love it, it’s a great program, It has its quirks and frustrations but for the most part but I’ve been able to find solutions on this board and the developer has eventually gotten back to me for others (busy guy I bet).

Now to my point, I recently Upgraded to prepared 3-D version 5.2 and had to upgrade fsuipc to v 6. I have an FDS cockpit for the A320 Which requires me to have two keyboards, I will get back to this, I recently bought a new keyboard for my second. 

Sooo, I’ve been pulling my hair out uninstalling and reinstalling everything over the last five days because the VOXATC starting to act up. My press to talk And responses were delayed would freeze up etc. I thought it could be the microphone, add on programs upgrade to prepare 3-D ( I kept my 4.5 version and even it was acting up too all of a sudden)… But if I use the first officer, it worked flawlessly. I was so frustrated today but I had an epiphany, what if I unhooked my new keyboard. And Boom, So far with the second keyboard unplugged and only using one, it seems to be working again.

So far with the second keyboard unplugged, it seems to be working 🤷🏼‍♂️

Sorry for the long post, but to my question. Is having more than one keyboard going to affect the way the VOXATC works As far as the PTT and responses and even opening up the panel? Has anyone had this issue? 

System is w10, Nvidia RTX 2070 super, i9 at 3.5 no over clock, traffic global with gsx, active sky and some add on airports

thanks!

 


 

 

 

Share this post


Link to post
Share on other sites
51 minutes ago, zedblk said:

Is having more than one keyboard going to affect the way the VOXATC works

I suspect so, but don't know directly so .... given my "tests" years ago failed when I tried to (fsuipc) map the PTT key press to the same trigger switch (button) on each of my 2 joysticks (sidestick & tiller on an A320) ie it was okay on one alone.

Others may know more ..... I guess one could try to see whatever with a second keyboard 🤔

 


for now, cheers

john martin

Share this post


Link to post
Share on other sites

Ok thanks,

I’ve tested this today for a bit, I have one wireless and one wired. I set the wired one in the VOX keyboard settings, but the wireless one responds as well for some reason with the same commands, so wireless off, works fine. Can still get buggy from time to time depending on flight plan, but that has always occurred, no fault of VOX I’m sure. 

Never thought that dual keyboards would cause an issue. It’s strange how through out it all though, if I left the FO on everything worked fine, even if VOX did lag a bit, the FO still worked with no lag if that makes sense..I just wish I would have thought of this earlier if it is truly the issue. 

Share this post


Link to post
Share on other sites
4 hours ago, zedblk said:

through out it all though, if I left the FO on everything worked fine

so in FO mode, initiating clearance / taxi requests by the FO with a PTT press on one or both keyboard/s worked ... or do you use PF "call for"'s usually (thus avoiding the issue of 2 keyboards).

out of curiosity, why 2 PTT's ....... just a layout / convenience ? 


for now, cheers

john martin

Share this post


Link to post
Share on other sites

vadriver, 

I would start a flight ok on ground talking myself, through a wireless headset, the issue came just after getting airborne,  VOX would start to really lag/freeze, my PTT wouldn’t work, if I pressed it, it was a long pause before it would sometimes finally “click” to talk. Made landing especially difficult because answering back for approach instructions etc backed up and I would have to disable/enable. But if I just switched to the F/O by pressing keyboard function, (mine was set to F) it would talk and answer itself with no lag through out the flight when I wouldn’t have to PTT to get the FO to answer for frequency changes etc. 

the two keyboard PTT’s was purely accidental, I bought a small half gaming keyboard to sit out of the way just in front of the side stick to handle VOX and GSX functions on the main sim computer,  My flight deck is all hooked up to the second networked computer to handle the deck only, so I can’t assign PTT to the side stick unless I hook it to the main PC, tried but side stick wouldn’t work right. I didn’t know setting up half keyboard on joystick setup would also by default set up second KB with same functions, which I should have known 🙄

second keyboard is a full keyboard, it has all the alphabet keys and functions, the half doesn’t, so yes having two was for convenience, I just left them both hooked up when I flew. 

So long story short, I can now say after testing,  if I shut off the second full KB, no more issues, VOX doesn’t like to share I guess. 

VOX will still occasionally lag/freeze up on flights (It always has for me as long as I can remember) but not consistently like it was before. Hope that explains it a bit better.

Share this post


Link to post
Share on other sites

Interesting conundrums you have there ...... in my "cockpit", I use a second (programmable) keyboard similarly but it is a Logitech G13 (though unfortunately no longer made).

But then, with my T7 flights I always use the FO mode (too busy taxing / flying to do the comms too & a tad unreal anyway).

The VATC feature whereby as PF one can ask the FO to request clearance/pushback/taxi etc. is a big plus.

& I also have fsuipc lua's that prompt the FO to report on approach.


for now, cheers

john martin

Share this post


Link to post
Share on other sites

Yea it is definitely a big plus, it would lessen the “workload” I suppose if I didn’t do comms too, but it keeps it interesting for me I guess, now if only I could figure out how to split the headset so I could have two when I have a live FO over for a flight session. 

All working well again now anyway with ppd v 5.2  (except for the annoying v5 screen flash with open/closing VOX and GSX windows) 

So hopefully if anyone else has this issue hopefully by reading my long winded post they can maybe save themselves some aggravation if they have a second keyboard.

Safe and happy flying!

  • Like 1

Share this post


Link to post
Share on other sites
10 hours ago, zedblk said:

now if only I could figure out how to split the headset

surely FDS hardware can do this ...🤔


for now, cheers

john martin

Share this post


Link to post
Share on other sites

The head set i have is just coming through the sim computer via USB, nothing fancy. I thought a splitter would work but no joy.

I’m sure the FDS could, but I have a dummy ACP panel for now, I’m waiting on installing a functional one for now.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...