mmerelles

i did a search, this was the post... but the developers did not chime in yet

no there is not! i am quite sure this feature was requested before, honestly i do not remember what the developers have said about it. you can speed up the -in cruise- time by pressing "CTRL + T" to accelerate the simulation or you can use the xplane local map to drag the aircraft.

you can not rollback to beta1. You will have to wait for beta3 now supposed to be released by friday/saturday if everything goes well fixing the bugs and testing. but, you can roll back to the latest stable version (10.45) by running the installer and disabling xplane betas checkbox. the installer will remove the beta and put you back to 10.45

yes, you are beta2. that is exactly the issue. Betas tends to be very unstable stuff, specially the first 2 or 3 iterations where most of the crazy things happen. If you decide tu run betas you should keep an eye on the developers blog periodically to see what is going on... link: http://developer.x-plane.com

@2legitoquit always attach your xplane "log.txt" found on your xplane root folder when you report an issue. are you running xplane 10.50beta? it has a bug that lights are broken and stays on to ANY aircraft

search feature is a friend to anyone.

just to confirm something, can you try again real weather checkbox DISABLED?

there is no custom command to map. you have to use a plugin or script to assign your button to write/manipulate the apu dataref "ixeg/733/apu/apu_start_switch_act" all custom commands and datarefs are documented under the aircraft doc folder "2. interface guide.pdf"

a few observations 1. once the engines are running prior to taxi you must enable GEN1 & GEN2 and transfer the electricity to load to the engine generators (you never takeoff using the apu generators you have no redundancy at all) 2. to use the apu to keep pressurization going, leave the apu on but on the BLEED panel only enable apu bleed to feed the packs, leave eng1/2 bleed to off. 3. i think the apu has a maximum recommended limit as well so do not leave the apu on forever, once you completed the takeoff procedure you can feed the packs via the engines. here you have a good video to achieve this, while LOWI is not a high altitude airport, he configures the aircraft to get high performance due to mountains surrounding.

please do a screen capture of your overhead panel when aligned on the runway prior to takeoff. In such case you get the alarm back you share the image to see your config.

i did the departure for you, haven't had any alarm. departing runway 32 atovo destination saez fl350 50 tons of zfw and 9 tons of fuel ohhh men the departure was a bit scary via runway 32 those montains ahead are so high, even doing the 180 turnback for the trasition... that was close call! The aircraft loaded heavy 50 tons at that altitude requires the entire runway and a slow climb out. the only particular config i did was to left the apu on to keep pressurization going from the apu to get the most out of those engines for takeoff/initial climbout

@capizolano please attach a screen shot of your entire overhead panel configuration when you are ready for takeoff. that would be easy to see what is going on. Also be sure you have set to FLT mode, on ground mode (default) it will not pressurize.

is a 0 or a 8? it seems you missed to rise the flaps up completely and the aircraft is protecting itself not to ripe them if you use an external hardware lever for flaps, that is a very bad idea, because xplane does not support nullzone for flaps / speed brakes axis yet, so they seem to be closed but they may be still 0.00001% open

attach your xplane log.txt file also, will be useful

it has been found several critical issues to beta1 wait for beta2 http://developer.x-plane.com

Please read here. FMS section.

@kickremi @Defiance_co @mgeiss PMDG always prices their products to their estimated real life value when they fist announce them on their shopping portal being close to release. The windows version was priced 12M before release as well as the mac version now awaiting for release. If you go an have a look for the newest 747 coming for FSX you will see it priced something like 230M as well.

Thanks for your log. As per your log file xplane is detecting: OpenGL Vendor : Intel OpenGL Render : Intel(R) HD Graphics 4400 OpenGL Version : 4.3.0 - Build 20.19.15.4331 (430/0) you fall under the Intel graphics 4xxxx not supported so far the chip has no power to render what required. I am not familiar with your laptop, does it has a R7 also? can you force your hardware to use it instead of the integrated intel?

can you attach your xplane log.txt file found on your xplane root folder? use "choose files" for attaching bottom left corner while posting. i have seen this before from another user, having a very limited intel 4000 chipset graphics card not supported as per the developers

you are welcome, happy to fix your problem!

when you run the installer BE SURE you clic SELECT xplane 10 folder and you have to manually clic on the window finder until you reach /Users/m_david/Desktop/X-Plane 10 it seems then, you are not selecting xplane 10 folder and the aircraft is installing on the wrong folder structure

ok, according to your log file the aircraft is not properly installed. This aircraft requires gizmo plugin to run and this plugin is not present on your system. Gizmo should be installed automatically by the IXEG 737 installer. When you installed the IXEG via the provided installer, did you received any error or warning? did you activated your aircraft via your mail/password? did you install the aircraft by moving the folder from another install (it will not work)? The installation was not completed at all as per the log.

yes, BUT: 1. do not copy/paste makes the post too long and difficult to read. You better attach the file as an attachment! 2. as per your log file you did not tried to load the 733 at all. please open xplane, try to load the ixeg 733 to reproduce the problem you describe, then close xplane then attach your log.txt file. note: i am a bit concerned on your hardware mac specs! they are quite low for this bird. But anyway attach the log, lets see what is going on...

attach your xplane log.txt file -AS IS- found on your xplane root folder.

Ethan as Mortem pointed out above, you are still runnin several plugins that are known to cause conflict. Please REMOVE any plugin from the xplane/resources/plugins folder except gizmo just to confirm no more crashes, then you can put them back one by one to see which one causes trouble. You are also having several scenery issues like chicago midway missing required libraries. Scenery can also cause xplane to crash. So i would recommend removing Chicago midway or adding missing required libraries first. Check on the page you downloaded Midway for required libraries and version! hope this helps