Andydigital

You need to download the FSUIPC SDK separately if you haven't do so already. There are some links at the page below.

Make sure your viewpoint is not inside the seat geometry behind where your head is in the game. If you are inside geometry then you can't click anything in the VC and thus it would look like mouse macros weren't working.

You can't its a modifier key which means it can only be used in combination with another key.

The TAB key is classed as another modifier like Shift, CTRL or ALT which is a lot more useful than being just a key as it gives you another set of keys to assign to. I just wish other games used it as a modifier too.

Have you calibrated your controls in the Q400 Control panel, the app is called MJC84 Control Panel. Obviously you can only calibrate when FSX is running. Start> All Programs> Majestic Software> MJC8Q400> "MJC84 Control Panel"

If you have created mouse macros with the previous version of the Majestic Q400 they will stop working when the gauge dll is updated in a new version, this is what happened in the update from 1.005 to 1.006. This is the main draw back of using mouse macros and its likely to happen again when they release another update. This is probably why you thought your profile wasn't working.

Edit the fsuipc4.ini calibration data for the axis in question directly in notepad so that the extremes of the elevator axis have a number that your device cannot possibly reach, such as +/-20000, I think that should work. Pete will surely correct me if I am wrong and this isn't possible with FSUIPC.

How much did you pay for FSUIPC4 and where from?

It doesn't apply to software, only hardware. All Tosh will tell you is that if you return the Laptop to its manufacturer supplied state via a restore disk everything will function correctly. If it doesn't work then you may be able to get something done, but a manufacturer of hardware does not have to guarantee compatibility with third party software or hardware for that matter.

I made that video a long long time ago with FS2004 not FSX, when you use the FSUIPC GUI with FSX the FSX window in the background turns black while the FSUIPC interface is on screen, it doesn't do that with FS2004. It makes no difference though, once you have pressed the button in FSUIPC that says "create mouse macro" another box appears where you type the name of the macro set you are going to create or amend, that is where my video starts, you can then go back to FSX and create the macros as shown in the video. When you are finished return to the same page in FSUIPC and the create macro button will now be called "End Macro Making" or something to that effect, press that button and your macro is finally saved to disk. Finally you assign those mouse macros you have just created to your joystick buttons or keys, via the relevant section/tab of the FSUIPC GUI.

You need to fix the registry because you moved FS. Forunately there is a free app available at the Flight1 free file library that will fix it for you via a little program "registry repair tool", you simply point this program to the new location of FS and it will automatically fix the registry for you. http://www.flight1.c...sp?page=library

Pete has gone away on holiday for the weekend, so I will reply. No it only works with one keyboard, if you have two plugged in it hasn't got a clue which one is which, but they both will action the commands assigned to them, you just cant assign a different function per keyboard/key. Yes this works perfectly and if you are just starting out with a fresh fsuipc.ini without any existing assignments then its completely transparent to you and just works. As for your question about keys being assigned in FSUIPC and FSX, well it is always best to remove ANY dual assignments and that includes key assignments, if you don't then unexpected things can happen, or at least both functions will be actioned whatever they maybe.

That means that FSX is still running even though it may appear like its closed, open the program manager and kill FSX.exe, now try the FSUIPC installer again. You likely didn't enter the registration details exactly as you did when you bought FSUIPC. Your name, the FSUIPC key and your email address must be exactly the same as shown in the store where you bought FSUIPC from and its the email address you used when you bought FSUIPC, not whatever your email address might be now. Login to Simmarket and look at your order history, you should see the registration details there, copy them EXACTLY. If it still doesn't work then it's possible that your PC date and time is incorrect. If the date on your PC is set to a date before you purchased FSUIPC the registration details will not work, as it will appear invalid.

http://forum.simflig...irst-installed/ I believe there are also instructions included with the installer that tells you how to use the FSUIPC-loader.dll to try and help people get around this problem.

Start by downloading it from the page below, then read the included instructions. http://forum.simflig...pdated-modules/

As far as I understand it there is only one trans alt in FS and that is the US standard 18000 feet and that covers the whole of the FS world. Any add-on ATC program that does support real world trans alts has them included in their own databases, you won't find them in any of the files that MakeRwys.exe outputs.

I must admit I thought Alan was using a client PC as well when I first read his post. What he actually meant was that he has bought a new PC that is dedicated to FS only and he wants to copy the assignments across to this new PC from his old PC. The old PC has now been relegated to WideFS duties, he isn't doing any joystick work on the client machine at all it would appear.

You will already have the complete list on your PC already if you have FSUIPC installed, look in the folder; ...Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC Documents for a file called List of FSX Controls.pdf

It does indeed sound strange and it doesn't do that on my panel. If you had explained the situation more clearly at the VRi forum months ago I probably wouldn't have sent you elsewhere for assistance. The way it was explained to me back then had me convinced 100% it was a assignment problem. Best thing to do is email tech support and explain to them in the same sort of detail that one particular button on you TT panel is intermittently registering a different button id number when pressed. Can you confirm it does the same thing in the Windows joystick calibration/settings app?

To me that sounds like you have some messed up assignments, probably two different ones assigned to the same switch. Maybe one assigned in FSX directly via its control assignment system and another assigned in FSUIPC. Either that or you have something assigned to the press function and something else assigned to the release function in FSUIPC.

Pots are no good for heading selection dials or anything similar, you need rotary encoders with fast and slow turn detection. Imagine even if you could get a pot that turned 360 degrees, it useless, think of the situation where you are on a heading of 350 degrees and you want to make a right turn to a heading of 10 degrees but the pot will only turn right as far as 360 before hitting its end stop. That means you have to turn the pot left 350 degrees instead and the aircraft will turn left too. Pots simply are not suitable.

I've just noticed you are using a 32bit OS as well, you are probably getting a lot of crashes due to the OS just running out of memory, there are really very few reasons not to be using a 64bit OS these days.

Autosaves are not the same thing as a previous flight save. The previous flight save is a flight that was automatically saved at the time you last closed the sim down properly. As far as I know you cannot turn off the previous flight save, it's not an issue though as it always overwrites the previous save so it wont waste any space or anything like that.

Press CTRL SHIFT Z then let go of all three keys and then if you see Null press the Z again on its own and it will work fine then. I've no idea why NULL comes up once in a blue moon but doing the above with the none modifier key seems to bypass the issue and still register the correct total number of keys pressed.

Temporarily remove the registration for FSUIPC by removing the FSUIPC key file from the modules folder, you can put it back when you have finished testing. If you still get your problems now then you know it's not FSUIPC causing the issue because the unregistered version of FSUIPC has no user configurable weather functions in it as far as I can remember.