Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Pahlmla

Members
  • Joined

  • Last visited

Everything posted by Pahlmla

  1. Thanks, Ron. Fantastic! Your suggested change to the .cfg file worked like a champ. I even had to zoom-"in" a bit. And Rodney, good luck on your 6-monitor setup. Larry
  2. While I'm thrilled with my new 3-monitor "surround" VC, I'm struggling how to best read the instrument panels without having to back away from the 6000x1200 display. Although I've used the "-" key to zoom out as far as I can, it's still not enough for me to properly view the flight deck without physically moving my chair further away from my desk. It makes using the mouse a bit of a challenge. I'm also using TrackIR and found disabling the z-axis helps, but still doesn't solve my zoom-out limitation. I almost feel I should do my flight prep in single monitor mode (1920 x 1200) and save my triple monitor display for when I'm in flight. But what I really am hoping for is any suggestions members may have in tweaking my configuration such that I'm good for viewing all aspects of the VC without having to go into the next room. Thanks. - Larry
  3. I became "un-stumped" regarding the 4th monitor being disabled after setting up the 3-monitor NVidia Surround". I right-clicked on an empty area of my desktop, then chose "Screen Resolution". I then selected the 4th monitor and changed the setting under "Multiple Monitors" from 'Disabled' (which NVidia had set this monitor to when going to Surround mode) to 'Extend Desktop for this Display'. I'm now able to run FSX in either Windowed mode or Full Screen and run auxiliary programs, maps, etc. on the 4th screen. Solution could not have been much easier.
  4. When I set up my 3-monitor Surround mode using the 2-DVI and 1-HDMI ports of my Asus GTX 770, my 4th monitor ("accessory" monitor) using the DisplayPort is disabled by NVidia "Configure Surround, PhysX" setup. All monitors work fine in NON-surround mode. I want to use the 4th monitor for maps, Reality XP, etc. Ideally, I would fly FSX in VC windowed mode with the ability to undock certain instrument or other windows and move them to the accessory monitor plus run separate related programs (e.g. FS Commander) in the 4th display. So far, I'm stumped on how to do it.
  5. .I'm about to replace my EVGA GTX 560 Ti (1Gb) with a 3-monitor, NVidia surround capable GPU. I already have my 3 monitors (Dell U2412M). Although I'm not quite over sticker shock, I'm leaning toward the EVGA 780 (3Gb). Any thoughts on this choice?
  6. I'm trying to figure out the best setup for my new 3-monitor (Dell U2412M) configuration. I believe my existing desk is large enough (46" W x 30" D) for all 3 monitors, but the desk has a 1/2" raised edge (leg piece) on each side of the desk that limits the individual monitor stands from extending over each side of the desk. So there's no way the 3 separate monitors will fit. I considered a new desk or modifying my existing desk until I saw the Ergotech 100-D16-B03-TW Triple Monitor Desk Stand. Is anyone using this stand for their FSX 3-monitor setup?
  7. Thanks, gb. I've added the new GTX 770 and GTX 780 to my candidate list.
  8. After completing my first FSX dedicated PC build, I was revelling in the satisfaction of reaching FSX nirvana. That is until I watched a YouTube video of a 3-monitor FSX flight. It became apparent that my 2-monitor setup is “surround-challenged”. From my research, it appears that to move up to a 3-monitor “Surround” setup I need to: Add a 3rd Dell U2412M monitor to match my existing pair Replace my GeForce GTX 560 Ti card From what I’ve read, it looks like a GeForce GTX 680 (or perhaps GTX 670) is the way to go. In particular, the ASUS GTX 680-DC2T-2GD5 caught my eye. I believe this is what ASUS calls their DirectCU II TOP video card. In addition to its hefty price, this triple-slot card has a hefty length (11.8”). I’m not positive it will fit into my Rosewill Blackhawk ATX mid-tower case. (Rosewill advised me max length is 11”, but I think I can re-configure the HDD cages so that it will fit.) Is the GTX 680 the right way to go or would the GTX 670 work as well from a FSX stand point? Also is a “stock” GTX 680/670 card a more prudent choice vs. the ASUS triple-slot TOP card given that this is pretty much a FSX dedicated PC? I think I have a build that is well equipped to move on to the next level of realism with a 3-monitor surround setup (Asus Z77 Sabertooth motherboard w/ i5-3570k CPU). I’m currently running at 4.2 GHz and if I ever figure out how to set the proper Vcore/VID/Offset values (I know, each CPU is different), I think I have enough cooling capacity to get 4.5-4.7 GHz. Any recommendations or suggestions would be most welcome. Larry
  9. Thanks, guys. I’ve come to a similar conclusion… System Mechanic will no longer be a part of my system. This comes up at a timely juncture as I’m about to do my first PC build, sans System Mechanic.
  10. I have System Mechanic (SM) installed and have experienced the same problem as Lon Duncombe (“Lon David”) described in his 5/7/12 posting (FS2Crew voice recognition stops working). When the problem occurs, and it has occurred many times, I can normally "recover" from SM's "disabling" of FS2Crew's voice recognition by running Safety Net. Safety Net, a feature of SM, allows you to undo selected SM "registry optimizations". If that doesn't work, I try a System Restore. Only once have I done a Windows re-install to resolve the issue. While the Windows re-install did fix the problem SM apparently created with FS2Crew, and as much as I love FS2Crew, I will never again do a Windows re-install if SM/FS2Crew is the only issue. It's just too time consuming. Unfortunately, neither Safety Net nor System Restore has fixed the latest occurrence of this problem I’ve just encountered. FS2Crew voice recognition no longer works on my system. If anyone has a suggestion of what I might try (short of a Windows re-install), I’m all ears. Otherwise, I guess my next step is to contact Iolo Technologies (publisher of System Mechanic) and see if they’re ever going to resolve this issue (ref. Bryan York’s comment that “System Mechanic damages SAPI in some weird way.”). I would sure like to find a “lasting” solution since I don’t want to give up System Mechanic and I really enjoy FS2Crew for my PMDG J-41, Leonardo Maddog, PMDG 747 & Level-D 767… and hopefully soon PMDG 737NGX.
  11. Thanks, Jim. I'll follow your suggestions for trouble shooting the freeze-ups. I also removed my system specs from my signature and moved that info to my profile page. That makes a lot more sense and is a good way to inventory your "hangar" of FS hardware and software.
  12. I get system "freezes" almost every time I fly. The freezes can occur during almost any phase of the flight (as early as taxiing, but usually after I'm at cruise level). It happens with the feelthere E-jet v2 Embraer-175, the Maddog MD-83 and the Level-D 767-300. Once the lock-up or freeze occurs, if I don't touch anything (i.e. no mouse clicks or keyboard entries), the system will "thaw out" (aka un-freeze) in about 8 minutes. Everything is then fine again. On rare occasions, I'll have two freezes during a flight. My flights are normally less than three hours. I've just been putting up with it. I do tend to run a ton of FS add-ons (FS Commander, AS2012, STB, Radar Contact, FS2Crew, Track IR, DreamTeam, Orbx, EZ Cam...). I'm running two LG W2252TQ monitors on a eVGA nVidia GeForce GTX 560 Ti DS. My frame rate is normally very acceptable unless I'm in a highly detailed terrain (Orbx, Aerosoft US Cities X) with a good dose of broken clouds. I think I've upgraded my processor to about as high as I can (Q9650 @ 3.0 GHz) and expanded my Ram to 8GB. FSX sure would be more enjoyable without these freeze-ups. I, too, am very interested in anyone's thoughts. - Larry
  13. Interesting topic. When I add up the PC upgrades (CPU, memory, monitors, sound card), FS specific hardware (Yoke, Pedals, Throttles) and FS add-ons (Aircraft, Scenery, ATC, Crews, Passengers, Airports, Flight Planners, Training, Sound Sets and Utilities ad infinitum) I've got invested over the past 3 years in my FS "hobby", I could have been well on my way to obtaining my RW pilot's license. FS can be very addictive to many. And like playing with toy trains as a kid, I always wanted to expand my layout, scenery and rolling stock. But unlike my toy train world, FS offers the challenges of RW flying and the spectacular RW scenery some developers (like Orbx) have created. Did someone say additction? I still have so many places I'd like to fly to and so many planes I'd like to try out. And I've been addicted since I first booted up FS on my C-64 some 25+ years ago.
  14. The "Duh" factor finally hit me. I selected another theme (dah) and it installed successfully. I don't know what corrupted my "custom" theme that I've been using for a long time, but I'm gald the themes install without any problem now. Hey, I got myAS2012 moved out of the x86 folder so it wasn't a total waste of time. Thanks again Dave for the suggestion.
  15. Thanks Dave. My UAC is indeed off. I installed AS2012 onto another drive in it's own folder (and removed it from the "X86" folder on my C:\ drive). Good suggestion. Didn't solve the problem, but it's still a good suggestion as I've read elsewhere "X86" is not the best place for FSX programs. I have no idea what the AS2012 errors about missing runway 11, 12 and airport parking .dds files is referring to.
  16. About a year ago, I bit the bullet and re-installed Windows 7 as a last resort to get FS2Crew Voice software to work. Painting my house would have been easier. But Bryan was right, re-installing Windows solved whatever the problem was and I have been emjoying FS2Crew add-ons ever since. As I have been a user of System Mechanic for years, it's possible System Mechanic had something to do with my problem last year. I have continued to use System Mechanic since then and have not had a problem with FS2Creww add-ons. Until today. Last night, I ran a System Mechanic "Deep Analysis" followed by a "Repair All". This took all night. Everything seemed fine until I tried to fly my Maddog MD-83 w/ FS2Crew. The FS2Crew starts properly, but the Voice button is not illuminated and will not stay illuminated. No FO actions or voice either. This is exactly what I ran into a year ago. I then tried my PMDG J-41. Same problem. I'm distraught. I'm about to try the System Mechanic "Safety Net" feature to see if I can rescue myself from this disaster. If that doesn't work, I'll be contacting System Mechanic support next week.
  17. Recently I have been experiencing "Theme Installed Failed" when I execute "Install AS2012 Graphics" after loading my flight plan. Part of the AS2012l og_export file reads: Error converting file to GFX: C:\Program Files (x86)\HiFi\AS2012\Data\Airports\runway11\\runway11.dds - Could not find file 'C:\Program Files (x86)\HiFi\AS2012\Data\Airports\runway11\runway11.dds'. Error converting file to GFX: C:\Program Files (x86)\HiFi\AS2012\Data\Airports\runway12\\runway12.dds - Could not find file 'C:\Program Files (x86)\HiFi\AS2012\Data\Airports\runway12\runway12.dds'. Error converting file to GFX: C:\Program Files (x86)\HiFi\AS2012\Data\Airports\airport_parking_space\\AirportParkingSpace.dds - Could not find file 'C:\Program Files (x86)\HiFi\AS2012\Data\Airports\airport_parking_space\AirportParkingSpace.dds'. I've never run into this problem before. I just installed SP1, but the problem still exists. No matter what Flight Plan I load, the result is the same: "Theme Installed Failed". I'm about to try re-installing AS2012, but I'm curious as to what might have caused this or if anyone else has run into this issue. Thanks.
  18. I second the motion. The J41 isn't for everyone. I saw more than my fair share of engine fires before I got through the learning curve. Once you've "mastered" flying the J41 solo, you'll find FS2Crew makes the J41 a pleasure to fly and, for some, their new favorite aircraft.
  19. Thanks. That's good to know. I use FSDreamTeam's GSX push-back feature a lot which requires engines off and GPU disconnected. I then do engine start using batteries only. After discovering I had to re-enter my FMS data when I do this, it soon became my practice not to program the FMS until after push-back and engine start (which wastes time and fuel). Now I can input the FMS data before the Turn Check where it belongs. This reminds me of another question I have: While the GSX works great with the PMDG J41, does this plane use push-back very often in the real world? I normally have the room to begin taxing without push-back assistance. I just like using the GSX push-back feature. It's fun to see how well it's done (great job Umberto!)
  20. Ground clutter it was. Tilt adjustment worked. Thanks, DanW! Also, I have FS2Crew as well and it works just fine with the W 500 radar installed.
  21. After installing Reality XP WX 500 Weather Radar, I noticed that the J41 had it installed without needing to run the configuration utility. However, the results are quite poor as the attached picture demonstrates. Before I run to Reality XP support, has anyone else run into this?
  22. I recently ran into an issue while flying the Leonardo Maddog (2010) at night. When I switch from the 2D panel (F10) to the VC (F9), most of the instrument gauges turn white after only a few seconds. Attached are the before and after pictures of the VC. I'm running FSX w/Accel, FS2Crew, EZdok, TrackIR v5 and Active Sky 2012. I don't think ithe add-ons are the cause as I tried a night flight with the Maddog without any of the listed add-ons and had the same "white-out" problem. Perhaps it's a behind-the-scenes add-on such as my "AddOn Converter X" by FlightSimTools.com. Any suggestions of what's causing this and how to fix? Thanks.
  23. I prefer to set up my aircraft in the "Cold and Dark" configuration. The FSX Carenado C208B defaults to engine running upon loading. Following the Caraendo "Shutdown" procedure from the manual, I should feather the prop. Can the prop be feathered? If so, how? I read elsewhere in this forum that setting the park brake on this aircraft automatically feathers the prop, but I don't see any visual confirmation of that. I can move the Power lever below the notch and into the reverse position (F2), but how do you move the "Propeller 1 Control" lever (teal-colored lever) below the notch into the "FEATHER" position? It also doesn't appear that the prop has any pitch animation, which is unusual for Carenado to omit. Maybe I'm being too picky, but attention to details is one of the reasons I love Carenado GA aircraft.
  24. Hi Glenn. I'll be interested in any routes you may come up with. I'm still on the J41 learning curve (I'm down to only an occassional engine fire due to pilot error, i.e. me) and I have the Blue and Gold NA Orbx sceneries. My brief perusal of the Orbx website forums left me quite confused so I'm glad to see a Orbx forum at AVSIM.
  25. Thanks. I forgot (I wouldn't dare say I didn't know) to try pushing down on the mouse's scroll wheel. That's all it took. Problem solved.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.