-
SWS PC-12 for msfs2024
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.
-
SWS PC-12 for msfs2024
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.
- Fenix A3xx Update v3 released [21OCT26]
-
Fenix A3xx Update v3 released [21OCT26]
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
-
FSS E170/190 FMC WASM crash - MSFS2024
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.
-
FSS E170/190 FMC WASM crash - MSFS2024
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
-
A220 Nothing Happens at Start-up
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
-
Simworks Studios Site Has Updated PC-12 5-18-2026
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
- Kodiak 100 (MS2024)...Is it over?
-
JustFlight Avro RJ problems
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
-
Admin Privileges
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.
-
Admin Privileges
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
-
Admin Privileges
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
-
Admin Privileges
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
-
Admin Privileges
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
Meeko
Members
-
Joined
-
Last visited