Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

capceo

Commercial Member
  • Joined

  • Last visited

Everything posted by capceo

  1. Tried to find a solution/answer to this, but haven't, so here goes nothing. On the first leg of the trip, FS2Crew works exactly as it should (animated FO, if that matters.) On the second leg of a trip, after pressing the event timer button or using the "let's start setting up" voice prompt, I encounter the same two bugs each and every time. The first is that he won't turn on the landing lights when I say "takeoff," and he also won't run the after landing flow when I disarm the spoilers after landing. This all works fine on leg one, but on leg two, he won't do these items. I can duplicate this over and over again. Any ideas?
  2. Can you post a screenshot of the issue? Can't reproduce it over here.
  3. Hey John, The GTN750 brightness, by default Flight1 settings, is rather dim. It can be adjusted in the F1 GTN750 configuration tool that is automatically installed when you install the GTN750.
  4. Hey Luis, One of the revisions in the next update will be to the fuel flow. At present, it isnt as accurate as it could be. Fuel consumption in the Lear, both in real life and in our sim, is extremely dependent on the altitude you're using for the trip. The trick with the Lear is to get it as high as you can, as fast as you can. Down low they burn an obnoxious amount of fuel. The turbofan powered 30 series airplanes are a tad more fuel friendly at lower altitudes in comparison to the earlier turbojet powered Lear's, but this is a relative statement. You want to flight plan for the highest practical usable altitude for the given trip. Assuming you get it up into the FL400-FL500 range, you can expect to burn anywhere from 1500-1800lbs in the first hour, and around 1000lbs per hour for every hour thereafter. In terms of reserves, try not to land with anything less than 1500lbs on the airplane. If you're low and slow with the power pulled back, it will be more than an hour of fuel which should allow you to set up a second instrument approach or proceed to an alternate.
  5. The simplest way to alter the flight plan in the default units is to just make the change in the flight planner menu and the click OK. The default units have such limited functionality that it's almost painful trying to navigate with them.
  6. The autopilot master in the Lear is a custom coded function, and therefore won't respond to the Z key or to a joystick assignment unfortunately.
  7. This is interesting. I've never had an OOM with the MU-2. I'll mention it to Mark and see if we can get an analysis going.
  8. Hey everyone, I'll try to make a takeoff video in the next week or so demonstrating how we manage the airplane in real life. The simplest way to explain it is that you have to constantly stay a few steps ahead of the airplane. This is true in any airplane, but things happen quickly in the Lear and you need to be on top of things. One thing of importance is the pitch attitude you establish for your initial climb out. It is common to pitch up to 17-20 degrees. The order goes something like this for a flaps 8 departure, which is the most common flap setting: -Set takeoff power -Rotate at calculated Vr -Get the gear up within a few seconds of rotation (positive rate of climb will be obvious :smile: ) -Through 170KIAS, flaps up -Reduce power at or slightly before reaching 200 knots -Lower the nose -Further reduce power as necessary Obviously, you may have to adjust everything after flap retraction to comply with DP's
  9. Were you able to get the issue resolved?
  10. Hey everyone. We tried to offer RXP integration, but unfortunately the devs over at RXP have gone silent. Meaning we cant get the source codes to code all of the custom 3D buttons to work with the gauge. It is disappointing, but once you fly the GTN750, you'll never think twice about your 530 again.
  11. capceo replied to Cellinsky's topic in Gates Learjet 35A
    Just keep in mind everyone, that the TR's have very little actual braking effect in real life. This holds true for just about every jet aircraft with thrust reversers. While they make a lot of noise, and you feel the sudden deceleration, 90% of that deceleration is coming from the brakes. Many jets dont even have a separate set of performance charts for TR's inop.
  12. Not just yet. I believe Mark intends to update the 441 for V3. Keep your eyes peeled!
  13. Careful Matt, flaps 40 should never be used for takeoff, regardless of runway length. The 40 degree setting is a bit interesting, in that it is the only setting that actually results in a drag increase the outweighs the lift increase.
  14. You'll be taking delivery of your new Lear in the next week or two!
  15. Yup! The LR35 will have an installer to get the aircraft into V3, and I believe Mark intends to update the installers for previous aircraft so that they install into V3 as well.
  16. Rain effects will be included as well!
  17. It does have cockpit glass with reflections that have been taken from a real 35A! I think you're going to be very pleased!
  18. Glad you got it resolved. I hope the 441 brings you many years of enjoyment! For the future, louisdecoolste is correct. Try to provide us with as much information as possible about the issue so that we can try and get it resolved as quickly as possible. Thanks again!
  19. Hey Everyone, Yes, the 35A will feature full systems integration, just as our previous releases have. I'm sure you're all going to be very pleased with the finished product!
  20. The bottom line is this. The beta team and development team, which you seem to believe is flawed in one way or another, do their best to respond to customer inquiries and concerns as quickly as possible. I'm sorry that you're unhappy louisdecoolste. I'll remind you again, as I have in the past, that all of us, with the exception of Mark, have real jobs, that pay us real money, and pay our real bills. The same real bills that you, I would think, have to deal with. And yet, we STILL find time to pop in here and try to and answer questions and concerns. Most people who work for a developer won't do a thing without a paycheck. Other developers, specifically a notable organization from Chile, pays 7-10 developers full time salaries to produce aircraft, and offer ZERO personal or forum based support. I really wish you would consider the effects that prolonged comments like yours have had on this small world of developers in the past. Many developers have spent countless hours producing fantastic products that generate very little revenue, only to decide to pack up shop and get out of the development world because their efforts go unappreciated. Unfortunately, some people are just impossible to please. The FS community was begging for an MU-2 for years. So we answer the call and deliver the first quality MU-2 ever seen for FS. And what do we get in return? Flak. I'll leave you with this. Most of our customers understand that we are still growing and evolving as a developer. So many of you have noticed, as I have, the continued improvement with each one of our products. We don't intend to stop improving now. Thank you to those who continue to support us. To address the actual issue at hand, I'll give you both my perspective as the beta captain, and my perspective as a real world pilot, since it seems that the latter has been lacking in this discussion. As a tester/developer: I was unable to recreate the issue. My trim tabs move exactly in the direction they are supposed to for the commanded pitch trim input. As a real pilot: As a real pilot, I can assure you that the pitch trim tabs are not visible from the cockpit. I think its a little ridiculous that this discussion has progressed this far. I will attempt one more time to recreate the issue. Perhaps a YouTube video with a demonstration and explanation is in order?
  21. Hey Richard, Unfortunately, it is not possible to interface the ground elements with a saved flight. The repair button is used to repair a default failure as configured by the failures window in FSX. Hope this answers your question!
  22. Very puzzling! Give me a chance to see if I can recreate the issue, and I'll see what we come up with.
  23. Thanks for the support everyone! This screenshot includes the GTN750 from Flight1 Software, and the WX500 from RealityXP. All of our products from the Cessna 402 on include GTN and WX500 integration. (C402, C441, MU-2, LR35) Of course, there will be a panel variant for those who do not own the GTN and WX500.
  24. Just a quick shot of the dynamic night lighting in the VC. More to come soon. We're getting very close!
  25. I'll have to check with Mark on this one. I'll mention it to him the next time we speak and see how it works.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.