Andydigital

Add this to the Autosave section of the FSUIPC.ini, it should fix it. AlsoManage1=PMDG\MD11\PanelState\*.FLT.0.rte AlsoManage2=PMDG\MD11\PanelState\*.FLT.0.slv.rte AlsoManage3=PMDG\MD11\PanelState\*.FLT.1.rte AlsoManage4=PMDG\MD11\PanelState\*.FLT.sav AlsoManage5=PMDG\MD11\PanelState\*.FLT.2.rte AlsoManage6=PMDG\MD11\PanelState\*.FLT.2.slv.rte AlsoManage7=PMDG\MD11\PanelState\*.FLT.3.rte

The software that was mentioned to you over at the AVSIM forums would be perfect for what you want to do as well, it looks like a very interesting piece of software, you could have many keyboards plugged in and each keyboard can have different commands set for each key or key combination. It was initially made for cockpit builders, I think, who wanted to make cheap panels with keyboard emulator cards, but it will work perfectly for you too. http://forums1.avsim.net/index.php?showtopic=253276 http://hidmacros.medek.info/whatisit.php

Actually I have the Saitek drivers and the SST software installed and have no problems at all, although I don't actually use the SST software for assigning functions. I've only used the X52 Pro with FS9, FSX and DCS Black Shark so far and its all worked fantastically especially in Black Shark.

Glad you got it working to your satisfaction, I bought an X52 Pro at the weekend because I wanted something a little more accurate than my Cyborg Evo Force, it was getting a bit slack around the centre (a bit like me ;)), and wow its really is a nice stick. I have opened it up already too because I didn't like the detent for the afterburner, it was way too stiff to overcome, the idle detent was fine though, but removing the AB detent meant that the Idle detent must go too unfortunately. Otherwise I am very happy indeed with X52 Pro and thoroughly recommend it, I got it in a sale for 30% off so it was a relative bargain too.

Take a look at the page below and pay close attention to 'hotkeyselect', you can then assign buttons in FSUIPC to the functions View_camera_select_n, n = a number from 1 to 10 You will find that you can assign keys/buttons to these functions within FSX controls itself as well, but not all of them have keys assigned by default. http://msdn.microsoft.com/en-us/library/cc526984.aspx The page below is full of useful information how to add new camera views to the VC of FSX aircraft. http://www.fsdeveloper.com/wiki/index.peras_views Also try playing with the keys F9, F10, F11 and F12, you will find these are already set to some of the views that you want I think.

No worries Jim, I did it myself in the past and I haven't got that excuse yet :lol:

You are pressing SET first before you press the key aren't you? I know it sounds like a stupid question but I'm sure you wouldn't be the first person to have missed this step.

Sounds to me like you have just upgraded to FSX SP2, many old odd items like that dont work correctly in FSX SP2 and require the textures be made compatible, or possibly you enabled "DX10 preview" mode and the same situation can arise with some add-ons.

Make sure that any software (exe) that comes with the throttle is run with the option 'run as administrator' if your operating system is Windows Vista, this must be the case for all programs that are connecting to FSX, including FSX itself and FDC etc. All you have to do is right click on the shortcut (icon) to the programs and select the 'run as administrator' option from there. If you are not using Vista or Windows 7 then this isn't necessary. It may not be this that's causing an issue but it is worth a try.

There is a chance it could be axis conflict (double assignment) in another device that has the jitter and not the PFC itself, especially if the other device is assigned in the sim itself rather than through FSUIPC.

FS9 will run far better on that setup, but FSX would run better if you invest in a good after market cooler for the processor and overclock it to at least 3Ghz and get the best fastest memory suitable for your motherboard that you can. My Q6700 is overclocked to only 3.22Ghz so its not pushing it too much and risking shortening its life. The memory I have is 2X2Gb OCZ Reaper 1000Mhz its actually clocked to 996Mhz 1 to 1 (IIRC), as Pete says memory performance and raw processor speed makes the biggest difference to FSX. Now blurries, first and foremost make sure FSX is not on the same hard drive as the OS, you should keep FSX on its own exclusive drive including most other add-ons for it. If you have any large photo scenery packages they should also be on a different drive to FSX, also try to keep them off the OS drive if possible. A 3 drive setup is the optimum in my opinion, you can get 500Gb drives really cheaply now and the speed of them is usually pretty good because of the high density, my drives all average about 80-90 Mb/sec read speed and I very very rarely see the blurries even at 1920 X 1200 on my 24" monitor. I found a little tweak to reduce the effect of the distant blurries in spot view by zooming the camera out to 0.5 and then moving the camera closer to the aircraft to fill the frame again, it works very well at tricking you into not seeing the distant blur which you can reduce even further by increasing the LOD_RADIUS= value in the FSX.cfg. The default maximum with the in game slider is 4.5, try increasing it to 6.5 but you may find performance suffers even more and the blurries will get worse if you haven't put in place the other hardware optimisations mentioned at the beginning of my post. Finally also make sure you have the line WideViewAspect=True in the FSX.cfg this will help set the default zoom levels correctly. Also keep the hard drives de-fragmented, if you have 3 drives like I mention above then the FSX and scenery drives will hardly ever get fragmented in the first place.

Does FSUIPC see the actual buttons being pressed on the GF MCP or do you have to assign keyboard button presses in FSUIPC and then use software supplied by GF to assign these keyboard definitions to the buttons and dials on the MCP etc? If you have to use GF software with key definitions, do the keyboard short cuts you have created actually work the function you have assigned them?

The problem in the MD11 was that the OP was trying to assign macros in the VC which isn't possible, you have to use a 2D panel to get it to work. Sorry I cant help you with this aircraft though as I don't own it.

Other than staying away from the refuelling stands and actually editing the AFCADS to remove the fuel stands, no there isn't I'm afraid.

Visibility settings were removed in the default settings in FSUIPC 4 because of problems, the thread found below explains more. viewtopic.php?f=54&t=73351

Are these paddles proportional (an Axis) or digital (buttons), I ask because 99% of paddles on steering wheel peripherals are digital.

Damian over at Hifi said to me that he thought he could find out via simconnect if the aircraft was in a cloud or not, as I suggested to him that he could possibly use it as a trigger to update the weather engine while in a cloud to make the cloud pop issues less obvious, he may have been wrong though.

I always use the latest interim versions as posted at the top of this forum.

The MD-11 works fine for me in FSX and FS9 with the registered version of FSUIPC.

Some hardware especially from Saitek is self calibrating and you have to move all axes through their full range of movement for this calibration to take place. You have to do this every time you reboot the PC, or at least I have to with my Saitek Cyborg Evo Force joystick, my Saitek rudder pedals don't need to go through this routine though.

Search the FSUIPC.ini file for FSHOTSFX and remove the line where it is mentioned.

Gerard why would you be wanting to make macro's in the VC, that makes no sense whatsoever. All the functions I made for the MD11 macros for VRi were made on 2D panels, trying to make them in the VC is just plane difficult and not required. There is only one switch in the VC that is not in the 2D panels and that is the switch above and behind your head for turning off the 3D animated switches and dials etc.

Where did you download it from? If it was from http://www.schiratti.com/dowson then its a false positive, ESET seems to be having problems lately, they are reporting all of Flight1's wrappers as Trojan's which clearly isn't the case.

Sorry as I said I don't own the plane and Pete is away till the 24th so I thought I would at least answer the question I did know the answer to, and at the same time give you my insight into the other matter. Sorry I could not help further.

You have to buy a registration key from Simmarket.com then you press the register button in FSUIPC and enter your registration details and key. Make sure you get the correct version as there is one for FS9 and one for FSX and the keys are not interchangeable between versions. You can have many different setups of levers for 100's of different planes if you wish, or you can have just a few different profiles which can be used with the same many aircraft if you like, its really up to you. I don't have the above planes in question so I cant answer your question with complete authority but it would find it hard to believe that FSUIPC cant do what you require, if I am wrong though I'm sure someone else will correct me. Just to avoid any confusion though you don't need the mouse macro facility to assign a lever in FSUIPC so your post wasn't really relevant to this thread (which is in appreciation of Peters work on the mouse macro facility) other than it was about the same aircraft.