Andydigital

I'm not even sure that works with the extended, that was for the original Airbus from years ago and the display facilities in LINDA are specifically for VRinsight hardware, they are no use to anyone else. I suppose you could use them to research building your own scripts though.

You will need to contact Simmarket via a support ticket and ask them to re-issue you a new key for WideFS using the exact same name as the FSUIPC key. The email address can be different as far as I can remember but the name has to be identical.

FSX will and does use 4Gb of memory, if you have SP1 or later installed then FSX is already Large Address Aware. If you use Windows Update then you should have had that LAA fix Kosta is on about years ago.

If you have a Razer Nostromo Keypad device make sure you are using at least version 4.91 of FSUIPC otherwise FSUIPC will get stuck in a loop causing FS to look like its hung.

No you have to make sure the hardware matches what state the software/aircraft was last saved in, there isn't a way to do it automatically because of the way Direct X works. This isn't the Linda support forum either, you would be better asking in the Linda support forum at AVSIM.

Make sure you save your flight just before you exit the sim and tick the box that says "make this the default flight". You will also need to make sure that you save a personalised panel state in the NGX with the switches in the position that you want them in and make that the default state that is loaded at startup. Note that you may find that not every switch in the NGX can be saved in your own preferred state.

I'll give that a try then Pete this is a very virgin install on a fast SSD so it may be closing too fast as you suspect. Thanks for the quick reply.

Hi Pete, I've been using the save previous flight facility for years with FS9 and FSX, during the last week or so I've been building a new Haswell based FS PC and I've been reinstalling stuff. I've noticed though that the Previous Flight facility is no longer working. I checked the manual and I see there is now a general section ini entry for this facility called SavePreviousFlight=Yes to enable it. I can't remember whether I ever had that line in my ini in the past and my old ini from my last PC didn't have that line in it, but previous flight did still save OK on every exit of the sim. Now for some unknown reason it no longer works with or without this entry. I'm using 4.91 and Autosave is working OK. Any ideas?

I misunderstood what you meant, if the numbers keys across the top of the keyboard work for other features even when using the CS727 then its possible you are not using the keys properly then. Try pressing and releasing Shift + P together then wait a second and finally press 1 or 2 to go left or right. If you try pressing all three keys at once it won't normally work, or at least has been the case in my experience.

Its very simple really, CS are trapping the number keys for their own use with their aircraft, there is nothing FSUIPC can do to restore proper functionality of those keys. The number keys across the top of the keyboard should NEVER be used by any aircraft for anything, as FSX uses them extensively to manage systems like selecting ATC, engines,doors, plus a myriad of other systems.

Perhaps this is a suitable thread to move to the FAQ area of Pete's forum.

As far as I remember the names have to be exactly the same for both FSUIPC and WideFS keys, so you will need to contact Simmarket and ask them if they will reissue you a WideFS key with the matching account details that were used for the FSUIPC registration.

You shouldn't be using the number keys across the top of your keyboard though, they are used by a multitude of FSX systems depending on what system you activated with a key modifier first i.e. when the ATC window is open and in focus the number keys correspond to the numbered options listed in the ATC window. When you press Shift + E if you then press number 3 at the top of the keyboard door number 3 will open/close. There are a multitude of other combinations too for many other systems.

I believe someone already did this via Lua Scripts and FSUIPC, I remember reading about it on the AVSIM forums, I even remember the guys username. Try searching there for the username "Dazz" and the term "Radio", I think that should find you what you are looking for. EDIT; Never mind found it for you, I've no idea whether it works or not as I have a hardware radio panel so I don't need this facility. http://forum.avsim.net/topic/336131-tuning-the-fsx-radios-with-the-numpad-of-your-keyboard/

I've not used the Saitek X52-Pro for over 2 years (I have a TM Warthog now) so its hard to remember what can and cannot be programmed on the Saitek Throttle part of the unit, I do remember that there were some buttons or rollers that could NOT be programmed, no matter what, the roller wheels on the throttle section are the most likely thing not to be programmable though as they are supposed to control the display on the throttle section.

Until you remove the god awful SST software you won't be able to do anything useful with FSUIPC, you should only be using one or the other solution, never both. The SST software is also likely putting the SaiDxxxx.pro files back moments after you deleted them.

Save a flight (in an aircraft that supports saves) at a time that is approximately 15 minutes previous to the point where you expect a crash, perhaps in a default aircraft, it may help alleviate the boredom a little, lol. Make sure you reboot the PC after disabling the scenery area in question as FS still caches some scenery even though its been disabled in the mean time, even after closing FSX believe it or not, rebooting is the only way to clear it for certain.

Remove the photoscenery and redo the flight and I bet you don't get the crash anymore. I have had similar experiences over the last 7 or 8 years as I am a big fan of photo scenery products (or I was at least), I also used to get the same errors and other crashes from time to time. Since removing all photo scenery products I very rarely get any crashes of any kind now. By the way FSUIPC does not stop all G3D.dll crashes, it only fixes a specific kind of crash that happens to be the most common g3d crash, but it won't stop all of them, this is explained in the documentation. If you still get crashes with the photo scenery removed then it is probably some other scenery you are flying near that is causing a crash, such as an addon airport or maybe even a mesh product, try disabling them systematically and retest until you no longer get a crash, you should be able to find the culprit like this.

Now you have explained it a little more I think its more likely that you have a corrupt default saved flight that is somehow stopping the systems working properly. Try deleting the default flight by opening the fsx.cfg and deleting everything after the equals sign in the line that starts with "Situation=" Another potential (haha pun not intended, electricians will get it) thing to look for is a line in the aircraft.cfg for the aircraft you are having a problem with, look for a line that reads something like this, the wording may not be perfect but its close to this; ElectricsAlwaysAvailable=1 Try changing the number to 0 I'm out of ideas if none of that works.

Do you perhaps have a dual assignment to the master battery switch by mistake, one assignment turns the battery off then the other instantly turns it back on again. Maybe one is assigned in FSX itself and the other in FSUIPC.

1. Yes you can edit the Macro files with Notepad, I change the names too from time to time as some add-ons cause some keys to not function because they trap them for exclusive use by that add-on. 2. I suspect the view is changing because you are using EZDok Camera, if you were using the default view system only then those keys would not do anything when you were naming your macro as FSUIPC traps them and stops FSX from detecting them when you are entering a name. FSUIPC isn't able to stop EZDok from seeing those keys being pressed as it is likely capturing them externally to the sim and so before FSUIPC gets a chance to trap them.

I use both of those without issue.

PMDG do not provide for door open indication in the SDK, they said last year that after the 777 is released they will be updating the NGX SDK and features like this were promised, I wont be holding my breathe though.

Hi Pete, Yes the VRinsight software had to install a gauge into the Airbus to enable connection to Aerosoft's SDK for this aircraft. When Aerosoft recently updated the aircraft to version 1.10 they added another gauge of their own too and this clashed with the version than VRi were installing and VRi installer was overwriting this addition. I should be fixed in future installer updates from VRi. I do have a temp fix on the Aerosoft forum and at VRi's forum which I wrote for the VRi Panel installer which makes it compatible with the 1.10 update. vrinsight.com/phpBB3_en/viewtopic.php?f=13&p=6844 Once Chris reads the FSUIPC manual and figures out how to enable access to the buttons on the MCP2A Airbus panel through FSUIPC, then yes of course he will be able to reassign the buttons. Whether Aerosoft supply access to those autobrake facilities or not I am not sure. Chris may be better off looking at LINDA instead and using the facilities available there, as I am sure there is an Airbus X extended profile available for it that probably allows access to the Auto brakes via Lua scripts, L:Vars and such.

There is entry right near the beginning of the dll.xml that says <Launch.ManualLoad>False</Launch.ManualLoad> If that is set to "True" instead of "False" then you have to manually start everything listed in the dll.xml (when it's called upon), this is the most likely explanation as for why this user is asked to start FSUIPC and any other associated module every session.