After a few more flights, I have a few odds and ends questions.1. On two flights I seem to have "lost" reverse thrust. At some point before takeoff, I've usually checked reverse thrust by putting the aircraft in to just a little bit of reverse power and looked for her to move backwards. I know this isn't exactly a kosher practice, but while I'm learning this bird it's sometihng I've been doing (i.e., once I get all the systems down it will not continue). Well, on a two flights the aircraft didn't move back at all, but when I brought the throttles back to idle, the aircraft lurched forward a little bit. On the landing roll for each of these flights it seemed that I also did not have reverse thrust (although that is hard to judge). The EIS indicated reverse thrust, but the engine sounds were a bit off (they seemed subdued) each time. I tried going through looking for common elements and came up with nothing, but at variable times during these flights before trying the reverse thrust I did engage cabin cooling, recirc fan, APR or prop sync. Cycling these switches to off did nothing, but I still don't know if something with these systems may have come in to play. Any ideas what could knock out reverse thrust? Is this a systems problem were I am doing something wrong or might it be an oddity of the simulator?2. How can I enter only part of a SID or STAR in to the FMS? The situation that came up was a short flight between MKE and ORD. No SID was to be used since the two are so close, but I wanted to tell the FMS I would be departing 7R. Well, if I select the "depart", I only get the "select?" option after filling out all the fields for STAR and transition as well. Is there a way to get past these to fields and just put in a runway?3. I was trying to program the Aspen VOR/DME approach in to the FMS for backup (VOR reciever was for primary once entering the approach). I was trying to program this on the ground and the routing was ROCKI7.DBL. I got this entered in to the FMS and ended up with RWY7 DEN CONNR DBL KASE for the route. I entered the first two bearing/distance waypoints based off of DBL just fine, but when I entered anymore it started kicking waypoints at the top of the list off so what I ended up with was CONNR DBL DBL* DBL* DBL* DBL* KASE (i.e., I lost RWY7 and DEN at the start of the FPL). Is there a limit to the number of bearing distance waypoints or just waypoints in general I can enter? Any thoughts what might be happening here.I'm really loving this aircraft and it's working beautifully right now. I'd just like to tie up some of these loose ends if I could. Thanks for any thoughts on these.Eric

1. Gotta be careful with FSX modelling, one of the greatest pains in the hinny for the developer was working with the Microsoft interpretation of a turboprop, loosely familiar to the PT6 sorta maybe. A slight bit of reverse and FSX wants to go full throttle reverse, then a little more reverse and FSX will calm down so the workarounds are tentative. The application of reverse thrust should be assertive (make sure you have the condition levers full flight). Attemping reverse thrust with taxi condition can melt the engines. I am sorry, this is my limited knowlege.2. The KORD SID is a vectors only departure. You have to manually keep track of the DME and altitude constraints given in the procedures (read the chart). I can't think of a valid reason that the FMS needs to know which runway you are departing if you are not selecting a SID. Either you are getting ATC vectors, or playing ATC in the cockpit in your mind (I do this) and the first thing you need the FMS for is either a direct to fix (DTO) or intercept a course to fix (INTC).3. I love the KDEN KASE trip. My route is KDEN ROCKI7.DBL KASE. To be realistic, after DBL you should be on the DBL transition to the LOC/DME approach flying with VOR/LOC navigation. The GNX is not certified for approaches and the 85deg turn to final course is a bit much for most computers anyway. This approach needs pilotage. There is a limit to the number of fixes in the real box, I'm not sure what the constraint is in the simulation.

Thanks for the reply. 1. I agree that I think this is an MSFS bug--just wanted to see if I could find out what was tripping the bug. It doesn't seem that this is the issues where MSFS wants to go to full RPM/Thrust with just a touch of reverse (I can bring them to full reverse and get the same thing), but nonetheless I suspect it's related.2/3. I know that in neither case is all this information needed. I just got in the habit when flying the bigger birds to give as much information as possible just in case you get in one of those situations where things hit a fan. Sometimes it adds to some situaional awareness or the like. I agree the runway is useless and have always flown the Aspen approach using the VOR reciever as a primary navigation...just nice to have some of that info on the screen for SA.Eric