Andydigital

No its telling you not to rename the file to something like OLDfsuipc4.dll or 4505fsuipc4.dll as these could still actually load into the simulator. You could rename the file to fsuipc4.dll.4505 to save as a back-up and this would not load into FS, you just have to make sure the filename doesn't end in .dll I have many back-ups renamed similar to the last example and have no problems.

The other thing to check then is to make sure your system clock is set to the correct date, if the date is wrong at its set at a date before the key was created then it wont work.

You have to log into your simmarket account and click on the my products/downloads link. A list of your purchases should appear including FSUIPC as the latest purchase. If you click on this product you should now be able to see your key. Simmarket never email product keys to the customer only order numbers/confirmation etc.

I was going bald at 18 and it was more or less all gone by 25, hence my avatar :lol: saying that though at 38 now I dont have to waste money on a barber 8)

Not all aircraft have taxi lights modelled in them, its as simple or lazy as that I'm afraid. The deafult FSX 737 is one prime example of this, there is a switch which moves with mouse clicks and keyboard short cuts if I remember correctly but no working light modelled on the exterior.

They didn't say it was or might be due to FSUIPC at all, they told you that you could probably fix it by using the registered version of FSUIPC's weather smoothing options :roll: :D

Morning Pete, I've been testing this during the last week (not as much as I'd like) and I can report that there are no adverse effects as far as I can see. I wouldn't be so bold as to say you should make this the default mode though, having it as a option would be more prudent I think especially until a such time as its been tested by a wider audience. The only thing I found a little odd was that variance seems to be different now, particularly wind heading variance. I only really had one flight where it seemed odd, but the variance seemed slow and too regular, although the METAR did specify variable winds so it was correct but just a little too predictable. Other than that I have nothing else to report, other than it does what I need well. Would I be right in thinking that this facility is still in the latest interim i.e. 4.505, I've not downloaded it yet because I was unsure if it was still in there. Thanks again for the changes.

Are you sure the name of the aircraft hasn't changed with the update?

Just a quick note to say that initial testing of a 90 minute flight in the Md-11 was very encouraging, but I wont be foolish enough to say you have sussed it out just yet. I've learnt my lesson from past experiences of saying something works perfectly only for it to turn around and slap me in the face 5 minutes after I've made a post on a forum. It does look very promising so far though, I even paused for 7 minutes while taking a phone call and all was well on my return to flight.

OK Pete thanks a lot for this I will certainly test it as much as I can over the next week, today is going to probably be out of the question though as I have a few beta's for various different FS developers to work through that were released in the last 24 hours. Thanks again.

Sorry Pete I failed to mention that I'm on the Beta test team for HIFI and so should have said that I use ASA as well. Believe me when I say and I'm sure you are probably aware that Damian and the guys are working really hard on ASA with PMDG assistance too to try and get the problems sorted out regarding wind shifts etc. Recently their understanding of what is causing the hunting/swaying problems in PMDG aircraft has shifted somewhat (excuse the pun). It seems to be caused by the way FSX depicts turbulence more than anything else. While HIFI may be able to tame the effects to a greater degree with ASA, there are other people who don't have ASA or ASX and they are still having problems with the default weather engine which requires your system to be used. I found that 2 seconds per degree or knot with turbulence suppressed/ticked in FSUIPC works pretty much perfectly for me in the MD-11 and LD767. I certainly don't need anywhere near 8 seconds Tom, which as far a I understand it was recommended by someone on PMDG beta team certainly not officially by PMDG themselves. I do really wish I didn't have to go into the menu's or have to pause the flight, but needs must at times like I mentioned already. Thanks for give this some consideration at some point in the future Peter it is very much appreciated by all I'm sure.

Can you not stop your time keeping when you see the user enter a menu. I sorry if this is a really stupid comment/question but I'm no programmer in any sense of the word, but I imagine from your response that it is a major thing I am asking for, and the last thing I want to do is create any more headaches for you Pete :lol: The reason its become an issue is because the new autopilot systems in the likes of the PMDG MD-11 and Level-D 767 get very messed up when the winds or wind speeds shift suddenly which most of the time result in a stall or overspeed condition. As you probably know far better than me winds can very often be as much as 180 degrees out to what they were 1 second ago in FSX and within a few seconds it can be back to where it was again, by which time the complex custom autopilot has tried to correct for the change only for it to be completely wrong again. The systems you have in place now work extremely well as long as you don't need to go into a menu and change any settings, which for some people is unavoidable I'm sure. For instance I tend to have to go and reduce my scenery density or autogen sliders at times when getting to a heavily built up area because my frame rates drop too much. Maybe I need to go into FSUIPC itself to tweak something or add a new button assignment or some such option. Needless to say there are many reasons to have to go into a menu unfortunately. I've also noticed that it can happen if you have to pause the flight for more than a few seconds, its a shame real life get in the way but us sim pilots are lucky we have the pause option when we are on short final and the door bell rings :roll: As I've mentioned previously if this is a major undertaking for you Pete than please don't think any more about it, you have done more than enough to warrant the asking price of FSUIPC many times over.

Hi Pete, further to what you have said above, would it at all be possible to add an option to have FSUIPC not release control of the weather smoothing features during menu transitions? It would actually help greatly with the aircraft that so much rely on your excellent weather taming facilities.

FSUIPC doesn't need anything changing as it is internal to FSX. You have to make sure everything else that connects to FSX in some way is set to "run as administrator" i.e. REX, VAFS and of course FSX itself.

I'm not sure what OS you are using or whether this will actually help in your case, but if you are using Vista then make sure all programs have the option "run as administrator" set in their properties. If you have a mix and match of some programs having admin rights and some not then Vista wont let them communicate with one another. A program without admin rights cannot interact with a program that does, and vice versa.

Have you tried "Heliforce" by Simon Robbins, I've not used it for a while but from what I remember it was very good and maybe what you are looking for.

It was deleting the files I mentioned above up to Alsomanage4 but I found out that since I had had written the original entries in FSUIPC4.ini a few weeks ago there were some new files it hadn't deleted, and I had to add some new entries at 5,6, and 7. Otherwise yes its doing what it should do on my system. P.s. you dont need to provide the full path as long as the files are within the PMDG folder that is within the main FSX folder. It may be worth just copying what I posted anyway, it wont do any harm.

For me its looks like this, some saves from the MD11 have less entries. 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

How about just Tab and the key you want?

Just to get around the problem for now (as it may be difficult for Pete to track down this problem before he goes on his Christmas break) You can also use Shift and Tab instead to gain a load of new keys to use, this is what I did before changing my mind and editing the panel.cfg Hope this helps for now.

I would first try moving the FSUIPC4.ini file to another location for now and let FSUIPC build another one the next time it is run. Reinstalling everything is a rather drastic step to take just yet.

Does the OP have "FS Flight Keeper" installed? as I had the same issue a few weeks ago when assigning a keyboard shortcut facility in FSFK to the ACARS gauge and then using FSUIPC to turn it into a joystick button press. I ended up just editing the panel.cfg instead and used a normal panel call button combo i.e. shift 3 etc. I've tried replicating the OP's problem with the latest interim build of FSUIPC4 and cant make it happen.

1. No you can do it on the ground. 2. You can do if you have assigned all axis direct in FSUIPC, but there is no need to do this. Leave the assignments set up in FSX and just calibrate them in FSUIPC while you are still learning FSUIPC as this is the simplest option. 3. An axis can only be assigned either in FSUIPC or FSX, never do both as they just fight against one another and cause problems. Also its worth checking once in a while that FSX hasn't automatically added the axis back in FSX, as it does this sometimes when you unplug a joystick then plug it back in again.

Engine speed is set with the FS prop pitch axis in helicopters, so just assign it to an axis of your choice on your Quadrant. The throttle axis in FS is tied to the collective function automatically as you probably already know.

Sorry I missed the fact that you were using FS9.