Meeko

Thank you YYW. I tried it and it made a huge difference. It baffles me why SWS can't configure the PC12 to taxi as good as it does now with your mods. Well done.

I like flying this aircraft. Taxiing is another matter. I'm finding taxiing is a real nightmare. Sometimes the nose swings 45 deg to the left, then correcting causes a 45 deg swing to the right. I just completed a flight and was taxiing to the stand. I wanted to turn right. I ended up with full right rudder but the nose was turning to the left and eventually off the taxiway. An outside view showed the nose wheel turned to the right. I have Turtle Beach rudder pedals which work fine with every other aircraft. Does anyone else have this problem, or is it only me? I have the 2024 V2007 installed. I have tried it with the aileron interconnect enabled and disabled. It's probably slightly easier to taxi with it disabled. Taxiing is a real pain to an otherwise great addon. I've waited quite a while for the 2024 model but now I'm just disappointed taxiing appears so difficult and, in my view, unrealistic.

Thankyou Sean. I appreciate that very much. All fixed now.

Aamir, if you're reading this; MS2024, the update went fine. I rebooted and loaded MS2024. I set up the A320 at a gate and then was presented with the "Sign into your account" page. After filling in my email and password, I get a reply "License currently activated on a different machine". I have since completely uninstalled the 320, including manually deleting two WASM folders. I've reinstalled using the installer, but I still have the same problem message. I have never installed the 320 on any other machine. Are you able to advise my next move? Regards Bruce R

Thanks Bob for coming on board with the link. I must admit the 190 was an Aerosoft app update. The 170 was a fresh install. It's a bit odd they both had an FMC WASM crash. Perhaps they're linked somehow. I un-installed both aircraft as per the documentation hub and started again. I did actually find some E170/190 WASM files in a MSFS2024 folder that the "clean-workfolder" left behind. I deleted those, reinstalled and now everything works. Cheers.

Went to fly the FSS E190 today but each time I opened up MSFS2024/E190 it opened with an orange WASM crash error. WASM crashes for me are pretty rear, so this was a surprise. The rest of the warning I couldn't read as the writing was too small. Both FMC displays were also orange. All other displays were black. Being the first day of AIRAC 2610 I thought perhaps an out-of-date AIRAC may somehow be involved. I was able to get into the EFB and into Navdata and press update. The update button flashed as if it was downloading but after about 10 minutes I gave up. I went out of 2024, back in and loaded an E170. It was just the same. Anyone else having this problem? Are there some WASM folders I should delete? If so, where do I find them? I've had a hunt around but can't for the life of me find them. Bruce R

Hello there Peterwk. Just make sure you have the latest Inibuilds Manager. It should be V 2.6.0. If you have, uninstall the 220, reboot and then reinstall. Hopefully things will be right then. Bruce R

When you install the PC-12 it doesn’t give you the option of the NAV radios like before. SWS’s Facebook page showed how to install the radios via the tablet. However, I had the same tablet problem as Janc above. At the very bottom of my Community folder I found files named z-LiM-SWS-PC12-GTNXi-EFB-v1.0.1 and also z-LiM-SWS-PC12-LiMEFB-v1.0.1. I deleted those and now the new tablet shows up. But, I have a new problem with the 2024 version. I have no ground steering whatsoever. I use the Turtle Beach rudder pedals and the only assignments I have for the rudders are the “Rudder Axis” and “Toe Brakes”. From an outside view, when applying the rudders, the ailerons move but the front wheel remains straight. Anyone else having this problem? Is there a fix? Bruce R

ALT + Q will get rid of the chocks. Bruce R

Maybe time to head over to the Just Flight 146 forum and ask over there. You'll most likely get a reply from one of the devs. 146 Professional | Just Flight Community Bruce R

Thanks for replying Bob. Yes the account is 'admin'. I was using W7 and had both FSX and P3D V3 installed. FSX was installed in C:\FSX and P3D in the default x86. Everything worked perfectly. Just last week I upgraded to W10. I then decided, as I was not really using FSX anymore, to un-installed it. I later found I couldn't edit files in P3D such as an aircraft cfg file. On suggestions in this topic I un-installed P3D and re-installed in C:\LM\Prepar3d V3. Now everything is back to working perfectly again. It's quite strange how this happened after upgrading to W10. Everything I have installed in both flight sims has been as an administrator so I guess it should have continued to work in W10. But that's computers for you. Problem has been sorted thanks.

Richard - After your first reply I went into notepad on my desktop, right clicked and opened properties / shortcut / advanced and clicked on the "Run as Administrator". Then tried to edit an aircraft cfg file again. I still had the same problem. I still had to "contact the administrator to obtain permission". That's what was confusing me. Hopefully it's all academic now because P3D has been uninstalled. Today's a new day, 0830 here in NZ, and I'm about to start installing into C:\LM\Prepar3D. It's quite surprising how things accumulate over the years. I have 50 - 60 scenery packages and 17 aircraft addons to install. It will keep me in doors all day. Just as well because the whole country is being hit with a cold blast today. Woke up to snow all around the hills. Regards

With W7 I had FSX installed in C:\FSX and P3D in it's default location in Program Files x86. Everything worked just fine. I took the plunge last week and upgraded to W10. Immediately after that I decided FSX had come to the end of its life so I uninstalled it leaving P3D in Program Files x86. Its only since then I've been having these problems. So thanks gents ..... I'll take on board your advice and uninstall P3D and relocate as C:\ Lockheed Martin \ Prepar3D V3. A job for next week I think. Thank goodness for retirement; it's not a 5 minute job. Richard A - thanks for the Notepad suggestion. As a matter of interest how do you open a file in notepad as administrator. I can't get my head around that one. Regards

Thanks Rob. Your last two suggestions - turn UAC to never notify, this has always been on the bottom (never notify), and "administrator" has always been checked. Your first suggestion is interesting. P3D was installed into the default location Program Files X86. I didn't realise P3D would have the same problems as FXS had. Do you think the problems could be solved by installing directly into C:\ ? Bruce R

I'm already opening the CFG file in Notepad to edit it. It's when I go to save my entry I get the message. Very frustrating. Bruce R

I have Prepar3d v3, all was well with W7. I have just upgraded to W10 and, as expected, have had my share of problems. Saitek Pro Flight controls was one of them. Problem was solved by FAQ over at Madcatz. Another problem I’m having is this; I’m not able to edit aircraft CFG files in order to install liveries. When I go to save I get the message; “You don’t have permission to save in this location. Contact the administrator to obtain permission”. Everything I have installed in P3D has been “Run as Administrator” so I am at a loss to know why this is now an issue. I’m sure there is an easy solution but I’m at my wits end trying to find it. Is there a tick box somewhere, or a slider to adjust? Any help would be appreciated. Bruce R

What you've got is all you're going to get. Carenado don't do manuals or flight tutorials like other developers. You're really left to your own devices. If you have a problem search this forum, and if you can't find an answer, post like you've just done. YouTube is another good source of information. You will often find tutorials there. Bruce R

Jakub, I agree with you, but even Carenado's, far from reality, G1000 is difficult to work out. The real G1000 in the video gives you some idea how it works. You can then relate that to Carenado's very simplified version. I was bamboozled how to figure out Carenado's, but the video certainly gave me some idea how things worked. I now know how to enter flight plans. With the lack of Carenado tutorials, this is better than nothing. Cheers Bruce R

Peter, have a look at this site. I was in the same position as you. It's helped me a lot. It's easy to relate it to the TBM 850's G1000. Cheers Bruce R

Thanks Ray and Jim for your replies. Got it! I knew where the course selector knob was, but I was finding it didn't do anything. I know now I have to be in VOR1 mode to have it display the course setting. Getting into VOR1 was a bit of a mystery solved by your comments. I must say it's not all that reliable. Even after clicking on the LSK1 on the PFD and hi-lighting the NAV SOURCE with a square box, and turning the outer DATA knob on the Display Control Panel, it doesn't always go through FMS1, VOR1, VOR2. I have to persevere a bit in order to scroll down. It get there in the end. Jim, I can see where you're coming from with the preset button. I wandered what it was for. I haven't tried it yet but will on my next flight. Thanks for your help. Bruce R

With the appalling lack of any flight tutorial, would somebody please give me a clue on the following; - When flying in Nav Source - FMS1, and approaching an airport with an ILS, what's the procedure in order to capture the ILS? I have entered the ILS frequency in NAV1 in the TUN page of the FMS but unsure how to enter (where-ever) the course while in FMS1. I've found pressing 'Approach' seems to bring it on the localiser, although that could just be the FMS1 doing that, but there is no indication of the glideslope. Any help would be appreciated. Bruce R

Eddie, when I read your reply I wondered what the hell you were talking about. But ..... after I installed again I looked for this 'dot', and low and behold there it was. I had missed it twice before. Now everything is up and running and am looking forward to doing a proper FMC flight. Thanks Eddie, and also 300hp for your input.

I have installed the Citation 'as administrator'. Antivirus was turned off during installation. When starting the sim 'as administrator' and selecting the Citation I get the following messages. Firstly; "Error: Object reference not set to an instance of an object". Secondly; after okaying that message I get " Access to the path C:\Users\(my name)\appdata\Roaming is denied". Thirdly; after okaying the second message I get a third one which is a rimmed box with 'FSX' with in the top rim but the box has no message. After getting rid of the third message the Citation loads in all its glory. At the moment the only thing I'm having trouble with is the loading of the database. The FMC displays "Loading Data Base" but doesn't do anything else. It appears to be stuck on that. No FMC buttons work. Bringing up 'shift 9' shows nothing is happening. I've left it for 55 minutes and it hasn't done anything. I'm wondering if it has something to do with the error messages I got. I have installed the Citation twice and it's only after the installations I get the messages. They won't appear if I go back into the flightsim. I'm running Windows 7, P3D V3.2. Could this be a Version 3.2 problem? Can anyone enlighten me? Meeko

I would check your IP address. If the 737 is working go into your tablets settings and open up the Virtual CDU (for the 737). Check the VAInterface IP = XXXXXXX (your IP address). Then open up the Virtual CDU 777 and make sure the IP address is the same. Bruce Ross

Yes, I use the M panel for the 777. The only thing that doesn't work for me in the altitude knob. It doesn't matter which way I turn it, it always goes back to '0' and stays there. Apart from that, it's great. Bruce Ross