Post by dazaxiii on Jan 17, 2010 14:47:26 GMT -5
I don’t use AI smooth or any of those kind of programs so occasionally I do get lots of aircraft on finals at busy airports and have to execute a go around or two. To try and combat this with time element of FS Captain I set the “deny ETE this close” to 5 (I assume this is miles) as you can usually tell by then if a go around is likely and I could therefore adjust my ETE time appropriately. However, on my last flight I was 21 miles out on finals according to the ILS and was denied a revision due to being too close to destination.
So is that a bug or is there some code in the software which chooses to accept or deny revisions based on more than just distance? Either way I think it would be nice if the time aspect could be edited by the user so they can use the software in a way that suits them. My two ideas, although I don’t know how workable they are.
First is the ability to input in the administrator + and – figures for what is “on time” In my case I could then set half an hour late to still be acceptable and not have to worry if I get a couple of go arounds. Second would be an extra command in the FCOM where I could report a go around to my dispatch and then automatically a set period of time, perhaps 10 minutes, gets added to the ETE to cover this.
It just seems a little unfair that if I fly perfectly to ATC instructions and then get told to go around then that isn’t my fault, it’s the idiot in the tower. But even though it isn’t my fault I can still get a minus figure for it.
While I’m typing I’ll just add one more thing. The FCOM button layout. Is there a reason why the keys are in columns F2 below F1, rather than rows which to me would seem more intuitive as most of do read left to right in rows.
Thanks in advance and keep up the good work. I’m still loving it. ;D
So is that a bug or is there some code in the software which chooses to accept or deny revisions based on more than just distance? Either way I think it would be nice if the time aspect could be edited by the user so they can use the software in a way that suits them. My two ideas, although I don’t know how workable they are.
First is the ability to input in the administrator + and – figures for what is “on time” In my case I could then set half an hour late to still be acceptable and not have to worry if I get a couple of go arounds. Second would be an extra command in the FCOM where I could report a go around to my dispatch and then automatically a set period of time, perhaps 10 minutes, gets added to the ETE to cover this.
It just seems a little unfair that if I fly perfectly to ATC instructions and then get told to go around then that isn’t my fault, it’s the idiot in the tower. But even though it isn’t my fault I can still get a minus figure for it.
While I’m typing I’ll just add one more thing. The FCOM button layout. Is there a reason why the keys are in columns F2 below F1, rather than rows which to me would seem more intuitive as most of do read left to right in rows.
Thanks in advance and keep up the good work. I’m still loving it. ;D