Jump to content

amahran

Members
  • Posts

    419
  • Joined

  • Last visited

  • Days Won

    3

amahran last won the day on January 21

amahran had the most liked content!

About amahran

Recent Profile Visitors

6090 profile views

amahran's Achievements

Rookie

Rookie (2/14)

  • Reacting Well Rare
  • Dedicated Rare
  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

438

Reputation

  1. After SU5, the issue is still ever-present. I tried to diagnose it and calculate it based on my inputs. Speed bug is at Mach 0.74, its position on the IAS scale agrees with the Pressure Altitude and the SAT. Current Mach (0.766 in white above the speed scale) and TAS agree given the Pressure Altitude and SAT. TAS and IAS disagree given Pressure Altitude and SAT It's the position of the IAS value on the scale (where the arrow is) that's incorrect, not the speed bug.
  2. Seconded, the zigzagging at high altitudes (i.e., the description below) still happens as of the latest version on the marketplace (as of Jul 24).
  3. Seconded this issue, although I have seen this issue even when the switching from IAS to MACH is done automatically at 31.5k, not just when manually switching
  4. I have a minor comment on a bit of a gripe, since I work all day with helicopters with giant rotor disks. The prop animation seems particularly "step"-y, transitioning from one phase to another to a third abruptly with no smooth transition. It's a bit jarring, especially when that effect is connected to FSX's turbofan animation (slowly spinning or spinning at speed, no in-between). It takes me out of the moment, unlike in reality where there's no visual change that registers in your brain as a "step"; real rotor disks get faster and faster and slowly get blurrier and blurrier to the naked eye until, well, they're at speed. I'm not sure if there is a solution yet to better blend this animation, but if it's possible, it would make prop planes far friendlier on immersion.
  5. Is this a vendor/host agreement that Aerosoft can push updates and new items to the store at their own discretion? Or is that just a product-level approval (i.e., each product requires explicit authorization for this level of delegation)?
  6. You know, we're supposed to stay home for Canada Day, so a CRJ900/1000 release by then gives me the perfect excuse anyways!
  7. Likewise. The routes I like flying are serviced mostly by 900s, and I love the tiny bit of performance challenge it carries for hot high and short runways.
  8. Move the camera in the cockpit using the arrow keys, so you’re looking at the panel. Get more comfortable with slewing/moving the camera. Of course it’s impractical to use the fuel panel from the left seat; that’s like trying to change thermostat from the couch without getting up.
  9. Have you flown a CRJ to compare it to something, though? This is all kinda moot, is simmers can only really have previous sims as a baseline.
  10. Good to hear that it's been resolved! I was seriously wondering how Hans had programmed the curve and was contemplating lending a hand in building him a FADEC, but I'm happy to hear the issue was a lot simpler than that!
  11. Was asked to add to this: the displays all freeze when full forward elevator is applied. In this example, climb power is applied but you can see N1 is at 21% on the CAS (the sim isn't frozen, and the engines were most definitely producing climb power. I'm also getting cautions about takeoff config):
  12. This is a bit of a bizarre one: When I moved my joystick (Microsoft Sidewinder FF2) to its absolute forward limit, the screens all freeze. Here's an example of the aircraft on the apron with controls full forward, then applying takeoff power: Then when I bring the joystick back from max fwd: Is it possible that maybe there's a bug on the flight control page that's causing this? E.g., the display being programmed for axis range -1.00 to 0.99 but not 1.00? I don't know how you coded your gauges though, but if it's that simple this could be an easy bug to fix:
  13. As shown in the screenshots below, the strobing of the beacon light is visible in the cockpit, more specifically on the limitations placard: EDIT: More specifically, this is with v1.0.0.1. I'm not sure if this was present in v1.0.0.0
  14. One more; this one I took with faster reaction times, but the planes slipped in Google Earth before I could take the snapshot. Once again, you see the same thing; the traffic is displayed on the ND at half the actual distance.
  15. Tried to take a better picture. Actual distance of 7.4 miles, ND shows roughly 4 miles. Mild inaccuracy as the planes kept moving while I was taking these screenshots over the course of maybe 10 seconds? : EDIT: Another one: in the exterior view I can see the aircraft is right over the threshold of the runway shown in the ND. The TCAS target however is halfway between me and the runway:
×
×
  • Create New...