RDG41

Thanks for that feedback Eric, that helps me alot. Can you tell me , when the wheels first touch the runway, what kind of response does it send?And while flying, is it always sending a vibration, or can you tune that down?

Thanks for the responses guys. I was really hoping that someone was actually using this device and could tell me what they thought of it in terms of flight.I know this isn't a PMDG specific question or topic but I thought this might be the best spot to get some feedback on a product used for flight.

Can anyone tell me if they are using this device for flying PMDG planes? I'm interested to know if on landing you get a more realalistic experience. http://www.simw.com/index.cfm?fuseaction=d...ls&pid=1596 Thanks.

Anthony, this happens with some airports in FS9. I haven't experienced this yet in FSX. Try updating your navdata and see if that helps. Also, if you do a search in the forum, there was extensive discussions on this already. Hope that helps.

Same here.

Maybe Pete knows something we don't.

Laurent you didn't say if it was FSX or FS9. Typically when I would see strange things like this I would uninstall and reinstall the aircraft. Try that first. Also, what are your machine specs? It's possible that after 8hrs of running a flight your system resources are maxed out.

Bjorn, this has always been an issue since this plane was released. I reported this along time ago and thought that in the last patch that it would have been addressed, but it wasn't. I can't remember but I think it only shows up in the cargo flight deck. I haven't flown her for a while as I'm always in the MD.

This may not harm your installation of your planes (but I doubt it), but I'm almost certain that this will mess up any scenery or other addon's that you have installed.In my opinion, and from my own experiences, your better off doing a complete install if you start messing around with uninstalling acceleration, but try it. The worst thing that can happen is you need to do a re-install.

I'm also having this problem of CTD on exiting FSX in Vista 64. I tried a few things , so here they are. I rebuilt the FSX config., still CTD. I discovered that when I loaded the 747 or the MD11, they also CTD on exit.So a common file for PMDG seems to be affected it appears after the installation of the J41 . I uninstalled the J41, but the 747 and the MD11 still CTD. I had to uninstall the 747 and the MD11 and delete any PMDG file left over,and reinstalled them minus the J41. When I did this, everything was back to normal.Just some added info for trying to solve the issue.

Thanks Markus,( and everyone else who replied). I don't go there very often and never thought to look there for the answer. I will be using it more now.

Sorry if this has been discussed before but after landing the MD11 and disconnecting the autopilot, I get the disconnect warning that won't shut off. Is there something I can do to turn it off? or am I just doing something wrong. It's really driving me crazy.

I have both panels and am sorry to say that the multi panel does not work with aftermarket widebody aircraft. The flaps work, and on the LVL-D 767, I can set the coarse in the radio panel, but thats it. With the MD-11, the numbers will go up in the cockpit, but don't stay in synch with the screen on the multi panel.If you fly GA or stock wide bodies, it works great. The radio panel on the other hand works with all aircraft.Sorry. maybe PMDG can write some drivers for this panel? :(

No problem Dan. I hope it will help PMDG to narrow down what causes this issue. As with many problems, it seems to be only a select few who have it.

Thanks Dan for the clarification. I didn't have european convention selected on mine when I checked. I did however try to find a font file somewhere within the PMDG folders so I could replace it with a backup file, but could not find one.An interesting observation after rebuilding the config file is that on selecting the MD11 as a plane choice, I didn't get any DLL confirmation messages, but did when I selected the 747. The 747 was fine with regards to the fonts.I decided to uninstall and reinstall the MD, and this corrected the corrupted fonts.

I'm also having this problem. I aready had all service packs installed and working fine. Then I updated the video driver and rebuilt the FSX config and it appeared.Dan, I'm not sure what you are refering too?system specs, E8600, Nvidia GTX285, latest drivers-182.5, win xp 32bit, FSX+ Accel

No problem at all. Glad that I could share that with anyone having this problem. Strange how it only affects the MD though :(

Dougal, I had this problem. It seems to be something with REX .I solved the problem by changing to the high intensity light option within REX. Hope that helps.

Hi Daniel, yes the plane will touch down all on it's own. I disconnect the auto pilot just after touch down.

Bob, have you tried re-installing the plane?

Oh it's no problem, I'd just rather be flying than looking up way points, but whatever turns your propeller :(

I'm creating all my flight plans with FSC and have never had any of these probems. Sorry I know you are trying to help but, if we had to type in our flight plans everytime we flew, I don't think anyone would be flying.I had this problem once with the Level-D aircraft and discovered that it was a conflict believe it or not with FSUIPC (which again you don't need to run this aircraft). I'm not putting down FSUIPC, I'm just trying to point out that you don't need it to fly.I would be inclined to try and reinstall the plane , but after uninstalling, make sure you go in and delete all the files left.

You don't need FSUIPC to run the MD11. I'm running with ASA with no problems as are many others. There is something else wrong in the sim I agree, but to suggest that he needs FSUIPC to me, is not the solution, just a band-aid to some other problem.

Well, after sevseral flights from KJFK to KORD (both from FS Dream team), I finally managed to complete a flight with no OOM. I would always get the OOM around 4000 ft of so , close to the airport on approach. So I decided to turn off the KORD scenery to see what would happen. My system memory usage was 1.95 GHZ at crz and increased to 2.14 GHZ on landing, with no OOM. :( This all happened with ASX in heavy weather, lots of clouds (in HD) , heavy snow at times, about 75% AI with WOAI. So, just some food for thought. My scenery must have been pushing the memory usage just over what could be handled. Unfortunatly, I didn't see what the usage was at the OOM points, so I can't give you thoughs figures.Give this a try if you are getting OOM trying to land at a non-stock airport.System: XP32, E8600 OC to 4.1ghz, 4 gig of OCZ Ram , GTX280 OC2

Thanks Harry for clarifying that. I didn't realize that it was a known FSX problem with the default scenery. I'll look into Airport design editor to try and correct the problem. Good thing I didn't reinstall :(