Hi Wayne, I believe you're wlbragg from the FG forum, with whom I previously discussed the Ramp Marshall. It's a pleasure to connect with you again here. I was eager to share this information in the forum thread, knowing you're actively developing enhancements for the addon, But I thought it might be valuable to first gain some insight into the scripts. Please let me know if there's anything I can assist with in your testing efforts. I'd be happy to help in any way possible. Just one more thing!...
Hi Wayne, I believe you're wlbragg from the FG forum, with whom I previously discussed the ["Ramp Marshall"]{https://forum.flightgear.org/viewtopic.php?f=30&t=20572&sid=764d573de5567a04d69501f2669983c5&start=75). It's a pleasure to connect with you again here. I was eager to share this information in the forum thread, knowing you're actively developing enhancements for the addon, But I thought it might be valuable to first gain some insight into the scripts. Please let me know if there's anything...
I am keen to find answer to those questions too, wKitty.
Hello wKitty, I believe I've identified the source of the error: the Nasal files associated with the Ramp Marshall add-on. Disabling the add-on didn't resolve the issue as we need to add 2 Nasal files manually to the data folder during the installation. I've not took a closer examination of the Nasal scripts to see what exactly caused the error but it revealed frequent mentions of "ICAO," which might be the trigger. It's a shame that the add-on requires modifying the data folder, as add-on installation...
Hi wKitty, I sincerely appreciate you taking the time to test this on your end. Your feedback is invaluable in helping me to determine the scope of this issue. I will try to clear the default and custom scenery folders to see if that helps. I haven't delved into traceback debugging yet, especially after a fresh development environment setup. Are you able to guide me on how to acquire the build info please? On a positive note, knowing that not everyone is encountering this issue helps narrow things...
Replicating this issue is straightforward within US airspace. Specifically, when departing KIAD towards CYQB, the issue manifests shortly after takeoff. One of the ICAO is:- 3md4
Hi Gijs, launching FG with both "--airport=7622" and "--airport=6452" was successful. However, the underlying issue appears to be related to the designated coordinates rather than the selected airports. Thank you so much.
Hi James, You can start at LFBZ and fly on a heading of about 55 degs. It shouldn't take long until it hits the issue. I've attached a screenshot of the point when it happened. Coordinates: 43.603327, -1.313679 Thank you so much.
Hi James, You can start at LFBZ and fly on a heading of about 55 degs. It shouldn't take long until it hits the issue. I've attached a screenshot of the point when it happened. Thank you so much.
I've disabled all add-ons and tested it with UFO. Unfortunately, the problem still persists. Do you have any other suggestions? Thank you.
It's good to find this longstanding ticket. I can confirm, after using UFO in my testing, that the issue remains unresolved.
Hi James, thank you for your response. I'm wondering if my guess was correct:- "when we deselect an option in "AI Traffic and Scenario Settings", it is not removed in the properties.", which is causing this problem. If so, any workaround? Thank you.
AI Wingman Issue
Hi James. I managed to correct the code of the aircraft which fixed the issue. Please go ahead and close this ticket. Thank you so much for the help, James and xDraconian.
Hi xDraconian, I hope you are doing well. I have new finding about the issue. Seems like it only happens when I make use of the Route Manager. I believe the exception occurred in "fgfs.exe!flightplanGhostSetMember(Context * c, void * g, naRef field, naRef value) Line 704 C++" is the culprit. > ucrtbase.dll!_invoke_watson () Unknown ucrtbase.dll!_invalid_parameter_internal() Unknown ucrtbase.dll!_invalid_parameter () Unknown ucrtbase.dll!_invalid_parameter_noinfo_noreturn () Unknown [Inline Frame]...
Hi xDraconian, I did not try the workaround since you mentioned it would be better to fix the aircraft issue. However, I'm getting a different error now. Please see the attached image. :) And below is the debug log. Looks like it is the same issue (please check out the last line) I encountered before this. Thank you so much. 'fgfs.exe' (Win32): Loaded 'D:\Games\FlightGear\Git\FlightGearBuild\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe'. Symbols loaded. 'fgfs.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'....
Thank you for pointing that out, xDraconian. Shouldn't the value be "1" rather than "-1" as shown in the screenshot? I apologize if I didn't understand correctly. Not sure if your "-1" indicates that something was flagged.
Hi xDraconian, I was able to compile the binaries and did a flight test. However, it crashed halfway. I have attached a screenshot of the debug log. Hope you could help me out with it. Thank you man!
Hi xDraconian, I was able to compile the binaries and did a flight test. However, it crashed halfway. I have attached a screenshot. Hope you could help me out with it. Thank you man!
Hi xDraconian, I am thinking of compiling the binaries. Referring to https://wiki.flightgear.org/Building_using_CMake_-Windows, may I know if the repositories mentioned in this article are the nightly or the latest stable version? Thank you so much.
Hi James, I can't remember when it used to work for me off the top of my head. Probably last year June. And yes, same crash dump when all the system DLLs are used. Thank you for always helping out, James.
Hi James, I removed the runtime DLLs but still getting the same issue, There must be something wrong with the 2020.4 nightly build since it works perfectly on 2020.3.17. Thank you, James.
Hi James, hope you are well. Unfortunately no, none of them helps. I just tested on 2020.3.17 but didn't have the same problem Are you able to recall what are the service packs? I'm considering whether to remove other related .dll files in bin folder, eg msvcp, vcruntime...etc.
Not sure if this is helpful, but this is taken from the dump file. Thank you. STACK_COMMAND: ~0s ; .cxr ; kb SYMBOL_NAME: ucrtbase!invoke_watson+18 MODULE_NAME: ucrtbase IMAGE_NAME: ucrtbase.dll FAILURE_BUCKET_ID: FAIL_FAST_INVALID_ARG_c0000409_ucrtbase.dll!invoke_watson OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 6.2.22000.1 FAILURE_ID_HASH: {ff968da7-5196-0e9d-7c2c-c6a2c196fc27}
FG Nightly crashes due to ucrtbase.dll
Hi James, thank you so much for your response. With ALS disabled, it appears to be working fine. However I did not test it on 2020.3.16. Thank you.
Some Metars causing Black Screen with ALS
Thank you, James.
Just wanted to add that the impacted aircraft tested are CRJ 700, DHC 6 and Citation II.
Just wanted to add that the impacted aircraft tested are CRJ 700, DHC 6 and Citation II.
Some sound effects aren't working after updating nightly version
Hi James, so this is a known issue. Is there a workaround at this moment? Thank you.
Unrecognizable Metar Strings
@legoboyvdlp. Hi there. I don't see it after the updates. Please close this ticket. Thank you.
FG crashes all the time
Hi James, thank you for your response. However the logging process slows down the performance of FG. I read from somewhere that it is possible to turn off the debugging using OSG_GL_ERROR_CHECKING=OFF, in Environment Variables. But the instruction isn't clear. I am not sure how I can do that and wondering if that would help.
Hi, New findings: 430.45 [WARN]:OSG C:\Jenkins\workspace\Windows-nightly\install\msvc140-64\include\simgear/debug/OsgIoCapture.hxx:37: Error in reading file : file not handled 430.45 [INFO]:io C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\model\ModelRegistry.cxx:383: Ignoring D:/Games/FlightGear 2020.4/data/Models/Weather/cirrocumulus_sheet1.rgb for inclusion into the texture cache because pixel density too low at 16 bits per pixek 430.45 [INFO]:io C:\Jenkins\workspace\Windows-nightly\simgear\simgear\scene\model\ModelRegistry.cxx:397:...
Error while simulating a thunderstorm
Great to know that! Thank you guys for the effort. On a side note, this is really a good place to report a bug or finding a fix.
Hi peridotite, that works for me! That explains why I felt it was an intermittent problem. I "cleaned up" the flightgear.org folder a few times while trying to resolve the issue. Is this a bug with the version, or just a problem on my computer? Thank you so much!
Is there any way I can download an older build of the nightly version? Thank you.
Hi James, thank you for your response. I was using the Feb build before this without this issue. Just tested current stable release: 2020.3.8 and all was good too.
Findings: Starting FG by command lines without launcher seems to be a workaround.
Log file attached.
No metar available in latest nightly version
Hi Huntley, I hope you had a restful weekend. You might want to join the discussion at FG forum, if you are keen. https://forum.flightgear.org/viewtopic.php?f=4&t=38227
Hi Huntley, No worries. That sounds good to me. I really appreciate all your help and effort.
Hi Huntley, I just test flew it after making the change to aoa value. Unfortunately, the problem still exists. Set right crosswind @ 10 kts. On the second attempt, I touched down at a lower speed around 80 kts, pulled the yoke back further than first attempt. It still swerved right but this time I was able to quickly steer to keep the aircraft on the centerline.
Hi Huntley, I just test flew it after making the change to aoa value. Unfortunately, the problem still exists. Set right crosswind @ 10 kts. On the second attempt, I touched down at a lower speed around 80 kts, pulled the yoke back further than first attempt. It still swerve right but this time I was able to quickly steer to keep the aircraft on the centerline.
I can see the stall aoa value is different from the original configuration. I will give it a shot.
Hi Huntley, I'm really bad at this but I will give it a try. May I know if the attached YASIM configuration has been corrected to what I'm expecting or I will need to alter it? Thank you .
Hi Huntley, Great to hear that you were able to see the problem. This is my first time reporting a bug here. So will someone (or you) be fixing the FDM files in FGaddon if the problem has been identified? How does it work? Thank you.
Hi Huntley, Thank you so much for your findings. I have not seen other versions, probably you can share them with me. I understand about weathervaning, but the aircraft seems to act abnormally when landed on the runway in crosswind. Even with the nose gear down after flaring, there is no way I can control/steer it. I have reached out to one of the members in FG forum (someone whom I loves all the aircraft he built) and he told me this is caused by the rudders (FDM), not gears. Do you mean this behaviour...
Cessna 550 Citation II landing bug