Jump to content

Tim013

Members
  • Posts

    251
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by Tim013

  1. Exactly. It's not an IXEG 737 feature, but a stock X-Plane feature that can now be accessed. Why you would want a 2D HUD view is beyond me, but it's there for you....LOL. Tim
  2. And, that is greatly appreciated. It is much easier to paint when the fuse is one piece, and not in sections. Tim
  3. Try putting them down to 40, and then exceed the flap extended speed for 40 degrees. The little things that are modeled are very cool. Tim
  4. I agree. The frequency mish-mash is so unrealistic, that it's a definite deal breaker for me. I understand their business model, and how they need to set it up to make it profitable and affordable, but that doesn't mean that it's what people want, or are willing to pay for. As I said, for simulator pilots who don't know any better, they probably think all of the frequency chatter is the shiznitz, but for real pilots, it's nothing short of distracting, to the point of being annoying. That's exactly what I'm talking about, the getting yelled at part. Real world controllers don't act the way the PE controllers do with the nitpicking dress downs I've heard on their network. In the real world, if you blow a heading, the controller will ask you for your heading. After you tell them, they will assign the same heading they originally gave you, or assign a new revised heading. You know you blew the heading, and the controller knows, and that is the end of it. Enough said. There's no on frequency b***h out from the controller. On Pilot Edge, when you blow a heading, the first words out the controllers mouth often times is "where are you going?" This is followed by an uncomfortable lecture for the poor pilot playing a game, that goes on for a good 30 seconds. Completely unlike the real world. Another deal breaker for me. Tim
  5. I would disagree a bit with you on the Pilot Edge thing. Having a lot of real world experience, I thought that PE would be great, as they try to simulate real ATC procedures. While this is a good concept, it falls flat when you start to see how they do it. The positive of guaranteed ATC coverage during open hours, in my opinion is overshadowed by the unrealistic combining of frequencies. I'm sure people who are only simulator fliers enjoy the nonsensical frequency combining, and don't care that you can be on the CLNDEL freq at KSAN, and hear aircraft being vectored at KLAX. To those people, chatter is chatter is chatter. To a certificated pilot, who PE is ultimately marketed to, that type of frequency shenanigan is a deal breaker. The first time I flew on PE, I kept checking my radios because I thought I had the wrong frequency dialed in, or I had COM2 hot. Lastly, the service area is small. I got bored making the same short hop flights over, and over, and over, and over. Whey you're first working them out, it's fun to learn the nuances of the procedures of southern California airspace. Once you get comfortable with it, it becomes less than fun because it's the same routes. I'm glad I did the two week trial. I almost made the mistake of signing up for real and paying for it without doing the free preview first. Maybe this is nitpicking too, but the controllers are no better than the best Vatsim controllers, and frankly, they are a bit over the top. In my years of flying, I've never really dealt with controllers that act the way the PE controllers do. So, in a nut shell, for me, PE is a good concept, just poorly executed. Tim
  6. I know others have reported uncommanded turns, and resistance to following the inputed route with hotfix 1.0.7, but am I the only one seeing "UNABLE CRZ ALTITUDE" AND "WAYPOINT NOT FOUND" when the FMC starts breaking down? I haven't seen anyone mention this on the forum. Tim
  7. I tried your flight just now, and got a gizmo soft crash. After rebooting, I kept getting the "UNABLE CRZ ALTITUDE" message for every waypoint entered into the FMC. Tim IXEG_FMS_debug.txt GizmoLog.txt
  8. Here's another one I just did from KFWA to KDTW Route: EDGEE MIZAR3 with runway 21L selected. The MIZAR3 FWA trasition and 21L COUNT intersection transition. FMC log included. Same deal. After crossing RAZIM and turning on course to COUNT intersection, after a couple of seconds on course, the aircraft turned right 100 degrees, and then continued on straight and level on the new heading. LNAV only, with speed and altitude controlled by the MCP. I hope this helps you guys. Tim IXEG_FMS_debug.txt
  9. One FMS debugging log coming up. Tim IXEG_FMS_debug.txt
  10. Yeah, I'm usually pretty cautious when it comes to software updates. I'm a "if it ain't broke, don't fix it" kind of user, but the hotfixes have been going so well, I didn't really think twice about it. I'm sure it will get sorted out soon. All this means is I can now put the IXEG 737 down for a while, and get back into the FlyJSim 727 cockpit! I recently upgraded to version 2, and it is really cool. This will give me the opportunity to do some old school /A IFR flying for sure. Tim
  11. Jan, OK. I haven't flown the IXEG 737 since my last attempt at this flight, so I will post that log when I get home from work today. Thanks, Tim
  12. LOL....yeah, really. I thought those were photos at first, not in game screen caps. Tim
  13. Yes, I have the Revision two of 1607 from Navigraph. I had this happen with the original 1607 as well. Good idea to always check that. So, it's a common flight for me. KMDW to KDTW Route: LEWKE GIJ LFD MIZAR3 departing from Midway on 13C or 04R, and landing at KDTW on runway 21L. I use the MIZAR3 LFD transition, and the COUNT ILS21L transition. I fly it with LNAV for lateral guidance, and use the MCP for vertical guidance......no VNAV at all. === I added the last log file in case any of the developers are interested. === Tim GizmoLog.txt
  14. Bummer. OK, thanks for the info, it's appreciated. Tim
  15. I asked this buried in another thread, but it might be overlooked, so I thought I'd ask it outright in a new thread. Can this be done? Thanks, Tim
  16. I've tried the flight again a few more times, with the same result. The last time, I even used simbrief to get real weight and fuel numbers to make sure I wasn't arriving too heavy, and tripping the "UNABLE CRZ ALTITUDE" message, but no joy. The arrival breaks off in a 90 degree turn to the right. I'm puzzled. Tim
  17. I have a similar issue with the MIZAR3 arrival into KDTW. It worked fine in 1.0.5, but not now in 1.0.7. I started a thread about it earlier this week. The odd thing for me is the FMC accepts the route, there are no discos, and the only INTC waypoint is after the approach, on the way to the holding pattern. For me, the arrival ends when I get the message "UNABLE CRZ ALTITUDE". This is followed by "WAYPOINT NOT FOUND" for any other waypoint I choose in the arrival to try and bypass the UCA warning. Is there a way to roll back to version 1.0.5? Thanks, Tim
  18. Tried the flight again. I was mistaken. The FMC doesn't give the message "waypoint not found", it warns "unable crz altitude." Both times, at the same place, the warning popped up, and a 90 degree turn to the right was commenced, then that 90 degree to the right heading was held indefinitely. There have been two revisions to AIRAC 1607 since it first came out, and this flight just now was with the latest revision number 2. Tim
  19. Had an odd thing happen yesterday. I was flying from KMDW to KDTW via this route: LEWKE GIJ LFD MIZAR3. Everything was going great using LNAV and the MCP for vertical guidance. After passing MIZAR intersection and half way to RAZIM intersection, the FMC popped up the message "waypoint not found", and the 737 immediately entered a right turn. I turned off LNAV, and got back on the beloved magenta line via the MCP and HDG control. Once I was back on course, I changed the FMC flight plan by moving TIGRZ intersection to the next waypoint (wanting to bypass RAZIM), and then activated LNAV again. The 737 tracked the new course just fine until about half way to TIGRZ intersection, and then the same "waypoint not found" message occured, and bingo, another hard right turn. What is odd is that the route, including the STAR and approach were entered before takeoff, and accepted by the FMC as being valid. There were no discontinuities. Strange it would navigate to a fix, in this case, two different intersections, and both times, suddenly say they don't exist. I'm going to recreate the flight today, and see if it can be reproduced. Anyone have this type of thing happen to them? The weird thing is, I've had hardly no issues with this bird at all. It's been great for me from day one, and I've been loving it. Final note: I'm using Navigraph AIRAC cycle 1607, just updated a couple days ago. Tim
  20. I hope you look closely at the performance impact of expanding the database. I think it's a very small minority of people that fly 2200 NM flights. Most systems are already stressed with the 737, HD mesh, cloud/weather textures, and feature rich airports. All I'm saying is this could have a huge impact on people that have already bought the aircraft and are running it fine on marginal computer systems as is. Maybe this should be a feature that is a year or two down the road to take advantage of more robust computer processors, and graphics cards coming down the pipe. Tim
  21. ...and there is a really nice replacement checklist by DrNerdRage I believe. Much more useful than the original. Tim
  22. I like Jan's accent too. It feels like I'm being scolded, but in a nice, and polite way. Tim
  23. Your answers helped immensely. Thank you very much. Tim
  24. The IXEG is my first FMC aircraft ever. Since I've been flying the crap out of it, and I see no end in sight, I'd like to update to a current cycle. So, do I understand this correctly: if I purchase the "FMS Data All Cycles (1 year) subscription", then I can use the data on all of the aircraft listed on their manual install page? I can use for my Carenado stuff, IXEG, and the x737? I just don't want to make the wrong purchase, and have to go through the hassle of straightening it out. Thanks for looking. Tim
  25. Agreed! These videos are very well done. They are straight and to the point, with good explanations of why things are being done in the sequence they are being done. No fluff, just good information. Even better is Greame's understanding that this is a flight simulator game. Yes, it's a game, created for entertainment. It's not a procedures trainer, and it's not a level D flight simulator that will get you a type rating, it is a game. The fact that he embraces that aspect, is fantastic. He works the modeled systems in such a way that walks the fine line between real world flight operation accuracy and fun. Because, after all, fun is why we bought this aircraft. He is also very easy to listen to. His delivery is very conversational in nature. You don't feel like you're watching a training video that's been scripted to the N'th degree, instead, you feel like you have a friend giving you the straight skinny on how to fly this aircraft in a reasonably realistic manner, given the limitations of a mouse, keyboard, joystick, and 2D monitor. I think these videos are especially valuable after you already have some seat time in the 737 Classic. After you've watched a bunch of videos, and done some flying, Greame's videos will give you a pretty good road map on how to fix any bad habits you may have formed on your own. Once again, excellent job! Tim
×
×
  • Create New...