sheepfu

To my knowledge the J41's fmc doesn't have an option to step through the legs of a plan displayed on the HSI. I have looked for a way myself and never found it.

I have encountered this on several turboprop ac's. My understanding is that it is a result of the fact that the FSX simulation of a turbo prop is horrible, so developers go around it. best solution, go into the config file for the J41 and crank up the effectiveness of the parking brake. While not fully realistic, I don't think that anybody is using the parking brake to make landings anyway, so knock yourself out.

Thanks a bunch. Started an Air Hauler company there and it is annoying especially when landing with a well loaded AC. I try to land soft when I know I have enough runway to stop.

I haven't done any scenery design before, but I have got a problem that may get me to dive in. In FSX KEGE, Eagle Airport, has got some random Radar box in the middle of a taxiway. It's checker patterned, so I am sure it is for the airport, but how do I get rid of it? Its really irritating to go off of the taxi way to get around it. Thanks in advance.

Ok???

Have you created a support ticket with PMDG? I had the exact same thing happen to me. However, even though I received the activation error, the AC operated properly. PMDG sent me a file to fix the bug, and I haven't had problems since. Give it a try.

Your link works, go figure :)

Is anybody else finding that the link to the review for the DC-3 is going to the review of the C 310?

I am amazed at the modeling of the engine. Not only are the fan blades modeled, but if you look at the second picture, you can see through the gaps in the blades to what is behind the AC. This must mean they modeled the interior or at least part of the engine too. Amazing.

B is the camera system.

It has got to be the search and rescue radar system. This C295 aircraft has a similar setup, notice the accompanying elongated window above the radar system just like in the Hong Kong J41. From what I can tell the black shroud for the radar dome is a special plastic made to withstand rocks kicked up by the front gear that fiberglass would not withstand over time.

I could be corrected if I am wrong, but ACARS varies greatly between airlines. Maybe, it would be better to state exactly what functions you are wanting to implement in ACARS. ACARS primary function is to send reports to the ground crews, useless for FS, however pilots can request information through ACARS such as weather at destination and high level cruise. This would be handy to have. Most airlines can use ACARS to automatically receive IFR clearance from ATC while it would not be terribly useful in FS, it might be handy to be able to send a flightplan to FS so that the built in ATC could know what you are doing and not try to fly you direct or VFR.

Have you recently updated your graphics driver?Does it happen in all stages of flight or just decent/approach?

I don't have a problem with assigning the buttons with FSUIPC, but if I erase the throttle axis in FSX, I get no throttles at all. Also if I don't use the Logitech Profiler, I can't use the hats the way I want to, mainly to pull up 2d panels in the VC and to adjust eyepoint. I made some progress last night by using the sync function in the FSUIPC calibration screen. The throttles will work better, but not quite there yet.Thanks again

I have a G940 unit and I have wrestled it into submission and it works pretty well. The main issue that I have is that if I have the Logitech profiler software running, the throttles are not even close to matched in FSX. At the bottom and top of the spectrum, throttle one and two are okay, but from about 10% - 90% they are not close. Closing the profiler software and then returning the throttles to idle they work like magic again. So here is what I have setup. All of the buttons, except the axises which can't be, are programmed in FSX (not profiler). Throttles are mapped in a registered version of FSUIPC. Throttle, Joystick, and Rudders axises are mapped in FSX as well. So I am wondering if I have too many pieces of software trying to run things. I would like to keep using FSUIPC as it is necessary for some of my add ons. Any help would be great.

Are you defeathering the props? I don't know about a cessna cold and dark, but the PMDG built in cold and dark requires this.Branton Turner

RESOLVEDWell it turns out the problem was not with any of the add-ons, but a strange fluke in the Nvidia G-force 7x drivers. FSX has a default of bilinear filtering, which from forums I have read can cause problems with other 3d type aplications. Any other setting, trilinear, etc, works fine. Just thought that I would post in case any one else ran into the issue.

I have been fighting for almost a week now with a very strange issue. Here is the history and I will try to be as complete as possible. I purchased 747X and installed it. When it would not run, I checked the PMDG support pages and found the info regarding the dll.xml files. At the time of install of the 747x I had the following add on aircraft installed: 737PIC, ERJPIC, Citation X, 777 PIC, Australian Sim Glass AIR 3, and Captain Sim 757. There were plenty of oportunities for any one of these planes to screw up the dll.xml. I followed the suggestion of the support page, uninstalled 737 PIC/747X and reinstalled them 747 firt. 747 fired up and worked great. However all other add on aircraft except Citation X did not oporate properly. Here is what would happen:1.When selecting an add on aircraft, the details screen(where you can choose airline, flight number, etc, would show a blank white screen instead of previewing the aircraft. The regular FSX preview, where you can change location, weather, etc, would also be blank white. 2. Deciding that it was possible that it was just a preview problem, I launched an aircraft (erjpic) all seemed ok. All views worked as normal. About 30 seconds later, the scenery went away and I was left with a blank screen and a fully visable 2d panel. Outside views and VC were also white. 3. I switched aircraft to a boxed FSX aircraft, baron 58, all problems went away. Here is what I tried to fix the problem. I uninstalled everything. FSX all aircraft, even FSPanel studio. Reinstalled FSX, added SP1, installed PMDG, installed other add ons in no particular order. After learning as much as I could about the troublesome dll.xml file, I watched for any addons that attempted to modify this file. The only add ons that did were PMDG, Citation X, 737 PIC. Still PMDG worked, but no other add on except Citation X.So this is where I decided that this may not be a FSX problem. I updated drivers, direct x, even rolled back some drivers to see if that helped. When none of that worked, I bought Acceleration to get SP2. That did not fix it. I contacted Wilco support they were unable to help me.Finally I ran the whole process again. Uninstalled everything and reinstalled FSX, Acceleration, 747x. The only add on I have installed at this time is the Glassair III. Which still does not work due to the blank screen problem. The dll.mxl did not change with the install of the glasair III. My question for you is what should I try next? Is there some other mystery FSX file that is getting corrupted? I am contacting you because the only common thread that I can find is the 747X. Hope you can help.Thanks,Branton TurnerP.s. I love the 747X