View Single Post
  #5  
Old 08-05-2010, 05:41 PM
Blackdog_kt Blackdog_kt is offline
Approved Member
 
Join Date: Jan 2008
Posts: 2,715
Default

That was something that's been mentioned in the past and i think there were also some screenshots showing that it was possible for SoW to have recon photos in the briefings.

My ideal briefing workstation would be like a small in-game html browser/editor with a few plug-in tools. Say you join a server with an ongoing dynamic campaign, fly recon, land back at the base and then make your recon pictures available to the team lobby.

In order not to put burden on the servers it would have to be a peer-to-peer exchange, but that would strain the player's bandwidth while he's flying. So, it could be something like an integrated file-sharing application...so you set the options like "make this file available from me, for a maximum of 3 simultaneous connections". Or, you could have unlimited connections and upload to your entire team but for a limited time period. Then when you're about to fly a sortie and need a good ping you could stop uploading it and the people who already got it could keep uploading it to the rest of the team. Something like bit-torrent for recon photos and flight plans, where users excange the necessary intel between missions without putting any strain on the server.

To take it one step further, the same picture could be edited once it's downloaded into your briefings and the same could be done for waypoints and maps. For example, say that your team is planning a multi-layered mission. It would be a mess to have all flight plans displayed on one map and all items marked on the recon photo. So, the same photos and flight plans could be modified, with elements added, subtracted or simply made invisible to help in planning.

To see how this would work, let's assume we join a server running a dynamic BoB campaign and we are flying for the axis team. The guy leading the He-111 bombers would draw up his flight plan first, mark known enemy airbases and flak concentrations on the map and mark the targets and aiming point on the reckon photo, along with other points of interest (eg, flak batteries in the vicinity of the target that are visible in the photo). Maybe more than one people could make notes and changes to it at the same time (collaborative editing), so that while one is finalizing the fligh plan another one is drawing circles of flak and radar coverage and enemy interceptor ranges. Then they would save this as "bombers.html" and upload it to the leaders of the fighter groups.

Now, these guys would have a wealth of information regarding the bombers' route. The close escort group would probably use the flight plan as it is. The forward sweep would use the original bomber route to decide on which areas to cover, draw up their own route and then either delete or "hide" the bomber flight plan, save it with a new name (eg, "fightersweep.html") and distribute it among themselves, probably not bothering at all with the recon photos. There could also be other groups, for example a flight of 110s going in low and fast for flak suppression. These guys would get the original "bombers.html" and modify it, so that it displays only their own flight plan and different intel on the recon photo. They wouldn't need to know the He-111's aiming point, but they would surely mark the locations of flak batteries covering the target on the recon photos. This could be saved as "SEAD.html" and distributed among the group.

Finally, when every pilot got the appropriate briefing, he could be allowed to make some changes on his own before launching the mission. Changes to waypoints could be possible even when flying the mission. For example, let's say that my He-111 is mauled over the target and as we leave the target area i have to drop formation and head to the nearest base. The prepared flight plan would be useless to me, so once i stabilised my plane i could draw another one. Deleting all the previous waypoints i would draw new ones that take me to the nearest friendly base, while avoiding as much of the dangerous areas as possible. Or, i could have the complete flight plan for the operation but the routes of the other groups were hidden. If i chose to momentarily toggle them as visible, i could see if my emergency RTB route takes me close to one used by a fighter group, so that maybe i could pick up a couple of 110s to escort me across the channel. Of course, to do this we would need 3-4 course plotting tools docked to our minimap display, like the ones used in Silent Hunter III.

I know my ideas sound crazy, but i know they also sound useful. The good thing is, if Mr. Maddox and his team have allowed for the use of image/text files and scripts in briefing and AI, there is no limit to what the community could come up with. For example, you could be running a navigator script that calculates estimated time of arrival to the end of the route and to each individual waypoint, estimated fuel burn and so on. It would not only be useful when trying to nurse a stricken bomber back to base, it would also be like having a full interactive crew. You'd still have to take the final decisions yourself but you wouldn't have to do everything on your own. Instead you would have the necessary information from your crew members to decide on the best course of action, just like real captains used to do.
Reply With Quote