January 18, 201610 yr Luckily my FO seems to work just as he did before, with regard to tuning the radios etc. I used the latest version of MT, and chose p3dv2 during the install, if that might make any difference? John Anderson
January 18, 201610 yr Luckily my FO seems to work just as he did before, with regard to tuning the radios etc. I used the latest version of MT, and chose p3dv2 during the install, if that might make any difference? I did both of those, but will give it another go, just in case of finger trouble. Petraeus
January 18, 201610 yr I'm using VOXATC 6.52 and MT 3.0.3.1000, with P3DV2 selected. Same problem - copilot doesn't tune the radios, and sooner or later I'm handed over to Oceanic while in the middle of the USA. Petraeus
January 18, 201610 yr I have the oceanic problem too, while flying in southern Europe, but the approach and tower works almost fine. I have to disable and enable it continously because it hangs, and it's very annoying during takeoffs amd landings because I lose the traffic and the clearances
January 19, 201610 yr I am only flying short haul in the UK, maybe that is why I don't seem to have problems with the co-pilot. Looks like we really need this update.... John Anderson
January 20, 201610 yr I haven't bought Voxatc yet, waiting for the official P3D 3.x version. Just wondering, the Oceanic clearance issue, is that a general Voxatc problem in Version 6.52 ? Or just a problem of using it now in P3D 3.1. ? Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
January 20, 201610 yr Just wondering, the Oceanic clearance issue, is that a general Voxatc problem in Version 6.52 ? Or just a problem of using it now in P3D 3.1. ? It was fine in P3DV2. But it's interesting that experiences are mixed, with some having no problem at all. I am wondering whether this is specific to 3.1 as opposed to 3.0. I'm running 3.1. Are those who are not having Oceanic or copilot problems running 3.0 or 3.1? Petraeus
January 20, 201610 yr I don't seem to have a problem with Vox atc and p3dv3.1, but only flying short flights within the UK. John Anderson
January 20, 201610 yr It was fine in P3DV2. But it's interesting that experiences are mixed, with some having no problem at all. I am wondering whether this is specific to 3.1 as opposed to 3.0. I'm running 3.1. Are those who are not having Oceanic or copilot problems running 3.0 or 3.1? I do have problems with it, esp with the co-pilot who's not changing the frequency over, sometimes getting stuck and not replying to tower and I'm not able to switch it off etc. Can't confirm the issue with oceanic clearances though :/ But there's lot to improve... P.S. using P3D V3.1 Balint Szarka CPU Intel i9 9900K OC'd to 5Ghz RAM 32GB Corsair Vengeance DDR4 3000MHz (2 x 16GB) GPU 8GB NVIDIA GEFORCE RTX 2070 SUPER
January 20, 201610 yr Those are not exactly "improvements" they work with other versions of P3D, we just need a new installer for V3.1. The real improvements should be a better vectoring (20nm approach for a Bonanza is a bit excessive) with terrain alertness, dynamic SID/STAR and some bug resolution (disappearing traffic and program crashes), but I would gladly pay something for this type of upgrades, as the software is great as it this, however the new installer is mandatory. I wonder why there's no official statement about it...
January 21, 201610 yr Yesterday, Stefanik Radar (close to LZIB) handed me over to Oceanic Center... Can you actually believe that... Ironically the frequency was 122.00 which if you use AS Next you know it is the ATIS' frequency. VoxATC is quite unusable sometimes... Balint Szarka CPU Intel i9 9900K OC'd to 5Ghz RAM 32GB Corsair Vengeance DDR4 3000MHz (2 x 16GB) GPU 8GB NVIDIA GEFORCE RTX 2070 SUPER
Archived
This topic is now archived and is closed to further replies.