April 29, 20233 yr I know this is a bug reporting forum, but I thought submitting a feature request (which might drum up some support from fellow forum users) here might be better than submitting a blind email to Pilot2ATC... So, I am using SimBrief exclusively for flight planning (who doesn't these days? -- with apologies to PFX/LittleNavMap/etc fans) and Pilot2ATC has a nifty feature that allows direct importing of the flight plan (no export/import required!). Of course in SimBrief one sets the airline code and flight# when flying airliners and so I think it would save a step (which I always seem to be forgetting) to autoload the airline (e.g. DAL, UAL, SWA, etc.) and flight# into P2A when pressing the Import from SimBrief button. The same feature could be applied to GA, I suppose: Callsign/tail#, e.g. Cessna 167TJ, Skyhawk 167TJ, Barron 167TJ, etc. I further suppose there could be a checkbox to enable/disable this "auto import callsign from SimBrief" feature (just in case one doesn't want to use it), either in settings, or each time when importing from SimBrief (or both, with the former providing the default specified in Config and able to be over ridden at the time of import). Don't want to make the feature do complicated to implement, though... Anyway, this would save me a lot of heartache when I get P2A connected, listen to ATIS, file the flight plan, get my 737 powered on from cold & dark, and then finally request IFR clearance, only to realize I need to connect P2A over again after forgetting to change my callsign (all while draining fuel while the APU is running). Maybe not a big deal to some, but a HUGE deal to me! Thank you for listening! Tim Jahns / Tucson, AZ / MSFS / ProSim B738 (usually)
April 29, 20233 yr Hiya Tim, perhaps I'm not fully understanding your issue but doesn't the "import call sign" on the import flight plan page in P2ATC do the trick? Mario Di Lauro
April 30, 20233 yr Author Well I must be as blind as a bat because it sure does, i.e. the upper checkbox to the right of the text box button containing the text "Import SimBrief' does indeed import the call sign. I guess my confusion was (from a UI perspective) that the box around "Import SimBrief", which looks like a section divider, implied to me that the checkboxes did not apply to that function. Oh well, now I know. Thank you for the clarification in any event! (Btw, I see the "Import Procs" checkbox works as advertised also.) -Tim
Archived
This topic is now archived and is closed to further replies.