Aerosoft Airbus and Vatsim

[Scottie5 1]

I am not sure if anyone has flown the aircraft on Vatsim.  Is anyone having an issue typing and transmitting text in Unicom when flying the A319?  Seems to be the only aircraft where I am having that issue.  Maybe someone much smarter than I am can shed some light on that.

[Hoffie3000 52]

Yes, same here.

Workaround for me at time is first to load a default Aircraft with power on the Radio (my Vatsim Client is vpilot).

No idea why the Airbus this cause.

 

 

[DaveCT2003 2285]

This occurred during Beta Testing (with me) and it went away when I received the next update (during the Beta).  The only work around I found was to load the Ready for Take Off State, let the aircraft settle out, and then return the Aircraft State to Ready to Start (Turn Around State).

 

One thing you can try is removing and reinstalling the aircraft, which will reinstall the Aircraft States related files (which are not saved flight files as they are in other aircraft).

 

I'll pass this along.

 

 

 

[Scottie5 1]

I am about to enter a controller's airspace, did this affect voice?

[DaveCT2003 2285]

For some, not others.

 

If using VPILOT and you have frequencies populated in the upper right corner of Vpilot then you're good to go.

 

[Scottie5 1]

Well, at least I can use voice for the moment.  Also happy to know I am not crazy. (yet)

[Scottie5 1]

Uh oh, now I can't tune the frequency.  freq is 120.570 and Airbus radio does 120.575.

[DaveCT2003 2285]

7 minutes ago, Scottie5 said:

Uh oh, now I can't tune the frequency.  freq is 120.570 and Airbus radio does 120.575.

 

If you're already in flight, and having this problem, then it's not going to work for you.

 

 

[Emanuel Hagen 5033]

51 minutes ago, Scottie5 said:

Uh oh, now I can't tune the frequency.  freq is 120.570 and Airbus radio does 120.575.

 

That's normal, VATSIM does not model the frequencies correctly.

The whole flightsim world uses the .25kHz spacing, so correct frequencies would be 120.500, 120.525, 120.550 and 120.575.

This is all P3D supports. VATSIM simply cuts off the last digit and makes it a zero, even though it would be a five.

 

Nonetheless, all pilot clients are programed to correct for this, so if you tune 120.575 in your aircraft the correct VATSIM frequency of 120.570 will be tuned by your pilot client.

[B777ER 5]

So vPilot and this aircraft don't work together as far as typing text in Unicom if starting from Cold and Dark? 

[Emanuel Hagen 5033]

For most people it works fine, it seems Dave is the only one who had this problem during testing.

 

For those who actually have this, does vPilot show you that you have tuned the correct frequency?

What happens if you use vPIlots text command to enter a frequency (.com1 122.800 for UNICOM for example), does it work then?

[marvic 183]

I found it did not work to text,  I tried inserting the frequency via V-pilot (.com1 122.800) and the radio panel. I only got it working after I noticed that the " Battery Master" switch was not turned on my Saitek switch panel until

after I was airborne. No issues after that.

[DaveCT2003 2285]

Guys,

 

The problem is that the radio isn't interfacing, worse than that really, it seems like the Radio part of VPilot doesn't know there's an aircraft loaded so teh radio (Text and Voice) in Vpilot isn't being activated.  But this is an Airbus problem, not VPilot.

 

So in short, neither Text or Voice will work.

 

Please see above for the work around until this is corrected.

 

 

 

[Hoffie3000 52]

Sometimes a Picture Show more:

 

This is the message from vPilot. If you getting this then no transmitting or receiving of text is possible.

COM2 at this point also not working.

Workarond see above

 

Wolfgang

 

[Mathijs Kok 32485]

We'll explore this issue later.

[FASTBACK77 0]

Has anyone been having issues with selecting Mode C with vpilot?

 

When I load the A319 in turnaround state vpilot is stuck with Mode C off and can not be turned on, however if I load up taxi state then Mode C is stuck on and cannot be turned off. Shutting down or starting the aircraft in either state does not change the issue with vpilot and Mode C....for me at least.

 

If I change to any other aircraft then vpilot Mode C works normally again.

 

Thanks

[Hoffie3000 52]

Hi, how do you activate Mode C?

Are you turning on via ATC Panel of the Airbus, or the Button of vPilot?

 

I use the ATC Panel and is working fine with exeption described above.

 

Regards, Wolfgang

[FASTBACK77 0]

Hi Wolfgang,

 

I am activating it via the vPilot program, I will try the ATC Panel as suggested and report back.

 

Thanks

Ben

 

Edit: Tried ATC Panel and Mode C now turns on/off in vPilot!

Thanks Wolfgang

[Magnus Gustafsson 0]

On 7/18/2018 at 10:36 PM, DaveCT2003 said:

 The only work around I found was to load the Ready for Take Off State, let the aircraft settle out, and then return the Aircraft State to Ready to Start (Turn Around State).

 

This one worked for me, thanks!

Magnus

[ronkurz77 0]

Same vPilot issues - and only with the Aerosoft Airbus (just installed it yesterday) - so this doesn't seemed to be fixed.  yet.

 

Thanks for the work-around - at least that works.

Ron

 

 

[Mathijs Kok 32485]

We know but currently we don't really know how to fix this. We tried inserting a timer loop but that does not see 100% reliable.

 

[DaveCT2003 2285]

I'm the first person to report this (during the Beta) and I'm working to try and figure out how it magically started working on my system.  No luck yet though.

 

 

[kingm56 6]

The problem is vPilot thinks the aircraft power is off; just set key commands to enable power within P3D and it will work fine. 

 

I discovered this when I noticed FSUPIC Offset 281C was set to 0, even when the bus' power was on.  I believe vPILOT uses FSUIPC as its interface; so, once I set it to 1, it worked fine.  i assume this is a problem for some and not other is based on the 'default' flight parameters.  If you're using a 'cold and dark' setup, and the main batter is set to off, vPilot won't transmit...

[kingm56 6]

On 8/15/2018 at 1:04 PM, DaveCT2003 said:

I'm the first person to report this (during the Beta) and I'm working to try and figure out how it magically started working on my system.  No luck yet though.

 

 

The problem is vPilot thinks the aircraft power is off; just set key commands to enable power within P3D and it will work fine. 

 

I discovered this when I noticed FSUPIC Offset 281C was set to 0, even when the bus' power was on.  I believe vPILOT uses FSUIPC as its interface; so, once I set it to 1, it worked fine.  i assume this is a problem for some and not other is based on the 'default' flight parameters.  If you're using a 'cold and dark' setup, and the main batter is set to off, vPilot won't transmit...

[DaveCT2003 2285]

12 hours ago, kingm56 said:

The problem is vPilot thinks the aircraft power is off; just set key commands to enable power within P3D and it will work fine. 

 

I discovered this when I noticed FSUPIC Offset 281C was set to 0, even when the bus' power was on.  I believe vPILOT uses FSUIPC as its interface; so, once I set it to 1, it worked fine.  i assume this is a problem for some and not other is based on the 'default' flight parameters.  If you're using a 'cold and dark' setup, and the main batter is set to off, vPilot won't transmit...

I concur.

 

Which version of FSUIPC are you using?