microlight

The gauge won't run because I already have the 2017 C++ redistributables installed, and my PC won't allow me to install the necessary 2015 version because they're older than what I have installed! Anybody got any suggestions?

I had regular stutters in both FSX and P3Dv2.4 Tried all sorts of cfg tweaks, nothing worked. Then I turned off 'autosave' in FSUIPC and hey presto, no more stutters. So yes, something going on in the background.

Hi all. Just found Rob's thread on this in the Tips and Tricks forum; unfortunately the link to the replacement cloud.fx file no longer works. If this file is still available, can anyone help please? Many thanks, Martyn

Ok, tried a new flight from ground level and the stutter was still there. Then I changed the affinity mask to Bert's suggestion, put the antivirus on gaming mode, and it seems to be slightly improved. Not gone, but improved. As Ian noted, priority seems to make no difference. The explorations continue!

All, Thanks for your input, and for the helpful suggestions. SAX 702, it happened anywhere. Any location, simple or complex airports. Bert, my affinity mask is set at 126, which I understand is correct for a hyperthreaded i7 quad. I tried the calculator on the Gatwick FSG page (http://www.gatwick-fsg.org.uk/affinitymask.aspx?SubMenuItem=hardware) which gave me a value of 84, but this value just showed the full-screen view on the top left quadrant of my screen! Using 126 has all eight cores (four real, four virtual) active in Task Manager, with 1 reserved for the Windows background processes, whereas setting it at 14 only activates the four real cores. Cianpars, I put Avast antivirus into silent/gaming mode, put fsx.exe at high execution priority and then sat and watched it for a few minutes, and I didn't see any stutters, so I'll try it out more fully tomorrow and report back. Cheers, Martyn

Hi all. Can anyone point me in the right direction? I travel a lot, so I invested in a fast i7 quad core/Nvidia GTX760/8Gb RAM laptop so that I can take the simulator with me. Using the AVSIM set-up guide, I have it running very smoothly indeed, and mainly fly around the UK using ORBX scenery, both in small jetliners and a Piper Warrior, as I learned to fly in one of those. I'm also using Active Sky Next and REX. The only fly in the ointment is that every maybe half a minute to a minute and a half (it varies), I get a stutter lasting a fraction of a second, which seems to happen more frequently on the ground. The only tweaks I've added to the cfg.file are the highmem fix, and a [jobscheduler] section (to optimise how many cores I'm using) and [bufferpools] for the autogen. I've removed both of these additional entries: no effect. I've systematically gone through the options in the display settings, sliding them to the left one by one: no effect. I even tried the Bojote tweaking tool, and that only made it worse. Don't get me wrong: my FSX sim is better than it's ever been, and I'd be ecstatically happy with it - if only it didn't do that occasionaly falter. Any ideas? Thanks for your input. Martyn

Have you tried www.flightsimaviation.com?

Hi Luis. Of course! I plugged the rumblepad in, and it was recognised, and I was so keen to get going that I neglected to install the Logitech gaming software that came with the rumblepad. It's done now, and the force feedback tab now appears in the FSX menus - many thanks for your help! Cheers.

Hi all. Can anyone help me with a conundrum? I've run FSX passably on a Sony laptop (Win7, 64-bit) for a couple of years: not great but better than nothing as I travel a lot. I've used a Logitech rumble pad, which has force feedback and which has worked fine. Then a couple of weeks ago, I traded up to a Chillblast Tiger Moth laptop (also Win7, 64-bit) to improve the FSX experience (which it certainly has done - and how!). Same original copy of FSX Gold - but now the force feedback doesn't work with the same Logitech rumble pad. The tab in the controls section for force feedback in FSX, there on the Vaio, doesn't appear at all in the menus on the Tiger Moth. I've investigated as far as I can in FSX, but I can't get any clue as to why there's a difference. Can anyone help? Cheers!

Hi Samson. As Kevin said, the FS9 Enigma 737-300 (visual and flight models, plus some liveries) was only available as a beta download from the Enigma site for a limited time, around 2011. Although it runs in FSX, it was a native FS9 visual model, so that it's not possible to merge a VC with it. Follow the story on the QualityWings forums to see how the FSX project is progressing. Cheers, Martyn

No, but I use it routinely with the PMDG 737-800 and -900 - it works perfectly, so I doubt that it's an incompatibility with PMDG. If you are only getting engine exhaust on one side then something's up with the location parameters in the [lights] section. For example, here are the settings for the Posky 744 that I fly: light.15 = 9, -22.9, -70.2, -2.5, fx_fanengine_heavy , //port outboard light.16 = 9, 6.9, -40.5, -6.0, fx_fanengine_heavy , //port inboard light.17 = 9, 6.9, 40.5, -6.0, fx_fanengine_heavy , //starboard inboard light.18 = 9, -22.9, 70.2, -2.5, fx_fanengine_heavy , //starboard outboard Note the minus signs: these are important. The first figure after the '9' in each line is the horizontal location for the effect, the second is the lateral location and the third, the vertical. If the scaling of the two models is roughly comparable (and I can't tell because I don't have the PMDG), the only one of these you might need to change to get them roughly in the right place is the first one.

Hi Alex. Failure to show up on one side usually means that the entries in the aircraft.cfg file are not right - this is actually the commonest issue people have. This can also affect the other lights which might account for the tail light flicker, as Autoenvironment doesn't make any changes to your other default lights. Can you post the [lights] section of your aircraft.cfg so I can have a look? Cheers, Martyn

Hi all. I'm putting together a FDE, and was wondering which parameters in the aircraft.cfg (or even the .air file) control the positioning of the nosewheel on the taxiway 'T' at the gate. The flight dynamics work pretty well, but on loading, the plane's nosewheel is about 10-15 feet in front of the T rather than on it. I've tried adjusting all sorts of things, including the reference datum, CoG - even the horizontal wing position, and nothing affects the plane's position when it loads. Logically I'd have thought that it must be connected to where the reference datum is, but changing it makes no difference. Not a big issue I guess, but I occasionally have to slew the plane backwards (e.g. at KLAS) to get the nosewheel on the T before the jetways will work! Anyone have any ideas, or am I missing the obvious? Thanks!

Sam,Our 757 will indeed be FSX only.I'm sorry to read that we give you the impression of a lack of user respect: thanks for the feedback. I thought we were doing a pretty reasonable job, but anyone can improve. Can you give me some specifics to work with?Here's just one example of our feedback to our forum members. http://www.enigmasim.com/forums/index.php?showtopic=1018Cheers,Martyn

The Wilco A318-21 buses seem to be ok; except that my FS9 brings up an error message on closing when I've been flying it. Any hints on what might be wrong, or how to fix it? The error box seems to indicate appcrash when trying to close the feelThere gauge.;)

Hi olkev, and welcome.No problem with buying a used copy. As Jim says, there is only one update (9.0 to 9.1) BUT check your copy before you try to install the update patch: more recent sets were already patched to the latest version, so if yours is one of these, you won't need to apply the patch. Check by going to Help/About Mictrosoft Flight Simulator from the in-sim menu; if it says 9.1, you already have the latest version.;)

It's possible to extend the battery life without having to resort to the electric_always_available switch. If you lower the amperage and voltage settings in the [electrical] section, the battery life extends. For example, this is how the default looks:flap_motor = 0, 5, 17gear_motor = 0, 5, 17autopilot = 0, 5, 17avionics_bus = 0, 5, 17avionics = 1, 5, 17pitot_heat = 0, 2, 17additional_system = 0, 2, 17marker_beacon = 1, 2, 17gear_warning = 0, 2, 17fuel_pump = 0, 5, 17starter1 = 0, 20, 17light_nav = 0, 5, 17light_beacon = 0, 5, 17light_landing = 0, 5, 17light_taxi = 0, 5, 17light_strobe = 0, 5, 17light_panel = 0, 5, 17I have mine reset as follows, and the battery works for at least 15-20 minutes - long enough to start a 737, going through the extended overhead startup routine, program the FMS (or FSNav), push back, start the engines and go onto the generators. (In fact with this setting, the gear won't retract unless you've switched over onto the generators as the gear runs from the left alternator.)[electrical]//BusType, MaxAmpLoad, MinVoltage BusTypes:0=MainBus,1=AvionicsBus,2=BatteryBus,3=HotBatteryBus,4-7=Generator/AlternatorBus(1-4)//Amended to extend battery life at startupmax_battery_voltage = 28generator_alternator_voltage = 28max_generator_alternator_amps = 60electric_always_available = 0flap_motor= 0, 1 , 1gear_motor = 4, 1 , 1light_wing = 0, 1 , 1light_logo = 0, 1 , 1autopilot = 0, 5 , 1avionics_bus = 0, 5, 1avionics = 1, 5 , 1pitot_heat= 0, 2 , 1additional_system = 2, 1, 1marker_beacon = 1, 1 , 1gear_warning = 0, 1 , 1fuel_pump = 0, 1 , 1starter1 = 0, 1, 1light_nav = 0, 1 , 1light_beacon = 0, 1 , 1light_landing = 0, 1 , 1light_taxi = 0, 1 , 1light_strobe = 0, 1 , 1light_panel = 0, 1 , 1;)

I've used the F1View module for some years and it has only ever worked for me with the centre mouse wheel, not the keys. The Flight1 download page states that it's for the mouse scroll wheel... sorry.

Hi Martin.Have you tried the free F1 View module? This allows you to use your mouse wheel to scroll forward/backward, plus left/right when holding down the Ctrl key, and up/down when holding down the Shift key. It also provides a very smo-o-oth zooming action in external spot view. It's here http://www.flight1.com/view.asp?page=library;)

This is what I've used to keep my FS9 database more up to date: http://www.btinternet.com/~gb.mitch/index.html ;)

Martin, Have you tried ai_sound.zip, in the library here? I've been using it for a couple of years and it's a great improvement on the default; you can actually hear planes taxiing past you and taking off etc. ;)

Hi Dillon. The effect is very subtle - it's intended to mimic heat haze rather than be a smoke plume as such, so is difficult to capture in a still. Here are a couple of examples; the 727 with the custom turbojet trail (curved in the background) and the 747 turbofan trail visible from engines 3 and 4 - both in FS9. The 727 was taken a few years back, the 747 this morning. The effect works at two levels, a low-level 'idle' effect and a more dense effect that happens when the N1 is at normal flight thrust levels, automatically controlled by an invisible gauge in the panel. Yes, it can be used with any plane; there is a range of settings for common models in the manual, and any others can be arranged with a little effort. For example I have it on the Enigma ATP also. It's not a one-click installation but the end result is worth it, I think. If you want to try it, search on 'autoenvironment' in the library. ;)

Glad to have been of service. ;)

You have mail... The Project Airbus effect is hard-coded into the model, so is non-transferable. You can switch it on or off, but that's it. ;)

Alternatively, just copy all of the files in the 'texture' folder of the -800 base folder and paste them into the individual texture folders for each of the variants: e.g. into the 'texture_SIA' Singapore Airlines livery in the '-841' folder. These additional files are the VC, gear and night texture files - et voila. ;)