Let's report small bugs here.  Big bugs can get their own topic for more focused conversation.

REPORTING RULES:

 Only submit a bug if you have replicated the same issue more than once! If you don't know how to replicate the issue, we will not know either and we won't be able to do anything about it. 

  How to submit a bug:

• Give us as much information as you can so that we can replicate the bug and then fix it.
• Give us clear steps on what happened and how we can replicate the issue.
• Always submit the Log.txt and Log_X-Crafts_main_debug.txt files when you submit a bug. We cannot help you without the log files.
• Please include the flight plan file Log_X-Crafts_CURRENT_FLIGHT_PLAN.txt as well if you're reporting an FMS bug.

Log.txt

Issue: The "FWD Passenger" and "Airstairs" status does not change after repositioning the plane.

How to reproduce (at least how I did it): 

1. Place the plane in any airport.
2. Attach GPU and turn on batteries.
3. Open the "FWD Passenger" door.
4. Deploy "Stairways".
5. Reposition the plane in a different ramp location (did not tested on the same ramp).

The plane is reset (no GPU attached and no electricity) but the "door" and "stairways" are active. Not sure if that is by design.

However, on my installation with a pretty fast computer, in playing with it quite a bit (nighttime), I'm finding that the lag in the auto-adjusting is a problem. I have multiple cabin cameras (X-Camera) that I jump through as I go through the cabin, and in most cases as I change position, the lighting tries to change but often lags. Sometimes when jumping to the next cam that cabin section of the camera goes into a full bloom (overlit/over-exposed) mode, eventually returning to a good light level.

The other thing I've noticed is that I can adjust the lighting, then jump to an external cam, then back to the cabin cam and the lighting has dropped down/changed a good bit. 

I'm not seeing any real FPS issues when any of this happens, although there is a bit more lag when at a very intensive airport such as EGLL or KLAXv2. But even at simple airports, the slow and somewhat ongoing lighting changes (modulations) detract a bit from using the Dynamic mode. 

Overall, it is a fantastic effect, and hopefully it can be refined and improved. And I can't rule out that it may be just a Mac ARM GPU thing either. But I thought I would at least provide some initial feedback on this fantastic new feature. Not the most important issue by any means, but it is really appreciated as a great step forward in lighting effects, especially with such a great cabin on the Lineage. Thanks again for the efforts to release such a spectacular airplane! 

Another thing I found on the "old" style winglets was that when the Strobe light operates, both the rear and forward facing lights' texture lights up all the time, yet only the actual lighting cone which is emitted by the strobes is alternating. Possibly this is the easiest way of producing the alternating flash sequence, yet it was still a thing that I noticed. I have also linked a video showcasing this:

Whenever I takeoff from an airport, doing a RNAV or non RNAV departure, once I engage FLCH/VNAV after LNAV engages, the SPDe on the PFD completely disappears. This always seems to happen whenever I engage the AP last. In other words, FLCH or VNAV will enable SPDe but it will disappear once I arm AP. This makes the airplane's AT to not hold the FMS speeds.

I have attached the Log texts below from my most recent test flight and the issue happened again. Route was KPIT-KLGA. 

Thank you. 

Log_X-Crafts_main_debug.txt Log.txt

the EFB is not displayed , the aircraft can not be started. 

Log reports that some plugins cannot be loaded

Using Xp11 on Mac. 

Thanks

log-4-xcraft.txt Log_X-Crafts_CURRENT_FLIGHT_PLAN.txt Log_X-Crafts_main_debug.txt

A minute from the TOD I got the aural warning and the diamond on the PFD. Plane began to descend at TOD, descended a couple hundred feet and then leveled off and kept flying at the slightly lower altitude. I put it into FPA to get back on the descent profile. Once on the profile tried twice to get back into PTH by pressing VNAV, but the plane would go into PTH and then nosedive. I flew the rest of the flight in FPA and everything else worked as it should.

The only thing I can think of is that I accidentally leveled off at FL280 instead of FL340. I used FLCH to climb, but had to put it into VS to stop the plane from porpoising as it gained and lost speed. Once at 340 I put it into VNAV to get the magenta ALT readout on the PFD.

I don't think this is the zero altitude bug, as I don't see any zeroes in the flightplan.

Log_X-Crafts_CURRENT_FLIGHT_PLAN.txt Log_X-Crafts_main_debug.txt Log.txt

2024-08-08 18-11-22.zip

Log_X-Crafts_main_debug.txt

One thing is still bothering me and we discussed this earlier in the beta phase. When entering a flight plan with airways/waypoints, some combinations cannot be used although they are valid depending whether upper or lower airways are used.

This issue still exists. For example, in the following flight plan:

EGCC/23L DCT DESIG L603 LAMSO DCT PETIK DCT RKN L980 SAS/N0401F230 Z88 UPDAT T236 ADMOS T959 KOJEC KOJE1V EDDP/26R

you cannot connect Z88 to UPDAT.

For now I use DCT in that case, however it would be great if this could be fixed for the final version.

This is IRL:

This is X-CRAFTS:

After flying over over waypoint "A", the HSI, Map and FMS match and show a current leg "A" - "B". After that the flight continues as expected.

Attached logs and images from an example flight KGJT - KDEN , alternate route KDEN Denver - KCOS Colorado springs.
I have seen this in two routes. It does not prevent flying but I was confused.

Log.txt Log_X-Crafts_CURRENT_FLIGHT_PLAN.txt Log_X-Crafts_main_debug.txt

Log.txt Log_ATC.txt Log_X-Crafts_CURRENT_FLIGHT_PLAN.txt Log_X-Crafts_ejs.txt Log_X-Crafts_main_debug.txt Log_X-Crafts_test_data.txt

Thanks!

Luckily, there's a simple fix. Just delete the plugins folder inside the aircraft package and re-run the updater. That should fix it.

This is NOT related to the CTD when reloading the aircraft, which is a problem caused by a 3rd party. We're currently waiting for that to be fixed by the 3rd party.

I hope that helps!

I tried instaling the jet again, then actived it and it crashed again, I also tried skunkcraftupdated to get the new version, but nothing seems to work

Log.txt Log_X-Crafts_main_debug.txt

It is possible to descend or climb in VS mode and FPA mode away from the selected altitude.
How does the real E-jet behave in that situation. Does it allow climb or descend without altitude limit ?

Pressing FLCH at selected altitude has no purpose, but I pressed anyway.
Aircraft reduces auto throttle power, but keeps the same altitude with some up and down oscillations.
Eventually the aircraft stalls if nothing else is done. How does the real E-jet behave in that situation ?