![]() How the plugin works for a given user is controlled by that user though - presently it's not possible to force all clients to do the same thing. The client log shows what the plugin has extracted and from where. ![]() Where an ID is provided along with frequency or location data, the user supplied data overrides that derived from the database. The plugin ships with a global database of stations, the ID of which (such as EGGD_TWR, or KLAX_APP) may be provided in place of explicit frequencies and location specification. In it's simplest mode of operation, all that is required for setup is for the COM frequency to be associated with the channel to be included in its name, its topic or its description and these are searched in that order for information.įor more advanced operation where range is to be considered, the Lat/Lon may be specified in any of the above fields in the format Nxx.xxxx Exxx.xxxx (obviousy S and W may be used). It has however only been tested with FS9, FSX, P3D (I don't know which versions) and X-Plane 10 and 11. The plugin should work with any simulation that provides an FSUIPC style interface. The program was born from work originally undertaken by ATC_ROO which offered the basic channel move functionality on the 32-bit version of TeamSpeak only.įrom there it grew such that it was possible to offer a degree of control over which channels in the list were to be considered for tuning (the BFSG has three separate groups which maintain their own channel set on the same server - we didn't want people moving between those channel sets), multiple modes of operation (Disable, Manual - where it is possible to manually move oneself between channels as well as tuning stations, and Automatic - where the only movement between channels is controlled from the cockpit), the behaviour of the plugin when no station is tuned, the consideration of range as a factor in whether or not a station may be tuned through to most recently allowing more than one frequency to be assigned to a single TeamSpeak channel. That functionality was to be able to automatically switch between TeamSpeak channels through tuning the radios in our simulated aircraft. BFSGSimCom was originally written for members of the Bristol Flight Simulator Group (BFSG) after we'd migrated from TeamSpeak2 to TeamSpeak3 only to find that functionality that we'd previously enjoyed with the earlier version was no longer available to us.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |