Jump to content

Litjan

IXEG
  • Posts

    5,604
  • Joined

  • Last visited

  • Days Won

    404

Everything posted by Litjan

  1. I have seen them behave both ways in both versions - never able to nail down why they sometimes pop, sometimes move smoothly. We had to make a custom logic for the spoilers - LR´s default model of autospoilers and roll spoilers simply does not cut it. Therefore we can not use the default flight-control surfaces, which "replay" captures during the normal flight. So we have to "record" the position of the spoilers with our code, and that is not as trivial as it sounds and leads to this quirky behaviour. Jan
  2. Yes, we are running a complex fluid dynamic calculation. We are breaking the coffeeliquid apart into 50 million particles (I know, a gross simplification), all bound by cohesive forces, calculate Braunian molecular motion (depending on the coffee´s temperature), then apply adhesive forces (where the coffee touches the cup). Finally apply (varying with altitude and geographic location) earth gravitational force and aircraft motion´s force, and we get a fairly decent presentation of a moving liquid. This will only cost you 50 to 80% of available framerate, dependent on your computer. We thought about making the effect optional, but we strive for utmost realism, and this one you just can´t go without (even though you may think you can)! Enjoy the coffee! Jan
  3. And a little hint - look at the coffee liquid during turbulence...
  4. Hi Abiofly, thanks for the nice words! Yes, it takes a while for the IRSs to align - thats why we always turn them to NAV pretty much right away after getting into the cockpit. It can take even longer to align them if you park further up north (we dont simulate that). I think the "turnaround" option is still pretty realistic - in real life only maybe 10% of my flights are really cold and dark, usually you either take over from another crew, or you flew the previous sector yourself. We get the request for detachable, fly-out windows quite a bit - and I don´t say never - but completing the FMC is the first priority after this next interim patch. There is an option to display the CDU on an ipad, I think, Tom has that (forgot the name of that application)... Happy landings, Jan
  5. No, if you do that it won´t fly well anymore! Jan
  6. Yes - we have thought of adding a "quick alignment" option...just never got to that. You can pick the "turnaround" or "ready to fly" scenario, the IRSs will be aligned already, Cheers, Jan
  7. The plane should "just work" with 11.10. The flight-model-changes are "opt in" - which means they won´t apply until the aircraft is re-saved in planemaker version 11.10. I can´t confirm any reports of navigation receivers or taxi-lights not working - nothing was changed in that regard between 11.05 and 11.10. That being said, we are finalizing patch 1.21 that will (among some more stability fixes and other small enhancements) bring new compatibility to take advantage of 11.10´s new features and also the reflective glass surfaces in the cockpit. Cheers, Jan
  8. Not that I know of. Cheers, Jan
  9. Hi, that is not possible (yet) - we plan to add it later (conditional waypoints) Cheers, Jan
  10. About the lighting and lights - this is realistic. When you get on board, the cockpit is usually totally dark - if there are no lights outside, you will need a flashlight (there is one in X-Plane, too!) to find the battery switch. The overhead panel only has integral lighting, but you can use the flood light (switch on top left overhead) to illuminate everything better. The light you mention coming on later is either the emergency lighting (after battery on and emergency lights in auto) or the light from the cabin. The outboard landing lights come out like the lights on a sports car (correct!) - thats why there are three settings on the switch - OFF, EXTEND, ON. We have not modeled the light in 3D yet, thats why you see it floating in mid-air under the pylon. Happy landings, Jan
  11. Thats the spirit! Have fun, Jan
  12. Hi Martin, we do not "force" failures on people with renewed licenses - not even if they don´t have a licence at all, the plane will simply not run . And your report about this is the first one we get, so I am inclined to think it is a problem unique to your computer or setup. If all else fails, delete your preference files, maybe there are some corrupted key bindings that trigger failures or so... You can see the status of the icing (and anti-ice) on the "data out" display, search for the correct data to output with the keyword "ice". Happy landings, Jan
  13. I just doublechecked and anti-ice is still working. There is ice accumulation on a "AOA 2" - but this is not used on our aircraft, so it should be inconsequential. Cheers, Jan
  14. Hi Laem, I have not really tried them recently - but the anti-ice used to work and I am not aware of any changes to the icing code or datarefs. But I will check it out just to make sure. You have to use wing-anti-ice and engine-anti-ice in icing conditions. The nose gear being "stuck" could be due to having X-Plane default failures enabled. Cheers, Jan
  15. Your impression is right - the pilot will not feel different CG´s as long as they are within the allowed envelope. Cheers, Jan
  16. Normally (on a real plane) it would - since the bags and pax stay in position and the fuel "shifts" its position. However, we treat the CG as shown in the "ground services" menu as the CG that is currently valid. This is the way that the real pilots would interact with the CG. They don´t see it shifting during loading/fueling - they just get a "final" CG when the loadsheet arrives. Happy landings, Jan
  17. Hi Mareckis, the trim is only influenced by the CG (center of gravity) - not by the zero fuel weight. You can set the center of gravity in the "ground handling" IXEG pop-out menu, or alternatively in the X-Plane weight and balance GUI. The recommended trim setting as read in the FMS will only change if you input the correct CG there - it defaults to 20% MAC (mean aerodynamic chord, a measure for it´s longitudinal position). You can also read the recommended trim setting in the ground handling menu, next to the CG value. Cheers, Jan PS: In the real plane (and also to some extent in X-Plane) the CG will shift during the flight - when people walk back and forth, and also as fuel gets burned, as the location of the fuel tanks does not coincide perfectly with the CG. The effect is pretty mild, though, and the pilot will typically not notice it.
  18. Hi Sylvain, I read you question, but I have no idea how to extract the flightplan from our plane. There are no datarefs or any easy way, and the same holds true for the EADI and ND. I know that Tom is interested in cockpit-building himself, so there is a good chance that this capability will be expanded in the future. Cheers, Jan
  19. Matthias is right - there is a bit of a conflict with X-Plane´s native settings (start with engines running) that can be selected in X-Plane´s GUI and the IXEG provided settings, which can be selected in the left-side pop-out menu. The recommended way is to have your X-Plane setting set to "start with engines running" - and then select your desired startup state in the IXEG pop-out PREFLIGHT menu. Cheers, Jan
  20. You are right - the real plane will use an algorithm to reduce the bank angle at cruise speeds - we have not implemented that yet. Cheers, Jan
  21. Awesome shots - good enough to print them out as posters or postcards!
  22. If flying RNAV approaches is what you are after, then that is possible with the current implementation already. As a matter of fact, the real 737-300 I flew was not certified to use VNAV during the approach - we flew them in LNAV and V/S. I think the problem was the single FMS/GPS receiver combo. So you can already fly the GNSS or RNP approaches to the LNAV minimum, but not to the Baro VNAV minimum. Cheers, Jan
  23. Hi Erich, I do not think that flying without that scenery should be the final solution - I would just like to find out what is causing the weird returns. Let me know how that goes, Jan
×
×
  • Create New...