Avwriter Posted January 8, 2018 Report Share Posted January 8, 2018 Hi guys, I know this issue has been mentioned a few times in different threads, but I wonder if FeelThere/Nyerges have seen it, or have a fix in the works. To summarize, commanding an arriving aircraft to "vacate runway (left/right) onto taxiway xxx" causes the sim to respond that it cannot and that the runway is too short. This command worked beautifully until a couple of months ago, and no longer does. It happens multiple airports (have not tested all of them, but have seen it at KLGA, KLAS, KBOS). Not sure whether it is connected with the most recent SP for Tower3DPro, or the most recent update to Nyerges RealTraffic. As I asked, have Vic and the developers acknowledged this issue yet, or do we need to document it with a log file? Andrew Link to comment Share on other sites More sharing options...
crbascott Posted January 8, 2018 Report Share Posted January 8, 2018 http://forum.simflight.com/topic/84644-tower3d-pro-exit-at-taxiway-strangeness-ft-andor-nd/ Link to comment Share on other sites More sharing options...
Avwriter Posted January 8, 2018 Author Report Share Posted January 8, 2018 Thanks Craig. Searched but missed that thread somehow. Andrew Link to comment Share on other sites More sharing options...
crbascott Posted January 9, 2018 Report Share Posted January 9, 2018 Posted it only a couple of weeks ago and it has already pushed to page 4. Busy forum! Link to comment Share on other sites More sharing options...
FeelThere Ariel Posted January 9, 2018 Report Share Posted January 9, 2018 Hello Andrew, Could you please provide us the game log? It would help us greatly! Kind regards, Ariel Link to comment Share on other sites More sharing options...
Avwriter Posted January 9, 2018 Author Report Share Posted January 9, 2018 I will try to generate one, next time I see it, but the .bat file does not usually run on my machine. However, there are multiple logs posted in the thread mentioned above. See: Andrew Link to comment Share on other sites More sharing options...
scoobflight Posted January 10, 2018 Report Share Posted January 10, 2018 10 hours ago, Avwriter said: I will try to generate one, next time I see it, but the .bat file does not usually run on my machine. However, there are multiple logs posted in the thread mentioned above. See: Andrew thanks! :-) each user that has an issue a log just helps ID the issue as each system is slightly different and can manifest issues differently (that IBM for 'outsourcing' the PC development 'back in the day'). Link to comment Share on other sites More sharing options...
crbascott Posted January 10, 2018 Report Share Posted January 10, 2018 Highly unlikely in this case, but you're the moderator ... so what you say goes and what posts you decide to delete goes too apparently Link to comment Share on other sites More sharing options...
VenturaGuy101 Posted January 10, 2018 Report Share Posted January 10, 2018 Craig, one of your posts got deleted? I thought that you way beyond the call of duty to research this bug. I am still wondering if anyone @FeelThere or @NyergesDesign saw the Vacate Runway bug that I posted with logs where accepting the command but then exit at a runway and direction they choose. It happened at KSAN. I hope FeelThere can find the issue since it is at multiple airports. It really causes issues at busy airports where planes do what they want and not what the controller needs. Link to comment Share on other sites More sharing options...
winsaudi Posted January 10, 2018 Report Share Posted January 10, 2018 FT, May I ask if your work has identified the cause of this bug? When may we anticipate an SP that fixes it? (And I thought my deleted comment was valid as it sought to avoid going over old arguments yet again). Link to comment Share on other sites More sharing options...
FeelThere_Vic Posted January 10, 2018 Report Share Posted January 10, 2018 Folks, As always we investigate each report, but before we can identify anything it's pointless to say anything. So yes, we are checking it. Vic Link to comment Share on other sites More sharing options...
winsaudi Posted January 10, 2018 Report Share Posted January 10, 2018 Welcome back Vic, At least we know the problem is recognized by FT and is being looked at. It appeared from an earlier FT post that some employees had no clue that the problem has been discussed a lot on this forum, investigated, reported, logs sent etc, etc. Then someone deleted at least a couple of posts that dared to highlight the string of previous discussions on this matter! Wayne Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now