brent.houston

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

1 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  1. Not really. Default FSX/P3D scenery in a flat area - not showing the horizon vs XP with addon scenery. Anyone with P3D + ASN and Orbx or Megascenery could match that. Apples to apples, please. I keep all 3 sims around for comparison, and find myself using P3Dv3 the most ( by far ) right now and XPlane the least ( by far ). XP does a lot of things that I really like ( night, sloped runways, better default FDE and ground handling ), but I hate the UI / Menus with a passion and I don't get much better performance than P3D. The fact that the majority of my high-quality addons for FSX work fine in P3D is no small factor. Shared cockpit / MP is another factor, although I don't use it as much as I'd like. I find the endless FDE arguments kind of amusing - at the end of the day, you're still sitting in an office chair, staring at a 3' wide screen with a chintzy plastic joystick/yoke w no force feedback and complaining about how "unrealistic" the flying is.
  2. brent.houston

    PC12 for Prepar3D v3

    You can regedit the path to trick the installers ( works for scenery as well ). If you've had boxed FSX and FSX-SE installed, I changed those both values of those as well ( just while I was installing aircraft / scenery ) Disclaimer: If you don't feel comfortable editing your registry, DON'T. 1. START > regedit 2. HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node 3a. > Dovetailgames > FSX ( if you have FSX-SE installed ) 3b. > Microsoft > microsoft games > flight simulator > 10.0 ( if you had FSX boxed installed ) 3c. > Lockheed Martin > Prepar3D v2 ( if you have/had 2 or 2.5 before ) 4. double click on SetupPath 5. edit the value to your current P3D v3 root directory 6. DON'T FORGET TO CHANGE PATHS BACK after your finished installing. If you're removing 2.5 for good, then you can leave the setup path pointing to P3D v3 ( leave the reg entry and folder for Prepar3D v2 ) Again, registry mistakes can lead to "Bad Things" TM - proceed at your own risk. I don't remember having an issue with the PC12, but this solved most of my other install issues with P3D v3 Hope that helps...
  3. brent.houston

    ORBX removing scenery on P3Dv3

    Active region in the FTX Central control panel? Fire that up to make sure whatever region you're trying to test is active.
  4. brent.houston

    How do you get around the VC

    SPACEBAR + Mouse/Mouse Wheel? ...or are you dealing with a homebuilt cockpit situation? "A" cycles between preset camera positions in the cockpit or cabin, if you're in VC mode. You can still use the mouse to look around/interact in any of the preset views. I also map the NUMPAD keys to move the camera position in the Virtual Cockpit ( + / - raise and lower your "head" position, mostly ) I find that too many aircraft have the default camera position way too low.
  5. brent.houston

    Why FSX/P3D over FS9?

    Not really... The seaplane and helicopter stuff haven't really improved. Better than nothing, but they need an overhaul along with the base FSX/P3D flight modeling and aircraft ground handling. P3D is exactly FSX ( from an experience standpoint ), with better lighting and shadows.... and much worse menus. P3Dv3 seems more stable and feels smoother than previous P3Ds and FSX/FSX-SE. The HDR lighting, cockpit shadowing and cloud shadows are not to be underestimated. You'll notice that pretty much every 3rd party developer takes screens and video out of P3D now. It's still CPU limited, like FSX and you can only throw so much video card and RAM at the problem. Probably the main argument to switch over, is 3rd party content - FSX/P3D is still over 80% of the flight sim market and that's where the money/quality addons are. Most FSX addons work fine with P3D, although you might have to tweak the install process for older content.
  6. brent.houston

    Weird "Gear Down" warning behavior

    This is probably the same bug as: http://www.avsim.com/topic/461523-gear-down-warning-and-no-steering-on-ground-partially-fixed/ I wasn't getting a gear horn, but the warning light and no nose steering... "Just to add my two cents. I hadn't seen any problems with the Saratoga TC in FSX or FSX-SE, but starting seeing the gear warning/nose steering issue when I brought it into P3D v3. After a couple tests in P3D, it seems the the failure will trip anytime you exceed VLO/VLE in any configuration. If you stay below VLO the whole flight, you shouldn't see the problem. If you do - a quick ingame fix is to go into the Vechicles/Failures Menu and click RESET ALL FAILURES. You should be fine until you exceed VLO again. Can anyone else confirm? I don't know why I'm only seeing this in P3D, but it seems like a solvable issue without having to turn off collisions or your gear warning altogether. "
  7. This is probably the same bug as: http://www.avsim.com/topic/461523-gear-down-warning-and-no-steering-on-ground-partially-fixed/ Just to add my two cents. I hadn't seen any problems with the Saratoga TC in FSX or FSX-SE, but starting seeing the gear warning/nose steering issue when I brought it into P3D v3. After a couple tests in P3D, it seems the the failure will trip anytime you exceed VLO/VLE in any configuration. If you stay below VLO the whole flight, you shouldn't see the problem. If you do - a quick ingame fix is to go into the Vechicles/Failures Menu and click RESET ALL FAILURES. You should be fine until you exceed VLO again. Can anyone else confirm? I don't know why I'm only seeing this in P3D, but it seems like a solvable issue without having to turn off collisions or your gear warning altogether.
  8. Just to add my two cents. I hadn't seen any problems with the Saratoga TC in FSX or FSX-SE, but starting seeing the gear warning/nose steering issue when I brought it into P3D v3. After a couple tests in P3D, it seems the the failure will trip anytime you exceed VLO/VLE in any configuration. If you stay below VLO the whole flight, you shouldn't see the problem. If you do - a quick ingame fix is to go into the Vechicles/Failures Menu and click RESET ALL FAILURES. You should be fine until you exceed VLO again. Can anyone else confirm? I don't know why I'm only seeing this in P3D, but it seems like a solvable issue without having to turn off collisions or your gear warning altogether.
  9. brent.houston

    PC-12 Bug List/Issues Found

    I hit about 5-6 minor bugs on the first flight 1. Top 500 screen goes black with Panel Lights on ( known issue ) 2. A/S indicator drops to zero above 12,500' or so ( inconsistent - doesn't always happen ) 3. Avidyne stops refreshing position after awhile ( cycling to a different page updates it ) ( 500s keep accurate position ) 4. Bottom 500 - wasn't able to tune NAV 2 radios ( inconsistent - doesn't always happen ) 5. GEN 1 Switch won't [Left click] or [ mouse wheel ] off - you can [Right click] and shut it off, but the switch indicated the on position 6. When changing time of day ( FSX World menu ) in flight, panel completely freaked out ( didn't keep correct panel state, even though switches indicated correctly - had to cycle everything on the overhead panel ) 7. When loading a saved flight ( already in game - loaded from cold n dark flight to running at hold short flight ) all test modes appeared to be stuck on - every warning and pusher was going off. Cycled test buttons to fix it. 8. Cabin lights ( known issue ) All and all - I like flying it ( after figuring out proper approach attitude and landing speeds ), looks great - can't wait for SP1 The approach attitude does seem steep, but then the r/w Cirrus seems steep to me too.... so.... ( Also, I realized the default payload is single pilot and nothing else, and I fly with 50% fuel - so the thing leaps off the runway / balloons like crazy if you have any speed while adding 40 flaps. )