Orlaam

Members
  • Content Count

    2,439
  • Joined

  • Last visited

Community Reputation

98 Good

1 Follower

About Orlaam

  • Rank
    Member - 2,000+

Flight Sim Profile

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

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    KPHX

Recent Profile Visitors

3,723 profile views
  1. The ultimate power off landing. When I was a kid I had this really neat shuttle book that had tons of information in it. I think it was actually published by NASA. I still remember the day class was interrupted in junior high, and we began watching the awful coverage of the Challenger explosion. I always liked the Shuttle launches as a kid. Not as remarkable as my mom's generation with lunar landings, but interesting nonetheless. I used to hear the Shuttle communicate with amateur radio operators on 2 meters. I never tried to get involved into communicating with them. Too much traffic. I did talk to Barry Goldwater though, for like 60 seconds, then the frequency (2 meter simplex) was nothing but heterodyne 🙂
  2. I posted in the VC brightness thread, because I have no idea how to match the brightness in the A2A Bonanza (eventually A2A Comanche and RealAir Duke as well) across both 2D and VC views. But in the meantime, how do I click close the 2D window? I'm in FSX:SE. I can click the left bezel in the VC, but I'm used to clicking on the actual 2D window somewhere to close it, especially if it's covering the VC version. And how can I resize the 2D window without losing aspect ratio but having a more normal size, as it's rather huge on my screen. I realize I can resize with the mouse, but that's not permanent or accurate. I have looked at the topics on this, and none really make much sense to me. Thanks
  3. Makes no sense to me. 😐 What exactly are you adding or changing to match the VC and 2D brightness? In the Bonanza (A2A) it's way too bright in the VC but changing it in the GPS makes the 2D dimmer. In the manual the NO_BEZEL option sounds as though you are losing the border of the GPS if you add those entries. Does this deactivate or alter the buttons and knobs on the bezel if you add a NO_BEZEL entry? If I could actually see the entire thing I'd just copy it. I assume once it's fixed you can use the brightness in the GPS menu like real life and have it stay the same across both views?
  4. Orlaam

    VNAV Utility

    The VNAV feature is similar to a jet with respect to display info. Enter an approach mode, under PROC from the HOME screen. Select the airport (if not planned) and desired APP. For ILS it'll enter waypoint altitude constraints on the screen and into the VNAV utility. It'll place a TOD on the screen as well with the next waypoint altitude. You can adjust the V/S by entering your own at that point or use 3.00 degree standard. I found it difficult in the Bonanza because maintaining the correct V/S through the plate into the ILS was hard. Somehow I ended up high. I think it works better in a GA if you can just select a FAF and descend to it, or if you are in a plane with more precise V/S entry. Maybe with practice I can work though the VNAV process in a simple plane using it, but I might look into just tweaking the V/S or selecting a VCALC method if possible. If you enter a flight plane, you will see on the FP screen with the waypoints that you can enter altitudes. That would be where the VNAV would come to life, or perhaps the VCALC is available if you just enter a fix and altitude (even the airport). I flew into KABQ and prior to selecting an approach in the PROC page, I noticed that KABQ had an altitude box on the FP page for entry. You can even adjust the altitude based on temp and density it looks like.
  5. These may, or may not, be bugs...FYI. I can post screens if needed. The standby analog altimeter displays a slightly different altitude than the plane. I was at FL390 and the standby displayed FL39150. Both obviously set to 29.92 (synced). The MCP LCD digits are sometimes the same color as the older non-LCD digits (not blueish white but that dull yellow color). Maybe a graphics glitch in my computer (e.g. driver)? I don't have this kind of issue anywhere else in any other plane or program though. If I turn the MCP LCD on and off a couple times it sets it to the correct color. The RAAS no longer shows up in the FSX menu or even loads in the freighter model. Someone said it works on the PAX version and selected other models. Still an option in the FMC either way. Also, this may totally be my fault, but I was unable to load Wx from Active Sky. I predicted some precip on the route from ORD to ATL, but I didn't see it. Nevertheless, I wasn't able to link the COMM to load winds. It simply said NO COMM and gave no option to load weather for the route or descent. I need to look at the settings again in the PDF maybe. I saw an option to create a WX PLN file and don't recall what that is for. I just know it always worked before.
  6. I was gonna post this as well. Flew the 744F to test the new update. No RASS. Thought it was removed but the option is still in the FMC. No longer in the FSX menu though.
  7. Orlaam

    [23SEP18] FSX 747 Users: URGENT READ THIS

    It worked without hiccup! 😊
  8. Orlaam

    [23SEP18] FSX 747 Users: URGENT READ THIS

    Thanks! Will try again! 😀
  9. I think it's both FSX and FSX:SE. I can't say about P3D. Have yet to see a P3D complaint.
  10. Got a reply from support. They're investigating the issue. w00t! Send in support tickets or await an official post from PMDG, as it sounds like it's not just operator error. 😉
  11. That would require installing the previous edition though, yes? Not that I'm opposed to that, but what a hassle. I'm gonna run out of activations soon and need to reset.
  12. It's just the act of installing the new 744 update, not the -8. You can't run the -8 if the -400 won't activate. Mine says 3.00.9008 in OPS Center, but no dice running the sim without the error dialog.
  13. That is weird then. Obviously not solely a FLEXnet problem inherently; If people are able to revert to the old version and it works. I tried almost everything. Uninstall two or three times. Uninstalled NGX and reinstall to "correct" FLEXnet service. Reboot using MSConfig and no MSSE or extra apps running. Only thing I didn't do was strip out the leftover files manually or deactivate the license since we are told not to, and frankly, having to reset my camera positions and extra liveries would not be fun.
  14. The running theme seems to be FSX:SE. I have all the simconnect packages installed, so it's not that.