jeff64

great. thanks

thank you. I will check the gns settings. Another question : any way to switch the baro settings to hpa in the pfd ?

Hello all Just bought the entegra SR22, and constated some discrepancies. I used it with RXP GNS. First : the waypoint name on PFD and MFD Secondly : on the MFD the green arrow should represent the aicraft actual ground track. I don't know what this triangle is showing (maybe the CDI), but it is not correct. There should be a magenta triangle showing the desired track. Thirdly : the cdi track was constantly jumping. You can see on the picture it is pointing 20° right, instead of straight ahead. I noticed some engine discrepancies too, but need to try it again. Dit not try with Laminar stock GNS

I have had the same problem on ALL of my aircraft, intermittently. I tried to troubleshoot this evening, and think this can be cause by activesky xp. Do you have this problem on this addon only ?

And below 1000rpm, you can eventually stall the engine if it is cold (already happenned to me on a.....SR22 G2.)

assist will just give you the delta peak, meaning the difference between current EGT and Peak, and should show you which cylinder is the first / last to peak. You see it in this video

Sorry no video, but the idea is the following. Leaning is a matter of Exhaust Gas Temperature (EGT). When you lean, the EGT will rise, till it will reach a peak. If you continue to lean, the EGT will drop (until a point where the engine will run roughly and eventually...shut down). Best power is done around 75°F on the rich side of the EGT Peak. This is called "75 ROP" or "Rich of Peak". You will burn more fuel, but will go faster. Best economy is achieved around 75°F on the lean side of the peak. This is called 75 LOP, or "Lean of Peak". You will go slower, but will consume less fuel. When you click assist leaning and start to lean, there will be a little indication which will tell you which cylinder will reach the peak the first (if you seek for ROP) or the last (if you seek LOP), then which will tell you the temperature difference between current and peak. It helps you in finding the correct setting for 75° ROP or LOP. Your engine is really sensitive, and one of the most precluding factor on the long term is you cylinder temperature. In cruise, but especially in climb and descent, you must : - keep the CHT below 380°F (the best), or at least below 410°F. Above 410°F can still be inside the limits, but will not be good engine management. - avoid shock cooling, especially in descent. I think I heard a rule of thumb is to limit the CHT reduction to less than 50°F per minute. But hey, this is simulator. Fucking an engine or a cylinder is not as expensive as in the real thing !

Not 100% sure it is a bug, but when changing frequency with the GCU keypad, it currently needs to press enter for the new frequency to be taken into account. As far as I know, the change does not need to be "ENTER"ed to be effective.

Hello all Since the release of the TBM, I was astonished at how the runway was small on the SVT. I fly on a (real) G500 equipped aircraft, and you have a good depiction of the runway at least to 10 miles, which allows you to correctly place your flight path vector on the runway threshold on the PFD. In the TBM, you only can distinguish a small box, and the runway really appears when you are a few miles to it. Lately I did a flight on this G500 aircraft, and on final, noticed that the runway depiction on the SVT was similar to the TBM one. And suddenly, I understood the reason : this specific day, I was doing conventional IFR training without programming the GPS. The aircraft did not know which runway I was going to, and for this reason, did not painted the runway until the short final. SO, THIS MEANS the HOT START TBM SVS Runway depiction is not correct, cause it does not differenciate if the runway is part of the flightplan (in which case it needs to be depicted very early on the PFD) or if the runway/airport is not part of the flightplan in which case the depiction is currently correct. Thank you for taking this into consideration in a futur update.

looking at those logs I see : 2019-11-16 11:20:34 TBM900[crash.c:455]: collision detected in zone wing_root_right (flex: 73.88, limit: 0.24) Maybe a conflict with the scenery ? edit : did some tests with another aircraft. There appears to be some "walls" on my scenery I keeping crashing one. And one of them appears to be right where the problem occured. So that's a scenery bug, not a TBM or myself one

here they are Log.txt TBM900_Log.txt

log_191116_100807_LFMT.csvHello there Strange thing today. I was doing a short flight from Montpellier LFMT to Cannes LFMD. Everything went smooth. Landed, exited runway, short stop to perform after landing actions, and continue taxi. While I was slowly taxiing, I received an caution alert + CAS Message " LOW LVL FAIL RIGHT R". I notice the right fuel level is crossed. Almost immediately, the windshield fully craks, the aircraft stops, the engine quits and takes fire. I position the throttle to the cutoff position, pull the crash bar, and evacuate. I don't understand what could have happened, because I don't think I mismanipulated the aircraft, the aircraft did not bounced nor hurted anything on the scenery. I attach the logfile. Hope it is the correct one. What would have happened for you ?

you also can press "ENTER" on the G1000 key pad

in the TBM menu, you have a menu for "visual effects", where you can activate or deactivate glass effects (impact performance)

shit I did not saw your messages earlier Cpuwolf gave me the same advice today. I updated flywithlua and it works like a charm now ! thanks