Right I only see two things worth addressing here:
1.RADAR
Quote:
Originally Posted by Osprey
4 minutes delay
This 4 minutes delay for response is interesting since information cannot be absolutely up to date. I'm trying to find out the delay between RDF station and reporting to the squadrons. 4 mins seems a long time, you could cross the Channel in that time. An alternative suggestion is that the flight leaders have a time delay between plot requests of a few minutes, so once they request and get feedback they cannot select again until that time has expired - this would add in the random factor for LW course changes and human error until visual confirmation, it would stop a flight leader from just hammering the button!
|
Quote:
Originally Posted by Osprey
About the 4 minutes delay. It appears to be bang on because the RDF data went through a filter station (where people examined the plotted information) before being passed to the FC bunker - this website is definitely worth a read.
http://www.ventnorradar.co.uk/CH.htm
"The edited data was assembled as markers on a large plotting table and this showed the situation as it had been something like four minutes previously : since then the bombers would have flown about another fifteen miles"
This is interesting too. Vector was only confirmed with the second reading.
"Repeated plots became the direction of travel (vector) with the height and estimated number of aircraft repeatedly confirmed"
CH was blind past the coast and then the OC was used. But was the delay resolved for the BoB???
"With the separate raids thus identified, the information was passed to an Operations room staff who could then make the tactical decisions regarding the deployment and vectoring of the defending aircraft, either those already in the air or presently on the ground, towards their ever moving targets. It was found that those best equipped to calculate the required courses were recuperating experienced pilots as they were able to better visulise the everchanging relationships between defending and attacking aircraft. However, once the enemy aircraft had crossed the coast the CH RDF could no longer detect them and then the Royal Observer Corps reports to the Filter Room became the sole means of tracking the enemy."
"The system of having to use correction charts before reporting plots to the Filter Room contributed to the four minute delay and and sometimes of course the human factor introduced errors. This problem was solved by 'The Calculator'. Designed and installed by the Post Office ( which later constructed the Colossi computers for Bletchley Park) and using relays and uniselectors, this little known and uncelebrated early form of computer automatically added the correction factors to the input plots and displayed the results visually as the grid reference. The machine could also correct heights in the same way and a mechanically linked teleprinter could send the data by telephone line to the remote Filter Room. Ventnor was equipped with its first calculator in June 1940 and received its second in April 1941."
|
All of which can be found here:
http://forum.1cpublishing.eu/showthread.php?t=30979
OK, so we can see that with help from the community, especially Kodiak and Osprey that we did our best to make the most realistic radar system possible within limits.
I cant currently find the part where WE (the community) decided a 1 min delay for requesting needed to be added to a 4 min delay in the message - essentially making it a 5 min lock out! However, it was agreed the Squadron Leader should not be able to "spam" it.
With this consideration I see no reason why the request lock out should not be 1 min (the time it would proberbly take to get through and talk with control) and that the information delay should not be 4 min with the estimated course as per normal.
EDIT1: I will have to double check this is indeed the mechanics of the script and that this is possible but Im pretty sure this is how it works and is possible.
SO FOR EXAMPLE:
SL (SL means tail number 1 or "A") connects to a single radar station. Requests information. waits 1 min, requests again. waits 1 min, requests again. waits 1 min, requests again. waits 1 min, requests again. Now he recieves the Estimated Plotted course from the position that is 4 mins old and gets a new Estimated Plotted course that is four mins old every min for the next 3 mins or as long as he kept requesting.
HOWEVER this does have certain draw backs. using this method the report will not track the same contact only reveal the closet applicable target. So you might find you are on wild goose chase as two targets are kneck and kneck in range but in two totally different sides of the radar. Just a thought
AIRCRAFT:
I dont think anyone would mind if the Spit IIa was used instead of the Spit Ia, we used it before and no one complained, however if anyone seriously does mind can they please speak up. This would also mean ground starts for the Spits.
Spitfire Ia substitution for any Hurricane is NOT going to happen. This is a historical campaign and we dont want to make it "fair" we want to make it accurate. You cant have the BoB without the Hurricane! You may however have the 87 or 100 Octane - Red teams choice.
Please also see the OP in this thread and here:
http://sowc.forumotion.co.uk/t8-how-...ill-be-run-bob
S!
Ok official mode off:
MY OPPINION:
Im not going to tell the red team what to do but I would consider the overall team tactics you are using (which you are doing by considering having "ground control") and
especially the altitude you guys fly at but what do I know?!