December 15, 20169 yr thanks i9 14900KF 64 Gb DDR5 @ 6 Ghz CAS 32 Asus Apex Z790 W11 64 bits pro sur Kingston FURY Renegade 2 To, MSFS 2024 sur 2 ème Kingston FURY Renegade 2 To, RTX 5090 Alim Asus Thor 1600 W Gold Ecran Samsung G9 57 pouces 8K WC AIO ARTIC liquid freezer II 420 Boitier Gigabyte 3d mars https://www.youtube.com/channel/UCEFAk464aSg22aGFZ2LxeFg/videos
December 20, 20169 yr Are any of you guys having issues with getting UT2Bridge to work? I have everything installed properly, and have run the indexer but the only AI that is being injected into the sim is the default Alabeo 300s, or sometimes nothing at all. Kevin Tao
December 20, 20169 yr did you run ut2bridge in administrative mode ? i9 14900KF 64 Gb DDR5 @ 6 Ghz CAS 32 Asus Apex Z790 W11 64 bits pro sur Kingston FURY Renegade 2 To, MSFS 2024 sur 2 ème Kingston FURY Renegade 2 To, RTX 5090 Alim Asus Thor 1600 W Gold Ecran Samsung G9 57 pouces 8K WC AIO ARTIC liquid freezer II 420 Boitier Gigabyte 3d mars https://www.youtube.com/channel/UCEFAk464aSg22aGFZ2LxeFg/videos
December 21, 20169 yr did you run ut2bridge in administrative mode ? Yep I did everything exactly as I did for all previous versions which had worked for me. Kevin Tao
December 24, 20169 yr UK2000 EGKK to Default EHAM IFR 737NGX Tutorial 1 flight Flightplan: EGKK CLN8M CLN UL620 REDFA REDF1A EHAM Navigraph data 1613 rev1 in both NGX FMC and Vox 1. Sounds used for starting and departing jet AI? (06:08; 14:52 ) 2. Repeated confirmation of progressive taxi instructions (09:00; 09:40; 15:45) 3. Proximity to progressive taxi holds (10:00) 4. Altitude restrictions not observed by Vox - Alt rest increases from 5000ft to 6000ft between Detling and Clacton VORs, and thereafter to FL250 as part of flightplan. Vox advises to fly flightplan but continually instructs to descend to 5000ft after Detling VOR. (32:46) [NOTE: I set vox to go through my headphones so it cannot be heard on the video, a quirk of shadowplay. The ATC by vox was there in sim and worked without problem.] Kevin Firth - AMD 9800X3D; Asus Prime X670E; 64Gb Cas30 6000 DDR5; RTX5090; AutoFPS
December 28, 20169 yr UK2000 EGKK to Default EHAM IFR 737NGX Tutorial 1 flight Flightplan: EGKK CLN8M CLN UL620 REDFA REDF1A EHAM Navigraph data 1613 rev1 in both NGX FMC and Vox 1. Sounds used for starting and departing jet AI? (06:08; 14:52 ) 2. Repeated confirmation of progressive taxi instructions (09:00; 09:40; 15:45) 3. Proximity to progressive taxi holds (10:00) 4. Altitude restrictions not observed by Vox - Alt rest increases from 5000ft to 6000ft between Detling and Clacton VORs, and thereafter to FL250 as part of flightplan. Vox advises to fly flightplan but continually instructs to descend to 5000ft after Detling VOR. (32:46) [NOTE: I set vox to go through my headphones so it cannot be heard on the video, a quirk of shadowplay. The ATC by vox was there in sim and worked without problem.] I now believe I may have made an error with this flight, having had time to reflect on it over Xmas. I think the flightplan used may have resulted in point 4. The plan originally used in P3D was inaccurate and could have specified the wrong cruise altitude. I have used Aivlasoft EFB to accurately prepare the same flightplan, using the same Airac data as in the NGX FMC, and imported that into P3D. It is much more accurate than the original flightplan I had used. I am intending to refly this flight using the updated flightplan to see if it results in a better outcome. I expect that it will, and therefore point 4 above will have been down to my bad planning. Vox is quite dependent on using a good flightplan in the sim it seems, something which I didn't fully appreciate. If you are having any issues, it may be prudent to check that the sim flightplan used properly reflects your intended flight and the route planned in an FMC. Results of the second flight to follow... Cheers K Kevin Firth - AMD 9800X3D; Asus Prime X670E; 64Gb Cas30 6000 DDR5; RTX5090; AutoFPS
December 29, 20169 yr I now believe I may have made an error with this flight, having had time to reflect on it over Xmas. I think the flightplan used may have resulted in point 4. The plan originally used in P3D was inaccurate and could have specified the wrong cruise altitude. I have used Aivlasoft EFB to accurately prepare the same flightplan, using the same Airac data as in the NGX FMC, and imported that into P3D. It is much more accurate than the original flightplan I had used. I am intending to refly this flight using the updated flightplan to see if it results in a better outcome. I expect that it will, and therefore point 4 above will have been down to my bad planning. Cheers K Not For Operational Use Lockheed Martin Prepar3D Flight Plan Gatwick -> Schiphol Distance: 454.8 km Estimated fuel burn: 1141.8 l / 916.8 kg Estimated time en route: 0:31 Waypoints Route Alt (ft) Hdg Distance GS (kts) Fuel (l/kg) Time off Leg 8563.8 0:00 EGKK Rem Est Est ETE 454.8 Act Act ATE *RW08R (waypoint) -D-> 537 257 1.6 443 3.6 / 2.9 0:00 453.2 / WPT01 (other) -D-> 1209 078 3.1 460 7.7 / 6.2 0:00 450.1 / D077C (waypoint) -D-> 2363 078 5.3 460 13.1 / 10.5 0:00 444.8 / WPT02 (other) -D-> 2543 077 0.8 460 1.8 / 1.4 0:00 443.9 / TUNBY (waypoint) -D-> 8671 090 28.4 460 70.9 / 56.9 0:01 415.5 / DVR31 (waypoint) -D-> 11885 091 14.9 460 36.9 / 29.7 0:01 400.7 / DET (other) -D-> 15259 016 15.6 457 39.3 / 31.6 0:01 385.0 / D014E (waypoint) -D-> 17256 014 9.2 457 23.2 / 18.7 0:00 375.8 / DAGGA (waypoint) -D-> 25000 014 49.9 457 126.3 / 101.4 0:03 325.9 / CLN (other) CLN5P 25000 084 24.4 460 61.4 / 49.3 0:01 301.4 / ARTOV (waypoint) UL620 25000 072 20.1 461 50.1 / 40.2 0:01 281.3 / REDFA (waypoint) UL620 25000 073 76.3 461 191.3 / 153.6 0:05 205.1 / SULUT (waypoint) -D-> 25000 060 73.5 460 184.1 / 147.8 0:05 131.6 / SUGOL (waypoint) -D-> 20208 077 38.0 460 95.3 / 76.6 0:02 93.6 / EH606 (waypoint) -D-> 13582 112 30.7 458 77.5 / 62.2 0:02 62.9 / NIRSI (waypoint) -D-> 9297 025 19.8 458 50.1 / 40.2 0:01 43.1 / EH607 (waypoint) -D-> 7349 090 9.0 460 22.6 / 18.2 0:00 34.1 / EH608 (waypoint) -D-> 5757 132 7.4 455 18.5 / 14.8 0:00 26.7 / EH621 (waypoint) -D-> 3912 183 8.5 448 22.0 / 17.7 0:00 18.2 / EH622 (waypoint) -D-> 3046 183 4.0 448 10.1 / 8.1 0:00 14.2 / *RW18R (waypoint) -D-> 1506 183 7.1 448 17.9 / 14.4 0:00 7.0 / EHAM (airport) -D-> 4294967286 149 7.0 453 17.9 / 14.4 0:00 0.0 / This is the flightplan imported into P3D. Laterally it seems to be accurate, vertically it is way out. Somewhere along the line between Aivlasoft and P3D the accurate altitude restrictions for the route have been lost. Editing in notepad will be required to align the vertical profile of this route to the FMC.... Kevin Firth - AMD 9800X3D; Asus Prime X670E; 64Gb Cas30 6000 DDR5; RTX5090; AutoFPS
January 21, 20179 yr I now believe I may have made an error with this flight, having had time to reflect on it over Xmas. I think the flightplan used may have resulted in point 4. The plan originally used in P3D was inaccurate and could have specified the wrong cruise altitude. I have used Aivlasoft EFB to accurately prepare the same flightplan, using the same Airac data as in the NGX FMC, and imported that into P3D. It is much more accurate than the original flightplan I had used. I am intending to refly this flight using the updated flightplan to see if it results in a better outcome. I expect that it will, and therefore point 4 above will have been down to my bad planning. Vox is quite dependent on using a good flightplan in the sim it seems, something which I didn't fully appreciate. If you are having any issues, it may be prudent to check that the sim flightplan used properly reflects your intended flight and the route planned in an FMC. Results of the second flight to follow... Cheers K Sorry for the delay in sorting this, my OS and P3D SSD died on Christmas eve and I've only got it back up and running properly and installed everything again now. With a new install, making sure everything is running the correct navigraph data, the flightplan exported from Aivlasoft works properly and altitude restrictions are observed correctly. This is NOT an error with VOXatc Cheers K Kevin Firth - AMD 9800X3D; Asus Prime X670E; 64Gb Cas30 6000 DDR5; RTX5090; AutoFPS
January 24, 20179 yr Sorry for the delay in sorting this, my OS and P3D SSD died on Christmas eve and I've only got it back up and running properly and installed everything again now. With a new install, making sure everything is running the correct navigraph data, the flightplan exported from Aivlasoft works properly and altitude restrictions are observed correctly. This is NOT an error with VOXatc Cheers K Video demo... Kevin Firth - AMD 9800X3D; Asus Prime X670E; 64Gb Cas30 6000 DDR5; RTX5090; AutoFPS
January 25, 20179 yr Were you then handed off to 'London Centre' or 'Oceanic Centre'? The hand off was to london centre, 118.47 at 6:07 on the video. I continued the flight to EHAM after the recording finished and was handed to Amsterdam Centre then to a Schipol freq... I can record the whole flight from start to finish if that would be useful, i just did a partial recording because on my crappy internet connection it takes a day to upload 30mins of video Cheers K Kevin Firth - AMD 9800X3D; Asus Prime X670E; 64Gb Cas30 6000 DDR5; RTX5090; AutoFPS
January 26, 20179 yr Thanks - my problem is being always handed off to Oceanic. However, that does not happen with the same version of VOXATC installed in FSX/SE on the same machine. Maybe I need to do a complete reinstall within P3D. Petraeus
February 1, 20179 yr Thanks - my problem is being always handed off to Oceanic. However, that does not happen with the same version of VOXATC installed in FSX/SE on the same machine. Maybe I need to do a complete reinstall within P3D. Are you using sid/stars? I found in the past that EFB would not copy the sid/stars to my flightplan and I was guided to the first waypoint by Oceanic centre, after passing first waypoint and handover to say forinstance Frankfurt centre all worked well as it should be. Am in the process of re-installing my flightsim and had fatal error message. After reading through everything above downloaded everything again, installed voxatc in folder it suggests ie: C:\programfiles (x86)\internal workings ect the indexer ran through it's thing and worked for the first time for me. All previous attempts failed and got stuck. I have NOT flown with it yet and won't be able to untill next week. I will let you all know if it works okay now. Regards Leo de Haan Scotland
February 1, 20179 yr I tried to do a reinstall, but it seems as though the current P3D beta version is expired, so I can't test anything. Petraeus
February 1, 20179 yr I tried to do a reinstall, but it seems as though the current P3D beta version is expired, so I can't test anything.Once you reinstall that is what happens. I imagine Tegwyn is pretty busy about now since the 60 day period since the original release has expired, but you could try writing him, and explaining what happened. Earlier on, he sent me a file extending my "registration" when I did something similar. At this point I'm just waiting to see what happens next. As for the Oceanic handoff, make sure you have the migration tool enabled when you use P3d.
Archived
This topic is now archived and is closed to further replies.