Jump to content

brent.houston

Members
  • Content Count

    17
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. Yeah, I'm seeing that as well - it seems different per plane, too. Like the X Cub HDG knob on the AP runs in 10 deg increments and the HDG knob on the G3X runs in 1 deg ( or vice versa ). It's been bugged a few times to zendesk, so I'm hoping for a fix down the road. I'd prefer not to clear bindings on all the Honeycomb panel switches ( which is the current workaround ) You can single click on the HDG knob to get 1 deg changes, but mouse wheel is randomly 1 or 10. ( I wonder if this is what's causing the NAV mode issue in AP - as it feels like it's over correcting by 10 degrees )
  2. I ran across this when trying to debug an issue that showed up after I bought the Mooney - wasn't getting any flight time logged. Turned out to be a problem with dev mode after the last patch and not the Mooney. While troubleshooting that, some guys had mentioned the avionics shutting off in the M20R, which I hadn't seen. The first time I turned off dev mode, the avionics failed, like everyone said. I ran another test with dev mode back on - avionics didn't fail ( and no flight time logged ). I decided I'd rather risk the Mooney avionics failing and get credit for flight time and turned off dev mode until Asobo fix the logging issue. I haven't had the avionics fail since then. One difference after noticing the issue, is that I was a lot more vigilant about making sure the switches on my Honeycomb were set correctly for however I was starting the flight ( engines running vs cold & dark ). Haven't tried to A/B past that - but also haven't had any issues since then, too.
  3. I'm really looking fwd to this for MSFS when it's ready. It made such a big difference in the immersion for P3D - you notice ships from such a huge distance away that it gives life to the environment much more than cars or anything else. I meant to mention this to one of the producers at MSFS as an official feature, as I think having the ships replicate in multiplayer would be key and I don't know what kind of support is in the SDK for that.
  4. It's about default level, to be honest. You can follow a real checklist and flick all the right switches and sorta use it as a procedural trainer - but it doesn't punish you if you do something wrong, or forget an item. That being said - I've only run across minor items and you don't run out of fuel halfway, like a couple of the default a/c. It seems a bit high on the performance... I'm flying a 182S IRL right now, and have never flown a 182T - but in my experience this one accelerates and decelerates faster than the real thing. I don't always bother to match weights, ( Carenado defaults to much lighter than I would fly - usually with 1-2 pax in back ) but I have loaded it exactly and it still seems OP. I've matched enroute flight times and it's pretty close... 1:45 IRL for one trip, and 1:41 in the sim with similar settings. So it might be ok for what you're looking for. Carenado does the best looking planes of any 3rd party developer, but systems are pretty much always default level. Don't expect A2A. Issues I've seen: Non-existent fuel cut-off valve is on, if you start cold and dark ( cut off is on the fuel selector IRL - not a separate valve like the default C172 ) - you need to hit ALT+V to open the valve. ( If you prime the engine w/o opening the valve - you still see fuel flow ) MP gauge on G1000 doesn't show decimals ( it does on XP11 and P3D ) Right Quick View doesn't work - shows Left Quick View I've had the AP go insane and try to flip the plane ( after active pause, maybe? - I think this is a global issue ) - normally works ok. Also, got stuck on 10 deg increments only on the Heading Bug part-way through a flight ( probably also a global thing ) - normally it's fine. This also seemed to affect the APs ability to capture a path
  5. This is my 3rd time buying it ( P3D, XP11 ) and I'm not regretting it. It's the closest thing to what I'm flying IRL ( C182S w half glass ) There's a bunch of little issues, but I'm still enjoying flying it and I'm not even that annoyed that there's no discount for previous owners - like Orbx's stuff.
  6. all the premium aircraft seem to be encrypted. there definitely needs to be a better solution for repainting!
  7. No docs here? .....\Official\OneStore\carenado-aircraft-ct182t-skylane-g1000\SimObjects\Airplanes\Carenado_CT182T_Skylane_G1000\Documentation also - be aware that if you're starting cold & dark, you'll need to hit ALT+V to open the non-existent fuel cut-off valve in order to start the engines ( although you'll see see positive fuel flow with priming - even if the cut-off is engaged ) verify your prop level position in the cockpit as well, before starting - as it doesn't always initialize correctly and will cause the engine to stall after a few seconds of running
  8. I had a similar issue on installing the Brasilia today. Updated GeForce drivers, reinstalled P3D, reinstalled the aircraft - same issue. Checked graphic settings and HDR was checked off ( from FlyInside VR override settings ). Checked HDR on. Fixed it.
  9. 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.
  10. 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...
  11. Active region in the FTX Central control panel? Fire that up to make sure whatever region you're trying to test is active.
  12. 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.
  13. 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.
  14. 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. "
  15. 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.
×
×
  • Create New...