Pretty sure you can change the folder name and everything should be OK. You obviously can’t change anything next level down, or it breaks.
I would however recommend using AddOn Linker. You can create folder structures however you want, drop the packages in without having to rename everything, and then just use AddOn linker to turn on/off directories or sub-directories. It’s smart enough to only link the actual MSFS package and ignores any folders without packages. It will search down the folder structure looking for packages. Very handy.
To add to the other Addon Linker suggestion, there is also a program on flightsim.to called WindSailor. It’s mostly a web browser, but does the tedious work of downloading, unzipping and deleting the old mod folder. It remembers the custom folder you downloaded a mod to, so after the initial download it’s one-click upgrades! But it depends on not renaming the mod folder so it can delete it.
Back on topic:
I have a little box that has knobs and buttons. I had SPAD set up for the TBM and all of the functions changed from AS3000_TSC_Horizontal_ to AS3000_TSC_Horizontal_1_ (for the left touchscreen) and i got the knobs working again. But the actual touchscreen buttons dont seem to have an event anymore.
Previously for the MFD DIRECTTO i had AS3000_TSC_Horizontal_Softkey_2 (to set it on MFD) and then AS3000_MFD_SOFTKEYS_5 (Direct to is the 5th button) and this worked fine.
AS3000_TSC_Horizontal_1_Softkey_2 works for selecting MFD but I cant find any replacement for the MFD softkeys, as i think the one i tried above is now referring to the row under the big screen. Does anyone know what they are?
Always had it before last update and still have it in every other airplane. I am able to do full systems take off and landing capturing RNAV and everything but just not getting the landing call out on 500…400…300… Is that a setting I need to turn on now? (Would assume it would always be on by default… Maybe it is a ground radar I am not turning on or something.)
Please help.
NOTE: I didn’t post to this thread originally. The forum admins moved this post into here. I am not sure this is a issue that is related to this thread as I didn’t see anyone else mention it.
Found a video of one landing in real life where you can hear out the call outs on landing.
Hi @KevinJG124
I’ve tried setting up the routing a few different ways and always get a “normal” route/distance. I’m on PC if that makes any difference.
I just did a normal WM setup of the flight and it imported correctly (KBLM to KLAX, hi IFR routing). I don’t have any mods in my test sim setup.
Hope someone else can figure out what’s happening.
Regards
Since AAU1 the beacon and nav lights are actually controlled on the touch controllers.
Nav lights default to on when you load turn on the plane. Beacon lights turn themselves on when you set either engine to “run” but can be manually turned on through the touch screen.
I appreciate the reply. Im on PC as well. Ive tried to import a plan through Simbrief, Navigraph and using the in-sim world map. They all result in the same. My first few flights had normal distances and times. Then, it just started to do this and hasnt stopped. Hopefully it works itself out. Its doesnt affect any operation of the plane, just more of a nit-picky annoyance. Also, no mods installed either since update was done.
That was a Community Mod, not supported by the new version. Likely the source of that roaddata would now have to be officially licensed for re-use by MS, who owns the new G3000/5000 - just like Navigraph Charts.
Please do not use VS in climb. You will slip the virtual mortal coil in the classic tradition of many pilots (i.e., you will depart controlled flight and crash). VS will force a climb rate irrespective of how fast you’re going - literally, it will keep that climb rate until you run out of airspeed and stall.
Use Flight Level Change, and refer to the Pilot’s Operating Handbook for best climb speed. That speed also can appear on your PFD if you enable Speed Bugs in the PFD GTC Control Page. Look for Vy, in the TBM that’s 124 knots. Whatever climb rate you get there, the plane will maintain 124 knots until you reach target altitude.
Was wondering about callouts myself. I saw something in the HJet Discord thread that the G3000 current API doesn’t have any hooks/links for callouts so they’re eventually going to do it manually for the HJet in a future update after the main AAU1 is integrated, so a manual WIP for the HJet.
On the WT Discord they said they couldn’t secure the audio for callouts, so that may be the case there .
mdapol
Agreed. RW pilot here with FAA IGI cert. I have been with Brand X sim for over 20 years. Typically. the first aircraft that newbies choose is complex and they immediately fly IFR, skipping all the VFR training one receives in the real world, and then wonder why they have problems.
THis AAU1 G3000/5000 upgrade is truly awesome. Works very similar to real deal.
If a sim works like the RW, then your training has to be like the real world. I recommend the free certs and training on VATSIM, P1-P4, VATSTAR has free one on one training also. Simply put, one could follow the training sequence similar to Embry Riddle, 172sp G1000 P1 VFR and IFR P2, DA42/62 G1000 for P3 MEL, then Longitude G5000 for P4 rating and ATP. These are the VATSIM ratings and aircraft I recommend. Everything is free. There are great FAA manuals also for free. I welcome all gamers and hobbyists, but they have to develop a strategy for training or just remain a hobbyist and fly for fun.
Hello LeeAus,
I realize your frustration. This is a truly great upgrade AAU1 by WT. It works very similar to real deal. I am RW pilot and FAA IGI. I would be glad to help if possible. Here is a very good, short test route for the TBM ( I use Longitude). KBUR-KLAS milk run. Just put KBUR as departure and KLAS as dest. ALT FL 270. Nothing else. PROC button, Departure, Slapp2.Misen then STAR Misen.Rndrz2 no intermediate fixes. then ILS 26L full approach at BERBEN IF (initial fix). This is a “Vector” departure DP. You will see a MANSEQ on DP and a MANSEQ between STAR and ILS approach, amazingly, just like RW. I always use 210 HDG bug on MANSEQ vector DP. Then wait for ATC to proceed direct when able to Slapp, whatever. Here is my point, If you don’t quite understand what I just said, that is OK and understandable. Maybe you need more training. Try it. See how you do. Get back to me with questions. Please don’t give up. This is a great hobby. Just get some free training from VATSIM if you like. P1-P4. VATSIM certs. …or just fly around as you like in vfr. It is your sim. Whatever.
I’m going to throw this out there under the guise of “support” per thread title for consideration.
There has been so much confusion and frustration here concerning the updated avionics (with more to come this year) that this thought just keeps bubbling up for me,
There is a large community of active/retired pilots, IPs, Stan evils, and knowledgeable simmers here that make the case for having shared cockpits stronger now than ever.
While doing just casual flights with other simmers interests large numbers of people here, the ability to directly interact and instruct another flyer would address several issues constantly brought up here (e.g. more realistic in-sim training).
I’m sure we would be able to develop a cadre of people who are capable and willing to help others correctly progress in the sim.
Regards
All systems seemed to work correctly. Used LNAV to intercept the localizer at 15 DME. It failed to be named in the PFD and when I switched to Localizer tracking and selected APP on the autopilot the plane turned away from the localizer and continued to circle. The glideslope marker appeared correctly and began to move downward but it would not intercept and track the localizer. I manually repositioned it on the localizer track twice, but each time when I armed the approach the aircraft just began to turn off track and continue to circle. I finally flew manually to the FAF and then it finally did intercept the localizer. The airport was UHPP runway 34L and the localizer freq was 108.70. All info sources verified a range of over 30 nm for the signal. The winds were very light and the approach was visual below the IAF. A previous flight using an RNAV approach worked perfectly and the plane accurately tracked the flight plan.
.