BluesmanEP

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

2 Neutral

About BluesmanEP

  • Rank
    Member

Recent Profile Visitors

1,488 profile views
  1. Save more settings between flighs

    Thumbs up to that suggestion! Thanks!
  2. Liveries request

    This livery was just posted today on the .org forum. Not sure if I can post a link there, but a quick search will find it.
  3. FMS setup for descent before ToD point?

    Haha that makes sense I'm comfortable flying manually calculating ToD and managing my own crossing restrictions, I just didn't think that's what you were 'supposed to do'. So from cruise, I should just set a new altitude on the dash, and use FLC / VS to descend - not worrying about re-programming the FMS at all? I assume as I get closer to the airport the FMS and my manual descent will 'sync' up again, once I pass the FMS calculated (but wrong) ToD point. Thanks for your help!
  4. FMS setup for descent before ToD point?

    so it seems that you can only edit the descent parameters while the descent mode is active. Once I reached the calculated ToD, I was able to change speeds etc. That makes it all the more confusing to me. I guess my general questions is, how do I setup an 'ad-hoc STAR'? When flying a real STAR the FMS knows that the ToD point is actually quite far from the airport, and there may or may not be various level-off points along the way. Once in descent mode, you're able to edit the descent parameters, and add / delete crossing restrictions etc. However, if my first required altitude is at the IAF of an ILS approach (say 3500') and I'm cruising at FL200, I may be given by ATC several "descend and maintain", or "cross XXX at 8000" commands. The calculated ToD point is such that I fly a straight descent to 3500'. It seems the FMS isn't happy when flying below cruise altitude before the ToD point. So my question is, how to I fly these step-down legs? Do I just keep setting a new, lower cruise altitude in the FMS? If I do that I always get a 1000 fpm descent rate, but no guidance on when to start that descent to cross a fix at a specified altitude. Is there any way to set a crossing altitude restriction, and have the FMS calculate the ToD to reach that point, even if the FMS isn't yet in 'descent mode'? Does this make any sense? haha... I'm very solid on flying a route with a SID and a STAR, but I seem to be having trouble understanding how the FMS wants to fly a route in a more manually managed descent mode. Thanks!
  5. FMS setup for descent before ToD point?

    That worked great, thanks! It did bring up a few more questions though I think the problem I was having with the ToD point is that I was flying a route without a STAR, so the calculated ToD was actually pretty close to the airport. By getting the "cross XXX at 15000" I basically wanted to start the descent at a point to capture that as a crossing restriction, not a new cruise altitude. Is there a way to have the FMS go into 'descent' mode on command? Rather than waiting for the calculated point? Also, on the CRZ and DES page, I think I should be able to specify a cruise speed (the TGT SPD box), but I can only enter mach numbers, I can't enter a value in knots. Additionally on the DES page, if I want to enter a new descent speed I enter /270 and click TGT SPD. I get an EXEC prompt, but the entered value doesn't show up. It's still the value it was previously. The top of the DES page shows "280kt PATH DES 1", even though I entered a restriction of 270 knots. I assume I'm doing something wrong... but can't figure out what. Thanks!!!!
  6. Problem on approach for SNA

    Don't disable Windows Defender!! Probably not a good idea to run without it... All you need to do is make an exception for your X-plane folder. Open windows defender, click settings. Scroll down to 'Add an Exclusion', and click 'Exclude a folder'. Navigate to your entire X-plane folder and click ok. You should be good to go! I had the same problem with the EXEC button until excluding the XP folder. I'm happily running windows defender on the rest of my system.
  7. FMS setup for descent before ToD point?

    Perfect! I'll give it a try tomorrow. Thanks! Sent from my iPhone using Tapatalk
  8. Hello! I recently ran into an issue while flying online. I was at cruise FL200 and got a cross XXX waypoint and maintain 15,000, well before the FMS ToD point. I tried to enter an altitude restriction for that point, thinking the FMS would re-calculate the descent point to meet the new altitude. The FMS accepted the restriction, but the next waypoint went back up to the cruise altitude setting. It seems the FMS was never in the 'descend' mode. At that point I lost all use of the FMS altitude restrictions, and had to fly the rest of the route and approach using only manually set altitudes and VS or FLC commands. What's the procedure for small altitude changes (descents) well before the calculated ToD point? Should I have entered the altitude as a new cruise altitude? Thanks!
  9. What did you fly today?

    Wow, beautiful shots @Defiance_co!!
  10. Wind noise sudden cutoff in cockpit with windows open

    I have a similar (the same?) problem. Sitting on the ground, with the window open it sounds like the wind sound loop runs out and ends abruptly, then restarts. It doesn't seem to be related to where the camera is positioned or facing. I have removed plugins and not seen any change. I have a Gigabyte motherboard with a RealTek HD audio chip.
  11. What did you fly today?

    Ha! For a second I thought this plane was flying upside down!! Sent from my iPhone using Tapatalk
  12. IXEG 737 Progress Update - March 12th

    That's fantastic to hear, thanks!! Sent from my iPhone using Tapatalk
  13. MU2 1.6 Transponder Problem

    Wonderful! Thanks!
  14. Xlife ready!

    It also can take a bit of time for the traffic to get going. Incoming aircraft spawn well outside of the airport, and need to fly the approach etc. The best way to see if it's working is to get an airport-widezoomed-outview, crank up the time acceleration, and open the airport data overlay so you can see what the plugin is doing. Good luck!
  15. Xlife ready!

    Which LOWI scenery are you using? I'm using the scenery pack linked in JAR's x-life scenery map. I load up the sim, start x-life and watch the traffic A note about x-life reading the ATC Routes of existing scenery. While it is true that X-life will read the taxi routes, they must be built in a very specific way in order to do so. Most importantly, there must be a taxi-route segment connected to every ramp start / gate location. This is more strict that was ever previously required for the default ATC(I believe so, anyway), thus many existing scenery packs- even ones with taxi networks - won't work out of the box. Many of them only have taxi segmentsclose tothe gates. This will cause an error, they must me connected to the start point for x-life to use them. It's not a big deal to go into WED and make the small adjustments needed for existing scenery. Hopefully, moving forward, the scenery developers will take these requirements into account when building their next projects. Hope that helps!