Ian P

That certainly wasn't how the 73NG sim I flew operated, which was a fixed-base, but training approved, one. Wonder if it's another one of the many "airline options"? Ian P.

Excuse me for butting slightly here, but I thought that you could silence the alarm by pressing the appropriate alarm button to acknowledge it, but the light would remain lit (and appropriate EICAS/carrot salad indications present) until the fault state is cleared? I only have a couple of hours in a realistic B73NG cockpit simulator (far too many in the PMDG jets, which very rarely break on me...), but my recollection of what to do in an alarm situation was to verify that both crew understand what the message is (Master caution, flap setting" or "Master Warning, engine vibration" for example, with a reply hopefully the same from the other seat!), then silence the alarm, then the Captain makes the decision of who deals with the fault and who flies the aircraft. If so, then there must be a variable for the MW/MC light clickspots, but I'd presume they'd be Local to the PMDG models and documentation, rather than being MSFS commands. I don't think you can do a thing with alarms in MS default aircraft, other than apply earplugs and resolve the situation! Cheers, Ian P.

I doubt it. Pete really quite likes his trains! ;) Ian P.

Sorry, I meant console logging. Posting too quickly with 28 forum windows open! Ian P.

Hi, No and no. You simply run the latest installer, available from the downloads/updated modules thread at the top of Pete's forum, which will not overwrite your FSUIPC.ini file, then select "check existing registration" when asked. To be slightly fair, this is all in the manual and installation notes. ;) Cheers, Ian P.

Hi, you probably just need to turn off logging, as per the FSUIPC documentation in your modules folder. Cheers, Ian P.

That's one of the things being covered by the upcoming patch for FSX:SE, according to DTG. It's to do with the "effects" slider setting, apparently. If you check the front page of simFlight.com, I posted the list of updates included in the patch yesterday evening. Cheers, Ian P.

Hi, The best place to check for the latest version is right here on this forum, just a bit further up: http://forum.simflight.com/topic/66139-updated-modules/ The current full installer is version 4.938b, so if you can check that's the one you have then you're sorted! :) Cheers, Ian P.

As Peter pointed out a few posts ago... This thread is almost 11 years old. ;) Ian P.

It might also be worth, if you are going to do that, looking at Burkhard's MyTrafficX forum and seeing whether you can find the discussion of case-sensitivity problems there. It was quite a while ago, now, so may be difficult to find though. The Hobbs scenery was done by Larry "Tako Kichi" Green, so it might be worth dropping him a message, maybe via the A2A forums or SOH if you frequent there, to let him know about this and see if he can make them match 'at source' and see if that fixes the problem. If you'd rather not, I will. Cheers, Ian P.

There are actually a number of case sensitivity issues in FSX - Burkhard has had to deal with a fair few within the MyTrafficX folder structure and P3D is even less tolerant. It sounds almost like whatever DTG have done is the same as L-M did with P3D. Whose libraries are causing the problems? Unfortunately there are a large number of WW2 scenery object libraries and only one of them is mine to be able to fix that one at source... I will keep an eye on it with mine, though, so thanks for the warning. Ian P.

Andy, Log into your simMarket account and the registration information will be there. Cheers, Ian P.

They've fixed some of the code that caused OOMs - FSX:SE releases memory after use that "FSX DVD" does not - but ultimately yes, it's the same FSX with most of the same problems. Having said that, so is P3D, which is also still only a 32-bit application and thus very memory-limited for the amount of load we put on it with complex add-ons and high-resolution textures. However, P3D is no longer the only game in town. Dovetail are only distributing FSX. They are also developing their own sim in the "MSFS" line - supposedly for release this year, although that seems a very short development cycle to me. Interesting times lie ahead! Ian P.

When will people stop referring to Pete Dowson incorrectly as Pete Dawson? ;) The simple answer is that each iteration of FSUIPC introduces fixes and updates, so supporting old versions is impossible. Also, this is nothing like a car, it's a piece of software and, if a piece of software is updated, there's a reason for it. Usually error correction, security fixes and/or including support for new functions. If you don't have to pay again, you should always run the latest version of any software. The first thing any software support person will tell you to do is run the latest patch and that's all you're being asked to do here. If you really want a car analogy, we have a very odd coloured Ford C-MAX as our primary family car. It had a problem with the door locks... The fix for the problem was to update the software in the car's VCU (Vehicle Control Unit - the main computer, basically) to the latest version. Just in case anyone thinks updating PC software is a pain, try updating the OS on a car!!! Seriously, you lose nothing by doing it and gain all the latest updates, so it should always be the first thing you try. I would strongly suggest that you do so. Cheers, Ian P.

The requirement to run applications as administrator is caused by Microsoft preventing users (including supposed "system administrators!" from being able to install things to specific places, because of constant accusations of it being too easy to infect MS operating systems with malware. It isn't software developers' fault that the files must be in those locations in order to work - it's Microsoft's decision and slightly inept response to a problem of their own creation. You can turn a lot, but not all, of the supposed security functions off, but not all, so the requirement to 'Run as Administrator' isn't going anywhere any time soon! Ian P. (Supporting Windows since Windows 3 and still shaking his head in disbelief at most of the decisions being made with each version...)

Thanks once more for your efforts Pete. Have a good Christmas, sir! Ian P.

There are a number of changes with FSX:SE compared to "legacy" FSX - registry keys are different, install locations are different, support file (AppData and My Dcocuments) locations are different. A number of add-ons will have real problems with this, even before you get into version numbers and Simconnect versions! Obviously Pete will have to comment specifically regarding FSUIPC, but it will be a not insignificant change for developers to support FSX:SE and it may be a while, if ever, before a lot of add-ons are supported on it. Ian P.

At the top of this forum, where it says "Download links". http://forum.simflight.com/topic/66139-updated-modules/ Ian P.

Hi, Simply place the .dll file in your Flight Simulator X/modules folder, replacing the one currently there. Cheers, Ian P.

...and make sure a P3D update will be released at the same time! ;) Ian P.

If you go to the "More reply options" page, you'll see a button immediately below the :) smiley, marked "<>". It's used to post code. You can simply copy and paste the text information into the section bound by the tags that the code button creates. Ian P. Forum admin.

Out of interest, what happens if, rather than exiting the sim directly, you return to the Create a Flight screen, then wait a while and exit from there. I have some add-ons which take a while to unload after ending a flight and, if you exit before the sim has unloaded all the code/textures/whatever it's doing in the background, then it crashes on exit. If, however, I exit to the "Create a Flight" screen, leave it for a couple of minutes and then close the sim down, it exits properly. Might be worth trying? I don't know how you exit the sim at present. Cheers, Ian P.

Pete, Many turbine helicopters use a similar system to turboprops, with three detents for ICO, idle and full power. FS doesn't support this, though, so if someone has put it into a helicopter, then it will be coded into the model - I can think of quite a large number of models that do this. I think what Dave will need is probably LVars for the power levers, or something like that? As it's a FS9 model, I don't know how you'd access panel/model code or even whether it's possible. If they can be accessed, it does look like this might be a job for LUA? Cheers, Ian P.

Hi Dave, Unfortunately Pete is away at the moment, so you'll have to put up with the forum admin instead of FSUIPC's developer trying to help for the moment... The key will work if it did before. They don't time out and work with all subversions of an FSUIPC version (i.e. FSUIPC3 keys will work with 3.anything) - the only reasons they would stop working is if ALL the information is not entered EXACTLY as it was when you purchased or if they are shared and thus manually blocked within the DLL by Pete. The reason I capitalise bits of that is the most common mistake when registering old keys is people who have changed e-mail address since and try to enter their new address. You need to use your old one. The other common mistakes are typographical. Can I suggest going back to your order page at simMarket and copying and pasting the registration information directly from there into the installer window? Post again and let us know how you get on with that, please? Cheers, Ian P.

Jim, That was probably Microsoft's fault. They set FSX (and ESP) up so that any new controller device, when attached, was given a set of default commands which equated to what they thought worked best on a Microsoft Sidewinder joystick. Needless to say, the same settings were utterly useless on rudder pedals, or throttle quads, for example! Unless FSX specifically recognises a device - which it usually doesn't - then is assigns everything these default buttons and axis settings, which you then have to clear manually before setting up more sensible ones. Cheers, Ian P.