Thank you Karim, for kind update.
1 Like
You have already landed there with a cj4 and had taxi light penalty but not strobe… now with this airplane just the opposite..
Landing lights instead are always ok..
- Do you have a separate button to turn on strobe and taxi?
- Do you switch off the strobe lights, in this case, in the same moment you turn off the Landing lights?
- I see both taxi and strobe lights, when it occurred, just after turning into the taxi way. I usually , when lamding , turn taxi on , and turn off strobe, while still on runway, before leaving the runway.
Take into account that simfly detects a taxi procedure, when your speed is between 4 to 30kts.
dc-6, il problema è lui , lo fa in tutti gli aeroporti , lo riconosce correttamente alla partenza ma non registra quello che stacco sempre in pista prima di fare il taxi , ho provato a fermarmi 5 minuti in pista e poi passare in taxi , ho provato a staccarlo prima , dopo nel mentre evia dicendo ma l’errore è sempre li , che poi magari mi dimentiochi qualche volta anche su altri arei è tutt’altra cosa , con il dc-6 l’errore c’è sempre
dc-6, il problema è lui , lo fa in tutti gli aeroporti , lo riconosce correttamente alla partenza ma non registra quello che stacco sempre in pista prima di fare il taxi , ho provato a fermarmi 5 minuti in pista e poi passare in taxi , ho provato a staccarlo prima , dopo nel mentre evia dicendo ma l’errore è sempre li , che poi magari mi dimentiochi qualche volta anche su altri arei è tutt’altra cosa , con il dc-6 l’errore c’è sempre .
il problema è che negli anni 50/60 quel tipo di luci non esistevano , quindi in manuali veri dove per esempio la redbull o altri li usano ancora , usano le luci di posizione in " position " e in " steady " questo però non funziona , a livello storico si potrebbero usare le Beacon (Anti-Collision Beacon) equivalente storico delle moderne luci anti-collisione ma anche qua poi se accendi i motori dovresti accenderle e quindi poi ti danno altro errore come se li spegni in pista prima di fare il rullaggio verso il parcheggio
dc-6, the problem is him, it does it in all airports, it recognizes it correctly at departure but it does not record the one I always turn off on the runway before taxiing, I tried to stop for 5 minutes on the runway and then go by taxi, I tried to turn it off before, after in the meantime and so on but the error is always there, which then maybe I forget sometimes even on other planes is a completely different thing, with the dc-6 the error is always there. The problem is that in the 50s/60s that type of lights did not exist, so in real manuals where for example Red Bull or others still use them, they use the position lights in “position” and in “steady” this however does not work, on a historical level you could use the Beacons (Anti-Collision Beacons) historical equivalent of the modern anti-collision lights but even here then if you start the engines you should turn them on and then they give you another error as if you turn them off on the runway before taxiing towards the parking
Ok.. ovviamente si puo chiedere a simfly di eliminare la penalità strobe dal dc-6..
Ma sul pannello c’è la posizione OFF ,oltre a position flash o steady. Immagino che non funzioni lo stesso..
No, non funziona lo stesso , ho provato tutte le combinazioni possibili , l’unica volta che non ho ricevuto l’errore era spegnendo le beacom , ma poi altre volte facendolo mi ha dato altri errori , non è che me ne freghi più di tanto ma alamno una risposta …
poi parlo più di procedura vicina al " reale " che per i due di penalità che alla fine non fanno nulla … e per le non risposte …
I don’t speak italian, but I don’t think this light problem is related with the problem of Taxi in or out not recognized in some airports, removing 10 or 12 to each flight score there and then involving PAX deduction for every landing/takeoff.
probably a separate ticket could be an option ?
Separate ticket?
Already done…twice but never responded, so now I’m “polluting” other posts…maybe it helps 
1 Like
Hello everyone,
We have resolved the airports that were reported and are currently investigating additional cases.
Resolved airports:
-
URRP – Platov Intl, Rostov-on-Don (RU)
Runway 05/23 updated: the placeholder grass strip has been replaced with the correct concrete runway geometry. -
KCRP – Corpus Christi Intl (USA)
Runway 13/31 has been realigned and corrected, and runway 17/35 has been added. -
HESX – Sharm El-Sheikh (EG)
Runway 10/28 has been extended and runway 16R/34L has been added. -
ZSYN – Nanyang (CN)
Runway 22/04 has been corrected. -
UUDD – Moscow Domodedovo (RU)
Runway identifiers and coordinates have been updated:
14C/32C → 13L/31R
14R/32L → 13R/31L -
ZJHK – Zhengzhou Xinzheng (CN)
The parallel runway 10/28 has been added. -
VDSA – Siem Reap-Angkor (KH)
Runway 05/23 has been added, as it was previously missing from the database.
We have also investigated the following reports and determined that no changes were required:
-
NIUE – Investigated and left unchanged. The OSM offset is only around 9–11 meters, which is below our 30-meter tolerance threshold.
-
HESX 16L/34R – Investigated and left unchanged. It matches OSM data within approximately 7 meters.
-
ZJHK 09/27 – Investigated and left unchanged.
You can now test these airports again. If the taxi procedure is performed correctly, taxi-related penalties should no longer occur.
This is our first solution based on community reports while we continue reviewing and correcting individual airport issues. At the same time, we are also working on a larger update of the airport database to improve overall accuracy across all airports.
If you find any other airports with potential issues, please let us know so we can investigate them.
4 Likes
Yesterday I opened a ticket “again” and posted in other posts a problem that I reported a very, very long time ago…
Yesterday with the ticket open I also reported a new problem, is it possible to know if you are taking into consideration the things reported?
Below is the text of the ticket opened yesterday…
**Subject: penality
Message:
*Good evening, I completed this flight 019e83a4-e4ed-7cd1-be08-b0ff8854eddf and I have two penalties.
First, as always, the strobe lights penalty, which was reported a long time ago. Now another penalty has been added, namely the one regarding a pause. On this flight, as on 019e6543-6633-77ec-9b98-c6a404a77217 or 019e7afd-3092-70d6-9f58-6fd08e036245 or , I didn’t use any pauses. I don’t know if you can see the times, but there were no pauses anywhere. I would like clarification on these penalties.
As for the strobe lights on the last flight, before entering the taxi, I turned off all the lights possible.
As for the breaks, it seems to me that something has changed on the latest patch, and a thought goes to when using external cameras in flight, I would suggest investigating this, as it is the only thing I do during a flight to take photos or anything similar.
*
Operating system: Microsoft Windows 11
Flight simulator used: Microsoft Flight Simulator**
Thank you Karim. These updates are greatly appreciated! Will try HESX today.
2 Likes
Yes, we have received it and we are working on it.
We will update you through support as soon as we have completed the necessary analysis and resolved the issue.
Can I also suggest to double check your keyboard/mouse/joystick binding. You can search also by “command” , if you write down PAUSE, see what keys or buttons show up..
Also check key combination of Xbox live tool bar or another app used, maybe there are similarities.
or also if you went on the settings page (obviously without going to main menu) on that particular flight ?
Sometimes , in order to take pictures I simply use the Keyboard PRINT SCREEN button, or call up screen capture from windows menù
Thanks for the suggestion, I had checked, but this shouldn’t be the problem since the error always indicates the same time on flights and in one case it lasts more than 20 minutes if I remember correctly in one case, so maybe when I exit the cabin view and switch to the external one maybe it mistakenly takes it as a break
Hello, Arrival at URRP Platov Intl. works well: no taxi penalty. I will test the departure after and I’ll report the feedback. Thanks,
2 Likes
Excellent, thank you for the update. I really appreciate it! 
2 Likes
Hello again. Departure test from URRP - Platov Intl. —> OK - No taxi out penalty registered. Many thanks!
2 Likes
A new case in MHPR
Taxi in was short, as most times with me, usually not a problem.
And I’m sure the landing lights were ON at take of 
Haikou Meilan (ZJHK)
The problem with the taxiway lights on the North runway has been resolved.
Pilots can now take off and land on any runway and use any terminal without fear of taxiway light penalties.
Thanks to SimFly and the users for all their contributions.
3 Likes
Hi, we’re currently carrying out additional checks and tests. I’ll update you as soon as I have any news.
1 Like