Create branch feature-td-calculation from 777
invalid branch
Jean-Yves Lebleu dev
invalid branch
Jean-Yves Lebleu dev
test: wip afds tests
test: update fuel test to be copliant with the updated code
fix: keep the preselected qnh even after transition altitude
fix: handy viewer displays the correct views
feature: can change standby qnh when in STD mode
fix: reverse now properly disengage auto-throttle
AFDS: Integrate WEU flap speed settings and enhance TOGA exit logic
PFD: Improved artwork
Sync updated assets (iCCP color profile updates) from upstream r15277
WEU: trying to clean it up a bit. Still a disaster
AFDS: Display 'RESET MCP ALT' on CDU
AFDS: Fix typo
AFDS: Remove Todo item: Mach-IAS switching logic
AFDS: Add helper functions for mode management
AFDS: enable auto IAS/MACH crossover in VS mode
AFDS: Refine IAS/Mach switching logic
AFDS: Implement IAS/Mach switching logic and add crossover constants
XML: update aircraft version and formatting
AFDS: Reduced some getprop and setprop
AFDS: Use maketimers for AP annunciator and fix a settimer storm
Electrical: reduce timer freq from 100hz to 20hz
AFDS: Fix PFD speed tape
Liveries: Added CES for 77W
AFDS: fix PFD airspeed
Datalink: update wxr api
AFDS: Code formatting and small optimizations
AFDS: Use me instead of afds when referencing inside the class
Hopefully r180 should fix this - testing needed
AFDS: Fix LNAV bug when directing to a waypoint
VOR R and ADF R not working in 2024.1
Fixed by r179 and pushed to FGAddon trunk/2024.1.
Fixed by r179.
Electrical: Fix DME R and ADF R not powered in 2024.1
It seems like that, unlike in 2020.3, in 2024.1 the power supply for adf and dme are separated. I'm having a hard time finding information about how should the dme and adf be powered, I think I'll supply them with lbus for now before getting more information.
It looks like unlike in 2020.3, in 2024.1 the power supply for adf and dme are separated. I'm having a hard time finding information about how should the dme and adf be powered, I think I'll supply them with lbus for now before getting more information.
VOR R and ADF R not working in 2024.1
I can reproduce this issue. This appears to be an electrical issue: adf[1] and dme[1] are somehow not powered in 2024.1 version of FG. Further investigation needed.
VOR R and ADF R not working in 2024.1
Bugfix: fixed ATC service in range button
I found that the problem description is not very accurate, but anyways, fixed by r177
Nav lights not controlled by cockpit switch
fixed by r177
Electrical: code formatting
Fixed nav lights still on after aircraft is powered off (a dirty fix, should revisit the entire lights controling logic someday)
xml error
Fixed by r175
Fixed xml warning (I don't fully understand this stuff yet, but it seems that we have to add the property tag inside input tag)
xml error
Problem with rendering on Windows 10
Rendering issue with Intel Graphics
Version check not working on 2024.1
Fixed by commit r174
Fixed version checking logic
Version check not working on 2024.1
Version check not working on 2024.1
Change autostart key to something else
Change autostart key to something else
Nav lights not controlled by cockpit switch
Nav lights not controlled by cockpit switch
Autopilot issue
Rendering issue with Intel Graphics
[AFDS] Refactor the input handling in AFDS.nas for readability and maintainability
I guess that's what you'd expect when you have no scenery, otherwise currently I really have no idea of what/where the issue is, sorry. Maybe try fixing your scenery issue first and see if anything changes? Kind regards, Sidi
yes. I tried 747-400, 787 and default Cessna. Outside scenery is messed up in all cases but internal flight deck is rendered correctly in them.
It's more likely a FG issue I think, have you tried other aircraft?
Problem with rendering on Windows 10
Instrumentation: Remove groundradar as it's not being used and causing trouble for AMD users
ND.nas: code formatting
Fix minor autopush bug
Add missing textures; autoconnect bugfix
Tweak jetway doors
tune wingflexer (again)
Finish autoconnect, add Autoconnect dialog, add functionality to automatically connect/disconnect 3D Jetways (also enabled in payload dialog), make settings persistent only if 'Store Ground Services between sessions' is enabled.
Improve deboarding/unloading logic and time calculation.
Wingflexer bugfix
Tune wingflexer
wingflex
wingflex
Branch CPDLC development (stalled)
Small checklists update
VC: Animation fixes
Liveries: Update UAE livery by Delta5142
hi Sidi, Sorry for the late reply. I can't think of any more optimal solution than my implementation. One optimization I can suggest is to replace the string comparison with an integer and send the same from the mobile app. BTW, my app is complete and is working fine and I am able to program the 777 CDU with this app. Here's the path to the repository. https://github.com/nitinsane/virtual_cdu_app Thanks. On Sun, Jan 15, 2023 at 3:18 AM Sidi Liang sidi762@users.sourceforge.net wrote: Hi Nitin, I've...
Nasal: Replace true and false to 0 and 1 for best compatibility as true and false are now keywords of Nasal
Switch from the old splash pictures to the preview images
777: Bumped version to today's date and enabled preview splash screen
Hi Nitin, I've read the code and understood what it's doing but I wonder if that's the optimum solution. I'd like to hold this ticket and wait until your external app and hardware to be finished, and see what we are going to do next. Does that sounds good to you? Kind regards, Sidi
Liveries: seperate liveries from different variants (should be last commit)
777: Restore a file that should not be uploaded in last commit
777: 2023
Liveries: seperate liveries from different variants
Liveries: seperate liveries for each varient
Thanks for contributing! I'll review it shortly. Kind regards, Sidi
interfacing external CDU hardware
Please note that the data from /instrumentation/cdu/key property gets sent to FG via the generic protocol using UDP from the external hardware.