Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Hi Appreciate your help! I am running Windows 7/64bit with 16GB of RAM. Presumably that's not it. AFAIK the filename is UiAutomationCore.dll, and there's actually three of them in the tree below my C:\Windows directory. No such file in the FSX root. It's true there is a lot of (mostly quite old) literature about that DLL on the web dealing with FSX issues, and I've played with it when I had Win7/32bit where FSX crashes rather frequently. None of the tips really changed anything (e.g. using the Vista-version), and since I didn't find any really technical explanation on why that particular file might pose a problem, I consider it more of an urban legend or myth that replacing, relocating or deleting it does any good. But no offense meant, that's just me. The actual remedy then was going to 64bit and more RAM.
  2. Alright my DX10SF version is 1.4 build 35 (not 2.0 as initially claimed ... sorry for that mistake). I got myself the AppCrashView utility (v1.12). Ever since I installed the Scenery Fixer, these crashes were recorded: Application name and version always fsx.exe and 10.0.61637.0 Exception Code always c0000005 Error Module, Version, Error Offset PMDG_MD11.DLL, 10.0.61355.62, 00118301 (twice) Note after these two in February I installed one more plane (a chopper) and one more scenery, played with those (with DX10SF active) and nothing went wrong. After that, I tried the MD11 again and saw the following CTD's happen: g3d.dll, 10.0.61637.0, 000ba79f (five times) g3d.dll, 10.0.61637.0, 000ba7e9 (once) After the first two of the above six (in direct succession), I posted the question. The remaining four happened arbitrarily during the tests that Steve had suggested. I have no record which crash belongs to which combination of settings (DX9 or 10, libraries installed or not) but as mentioned before: After every crash, I immediately redid the same flight with the same settings, and it went through every time.
  3. Found and scanned it & will follow the advice ... This for now, just the raw data, guess it may help to assess the situation: i5-3570 (3.4 GHz x 4 CPUs) 16GB Win7 64bit Home Nvidia GTX660 (updated the driver once but I am not using any of the tools like the inspector) Yes, HIGHMEMFIX=1 UsePools=1 BufferPools=262144 Bojote applied - the effect was dramatic, up to 100% more frames depending on scenery The AA setting in the FSX settings GUI is "anisotrop". I like to fly above Central Europe where I have a lot of Aerosoft-sold stuff installed (aereal photos and airports) but no ORBX products. So I can't tell you yet if the crashes happen over native territory too. I'll be back, thanks so far.
  4. Sorry for the long pause ... explained below. I did as told, programmed a ~45 minute flight with "pause at T/D" set to on ... but it didn't (I noticed this earlier, sometimes the sim waits for you, sometimes it doesn't). The plane just went on in runway heading at cruising altitude (did not descend either). I caught it, prepared to do a manual landing at the nearest suitable airport and boom was rewarded with a white-out CTD after about 90 minutes airborne time. Now, I usually do not do long flights so that crash in my case was an insignificant test result. What I did then was a number of 2-hour automated test fligts in all four combinations of DX9/DX10 and DX10SF libraries installed/not installed. ("Installed" means, as you recommended, with all options and shaders off). I experienced two CTD's but both were not reproducible: I restarted FSX immediately (no reboot) and re-flew the test that had just crashed with otherwise unchanged settings, and in both cases there was no CTD. In one word: inconclusive. I'd really like to continue with DX10SF so maybe you have more advice on how to continue the experiments until the crashes become reproducible. Thanks again for your patience. p.s. diagonal lines that are just a bit off-horizontal don't look nice with DX10. In the DX10SF GUI the antialiasing setting is "4x". Any recommendations? Or should I leave it as it is during my tests?
  5. Hi Steve, hi everybody Peaceful holidays to all I did as told: used the DX10SF GUI to uninstall its libraries, made sure that DX10 preview was "on", and flew a few tests, among them two legs with a full stop between them within the same session and one "longer" flight (90 minutes ... usually my flights are shorter as enroute flying is not my primary interest). No crashes. Framerates were so-so (depending on scenery) (didn't it say that DirextX 10 performs better than 9?). Of course I saw all the little quirks that DX10SF was made to fix. The plane itself looked *much* better though, certainly there are optical improvements over DX9.
  6. Ah ok thanks!! Tonight's soccer on TV (writing this during halftime) but I'll pass on any progress on your tip soon as I have something...
  7. Hi Steve Thanks for taking the time ... unfortunately I'm more of a pilot than a mechanic so I don't really know how to follow your advice. DX10 controller? Envmap? I suppose you are describing a hack to revert the effects of the DX10SF without actually de-installing it completely. I must add that I flew a recreational short hop Frankfurt/Brussels last night with the default 747 with DX10 preview off. Sometimes it's gotta be heavy metal, you know. I made it to cruising altitude but it CTD'd anyway. Never had that ever since I moved to the 64bit version of Windows 7 - at least not before the second or even third leg without restarting FSX. Please don't be offended just because somebody's pessimism - I know about the sensitivity and the "airs and graces" of the diva called FSX. May well be that I am just using up too much memory with my sceneries and airports. I know I should eventually try a tool that loads add-on sceneries conditionally.
  8. Hi everybody I fly FSX with Accel Pack and the usual bunch of add-ons, including Global Ultimate Eur, UTX Eur, Aerosoft VFR Germany West and a number of airports in that wider area. Guess where I live Ever since I installed the DX10 Scenery Fixer (it is v2.0), my MD11 crashes to the desktop a few minutes after take-off after whiting out the screen and displaying an "unrecoverable error" message. Other planes (default or add-on) don't seem to be affected. The problem does not go away when I unselect "DX10 preview". I admit I have experimented only a little and did not try all conveivable combinations of settings, airports and planes. One reason being that I am a bit disappointed regarding the DX10 effects on image quality and framerate so I probably will de-install it and write off the money, in spite of the apparently many true fans of this tool. No offense meant of course! Anyway I thought maybe somebody here has come across this. Posted it on the MD11 forum too. Thanks
  9. Hi everybody I fly FSX with Accel Pack and the usual bunch of add-ons, including Global Ultimate Eur, UTX Eur, Aerosoft VFR Germany West and a number of airports in that wider area. Guess where I live Ever since I installed the DX10 Scenery Fixer (it is v2.0), my MD11 crashes to the desktop a few minutes after take-off after whiting out the screen and displaying an "unrecoverable error" message. Other planes (default or add-on) don't seem to be affected. The problem does not go away when I unselect "DX10 preview". I admit I have experimented only a little and did not try all conveivable combinations of settings, airports and planes. One reason being that I am a bit disappointed regarding the DX10 effects on image quality and framerate so I probably will de-install it and write off the money, in spite of the apperantly many true fans of that tool. No offense meant of course! Anyway, although I did not find this specific issue in the DX10SF forum, I thought maybe somebody here has come across it. I'll post it there too. Thanks
  10. The missing textures happen to me too every once in a while, like parts of the plane are suddenly missing or like the 3D panels just vanish while the gauges and screens stay where they are. Makes for a much better view forward/down though :-) A CTD or OOM then comes up sooner or later. Always flying with a freshly started FSX helps to make that happen less often. Frequent shuffling through outside views (i.e. pressing A often) in the "runway" or "traffic" views is also a memory killer. But a little anecdote - In the old FS9 days, I liked to fly with extra windows open just for the nice sights. Not so in FSX, not enough frames. But applying HIGHMEMFIX and all the Bojote goodies (http://www.venetubo.com/fsx.html) recently had a dramatic effect on my frames per second. Now I did it again, watching myself fly in a second window, and guess what: The MD11 in the second window (actually, on monitor #2) eventually started to turn into a skeleton as described above, while the outside view in the primary window stayed intact (full screen window on monitor #1). All of that with 15 to 20 fps in mid air. Then slowly, stuttering started to set in, the fps dropped, and the Black Squares Of Death started to show up on the secondary window. So I closed it, and guess what, the FSX actually recovered and let me land like 45 minutes later without any problems (other than my flying skills). Could even reproduce this behaviour, so I can afford to at least taxi, take-off and land with a second window. I've actually never before experienced the FSX to fully recover from a memory shortage and/or texture/rendering issues in mid flight.
  11. @Markus See what you mean and you got a point there. We agree that the flaps are meant to enable you to fly slow, never mind how you manage to decelerate to that desired slower speed. >> (the flaps) increase drag but at the same time create LOTS of lift. ... and thus slowing you down even more, beyond the additional drag. To prevent that, and to stay reasonably near the desired descent angle, I tend to push the yoke right into the initial effects of a new flaps setting. That's to keep the nose steady where it was. That way, the additional drag does part of the job of slowing me down. And I am pretty sure that I see the PROF and APP modes do the same thing when I "disturb their circles" with extracting the flaps.
  12. >> any way I can review my selected SID or STAR before inserting it No. Gotta be familiar with the charts and hope that they match the nav data in your plane. Afaik, the FMC takes the pains of calculating path, turns, speeds and altitudes only upon actual insertion.
  13. Thanks everybody for your patient and helpful advice, some of which I am using below, and a Happy New Year too: The skies is where to go, not the heavens Apologies for being afk for a while. I was on a holiday and then followed my own advice first and just practiced a bit. As mentioned before, I am more into manual flying - man against machine - than into simulating real-world aviation although you can learn a lot from watching how the autopilot does the job. On topic: What I do now, if I used the autopilot at all, is setting the throttle lever to the appoximately right position (labelling them helps) in cruise flight, then disconnnect the ATS before the descent and take it from there. That way, there's some margin for error, and flying a curvy descent manually, observing speed and altitude restrictions, is in fact a nice challenge in a big and lazy airliner. If in PROF and FMS SPEED mode, you can also wait until it goes to idle engines and disconnect then, for an even smoother transition. A few more observations. More experienced pilots will probably smile at my weak attempts to stay alive at the controls... # After all those years, I like to think of myself as being quite good at fumbling small and medium (simulated!) planes up to say a 737 down onto the asphalt even after an imperfect approach (= corkscrewing around the glideslope with, well, an improvised speed profile), even in bad weather, but the slow reaction of a big baby like the MD11 takes a lot of foresight and pre-emptive action. Now, if you approach with AP OFF (pressing Z twice or clicking AUTOFLIGHT twice) and ATS OFF (I programmed SHIFT-R to do that, also press it twice to silence/unblink the warning), and if you then get into trouble staying within or above the glideslope, and/or if your speed drops too low, then some kind of envelope protection kicks in, first wildly blinking the annunciator in the PFD and eventually re-engaging the ATS and giving full throttle, thus forcing a go-around. You can of course switch it off again, but it will come back on. Sure a good thing in real life, but not with Yours Truly at the wheels. So what I do is push the two big AFS OVRD switches both down, and then it's ME having control. Or what I like to call control. Most any time, I make it down onto the runway with no other damage done than to my nerves. # If you reduce throttle in level flight, most every plane will start to descend but not the MD11. I guess it's the LSAS that gradually moves up the stabilisers to increase pitch and hold altitude as long as it can, while the plane slows. All of that with AP OFF. Nice to watch that behaviour in PROF & FMS SPEED mode too, e.g. at the T/D. You then have to actually talk her into the descent. I didn't like that initially but find it helpful now. You can still operate the stabs manually, and the LSAS will take it from there. All of that helps you to quickly find a smooth descent (airspeed and vertical speed each being constant). # The slower I get, the speed tape tends to oscillate more heavily, and I see erratic appearances of the thin green upward/downward bar that indicates the direction and rate of speed changes. With ATS on, the throttles rock wildly to and fro so you are unable to touch the disengage button with the mouse without pausing the simulator. @3-2-1NOW, thanks for the many hints from November 23! > NEVER use the flaps to decelerate! That is not what they are for. Use the speed brakes. Well but the flaps DO decelerate the plane don't they... and the lift effect of extracting the flaps is dramatic in manual flight, especially from slats out/flaps zero to flaps 15. I do that as early as I can to have as much margin as possible to manage the effects of the additional lift and drag. > She also does NOT require back pressure during turns Can't confirm that fully although LSAS indeed seems to be helpful. Also, coming out of the turn, you have to push too to hold altitude, like in every other plane.
  14. >> Idle thrust will vary with altitude. The higher you are, the higher "idle" N1 will be. Um.. never thought of that. But if she doesn't let you go below 200 KIAS with N1>40 and refuses to deploy spoilers to calm her down.... quite a challenging landing but in that specific case just the other day I actually made it onto the asphalt in one piece and even got her to stop before the runway was out. Haven't defined failures yet, and nobody gets at my PC to set them behind my back .... I'm a hero ;-) >> Are you sure you aren't disconnecting the A/P, then accidentally reconnecting it with an extra button/key press? Yes I am. The PFD tells me AP OFF in a white frame around the HDG and ALT fields, and I check it all the time for heading, ILS indicators and the tapes, while the SPEED field sports a flashing red frame saying ATS OFF (or similar). Quite annoying. In PMDG options I have "joystick disengages AP" set to "never" so I guess it can't be that it goes on and off depending on my battling the joystick.... >> You could try re-calibrating your hardware Will do. However, with other aircraft all of that does not happen .... >> As long as the plane is within it's normal flight envelope Good point. Of course I had hoped to have a common problem with a common solution and there was a few plausible hints so thanks for that so far. I might still be a bad pilot that's true and no offense taken. I am a seasoned sim pilot (yes from Apple II days on, with long pauses though) but the MD11X is my first ... well "real" plane if you know what I mean to say by that, and the biggest one for that matter (the default FSX 747 is a toy). I should practice more without any AP and ATS and see what the plane does in reaction to what I do.... *think
  15. So many replies in a short time, thanks! >> SOP is to leave the auto throttle engaged even when hand flying the approach, pretty much the same as the 777. Well, concerning the 777, what went wrong with the Aseana 777 landing at KSFO recently? That was OT sorry Apart from that, we are in a sim. And automatic landings, or even manual landings with autothrottle are boring. I mean it's interesting to know how it works and learn and be able to operate the plane properly, but it's also like watching two chess computers play each other. What's your part in that? :-) >> my method was to disconnect in the approach around the same time the autothrottle was commanding idle thrust , that way a smooth disconnect was always guaranteed. "Idle" on the MD11 is like 25% N1 right? Never saw it that low in a descent. However that could be because, when going manual at the TOD or even earlier, I am too quick with the flaps. I am not a pro so I extend the flaps one more notch whenever I feel that the plane needs my help to decelerate. That way you get slow-flying "powered descents", I know. I suppose what I should rather do, even in manual flight or when flying with manual A/P settings, is follow the pink FMS speeds displayed in the PFD and the proposed flap settings in the speed tape. Just talking to myself, you can see that :-) but comments are welcome. >> I'd set the hardware lever(s) to idle before disengaging ATS. If you don't touch the levers after disengaging ATS, the sim will continue with the last simulated setting it knew. Not with the physical setting that it reads from the sim'd hardware. And there's the whole problem - if you then touch the levers ever so slightly, the sim wakes up and adjusts to the physical settings - which may mean that it goes from an "assumed" e.g. 60% N1 to e.g. a physical 25% in one tenth of a second. Even if you move it back up immediately, the instability begins right there. I consider that behaviour a programming error. Maybe there's no actuator to move the hardware levers on your joystick or Saitek lever unit etc., but they *could* read out the physical setting and help you adjust it properly before disengaging the ATS. Flying with the F2/F3 keys (decrease/increase thrust) does not have that problem because this method does not have an absolute setting. Pressing either key takes it from where the simulator thinks the setting was. But hey.... In conclusion, I'd go with riccardo74 and set the levers to an estimated correct physical position, then disengange ATS, then touch the levers a fraction in order to see what the plane makes of it, and then react to that. * * * Anyway: What about the apparent erratic behaviour of the plane when it gets a bit disturbed on its glidepath, e.g. when going to manual at 1000ft AGL with intitially mismatching thrust levers? Is it just me? Or a sim problem? Is it some kind of "envelope protection" that keeps me from touching down when the final approach gets too rough? E.g. it happened that the plane, with A/P and ATS off, would refuse to go below 40% N1, refuse to go below like 160...180 KIAS, refuse to deploy spoilers, and refuse to be forced down onto the runway, with any conceivable aural warning shouting at me. How long could a real plane try to to keep the pilot from grounding it? Even a bad pilot must be given a chance before the fuel is out, and I am really good at setting them down safely after a curvy and bumpy final .....
  • Create New...