bhorsoft

Mostly some older and more obscure locations. Drzewiecki Design UUEE, KLGA and KEWR, LatinVFR SLVR and SKBO, I also got SAEZ, SBRJ, and LTBA from some other vendors. I was under the impression that scenery had changed some for 3.x in an attempt to make the 3.x series more "upgradable" without clobbering scenery. I think the idea is to keep the scenery in directories separate from the P3D directories. That said, I have a couple of the titles don't give me a path option on install - just FSX or P3D 2. Chatter on some of the developer forums mention issues with the 2.5 versions working in 3.x. Most of the developers say they are working on upgrades. I am guessing I can install the scenery in 2.5, copy to 3.1, and manually add. It might work well enough. I have tried the same thing earlier by copying some FSX airport scenery to P3D 2.5 with mixed results. So, the question still stands: Is it possible to install PMDG P3D aircraft in both 2.5 and 3.1? I do have other aircraft that ask me at the start of the install which simulator I want to use - v1, v2 or v3. I just want to use the PMDG because they are my favorites. I'm still flying my old FSX on occasion because I want a good 747 to fly.

I've bulked up my system enough that I can run Prepar3d v2.5 and v 3.1 on the same machine (though not at the same time ). I already installed the 777 and 737 NGX in 3.1. Now I am trying to install in 2.5 and all I get is a dialog asking if I want to modify, repair or replace my existing installation. The different versions of P3D are installed on separate drives. The reason I want to install on both versions is I have other add-ins (mostly scenery) that only work in 2.5. When (and if) all my add-ins catch up to 3.1 then I'll ditch the 2.5 but for now I need the older version for some flights. Is there a way to install the PMDG aircraft in both versions of P3D?

Thanks! Not exactly what I wanted to here, but it will work for me. Makes my app menu and shortcuts a nightmare with near duplicates. I did neglect to mention that I'm running P3D 2.5 and the panel.cfg files were identical - I ran them through BeyondCompare. V3 is my next challenge once I pony up the cash for it and let the add-on market settles a bit for it. Fortunately, I backed up the original panel.cfg before I made changes to it for FS2Crew so all I should really have to do is restore the original panel.cfg instead of reinstall the aircraft. It looks like there are no common files between installations -- everything installs in the flight simulator directory. Perfect if I install V3 on yet another disk...

I have FS2Crew for both the PMDG 737 NGX and the 777. I initially installed for P3d since that is all I had running. I've expanded the system and now have FSX installed on a different drive. I have compared the panel.cfg between the NGX for P3d and FSX and added the entries for FS2Crew in the FSX version. They were identical other wise. I also mapped the autofeather key in the FSX NGX as specified in the Main Ops Manual. Unfortunately, I still can't get it to work in FSX although it still works in P3D. So, is it possible for the same FS2Crew installation to work for both FSX and P3D? If so, what step am I missing. Or, do I need to do a separate installation of the same FS2Crew software to a different location to make it work for FSX while still having it work in P3D? I'm a big fan of FS2Crew and plan on trying to do the same for the 777 and later the Airbus.

Happy Birthday and good luck with the hardware replacements. I hope you bought Murphy a beer on St. Paddy's day and you did the voodoo dance to dispel any gremlins

I was using the default FSX sceneries for this flight. However, I added some sceneries afterwords, ran the makerunways for RC (and FSC9, and...), rebooted the PC, and now they are both working perfectly together. I can't say for sure it was the makerunways that fixed it, but it was a good tip to keep in mind should it happen again. Thanks!

Sorry to dredge up an old topic, but I just got FS2Crew for the NGX. I've had it a while for the 767. I'm also a RC4 user. I don't use RC4 with voice commands, just to handle comms with the ATC. It works great with FS2Crew for the 767. For some reason, I'm not hearing all the RC4 ATC commands with the NGX. I hear some, but critical commands like "Line up and wait", or "Cleared for Takeoff" are silent. I hear the RC4 Copilot and FS2Crew just fine (and FS2Crew responds to voice commands well, too.) Any ideas why this might be happening in the NGX but not the 767?

Thanks, folks. Some info I can use. The interesting thing about the past two times it happened is I was at cruise altitude and flying essentially a straight line through several waypoints. Not much AI going on, no turns, and pretty quiet from the controller. Should have been within the 5 nm enroute circle. I've noticed when I miss a waypoint on climb or descent the controller is on me almost immediately. In the past two cases for me, I was over 1000 nm from the waypoint (and had passed through several others) before the controller started complaining about it.

I've noticed recently on longer flights that RC4 will skip a waypoint. My FMS or GPS shows I've hit them, along with my FSC9, but RC4 will be stuck on a waypoint and show an ever increasing distance from it. I sometimes won't notice it until about mid-decent, when the controller starts telling me I'm off course and to take a heading to the missed waypoint. Any way to prevent this or to tell the controller I didn't miss the waypoint? He gets pretty insistent that I'm off course when I'm not.

Family is most important and I applaud your decision to focus on them. It's hard to give up something you love doing, even for a while. I understand. I have Multiple Sclerosis and have had it for 25 years. It has only been recently that it has really started taking it's toll. I've had to give up a lot as I've lost mobility. That said, I'm also finding new things. After not simming for 20+ years, I've rediscovered Flight Sim and all the wonderful addons like RC4. I think I'll be able to to this a while. So, keep your chin and spirits up, enjoy your family, and come back to RC5 when you are ready and able.

My FSX was working beautifully until yesterday. All the sudden, I started getting all the usual CTD symtoms. What was peculiar was I could fly the standard FSX aircraft without changing airports or anything, but if I used a non-FSX aircraft (Feel There, Just Flight, PMDG, Abacus, etc.) it would CTD almost immediately after pressing the Fly button. Uninstalled FSX and all aircraft and utilities and stuff, re-installed, still same after the fresh install. Moved and removed all the standard DLL fixes - still no luck. Finally went to the Windows application error log (I'm running Win7 x64). I'm seeing FSX crashing on atiumdag.dll. Google that and find out that is an ATI video DLL. I had just updated the drivers to the 13.9 version for my Radeon 6900 series to the latest ones from 13.4 version. When I completely uninstalled the Catalyst software and drivers and installed the older version back - FSX works fine now. So, warning to you Catalyst users - latest versions for your Radeon cards might cause problems. Wish I had figured this out first instead of last.