fs1

Well, you can change all CFG fuel parameters, if this is what you mean

Yes, you can fine tune all FDEs

Let's keep calm guys. Thanks

Guys. This is the reference of FDE 2024. And all parameters https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/CFG_Files/flight_model_cfg.htm

Thanks, well it is in development still. But basically is a tool targeted for devs and final users to fine tune the FDE in a very simple intuitive way. You can also check the changes very easily in the sim.

Hey! I am coding a new FDE Tool for MSFS 2020 and 2024. This will be able to fine tune the FDE very easily. I need beta testers, so any interested ones can send me an email to: fsprgrs [at] gmail [dot] com or DM me. Devs are welcome as well. Thanks Federico

Kyle, I am researching into this, making the cameras in the VC and 2D gauges work without performance issues. I will be able to share the results when ready for the benefit of all fsx developers.

Getting a texture from DirectX does not cause any stability at all - maybe there is a misconception here. The only complexity and delicate part is to code it, which if done correctly it's safe and works without any problem. This is true, 3 cameras = 4 times repeated rendering (3 cams and the main view).

Amazing job Jon !!

Dear All, The J41 FMC has another BUG. In my previous post User Defined Waypoont are missed by the AP, due to a problem in the calculation of the Latitude and Longitude coordinates by the FMC. In addition, Offset Waypoints do not work. For example, I entered an Offset Waypoint: Parent Waypoint: KFHR Radial: 120 Degrees Distance: 16 NM The LAT/LON for the Offset WPT thrown by the FMC is: N48 19 28 and W122 45 14 which is wrong. Please see the right Lat/Lon calculation at http://www.movable-type.co.uk/scripts/latlong.html Basically, the FMC has a serious BUG. I have submitted several tickets and the team is trying to contact the Developer who coded the FMC but no luck. Can someone in PMDG help me? Thanks Federico Sucari

Chris, I am working with the support Desk to fix this. They seem to be good, so may be it is a good idea for you to open a ticket as well? I would like to see this fix.

I am in contact with PMDG support team, as it seems to be a Bug in the FMC.

I found the problem. The FMC doesn't compute the right Lat/Lon when inputed by the pilot. What I did was I created a FPL with a user defined Waypoint. Then I saved it to a RTE file. When I open the RTE file I find that the FMC rounds up the lat/lon to the minute (no seconds!!). For example: If you input the KFHR waypoint by hand through inputing its correct lat/lon, instead of N 48.5220 W 123.0244 (correct lat/lon for KFHR), you get N 48.5167 W 123.0167 (which is rounded to the minute!!). Same when inputting KLAX, instead of right lat/lon the FMC throws N 33.9333 W 118.4000 (same, rounded to the minute) I need PMDG help! Thanks, Federico Sucari

Screenshot of FMC exact moment crossing TEST waypoint Federico Sucari

I fly the TEST leg, reaching waypoint is ignoring the decimals. The lat/lon (above in picture) are the same as thrown by FMC. Federico Sucari

Dear Sirs, Hope all is well. I have a problem with the FMC and AP in the J41. I have made a FPL through the FMC, where one of the Waypoints was user defined (not offset), I have entered manually POS: N 48 31.19 W 123 01.27 OverFly: YES When flying to this Waypoint, the Autopilot misses it, it flies (EXACTLY) over N 48 31 W123 01, ignoring the decimals (or seconds). Please note that when flying to an existing Database Waypoint this issue doesn't happen. Can anyone help me? Thanks Federico Sucari