Jump to content

airfrance

Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by airfrance

  1. Problem was when it happened I was in the takeoff phase and didn't realize it until after it had happened so I wasn't able to keep track of certain details that may have caused it. I was in pretty choppy air and trying to fly the SID so I had a very heavy workload and couldn't focus on that stuff. From now on, I will keep track of these things so if and when it happens again I can provide you with some kind of information.
  2. Latest version of Gizmo 64, I've had one small issue but 3 times now. Only once did Gizmo 64 actually crash and I had to reload it. The FMC is getting stuck at the flaps restriction speed of 225 knots. Sometimes it doesn't and sometimes it does. Upon going to flaps up, the speed never resets and stays at 225 knots. I remedy this by using LVL CHG mode and setting the climb speed on the MCP. (However VNAV becomes unusable, even during climb as it's stuck under the flaps speed restriction) But this last time, Gizmo 64 window came up and said it crashed due to a parsing error and something about "FMC CLB" or something like that. Either way, looks like there's an intermittent error that makes it so the FMC won't reset the speed after flaps up.
  3. Yeah that's what I figured. I always fly green dot speed in OP CLB or OP DCT... While I have you... I want to upgrade to the newer version of Gizmo 64 and wondering if there's a way to do that without having to reinstall the whole airplane. I always just check to install the stable version but I haven't seen anything regarding issues with the new one (that says is in beta) and would like to give it a try to see the performance increase. With the current version, I still get little micro-stutters which I think the new version of Gizmo is supposed to fix. I just didn't want to create a new thread just for this.
  4. Haha... I can't ever think of a reason to use expedited climb on the bus unless you really needed to do as quick of a climb as possible but I feel like OP CLB does the same thing. It's going to climb and descend the plane at the fastest rates. I've noticed some A319-321s have had that button removed or had an INOP sticker added. Like I said, speed intervention on the 737s that have it is certainly a nice feature. Probably the best part is for an approach where you want to fly faster than the published speeds. Or even the flaps speed. If ATC tells you to fly 180 knots even though the published speed is only 160 for example. Or maybe you want to start setting approach flaps but still want to keep your speed up. Considering you can fly something like 220 knots with flaps 5, you can use the speed intervention for that, although I don't know why you'd want to as the higher speed is going to make it that much harder to get down. Anyways, I like that the classics have the quirk of not having this. It makes me appreciate it more when I fly the NG.
  5. Well that's no fun! Of course I've only flown the 737 in XP but I can say I prefer the NG over the classic just because of all the upgraded features that the classic can't do, like no speed intervention. Gosh I wish the classics had that. But I also love the classic so I manage. It makes it more fun to change between types. Flying a 300 classic one flight and a 900ER NG the next. Everything is pretty much identical as far as flows go. Just a few differences. I fly the Airbus in XP as well (A319-A321) so I guess I'm "type rated" on the 737 and A320 although that doesn't really exist in XP. But the two are equal but also very different. Like I've been amazed how much runway the small A319 actually uses up under certain conditions. Same with the 737. 12,000 foot take-off rolls on the 737-800 are not uncommon! Haha... anyways, this forum is for the 737, not the Airbus.
  6. Thank you for your engaging response with the community. If I came across as rude in my original post, that was certainly not my intention. As we all know, it can be very hard to judge tone and other things over text. Like I said, having this knowledge will help me fly the 737 Classic better. It's another difference from flying the 737NG that takes a little getting used to. Obviously many 737 pilots started off on the classic before moving to the NG so all the little quirks and differences wouldn't have been anything foreign. - I'm sure you can speak to this if you're still flying the 737 today. Your product is in my top 5 favorite ever produce for X-Plane, despite the little bugs and imperfections. And after 4 years, I love seeing that you guys are still trying to keep it updated. (I won't name names but another big producer of X-Plane aircraft should be taking some notes...) I hope to see you guys keep this product alive as long as you can, maybe even taking it a step further with different varients, updated model taking advantage of new XP technology, etc. It's a marvelous airplane and very fun to fly.
  7. Okay. I missed this thread. Sorry, there's a lot of information on sites like these and sometimes you miss something. Anyways, I digress. So you are aware that there are VNAV issues on descent. That's more or less what I was curious about. VNAV climbs the plane very well. It's just the descent that is the issue. I'll be honest.. like most I fly other airplanes as well but love the IXEG. So when I come back to it, it's easy to forget little quirks it has. But I suppose the VNAV issue was something I never really noticed before. Maybe I've always gotten lucky with approaches that didn't have all the restrictions. I'll just have to change how I fly it is all. Having the knowledge of this will help in the future. I didn't see on there if the VNAV issues are supposed to be fixed. I know it's a list of things that still need to be worked on and what is high priority but after the VNAV, you don't have anything regarding a timeline on when/if it's getting fixed. And to answer your question, the T/D was calculated to start 33nm away from the destination (DEN) and E/D. From 35,000 feet. At first I thought maybe it was because there was no PERF information yet and it would recalculate once the CRZ ALT was entered, etc... but it never did. So I had to manually descent when the PROG page showed about 100nm away. Then I used the green arch and V/S to match where I needed to be according to the approach charts. Sometimes the VNAV would randomly catch up and I would be able to use it but as soon as it lost the profile, which it always does, I reverted back to my method. - Not ideal or how it would be in real life as a 737 would almost always use VNAV for descent but for the IXEG, my method will have to do until/if you guys fix it.
  8. FLATI1 arrival for DEN rwy 34R. The VNAV is calculating the T/D as being literally when I'm over the airport. From FL350. This is not correct at all.
  9. Should be at 5,000 feet and I'm still at 22,000 feet in level change mode. Airplane incorrectly calculated the VNAV and never started descending properly. Now that it's caught up, it's over 13,000 feet high and I'm gonna have to make a big circle to lose altitude. If this was a new thing, I probably wouldn't post it but it's a constant issue, time and time again with the IXEG 737. Google IXEG and VNAV and a bunch of stuff comes up. There are several 737s to choose from that don't behave this way so I feel confident in saying that it's something with the coding or whatever. But it's never fixed. Also wondering why it's not flying the speeds on the FMC? Not in this picture but often times, it won't fly the commanded speed in the FMC. I'm just feeling like I'm finding many bugs with the FMC, A/P, VNAV, etc. After 4 years and after flying other 737s. I'm trying to grasp why the IXEG 737 is the way it is.
  10. I feel like ever since I bought this plane, as well as what I've seen other people say, the VNAV on this airplane, mainly on decent is just not working like it should compared to flying other 737s. Calculating the top of the decent 60nm away from the airport and it rarely follows the VNAV profile. The legs show it should be at a specific altitude but it never started descending. Or the VNAV path is all screwed up. Constantly being too high or too low. Is there any kind of fix planned for the fairly poor VNAV or is this it?
  11. Okay so I understand now that you can't arm the LNAV and VNAV on the ground as the classic uses the older A/P than the NG. Activating the proper TO/GA mode will engage a pitch and roll mode and then you can engage LNAV and VNAV after takeoff. My issue is I can't ever arm VNAV. Not sure if it's a noisy yoke axis or what. It takes forever and I often have to keep clicking it over and over before it will finally engage.
  12. Hello, I'm on 1.32 and I keep having issues arming the VNAV. I can't ever get it to arm on the ground so therefore when I go into TO/GA mode, I'm not getting the correct thrust for the climb profile and I'm not getting the magenta lines on the PFD from the F/D. Only after I lift off and I get positive rate am I able to arm VNAV (and LNAV for sake of argument. Can't arm LNAV on the ground either.). When I engage the A/P, VNAV immediately disengages and I get a CWS amber light under the CMD green on the PFD. It immediately will go into CWS mode for pitch. I have to keep pressing VNAV over and over and it will finally engage. What is going on? For example sake, I needed TO/GA thrust for take off which was 91.7%. I hit the TO/GA button (with VNAV/LNAV disengaged but they never would engage on the ground) and only got about 87% N1. Once I lifted off and hit VNAV and LNAV, the thrust went up to 91.7% where it was supposed to be. I find myself pulling back too hard because I don't have F/D help on takeoff.
  13. Sorry I missed this. Thank you for the update!
  14. Hello, Updated to 1.31 and now the FMC doesn't work. The airplane is unflyable using the FMC for navigation. Please see below for reference. NAV data was installed both manually and automatically with no change. This is the error that comes up when a waypoint is entered into the FMC. IXEG_FMS_debug.txt
×
×
  • Create New...