Jump to content

TheHorsley

Members
  • Posts

    45
  • Joined

  • Last visited

Recent Profile Visitors

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

TheHorsley's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges

3

Reputation

  1. To determine a vertical speed required from the gradient , multiply that number by your ground speed. If your missed approach speed is 150 for a 5% gradient you need 750fpm to maintain the gradient. That’s all you have to achieve to be able to use the minima attached to that required gradient. the next step is to determine if your aircraft can actually achieve that - i can’t help you with that at the moment as I don’t have cl65 performance charts - but there will be a table where you can derive your max weight to maintain that gradient oei.
  2. Start bleeding the wind additive off from about 100 - 50' to touchdown, this will mean slightly less thrust than normal so you'll need to be ready to catch it - aim to be touching down at Vref. If you initiate the flare at Vref + wind additive youre definitely going to float, if you can't bleed the additive off just drive it onto the runway, but be careful not to land nosewheel first as the landing pitch will be very flat.
  3. Is this much analysis into wing flex really necessary? they're a small wing, they wont bend that much anyway. i offer in exchange - actual wing flex
  4. Understood, I’ll keep a copy of both handy and swap them out if I find a solution. I might have to park the 737 for a while to make sure this doesn’t interfere with other gizmo product performance
  5. Cool I’ll give that update a go. Yeah gizmo 18 crashes, 20 is fine , I got that version from a support post on here, I thought that was the latest version. I’ll try the installer again
  6. No problems there, so how do I stop the one that’s included with the installer from crashing after around 5 minutes ?
  7. Dear Ixeg support I'm having problems with the 737, ive read a few threads here but nothing seems to be exactly like the problem i'm experiencing. I install the 737 and use the old stable 2018 gizmo version, this makes the aircraft work fine, but every aircraft that uses this will crash to desktop after around 5 minutes. LES Saab and IXEG 737 are the main trouble spots with this when i use version 20 or the beta version posted in another thread here, i get good stability no more crashes, LES Saab works fine, except the 737 avionics dont work at all. also the side menu doesnt work with the newer version of gizmo i've attached a screenshot i've also re-installed numerous times, this is definitely gizmo related on my end, but with one version of gizmo i get 5 minutes of gameplay, the other version i get an unflyable product. please help Chris Log.txt
  8. Thanks for the reply Frank! The first time i had this problem i re-installed x-plane to reset the textures back to default, however i watched the file during the boot of xplane and could actually see the file size change as it corrupted during the boot process. Next time i come across this i will try your solution to deleting the default sky colours and see how it goes. AOS seasons extensions i have no idea what that is, i just found it in the log as you mentioned... it must have been installed along with some other add-on without my knowing, i will investigate further as to what this could be. thank you again for your time Chris
  9. Dear Skymaxx team i am having an occurence occasionally where it seems skymaxx is corrupting my moon.png texture. I try replacing the file with a known working version, yet when xplane is started, this file is then corrupted during the boot process and xplane crashes. I have isolated this to skymaxx, as re-installing the add-on fixes the problem for a while. Are you able to assist? My solution at the moment will be to remove skymaxx from my system, but i'm not keen to do this. regards Chris Log.txt
  10. Hydraulic pump in auto?
  11. I try this. but my quadrant sends the occasional spike through to the sim which is enough. everytime. I can vouch that the real plane doesnt mind being slammed into full reverse from flight idle once the WOW switches release the gates
  12. I also find 1.5 to be a more usable version. Since the update I haven't been able to enjoy the Saab as much as the previous version. My main problems i have are: Halfbank is always engaged - drives me nuts. Engines turn off upon landing - drives me nuts reflections on the engine instruments render them impossible to read. Granted i havent used the product in a while because of these issues, i'm curious to see if the halfbank is actually cured. there are other small niggles in the systems I would love to help improve if you would like my input. I have a bit of SF34 experience regards Chris
×
×
  • Create New...