Der Michel
-
Posts
300 -
Joined
-
Last visited
-
Days Won
10
Content Type
Profiles
Forums
Downloads
Posts posted by Der Michel
-
-
still an issue in 1.1.0
-
still not fixed in 1.1.0
- naming of Anchor Point is still wrong
- the achor point (it's avirtual one) has to be displayed on ND
- during descent the FLS glidepath was going up and down during last few hundred meters. (magenta double diamond)
-
CDA looking good so far
-
With 1.1.0...
So, we have now the VIEW ALONG ACFT TRK message, but the logic during cockpit preparation is wrong.
Magenta part according changelog implemented....I don't see any.
Radioaltitude: check
The rest of the issues still to do.
I would say...still a long way to go.
-
The ILS and HDG overflow box at ND and PFD is not updated with correct value in TRUE mode:
-
still an issue in 1.1.0
-
still an issue in 1.1.0
sorry, but this is basic stuff for the F-PLN building logic!
-
still an issue in 1.1.0
-
still an issue in 1.1.0
-
1. With the ADIRUs off, there can't be any GNSS position at the GNSS page of the FMS.
- "For initialization purpose and GNSS position validation, the MMRs receive the last valid A/C position from the ADIRS through the Aeronautical Radio Incorporated (ARINC) 429 bus. Once initialized, each MMR sends the GNSS calculated data (GNSS A/C position, etc.) through the ARINC 429 to each Air Data/Inertial Reference Unit (ADIRU)."
2. The altitude of the GNSS should indicate the AC altitude. Currently at EDDL it should be ~ 148ft
-
1
-
FIXED, can be closed!
-
Ok, the big update is released. Thank you!
I will cross check all my reports during the next days…may take some time.
I already missed some really big issues in the fix list. We will see…
-
1
-
-
You can delete discos, except the one behind a manual leg.
-
1
-
-
@Eddie did you also forward this one?
-
30 minutes ago, Captain Mako MSFS 2024 said:
Hiya all,
Do you all have similar problem when about to start loading the airport with A350-900 then CTD??
MSFS SU3 Beta 1.5.10 updated today.
Yesterday I completed a long haul flight and no problem.
Just set the today flight before I start to FCR load from yesterday. Started loading now then CTD. It is unplayable now.
Also I can't move back to SU2. See below from Steam App.
Information you might like to see if problem with A350. See attached file.
Inibuilds, help please?
Thank you.
And how is selecting just NONE ? Won't you leave by that the beta and be automatically in the stable SU2?
-
1
-
-
It's a large scale SU3 Beta problem. Not related to the A350 in first place...
CTD loading into 1.5.10.0 - Sim Update 3 Beta | MSFS 2024 / CTDs - Microsoft Flight Simulator Forums
-
Since we didn't get an update last week, I assume you are working towards the large scale update? With all bugreports being logged I also hope that this update will not only cover ULR and HUD, but also a very, very long list of bugfixing.
Please take your time with the update, especially testing the fixes and new features.-
1
-
1
-
-
@Eddie also this one, please.
-
@Eddie is this one also logged?
-
1 hour ago, foliainfx said:
Does it change if you press REFRESH?
No, when I pressed instant loading (set ZFW) refresh doesn’t change anything.
I think the AOC is a preliminary ZFWCG. What’s missing is a message with the final ZFWCG. So the OIS/EFB one might be the correct one.
But some clarification by ini would be welcome, if its a bug, if a final loadsheet is missing and what is the correct value.
-
1
-
-
And some info what speed is relevant for what to compare with:
-
7 minutes ago, Eurosky said:
RNP approach v RNP AR approach.
The FLS function becomes available if the crew selects a VOR, RNV, GPS, LOC or BAC approach on the FMS arrival page.
LS pb pressed on the EFIS control panel. FLS capability appears on the FMA.
RNP Approach operations corresponds to RNAV(GNSS) or RNAV (GPS) operations. Equipment needed: One FMS, One GPS, One MFD, Two IRS, related KCCU, One FD, One PFD on PF side and Two NDs.
Procedure to fly this approach using F-LOC F-G/S. The FLS function can be used if the FLS capability is F-APP or F-APP + Raw.
RNP AR on the other hand will NOT be flown using the FLS function. APP-DES and NAV will be the FMA indication. Lateral guidance is NAV and vertical guidance is APP-DES. LS Push button OFF.
Long story short, RNP approach can be flown using FLS. RNP AR cannot be flown using FLS. Picture above is correct for a standard RNP approach.
This is how it is on the A380. Would be surprised if it is different on the A350.
Yeah, correct. I was talking about RNP AR. But you will get exactly the same picture if you try to fly a RNP AR. And deselecting FLS is not working (which shouldn’t be necessary).
-
There is another big bug I already reported. A RNP appr can’t be flown with FLS. It shouldn’t be avail at all for that type of appr.
-
2 hours ago, foliainfx said:
It's dashed when the FCU altitude is different from the CRZ ALT entered, this should also be fixed in the next update already
NO.
Last picture from my last post. FCU alt 5000. CRZ ALT is definitely higher, you also see the dashed vertical profile. And here the vertical line at the end of the scale is solid, not dashed.
And the other photo....FL400 pretty sure the current CRZ Level...dashed when arrow is displayed.
Now this photo:
Also FL400 and pretty sure the current CRZ level...solid without arrow.
Sad to say I am losing hope with this aircraft now (v1.1.5)
in Systems
Posted
I have also the same impression. It's the first post from me since a long time. I only checked the last changelogs and didn't take the A350 for a ride. In the past I posted so many issues, but I have not the impression there is anything going on. Yes, maybe in future with a slow cadence.
At some point I will revisit the A350 and check all my reports. But to be honest, I'm not expecting anyting.
Currently they are working on the A340 and it willl have the same issues.