Jump to content

StewartH

Members
  • Content Count

    814
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by StewartH

  1. Yep, that's what I did last night. Thanks for the advice, sir. That's my impression, as well.
  2. Stated this way, I guess it makes sense, but the Cessna 310R from Milviz has a taxi light on the nose wheel and landing lights on the wings, and those aren't so small engine nacelles on that bird. I'm still confused about the statement in Frank's post about the update that the landing and taxi lights were inverted. This is where I'm confused, I guess. Did my dl in 2017 include any kind of correction, or was the original configuration actually correct? Or what? Hard to say two years after the fact. And taxiing at night, I want to see the guidelines on the taxiway--the nose light highlights it perfectly, the lights on the wings do not.
  3. It makes sense that the landing lights are on the nose wheel? That's not the case with the Cheyenne II--the landing lights are on the wings, the same company that made the Malibu.
  4. Now I'm confused, sorry! FDEdev says the lights are correct. Frank's post seems to imply the original issue has been updated by a service pack. I downloaded an update from PC Aviator which allowed installation into P3D--that is, it was an update for installation into P3D dated 7/12/2017, since my original purchase was for FSX. Wouldn't this update have corrected the issue? Then again, maybe not, and I need to find that update.
  5. Is it the case in RL that this aircraft's landing light(s) are located on the nose wheel and the taxi lights are located on the wings? This is backwards, to my way of thinking, yet this is what I observed last night in preparing for a night flight out of KMRY Monterey. Can someone perhaps point me to a fix that's been posted, or perhaps a correction someplace in the aircraft.cfg, please? Thanks! Stew
  6. Hi, David. He also works ATC in Chicago, as does the wife. Different sections, though. He has a video "I Love My ATC" in which he and his wife are in comms while he's enroute to someplace or other.
  7. All good points, Frank. I only remember his remark about the wonky gauges, so it stuck with me. Stew
  8. I found the video absorbing and very interesting. I kept comparing my panels and switches to his! Wish I could color-code my switches as he has done. He also explained why his mixture levers are offset the way they are--"fuel pressure gauges are wonky." Worth the watch, definitely. Stew
  9. Thank you, Bill. I appreciate your insights into the Cheyenne.
  10. I'm curious why there are two "on" positions for the fuel pump switches in the Cheyenne II, one "1" and the other "2"? When does one use "1" and when "2"? Both positions work, obviously... Stew
  11. Thank you for the update, Bill. Enjoying flying this bird. Stew
  12. Success starting both engines after Bill's advice--no more engine fires, although they looked pretty cool! Also a tweak that allows ATC to refer to the Cheyenne properly: [General] atc_type=Piper atc_model=PAY31T Cheers! Stew
  13. Thanks for the reply, Bill. No problem waiting for your reply. This could be the key to the problem and warrants a closer look. Thanks again. Stew
  14. I'm doing something wrong. I can successfully start the left engine, but I've had two right engine fires on successive startup tries. The fire looks really true to life, but darned if I can get a successful engine start, using the same sequence that I used with the left engine. I'm following the Checklist as best as I can see, so what should I be looking out for? Anything to especially pay attention to that I may have forgotten?
  15. Thank you for this, David. It works well, but accessing the control panel took some searching to find the .exe. It is now pinned to the taskbar in case I need to make adjustments.
  16. Looking forward to the new Moo. Any predictions about the Conquest II?
  17. Frank, I used your sound fix for the Altitude Alert in the KAP 140 for use in the Twin Comanche. It's the same sound file, SND24.
  18. I posted this over at the Milviz Support Forum, but thought it might find interest over here: If you insert "PA30" (no quotes) after atc_model= in the [General] section of the aircraft's aircraft.cfg, like so: atc_model=PA30, then ATC will correctly identify you to other aircraft as "Piper Twin Comanche", rather than "Piper <blank>". Cheers! Stew
  19. Thank you, Scott and Frank. I recall watching that video several months ago, but didn't realize it also had to do with Saitek's "Multipanel". Thanks again. Stew
  20. Can either of you fellows, Scott or Frank, explain what you mean by "using the Multipanel"? Does this have anything to do with FSUIPC and a throttle/yoke setup, which I do not have? Just curious, while I'm following this thread. Thanks. Stew
  21. Has anyone else noticed this? Hovering over either L or R fuel supply needle, the pop-up label is incorrect, i.e., the label doesn't reflect the quantity the needle is pointing to.
  22. Yes, I saw the exchange there. Glad you got it sorted.
  23. Have you expressed your concerns over at the Orbx Forums? I haven't seen anything over there that suggests CTDs in P3D4.4 are related to Orbx products, and I myself have not experienced any such CTDs.
  24. Ok, but doesn't FSX have something similar regarding prop settings or feathering? I've forgotten.
×
×
  • Create New...