martinlest2

Yes, let me know., I don't fly at night very much as so many aircraft (not all, of course) and no small number of airports have pretty poor night lighting, and I can't see to well where I am taxiing! Besides, I prefer to watch the scenery outside :-)

Hate to look a gift horse in the mouth but frankly, if I have to go and look up the airline ICAO code I might as well look up the callsign directly. OK, I know British Airways is BAW; but knowing that, it's very likely that I also know the callsign is 'Speedbird', to cite just one example. Who knows all the ICAO codes off by heart for the myriad of less well-known airlines though? If you do, this is the tool for you. If it worked with the name of the airline it would be SO much more useful...

Well, I flew round and round the airport for about 45 minutes at 1000' in a Cessna, landed again, took off, toured Warsaw City - all in low, dark cloud and freezing sleet, courtesy of AS6.5: very realistic (both airport and weather!) - I had no crash or any problems at all. Maybe I was lucky this time. I have certainly had crashes here in the past, but it's very unpredictable. The only thing I removed was the static aircraft bgl file ("High quality static aircraft" is always a contradiction in terms, IMHO), but I doubt that is significant. Are you still having problems ? How often, and how soon after FS9 loads there, if so?

I'll do a bit of testing at EPWA soon and post back any findings Harald.. Martin

Yes, perhaps you are right, assuming that they are not liveries that came with the PMDG original. On the other hand, the 'protocol' for freeware seems to be that it's generally OK so long as the original painter gets the credit. I probably have the original downloads somewhere on an external hard drive, I may have a look when I have the time, and inclination... Depends whether the O/P ever comes back to this thread of course

I have both these liveries for my FS9 PMDG 747-400F installed. What are the copyright issues here though? I am only willing to supply them if it is completely legal and OK with PMDG. I didn't repaint them (as far as I recall - I do do quite a lot of repaints, but don't think I did these! Let's assume not for this purpose). Martin

Sorry if this has already been answered (in which case I missed it as I scanned through), but are people having the crash who do not have Warsaw City Scenery installed as well? I thought that that was the issue. Maybe not. I too had no problems with the freeware version, but (having just come back from 'real world' Krakow - and I think Drzewiecki Design had a sale on) I bought both EPKK and EPWA as well as Warsaw City Scenery to fly 'nostalgia' trips (I didn't actually visit Warsaw, but no matter!). Just updated to v.1.2 of EPWA: No crashes, but I only flew one flight. I need to try a few flights and see what happens. Difficult to follow the posts over at the Drzewiecki forum if you don't speak Polish (laborious putting everything into Google Language Tools. I think Stanislaw over there is really frustrated, upset even, about this, people complaining and still unable to nail down the culprit as he is. Poor guy!

Yes, I do see a big difference between 60fps (ultra-smooth panning) and 25fps (less so). That wouldn't be a deal-breaker, but as I say, I used to run FS9 at a much lower frame rate (for years) - I think 24 was the 'magic' number, but I have always had these short periods of stuttering whatever the fps limit I set, so sacrificing the nice smooth panning seems a bit pointless, though your comment that the brain would adjust may well be true. But thanks anyway for the suggestion

So no one has any fix to the brakes locking up on landing? If you forget to 'tap' the brakes soon after touchdown (easily done, as no other a/c in FS9/FSX needs this) it always happens. Too late much after 80KIAS, the brakes will not release I am only using FS9 menu keyboard shortcuts for brakes, not FSUIPC, and I don't use pedals. Someone suggested deleting the FSUIPC.ini file - which I doubted would change anything as I don't use FSUIPC for the MD-11 at all (and sure enough, it didn't). Thank you.

OK, here's a video of what's happening to make it clearer (small 12MB download - ho do I embed videos here?): https://mega.nz/#!OopHRISK!EoVTFiWw_AByaUR8wb3hxrTuX2XK-q-IPfg4ozggsiw I am always using the same key on the N52 keypad..... The N52 is programmed to type a letter 'f' 1. I tap the key a few times with the focus on a cmd window.. 'f' produced. Great... 2. Again, but with the focus now a text editor window. Again 'f' - as expected 3. I repeat 1 & 2: all still OK 4. Put focus onto FS9 window, but that's all I do. 5. Move focus straight back to the cmd window - the same key on the N52 is now producing not 'f'' now, but Ctrl+Y! 6. But back in the text editor, the 'f;' is still OK there 7. Somehow, having hit the N52 key while the focus was on the text editor, the programmed key press is restored (???) 8. ... but shift the focus to FS9 then straight back to the cmd window and the wrong key press is produced again. The Ctrl+Y was in an old N52 profile, deleted from my PC. So where is the information coming from? The upshot is that the N52 is sending the wrong key strokes to the programmes I am trying to control with it. I uninstalled the N52 software completely and reinstalled it. No change. Could the key presses be in FS9 somewhere? I really don't get it!

Can anyone help me find out why the N52 gives the key responses propgrammed into the profile just fine - but only until I open FS9. I tested this by opening a cmd prompt and pressing five N52 keys..FS9 has not been started at this point. In the cmd window, this appears every time: C:\Users\Martin>^W^N^Yfk that is, five keys which send the key strokes: Ctrl+W; Ctrl+N; Ctrl+Y; F; K ... which is what I want to send and is what is programmed & shows in the N52 profile. However, as soon as I run FS9.exe, the same keys on the N52 kepad immediately send a different set of key presses, according to the command window: C:\Users\Martin>7^W^N^Y i.e. 7; Ctrl+W; Ctrl+N; Ctrl+Y - and the last key does nothing. That is, I think, part of an old N52 profile which I deleted when I created the new one some days ago. No trace of the old N52 profile on my PC If I close FS9, I get the first sequence back, but only if I close the cmd window and start a new one.. So the question is, how is FS9 changing the key sequences that the N52 keypad sends - where is it getting the information from the old N52 profile being stored? The registry?? Not the FS9.cfg file as I deleted it and the new one didn't change anything. The profile editor for the N52 always shows the first, correct set of key sequences programmed, that never changes. Any insights (assuming you can make head or tail of what I am asking!), would be welcome as this is driving me nuts! Thanks

Thanks Jim. A pity if FSUIPC can't do this for FS9. I will have a look at the log again anyway. Martin

Hi. Thanks - I should have perhaps said what I had already tried (sorry) - I had changed the pan rate to 800, but that just seems to make the panning faster, not smoother, if you see the difference. The spot view panning 'glides' and the panning quickly slows down to a halt, rather than the split second you stop panning. The effect is much nicer IMHO. Do you really get this smooth panning in the VC in your sim?

that is not going to happen :wink: I did look at the FSUIPC log but didn't see anything. What does the entry look like, has anyone got an example? What is it that FSUIPC 'catches' in FSX? How does it work there? Thanks

The AVSIM CTD pdf guide says: I have the latest (registered) version - FS9 - in what way will it help fix these CTDs - do I have to 'do' something, in addition to having FSUIPC installed? There is no further mention of G3D.dll.. Thanks.

Thanks for the comments.. Over the years I have run FS9 with different fps limits between 20 and unlimited. The sudden tiny frame rates isn't dependent on that, I am sure. 25fps is not one of the 'recommended' settings - a lot of technical threads about this out there but I can give it a try, easy enough to test. I haven't had 1fps again (I think it was less than that, but lower frame rates aren't registered of course!), but with the MD-11 it certainly seems to happen more often - it does happen with any a/c though, and at all parts of the world. I have used all kind of AI traffic over the years... again none of these seem to be the culprit as when I change them for new installations, the low fps sessions do not end. Nor when I have zero AI traffic set does anything different happen. In any case, I don't think the symptoms would lead me to think that is the problem: I fly for 10-15 minutes with fps showing at 59-60, then suddenly I get between 5 and15 seconds of around 5fps, then it clears and back to 60... I have never flown out-of-the-box FS9 - I do have a clean installation I can try though and will let you know. I have indeed tried dtxfixer and fixed quite a lot of bitmaps.. I spent quite some time on forums at one time on this. Some bitmaps refuse to be 'fixed' though and returned error notices, (or the programme just ignored them, I can't quite recall). Worth another look at that.. From when and where it happens I think texture loading is in some way the most likely cause..

Hi, I already have Track IR, thanks, but I only use it for slow VFR flying. For 'heavy jets' I generally use the 2D cockpit, but would like to change the 'dry' panning when I do go to the VC.. if that is achievable.

4GBs! :-)

Does anyone know a way to get smooth panning in the VC? That's to say, similar to the way the sim pans in spot view if you open a flight plan (.flt file) with this value: SpotFastTransition=False .. you get a nice 'gliding' pan (continues a very short time after you release the hat switch) rather than the 'bone dry' pan (stops at the exact moment you release the hat switch) that setting the above option to 'true' produces. I'd really like to have the same smooth panning in the Virtual Cockpit, if that is possible somehow... Thanks

Anyone any ideas or experience of this? In summary: I am flying happily with fps around 60 and then, for up to about 20 seconds, frame rates fall to a juddery 3 or 4 (occasionally lower). I've always had this problem, on every PC on which I have ever run FS9 over the past 12 years or however long it is. I have been trying to get to the bottom of the problem for the same period, though have pretty much given up over the past few years. It happens most flights as far as I can tell, though not 100% certain of that. If I am in the 2D cockpit it is not always obvious. I have never managed to pin anything down using Process Monitor or Task Manager - there's no obvious programme hogging the CPU. I have 16GBs of RAM, and there's always plenty available. The page file has been rebuilt on many occasions (corrupt?) - I use only SSDs now, so fragmentation isn't an issue. I think the problem must come from within FS9.. any ideas from where though? I get it with no external programmes, such as Active Sky, or AI Separation running. Really no idea how to troubleshoot this any more - I have tried everything I can think of. (Plus it takes a long, long time to see any change, as the problem is sporadic and I need to take a whole flight each time to test any improvements). I wonder if it's aircraft related - flying the PMDG MD-11, as I have been all week, it is far worse than usual. I need to change to a different a/c and see if there's a difference. Thanks.

No, this is before I engage LNAV, just using the heading controls with autopilot on. I only engage LNAV when I line up with the flight path. Thanks for the suggestion - I feel that I am 99% OK (well, 95%!) with this a/c now - but will certainly have a look at the "Angle of Attack' (rings a bell - maybe I have looked before, but would be a long time ago if so)./

I'll check when I next have the problem - I don't recall for the flight in question. I am flying the a/c on the other PC at the moment and it is responding fine in HDG mode. Thanks..

Hi. Yes, I did the London to Zurich flight. To be honest I haven't worked out the barometer dial on this a/c at all - it seems to have a mind of its own compared to all other a/c I have (like the PMDG 747). It locks up and then half an hour it's unlocked, then locked again - I can't get it to change between STD and local pressure .. For now I am just having to 'go with the flow' and adjust QNH/QFE as and when the dial allows me. Again, as per your reply re. HDG/TRK, I tend to think I may be expecting this to behave like, say, the 747, but it doesn't at all. I need to have another trawl through the pdf manuals to see if I can find an explanation...

Thanks for the reply - I do understand the difference. Your comment about the 'operator' being the issue is quite possibly true in many of the posts though: but that's fine, surely? I haven't pretended otherwise: I mostly post here to learn correct procedure that I haven't been able to work out from either the manuals or practice, I'm not automatically assuming anything that goes wrong is the software's fault. The reason for all the posts at the moment is that I have only been flying the MD-11 for some days now, in order to 'master' as many of the details as I can. My posts in this forum will die away, fear not, as I assimilate details like this - most of the plane's fairly complex operation I have no problem with.. As for the HDG/TRK question, I should have been more specific. On my last flight, say I was heading 360. I needed to turn, again let's say 270 to intercept my flight path. When I engage the HDG knob by setting the correct value and pulling, the aircraft turned right, not left, as long as I had the selector on HDG. When I turned it to TRK, then we turned left to 270, as shown on the instruments. Back to HDG and we turned away to the right again. A long way to the right, not accountable for by wind or whatever. That is what I was asking about. Did the a/c have a temporary brainstorm, or is there an explanation (from which I can learn)? I am not new to this a/c, I bought it a long time ago, but haven't flown it for a few years for one reason or another, so am very rusty..

No very true of course. I'll try a couple more flights, then maybe go back to the PMDG 737NGs for a day or two! Head starting to swim a bit! The MD11 actually follows the FD quite closely when hand flying, with very little input from me...