Rene Feijen

With 1.06 I can at the moment run with AIF 16x, about 20 minutes test flying Varjo Aero 39 PPD 36 fps smooth at FL240 above Australia, and upscaling in the Ohnespeed OXRTK mod. Occasional a microstutter.

Started 1.05 today, with AIF 16x > CTD Will now do AIF 4x EDIT: With AIF 4x now 10 minutes in flight...

Started well now with Aif 4x. FLying about 15 minutes without CTD. Have to test more of course, but encouraging.

For me it is a bit different: I put on my Varjo Aero, get an outside view, and when I want to center my view or when it is centered and I enter the cockpit view (I then already entered the cockpit with Shift C in 2D mode) then I get a CTD. Sim freezes for a moment and then CTD.

Finally got rid of it with the Clear button. Tested only once though.

For me the A350 CTD's happen in MSFS2024 mainly when I switch from 2D to VR. In MSFS2020 I have the TCAS issue, and fps was very low with BATC Traffic Injection. But good fps without traffic injection and no CTD so far (only 2 flights done) without TCAS.

I get a annoying warning repeating warning sound after landing manually. Messages in amber only says AP OFF, which is true..... but should not trigger an alarm? And I can not click the warning sound away. Anyone has an idea?

Wanted to fly LFPG EGSS in MSFS2020. After startup and long long taxi to 09R, the moment I switched on TCAS I got a CTD. So will try without TCAS indeed.

I now updated to 1.02, and finally I could fly the A350 in VR in MSFS2024 without immediate CTD when entering VR. Hopefully it stays like that, will test tomorrow longer.

For me the A350 does a CTD as soon as I activate VR in MSFS2024. Latest Varjo Base driver, latest Nvidia driver. DLSS4. Dont have this problem with other planes.

Update to SU1 beta requires to have 2024 installed and bought at all. Not cheap. (I myself am not complaining about this in particular, I have it installed, but many have not)

I had sort of the same. I could get it to manual VS mode. But then at Cardiff it overshot the ILS in APPROACH mode, did a go around, and then the A350 came in sort of a holding pattern at a random point over the sea, and did not react on any inputs anymore. So ended the flight mid-air. MSFS2020.

I updated to the latest Nvidia driver, 572.69 yesterday. Performance in 2020 and 2024 in general is smoother in VR now. In 2020 I have no problems with the A350, but in 2024 with only the A350 as soon as I want to fly in VR I get a CTD. Not so with other default or addon planes. No problems in 2D.

Works indeed fine with the update in 2020 also now! Great!

Navigraph Charts works fine in 2024 version A350.

BTW I do see the ENROUTE chart, which I suppose is also Navigraph by the looks of it.

In MSFS2020 I dont get the EFB to sync the weather on the TO Performance page. Importing Simbrief on the right side of the same page does work.

Same problem here with Navigraph charts in MSFS2020. Have to try in MSFS2024 yet.

I had the same. I knew already of the DH speed bug, but thought it was only optical, because we could also (hope to) rely on the blue line for set speed on the speed tape. But apparently the DH bug not only prevents showing a set speed but also actually setting a speed.

That is what I meant to say. From the gate I do pushback, and after pushback I wanted to taxi to the left, but it went right. THEN I did pushback again (on the taxiway, so strange /wrong place), as described above, and then I could use my rudder fully finally in both directions.

After about 25 flights without taxi steering problems, today , after pushback, I could only taxi steer -after pushback stopped- to the right with my TPR pedals. (although rudder pedals and tiller in cocpit turned left) . I pressed pushback STOP again , and a bit random again pushback straight and then pushed for a turn. Then STOP again... et voila... my rudders worked again for taxi steering. My 2 cents.

Aha... activating the approach phase on the FMCG. Never done that before. Cant remember seeing youtubers doing that but maybe overlooked? Will try.

A friend on mine (living in another country) practical always has autothrottle kicking in in the approach phase. I suspect his speeds are outside limits for normal (auto)land. Now I dont have this problem. Am I right to think that I first have to select a stage of flaps, thus allowing AT in PROF mode to let the speed go down, do a next stage of flaps, etc. And not the other way around: waiting for the speed to come down (which I would say will not happen in PROF mode but in some manual speed mode), and only then selecting flaps? Is somewhere in an SOP or FCOM described what to do in what order?

Thanks, nice to know, I have just started part 4 of my RPL MLA theoretical lessons, about Aircraft Aerodynamics and Performance.