Re: RCs public previews
Posted: Sat Feb 02, 2019 4:37 am
RC23 crashes after selecting a SID. Competely new installation, current AIRAC, new settings file, no multi-voices. XP11.31r1, Win 10 x64.
The function looks for the closest airport, and look for the pertinent ACC. There's not call to SDK, X-plane doesn't provide any acc data.RandomUser wrote: ↑Sat Feb 02, 2019 3:23 amDowngraded to RC22 and redid my last flight (EDDV - LEPA; viewtopic.php?f=9&t=17&start=180#p3919)
Good: No X-Plane crash.
Bad: No SID selection, no STAR selection, no center handoffs.
Again: How does the handoff and center lookup work? What X-Plane datarefs or XPLM functions are accessed? What does 124th do internally to trigger a center handoff or a SID/STAR selection?
XPLMFindNavAid is called globally in order to find the closest airport, but the frequency function doesn't interacts with SDK
Sorry for the late response. I can't say that for sure, but I tend to say no, at least the crash would not happen immediately after using a custom command.ntnll wrote: ↑Mon Jan 28, 2019 9:42 amLast line of the log are the custom command invocation for the flight information. Did you noticed any correlation between the crashes and the custom command?
argonius wrote: ↑Tue Feb 05, 2019 11:35 amSorry for the late response. I can't say that for sure, but I tend to say no, at least the crash would not happen immediately after using a custom command.ntnll wrote: ↑Mon Jan 28, 2019 9:42 amLast line of the log are the custom command invocation for the flight information. Did you noticed any correlation between the crashes and the custom command?
I am currently busy with my aircraft upgrade project, thus I did not have time trying to reproduce / verify a correlation with custom commands. I'll do as soon as I find some time
Roughly three minutes
Any chance this could cause a crash when, coincidentially, being near a 1°x 1° dsf tile boundary?
That's correct. Which is the fp is causing most of the crashs, is it the following?RandomUser wrote: ↑Wed Feb 06, 2019 6:19 pmAny chance this could cause a crash when, coincidentially, being near a 1°x 1° dsf tile boundary?
If I understand you correctly, every three minutes, 124th will invoke "XPLMFindNavAid" using the current aircraft latitude and longitude as input parameters and "XPLMNavType = 1" (airports) as inType, match the result with the list of airports in acc.dat and retry if there is no match?
Crashes vary with flight plans and there is no reliable indication what could cause them.ntnll wrote: ↑Thu Feb 07, 2019 8:14 amThat's correct. Which is the fp is causing most of the crashs, is it the following?
(EDDV) WRB RANAX EDEGA AMETU SOGMI BOMBI GIGET ABUKA KRH PABLA HERBI MOPAN OLBEN LUTIX BENOT NEMOS VEROX MILPA GIRKU BALSI KOTIT RETNO DOTIG GIROL TUPOX MTG DIVKO VATIR PIVUS SULID SISMO KENAS (LEPA)
No. My only mod was adding Warszawa Center, but that one is default by now.Did you ever modified the acc.dat? If yes, please try overwriting it with the default one.
As I've posted before, I've managed to complete the flight on another day.In the last tests I made, I was unable to replicate the issue, I'll try again this evening.
RandomUser wrote: ↑Fri Feb 08, 2019 12:17 am
Did you get center handoffs during your test?
And have you considered redesigning the center lookup logic?
My first idea was using the real airspace boundaries and point-in-polygon logic, but this is very hard to implement
My second idea is using X-Plane's map grid and assign a center and frequency to each tile (could be reasonably accurate), store it in a database similar to acc.dat and then have 124th somehow determine which tile the aircraft is on and simply read the associated center's frequency from said database.
This would be a lot faster than basically continuously scanning any surrounding airports for the ones that are in the database, but so far, I have not found a quick and easy way to get the number of the scenery tile that the user aircraft is on at the moment.
I normally ignore it too (but then you normally need to ignore altitude as well and stick to the STAR altitudes, otherwise you end up to high at IAF, like in the example above I was still at FL150). This time I have "obeyed" to show how weird the vectoes given are.RandomUser wrote: ↑Sun Feb 10, 2019 8:27 pmWhen flying STARs, I usually ignore vectoring calls.
Ideally, 124th wouldn't vector you at all if the current approach mode is STAR (and only provide speed and alitude clearance), but you'd be able to revert to a vectored approach at any time (to make a short visual final or so).
Speaking of: Can the "Look for SID/STARs" function from the flight plan tool be moved to the controller dialogs?
"Request clearance (no SID)"
"Request clearance (pick SID)"
"Request clearance (Auto-SID)"
"Use vectored approach"
"Use STAR approach (pick STAR)"
"Use STAR approach (Auto-STAR)"