Jump to content

SeaJunk

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

8 Neutral

About SeaJunk

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good news. Two successful flights that got past the 10kt check with 1.0.3.2. No reinstalls other than A330 update. P3D v5.1 HF1 A330 1.0.3.2
  2. Just happened to me. You can fix it by setting a direct waypoint (DIR) after takeoff. You just have to put up with the green nav line until then On this flight I forgot to set Load/Fuel until after INITA and the flightplan. Could be coincidence.
  3. The checklist seems to be stuck on initiate taxi after built in push back is complete and the 'before taxi checklists' are completed. It doesn't seem to sense the taxi speed. A330 1.0.3.1 P3D 5.1 HF1 (5.1.12.26829)
  4. Just upgraded to P3D V5.1 from 4.5 and hit the same problem with the A320 on an RTX3080. Disabling TrueGlass solves it, RealLight can be left on. I'll checkout the tfdi discord.
  5. Appreciate it when you can take a look for a future release. In the meantime I'll stick with a working version in P3DV4_V1310. Something in the experimental updates caused this. Its being reported across the board in all external programs and hardware that can change the com frequency. Personally i experience it with both the Logitech (saitek) panel and Pilot2ATC. https://www.avsim.com/forums/topic/587846-aerosoft-airbus-radio-frequencies/
  6. Chiming in with the same issue. Logitech (saitek) radio panel with logitech driver on P3D V4. A318-A321, A330. The numbers flicker on the panel but do not change in the cockpit. Changing the freq in the cockpit does change the numbers on the panel. Rolled back to last stable busses fixes it.
  7. Setup a medium haul flight from JFK to LAX at FL380 in the A330 1.0.0.8. Step away for 4 hours and came back to excessive speed and FL400. Also reported by another user here: Reset back to FL380 by toggling ATHR and AP, just like the AFLOOR issue.
  8. I had the same problem as the OP. Fixed it the same way as the 319-321 installs: install 1.2.5.0 no vehicles - solved Either use the Lorby addon organizer and check the encoding of the addon files (on the tools tab) or add <?xml version="1.0" encoding="utf-8"?> to the top of the A330 add-on.xml file. Im not sure whats going on with my system but ive had to do this with every aerosoft aircraft install for a while now. They will then show up in the vehicles list.
  9. I had an installation problem similar to @globetrotter over here After uninstalling a working 1.2.4 and installing 1.2.5 as i had done in the past, no airbus vehicles were available and the add-in wasn't listed in the p3d startup add-on pane. The A320-A321 entry looked ok in add-ons.cfg and lorby reported no issues, the entry was shown in packages and other addons. The fix The A320-A321 add-on.xml file had an entry for fonts even though no fonts directory was installed in the path. For reference im on Win10 1903. I used Lorby addon organizer to remove the fonts
  10. A319 CFM on 1.2.3.2 LEMH MAME1D MAMEB DCT PTC UN851 VJF UL82 IBALU UN857 TERTO TERT6V GCLA (simbrief) FL 370 Speed drop occurred on the climb out at around FL340. Magenta text was 102 but the green dot was around 200.
×
×
  • Create New...