Search the Community
Showing results for tags 'known'.
Found 6 results
-
If this is not considered a bug, please move topic to the correct forum Hello dear devs, as I was curious if the AP can handle an Autoland with the new downwash effect, I did a quick test. Conditions: EDDH rwy 23 with weather set to clear (no wind, no rain, no clouds, no turbulence) GW 52,2t 11.32r2 (beta) The plane flared, "ballooned" at about 20 feet RA, then descended again and touched down. So it looks like the autoland function or the flight model (whatever, maybe both) need a recalibration to work with the new downwash effect. Kind regards from Hamburg Germany
-
- 1
-
-
As the title of the thread states, when you enable the "Draw Vortices" option in the side panel, anything that's placed against clouds in the sky starts rhythmically flashing. This is in the current version of x-plane (not beta). Here's a demo video: -
Hi I purchased XP11 & ixeg several days ago and really happy with it (after being devoted fan of PMDG B737NG on FSX). It is a very fluid, immersive and realistic simulation of B737CL, on par with PMDG, if not beyond. However, there is a number of bugs which I discovered having completed about 10 flights so far: 1. While on ground, unable to enter CRZ speed in FMC (e.g. "0.7", "0.72", etc.), "not allowed (or so)" message prompts, this is however possible when airborne; 2. Unable to enter DES speed and speed restriction in FMC, although EXEC prompts, fields remain blank; 3. ANP value not given (0.0); 4. Climb de-rate (apparently) not removed gradually to full CLB while climbing to cruise flight level; 5. By switching seatbelts off at night time cockpit becomes lit with light (dome light apparently); 6. On takeoff, after rotation, "glideslope" aural message plays (I always set NAV1 prior departure to ILS for emerg return, as per SOP); 7. Autobrake either does not perform at all or performs insufficiently for the selected position (I DO arm spoilers on approach with the appropriate light illuminated, and there is no "disarmed" light upon rollout); Please, consider allowing entry of raw coordinates and/or radial-distance waypoint in FMC. This is a pretty crucial thing, I couldn't believe at first it was still not implemented, as it is such a basic thing to have. In general, FMC needs significant further development and refinement. VNAV issues, HOLD page, inhibition of DME-VOR-GPS, custom waypoints, fuel predictions, supplementary pages & functions, etc. It would be also nice if you could specify what exact FMC software version you replicated (U5.0, etc.). Own failure model would be nice too (I'm aware about that small LUA script). Other systems, designs, dynamics, performance (especially fuel burn) are spot on! Thank you!
-
Most of the issues which I have with your aircraft is related to the functionality, 75 USD is a high price to quote unless you think people are paying that money for eye candy. Let us do this in a structured manner shall we. First, the Frames are unbelievably jumpy that is an indication of unoptimized programming. The VNAV is still majorly buggy. VNAV SPEED and PATH can be selected but the integration is poor and doesn't follow the FCOM, there is no provision for STEP CLIMB. Apparently your FMC don't feature a CAPTURE mode. FMC functions by agility tuning which cannot be verified unless the NAV STATUS page is simulated. Speed restrictions cannot be set in the FMC using the DESCENT page, there is a way to do that dial in the speed you want and press ERASE yes you herd me right ERASE NOT EXECUTE. Sometimes VNAV wouldn't engage even when all the parameters are met. VNAV engagement without LNAV till the aircraft is maintained with in the RNP depending on the section of your leg is not simulated. IRS alignment 2nd pass test not done properly check the FCOM for further details. SPEED mode in MCP IS buggy takes a while before the plane realises it has slowed down too much, CUSTOM WAYPOINTS not simulated, OFFSETS and HOLD patterns are a known issue. Right now I am in the process of reading the FCOM just finished 100 pages in the NAVIGATION section and so many issues came up. Then did not mention which version, revision and update version no. of the FMC is simulated. FMC logic with the radios are okay but because of the primitive nature of the radio I cannot manually select the DMEs I want the FMC to use during alignment as reference. Progress page is just depressing quite honestly. Alternate destination has issues as well. VNAV speed and path cannot be interchangeably used if I do that it messes the VNAV path. During level change climb sometimes if I want to reengage VNAV it wont engage. I'm really sorry but the aircraft is not well done and don't use study level because its just not. I seriously regret spending the money. I'm certain in days to come I will find even more bugs as and when I learn about the systems. Every page in the FMC has something or the other missing. Your aircraft is quite frustrating. The ZIBO mod does a better job than you. I'm really sorry but its not even close to a pay ware and you are charging 75 USD.
-
Hi guys, I clipped a video to show one of my landing replays to help highlight a bug where the spoilers pop up rather than deploy realistically. As many might agree, we like to watch landings on replay from various angles as we pretend to be airline pilots, and watching the spoilers deploy realistically adds to the enjoyment! I hope this video helps. It was made in XP 11.05, but this problem existed in XP 10.51 as well.
-
Hello. It seems that the ETO over next WPT on the upper right corner of the ND is not calculated correctly. E.g.: as on a flight today, distance to next WPT was 64NM with GS of 432. Makes a total time of 9 Minutes. The ETO shown on the ND was however 13 Minutes to go from actual time, so a gross error of +4 Minutes. On another leg, the Distance to the next WPT was 251NM at a GS of 431. Makes a total time 35 Minutes. When 251NM from next waypoint the ETO on the ND differed by +22 Minutes from the actual Legtime... Anyone else experiencing this? Edit: when approaching the next WPT, ETO on ND is subsequently updated and is finally down to the correct value when overfyling the WPT. Best regards
