Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/21/2018 in all areas

  1. Hey y'all It's been a while since I've lurked on this forum. I must admit it's very flattering to see that my 767-400 is still the top download in the forum haha. I'll cut straight to the chase, as I'm mostly here to tie up loose ends regarding what has happened to my projects and where I am now. After high school, I simply haven't been able to find time to continue developing the 787 project. The short of it is, the project is dead. Source files for the aircraft probably don't even exist anymore, and if they do, I certainly can't find them. I do apologize for being so silent on the issue, I genuinely didn't anticipate how crazy life would become in the years after 11th grade. These days, I don't really fly anymore, though I'm tempted to jump back into it some day. That being said, I still work a lot in the 3D modelling and CGI world now as a full time job, working with VR imaging companies and doing my own CGI visualization and photography work in the automotive industry. (I've enclosed some examples of my recent work, if you guys are curious). I'd like to try and get back into the community eventually, just as a member for the forseable future, and maybe someday as a developer again. Cheers. Michael.
    1 point
  2. Hello everyone. Ben, Just in case you still looking for additional info regarding this bug. I am also getting the same error when starting X-Plane with Zibo737 and then changing to IXEG. Just tried to start with default Cessna. Switching from Cessna to IXEG, same crash (Loading IXEG first, works without problems): I am using the latest Gizmo from your Facebook page: Gizmo64 v18.02.12.240 Edit: Reloading the Current Aircraft from X-Plane Developer menu, reloads IXEG without crash. I am currently on my MAC laptop. Can try the same on my main windows PC if needed.
    1 point
  3. Sorry about being unclear, but yes, as I remember it was the same at least in the respect of "OnKickstart" and "GateKeeper". I tried to reproduce it again but couldn't. The one thing I changed between then and now is that I installed current navdata (1802, before it might have been the navdata that comes with the installation), which I missed before since the FMS didn't work after all. That's all I have time for right this moment.
    1 point
  4. My Pilots Handbook says : LIGHTS TEST Select TEST, NOT all the lights come ON. NOTE: MKR BCN, FLT ANNUNC, PARK BRAKE don’t come on at all. NOTE: On “some” planes, the FIRE HANDLE and WHEEL WELL LITES do not come on during test. So, obviously it may differ between planes.
    1 point
  5. When ATC tells you to set Squawk code to i.e. 6366. You just enter that Squawk. Sometimes they tell you to set a Squawk code and ident. Then you enter assigned Squawk Code followed by pressing the ident button. If ATC require you to set Squawk Mode Charlie on ground you set the transponder to "ON". On "AUTO" (default) the transponder automaticly sets it to Squawk Mode Charlie on takeoff/when airborn and back to Standby when you have landed. https://www.vatsim.net/pilot-resource-centre/general-lessons/transponder-and-squawk-codes
    1 point
  6. By default the transponder is set to AUTO. This means it will not start squaking (no matter you are mode C and code set) until you are on the takeoff procedure. On real life, you start squaking departing and stop squaking clearing the runway. This is because there may be hundred of aircraft on the ground and all of them squaking will congest the controller's screens giving them a hard time to track critical aircraft airborne on the airport's vicinity departing/landing. During taxi in / out from the gates, ground controllers can actually see you from their physical elevated location to track you against other aircraft. On VATSIM / PILOTEDGE virtual world (online networks), the controllers can not see you, so they need you turn on your transponer as soon as you start moving out of the gate to track you against other aircraft. When you fly online, set your squak code as required, set mode C, BUT also set transponder to ON manually as soon as you leave the gate for it to start squaking and controllers being able to track you on the ground against other aircraft. Upon arrival you also leave it to ON, do not turn it to AUTO neither OFF until you parked at the gate. Hope this helps
    1 point
×
×
  • Create New...