Aerosoft official retail partner for Microsoft Flight Simulator !! 
Click here for more information

Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


giltender last won the day on June 16 2019

giltender had the most liked content!

Community Reputation

12 Good

About giltender

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I can't think of anything that doesn't require an EXEC other updating the fuel. Last time I flew that -200 sim in Toronto the screen exploded onto the cockpit windows. lol
  2. When I am setting up an ILS approach we are usually still in cruise and in "white needles" or FMS navigation. the RTU's are usually in auto tune mode which means they automatically tune available nav aids in range as a backup to GPS navigation. I like to use the radio page in the FMS for entering ILS freq's as well as squawk codes simply because its faster. Once you enter a freq in either the FMS radio page or RTU primary spot, the radios switch to manual mode. We put the same ILS freq in both active NAV 1 and NAV 2 and each sides MFD displays its respective NAV side for redundancy. NAV 1 on the left, NAV 2 on the right MFD. you still have a backup freq you can use for a VOR for a missed approach in the RTU. You get the "preview" blue needles when in FMS NAV mode with a valid and identified ILS freq tuned on the RTU. Once the controller puts us on a heading for vectors we usually switch to green needles. Only the 900-NG version auto switches from white to green needles on its own. Let me know if you have further questions Mike
  3. It's not a new thing. The FMS doesn't handle edits very will at this point. I've had the above scenario happen to me. It also is not adding the proper discontinuity's or transition way points on some approaches. Now that they have the CTD problem with Navigraph fixed I hope the team has more time to address these FMS issues. Mike
  4. I am playing with the demo right now. Looks like it has a ton of potential so far. I am however having trouble getting the FO to say the following items in my custom checklist. [ ] fms initialization -- complete (he just says fms) [ ] glare shield -- checked (can't say at all) [ ] EFIS control panels -- checked //1 checked right (say's "E control panels) [ ] upper pedestal -- checked (doesn't say pedestal) [ ] m l g over heat -- tested (misses the word "over) [ ] thrust lever quadrant -- checked (doesn't say quadrant) [ ] lower pedestal -- checked (doesn't say pedestal) am I doing something wrong or can they be added to the vocabulary? Also is there a way to have him say a response other than what I say. for instance circuit breakers - I say "checked left" and then have him say "checked right" in response? Thanks, Mike
  5. The sound set is actually pretty good. AS has nailed the sound of everything going quiet when you hit the start button as the packs come off. You don't hear the engines at all in the RJ. In the real aircraft, when you hit the start button until starter cutout (N2 50%) is usually 30 seconds or so. After that, the rest of the start takes another 20-30 seconds so your looking at almost a minute for each engine to start and stabilize.
  6. wwittkoff, The reasoning behind staying up high as long as possible and then making a steeper decent further along the route is for fuel savings. You burn a lot less fuel at high altitudes and the longer you are able to stay up there the less you burn. The ideal decent is a steeper and constant decent with power idle the whole time and no speed breaks down to the start of the approach. This isn't always possible due to the altitude and speed restrictions on different sids and of course ATC instructions for spacing ect but that's the goal. Just got back from a 4 day pairing and I watched the bank angle as the autopilot was making turns. It will turn a maximum of 30 degrees without 1/2 bank selected and 15 degree's with it selected for those who are wondering about the aggressive turns in the sim. Hoffie3000, in your screenshots the FMS is displaying what we call a devils tail. It is a result of the waypoint being an "overfly" waypoint denoted on north american charts as a star with a circle around it. This essentially means the procedure calls for the airplane to actually fly over the waypoint rather than smart turn before it as it transitions to the next fix in the legs page.. the autopilot should fly the aircraft over the overfly point and start a turn in the direction of the devils tail and then attempt to get back on course to the next waypoint using 30 degree bank turns. Maybe this is what's causing the strange turning behavior in the sim. The waypoint "STTIK" on STTIK 4 SID in ksfo is also an overfly waypoint and the FMS doesn't seem to know how to handle it properly. Mike
  7. I notice this happens as well. I fly the real aircraft and it smart turns using a method similar to what GEK describes above. The faster you are flying and the larger the turn the earlier it starts its turn. It doesn't however do this in green needles and Han's is correct, You need to be very careful with your intercept speed. The real airplane will blow through the loc all the time if you are going faster than 210 with too great an intercept angle. My rule of thumb is to be at flap 8 and 180kts for a reliable intercept and capture. Also try flying the SSTIK 4 SID off runway 1L at KSFO. For me it makes the left turn at SSTIK and instead of doing the 180 and heading straight to the next waypoint it continues doing 360's over SSTIK.
  8. First of all, I want to congratulate Mathijs, Hans, and the rest of the Aerosoft team for developing such a great aircraft. It blows me away that you are able to replicate a multi million-dollar aircraft and its systems so accurately for an $80 product. I love how involved you still are in making this aircraft even better. I see you responding to questions and concerns on the forum within hours, and that’s a big reason why I am taking the time to write this. I have been a flight simmer for 20 years. I fly the CRJ-900/900NG for a regional airline in the real world, and I have had an opportunity the last few months to fly the real thing and then come home and fly the Aerosoft CRJ-900 version immediately after and compare the two. This has given me a great perspective on where the differences lie between the sim and the real thing. I have compiled a list of small things I notice that could be tweaked in the next update. I am not a programmer, and I am sure a lot of the things I am going to mention here are things you would love to fix but can’t because of programming issues, development costs, sim-ism’s, differences in my system ect. Maybe some of the things you haven’t thought of, or they weren’t caught by the original beta testers. Anyways, this is not me complaining about the aircraft at all. I really love it and you guys did a great job. It is simply me trying to help you guys create the most life like and accurate aircraft possible with this next update. For the record I am running P3D V4.4 with the latest CRJ update. I use Navigraph to update the FMS database and Pilotedge when I fly. I am going to break this down into two categories. Aircraft handling/characteristics and FMS/System differences. Aircraft handling and characteristics. Only two big things: I would say the biggest difference in how the real airplane behaves vs the sim is in decent. The real CRJ-900 does NOT want to go down and slow down. It is legendary how slippery this airplane is and managing the decent is really one of the biggest challenges of flying it. Descending from FL360 at 3000FPM with idle thrust you will still be accelerating all the way down and will have a hard time keeping it under 300kts. Speed brakes are pretty much useless until below FL250 because of the thin air and how small they are. I find the speed brakes in the sim WAY too effective. In the real aircraft I use a 12/12 rule to make 250kts at 10,000. The rule is at 12,000ft select 1200fpm (idle thrust/no speed brake) that will get you from 300-290kts to 250kts barley in time at 10,000. That gives you an idea how bad this thing doesn’t want to slow down. I find in the sim if you chop the thrust at 3000fpm you immediately start lose airspeed quickly. Most of the time I find myself having to use 50-60% thrust to mimic the rate and speed the real aircraft descends. In real life I am always at idle thrust while in decent and it still wants to haul ass. Second, I find the Sim aircraft performs too well in cruise at high altitude. I realize there are a lot of factors that determine this, but I usually have a similar fuel, pax load and altitude as I fly in the real world and the performance is much different. When you programmed the sim aircraft, I imagine you used Bombardier’s performance numbers which makes sense. I imagine these are achieved on brand spanking new engines in ideal conditions. A real world CRJ-900 fleet that is well maintained will have tails that average 8-10 years old. Those engines can get tired over time. In the real jet, in cruise from FL340-FL390 you will need 87-89% N1 and a fuel flow from about 1800GPH-1950GPH to maintain .78. It is very very sluggish at altitude, especially anything over FL360. Any small power changes can take 30 seconds to even see much of a change in airspeed. Not responsive at all. And to barber pole it up high would probably take everything it’s got. FMS/Systems Altitude windows on RNAV stars: when the FMS is loaded with a STAR, and that STAR has an altitude window at one of its waypoint altitude restrictions, its is displaying the top of the window altitude or above (A) as the target for VNAV. Example: a window between FL230 and FL200 the FMS is showing FL230A as default. As I’m sure you are aware, the real FMS shows both the top and bottom of the window like this FL230B/FL200A. I’m sure this was simplified to keep development time and cost down in the sim which is fine. While the real-world aircraft’s default VNAV target is still the top of the window (non NG) its not correct that it is an “above” altitude. If you’re not going to display both top and bottom altitudes of the window on the legs page, it makes more sense to have it default display the bottom of the window altitude and Above (FL200A in our example). Often, we will just hard code an altitude between the two windows to get more effective vnav info. The RTU volume knobs work backwards. Pushed out is muted, pushed in is on. All altitude and speed changes on the legs page should require an EXEC to take effect. Legs page Missing “cancel mod” option to discard any changes you don’t want to make anymore The last page of the legs page should be for the alternate flight plan The speed trend indicator is much too jumpy. In real life it is silky smooth FO’s side FMS Direct Intercept page doesn’t display the modified vertical path programmed on the legs page of the captain’s side. We often have these two pages up at the same time so we can see feet per minute requirements of waypoints further down the STAR. I don’t think this page is syncing properly with the other side. Direct intercept FPM rate is jumpy. Its changing at much to fast a rate and its hard to read. This is a very important page we use for decent planning. It should only show changes in hundreds of feet. It changes slowly in real life and is easy to read. When hitting NAV mode on the FCU the FMS1 goes green right away without it arming at all. In real life, even if you are right on the lateral path the FMS takes a second or two to turn from white (armed) to green (captured) this triggers very important standard calls we make, and if it doesn’t arm at all first its not realistic. I find the aircraft ALTS CAP a bit too early (I’m being super picky) I know it depends on the rate of accent or decent but the real thing usually doesn’t ALTS CAPs until 100ish feet below and 300-500ft in decent. Once and awhile it will stop climbing before I reach altitude as well and I have to VS it to complete the climb. The VNAV snowflake is much bigger on the real display, and I find it hit or miss if I get it in the sim. Same with a TOD point. I’ve had a problem flying the SSTIK 4 RNAV SID off Runway 1L/1R in KSFO. The FMS makes the left turn at SSTIK but instead of heading to PORTE it starts doing 360deg turns after SSTIK. This might be a similar problem some people have reported about the FMS getting lost sometimes and making high rate and high bank angle turns. I have had this happen to me. The real plane does not bank like this at all with autopilot on and with ½ bank selected 15 degrees of bank is the maximum it will do. After an approach is loaded and executed, the hold should be automatically be loaded in the hold page. The Fuel pumps should operate fully independent. A lot of times we shut one off for single engine taxi HCP values should clear when you start entering a new elevation or distance. You don’t need to delete what’s in there first. Might just be my system but the sound cuts out momentarily when I enlarge the FMS. That’s it for now. Sorry for the length, but I am very passionate about this airplane. If you make these changes you will have an extremely life like simulation of the real thing. If you have any questions, comments or would like to add me to the beta testing group I would be happy to send you my credentials to prove I am who I say I am. please contact me and I will be happy to help out! Mike
  • Create New...