poodster

It's probably a database bug like you said. Try other airports like cyyz, klax, etc. Those I know have valid Sid and stars

Ghd does work with this plane.

Did you change your altitude bug to 4000?

It does not light as there is no flight plan in your fmc. This is like the real fmc as well. Jan recorded the tutorial video before the aircraft was released and this change was one of the last minute changes that were added.

Do you have hdr enabled? Because these lights work for me.

What do you mean by winter textures? The ground texture? Are you using the season Python script?

The manual and tutorials for this plane is located in the airplane folder, then inside documentation.

@Colin S Just saw you have started maui. It's looking amazing! I've been to maui on vacation before and I can't wait to fly around the island and do island hops to lanai and molokai.

Did you match your throttle with the ghost throttle on the bottom left hand corner of your screen?

They are currently adding features to the cabin and other areas of the plane to put in for 1.1. It'll be done when it's done. Let's think of it this way. Would you rather ixeg tell you a date and then miss the date? (which would make people irritated) Or would you rather wait until the update is ready and he presently surprised.

I didn't skip any waypoints. Flew the whole route. I'll try again today though.

And it shows! Hard to fly other small jet liners now haha.

I had the same thing as well. It didn't reset when I arrived. From cyyz to cyow.

As Ben said, this is normal. In the next full update I believe, there will be an inop next to the logo light switch.

Check your null zones. Try raising them.

The temporary hotfix works just as well. I did it and it upgraded to 1.07 perfectly.

What plugins do you have? Fluctuation is somewhat related to plugins as to what I've seen. Or related to the hardware used to fly.

There seems to be an issue with x-plane, since it hard crashed when you alt-tabbed. Remove your plugins back to stock (except gizmo ofcourse). And make sure you remove them and put it in a seperate temp folder, since disabling them won't help. Can you post your logs so we can see what x-plane is thinking before the crash. (Could be a scenery or plugin conflict). I'd also try reinstalling the 737 just to fully make sure nothing happened during the hotfix.

If I'm not fully mistaken based on what I'm seeing. This will be put into the emergency hotfix coming very soon. (few hours or less hopefully)

Will the emergency hotfix include the gizmo crash when deploying and setting flaps? These were the errors. error: 3563.149: RunLuaFunction(timer): run_Flaps: [string "ixeg.733.fmc.climb.lua.aes"]:133: attempt to get length of field 'climbSpeedRestrictions' (a nil value) error: 3565.125: RunLuaFunction(timer): fmc_periodic: [string "ixeg.733.fmc.climb.lua.aes"]:133: attempt to get length of field 'climbSpeedRestrictions' (a nil value) Thanks for the hard work to get this emergency hotfix out as quickly as you can! EDIT: Just saw on facebook the emergency hotfix will fix the flaps as well. Thank you, can't wait to fly this plane. (hopefully this evening)

Don't put the ixeg in a different folder. Keep it to where it's supposed to be. There's a good reason why it's supposed to be where it's meant to be.

Hotfix server is down at the moment.

Upload your log files and crash report. You should also try removing your plugins back to stock (except gizmo ofcourse) and see if it still happens. Also, are you using the IXEG built in view presets?

Most people don't have an issue with frames when not using the fmc. And considering no one knows why, it's hard to pinpoint and work on a solution. As well its computer based. Not fully ixeg based. What are your PC specs? Try reinstalling the plane. Also remove the plugins back to stock configuration. Except Gizmo ofcourse.

Download them and put it in the livery folder, which is in the aircraft folder.