Orlaam

Members
  • Content count

    2,361
  • Joined

  • Last visited

Community Reputation

71 Good

About Orlaam

  • Rank
    Member - 2,000+

Flight Sim Profile

  • 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,048 profile views
  1. I think it is important to note that this is not a matter of gun control. It is a societal problem, and one that requires scrutiny of environmental concerns. People need to understand that fully automatic (select-fire) rifles were extremely cheap prior to the FOPA ruling in 1986. This effectively made the sale or manufacture of select-fire weapons as new to civilians a felony. Only the circulating select-fire weapons on the street could be sold via a process of registry regulated by the ATF and therefore was a transfer sale through the government. Those weapons are upwards of 15,000 dollars or more, depending on the model. Middle-class America has become priced out of the machine gun game. However, prior to 1986, M16s and other combat rifles were readily sold for as little as 500 USD. Now, it's a little funny that legally owned machine gun were not used in crimes before or after 1986. Only one case of a law enforcement officer (or retired - don't recall) had been documented as using a legally owned select-fire weapon. Any machine gun used in crimes in the US have been illegally owned or modified since the beginning of time. But again, doesn't anyone find this a little odd that so many battle rifles were in circulation in the 30s, 40s, 50s, 60s, 70s, 80s, and 90s, yet only in the last 20 years have we seen an increase in mass shootings. Is it the desensitization of the internet, the realism of battle-style games, and violence in movies? I think there is much more at play than people want to admit. To blame guns when guns have been around for ages is ridiculous. Yes, we have had some mass shootings in the years prior to 1990, but this is a whole different level of violence. And you can't say that what is available now is much different. Like I said, fully automatic M16s in any flavor were around since the late 60s. No different than we see here.
  2. I did two flights today with the updated version. Prior to the update everything worked fine. Today in the -800 I had a minimums call at 30 feet when my baro was set for 200 minimums. Then in the -700 tonight, landing in PHX on RWY 26, baro set to 251 for ILS, I had no callout and the green indicator for the minimums was nonexistent. I couldn't even dial it in after landing and the altimeter was set correctly. Why am I having problems I never had before with the minimums call and recognition? I kinda think I missed some call outs on final too, which has been an issue in the queen. All other sounds work fine. And this is the only add-on that seems to have sounds missing now. Aside from that, even the baro setting was ignored on the PFD. I got the number but not the green triangle on the tape. ??
  3. Sorry, I've been busy and haven't even been able to open the sim. Work :-/ Anyhow, it's option one. I load a default Cessna for example, click on the add-on menu (e.g., FSUIPC, Active Sky Wx request ...). I mouse over the Reality Xp and select the option to setup aircraft. At that point it minimizes the sim. Windowed or full screen, it doesn't matter. Nothing even happens except for a minimizing of the sim from full screen. Windowed mode doesn't minimize, it just shuts the sound off, bringing the desktop to the front per the task manager, if that makes sense. In other words, that menu does nothing for me in FSX:SE. The only thing that works is if the gauge is already installed and I shift click on the top of the GNS to set up the options per the manual. Make sense? If you still need that log I'll try and run it today later when I get time.
  4. OK but that was what I tried doing. Adding to a default Cessna. It won't do it with the menu utility. It just minimizes the sim to desktop. I'll look at the log.
  5. I am unable to add the RXP GNS to a default plane in FSX:SE. It simply minimizes the sim when I select from the add-on menu. I tried windowed and full screen. I am able to get this menu in the A2A Comanche, but apparently adding with the menu in the sim does nothing.
  6. I will try it tonight. I haven't had a lot of time. I'm not doubting the GNS, the old GNS in FS9 was perfection. I'd still like to see the A2A GA work well with it too. Since DF is no longer a player, I don't too own many other GA add-ons now.
  7. I;m not seeing anything like that in any files. Seem to all be just window placement values in the panel.cfg. As an aside, I have the F1 GTN, and it does not have any deviation/tracking errors and updates rather fast, even in turns. The A2A Comanche AP is said to be archaic, thus won't negotiate hard turns in TRK modes, thus one must use HDG or ST to recapture the DTK, but the GTN will only overshoot a mile or two (IIRC) and reestablish pretty fast. This being tight turns. Less dramatic turns don't deviate as much. I don't see any values in the CFG files for this plane that would make any difference in the ability to track, regardless of GPS input.
  8. I know it's hard to tell, but essentially wanted to show how I had it set up and the modes. The second and third shot, where the GNS are popped up, are displaying that the desired track is 172, but the plane is wavering between 168 to 175 all the way from the 50 mile mark; the point in which I activated the approach. It never really settles on a HDG, rather fumbles around as if it can't capture it completely. In motion, you can see the plane list from side to side, like a boat in the water. Everything else is working fine. LPV is displaying on the G/S for vertical guidance and the CDI is being driven by the GPS. It's just the tracking that is unsteady. Thanks for looking into it!
  9. I haven't attempted this in any other aircraft yet. Here's what it's doing, back and forth about 5 or 6 degrees. I have no idea what you mean by my time scale. I don't use compression, and my values in the aircraft.cfg match yours posted exactly.
  10. Hi Nick, essentially what it does is S-Turns, but they are slow 3-5 degrees. Like a drunk person flying basically. FPS is locked at 30, totally not the issue. Later today I'll post the map view and show you. I meant to screencap it last night for posting, but was tired and forgot once the flight was over.
  11. Weird. I've done two flights so far, and both had this issue. It's subtle, but noticeable enough to be abnormal. Never had this before with any add-on, including the original RXP GNS. It's FSX:SE I'm using. I'm not sure how this could be corrected... ??
  12. I have noticed the lateral tracking is very unsteady. The plane will list from side to side between waypoints. This is maybe a 3-5 degree deviation back and forth, as if it never really stays on the path correctly. This is with the CDI/HSI slaved to GPS and GNS flight plan entered manually, not imported. It's not a weather-related anomaly either. Is anyone else noticing this problem? A2A Comanche, if that matters.
  13. As stated, the QOTSII does a much better of VNAV through the waypoints. Some STARs are a bit challenging for sure. Not knowing your destination runway makes planning tough at times. In the real world, most often you are vectored off the STAR at some point, maybe 30 miles out or sooner. But you are also given specific descent instructions. Make no mistake, you will be given a high approach my controllers in the real world too, but they are realistic to adjust to. A lot of pilots will tell you the old 3:1 ratio is now 4:1 with the winglets and slippery designed jets.