klem

Towards the end of the BoB some Squadron commanders had come to the conclusion that the Vic was not fit for purpose. Various changes were tried at Squadron level including two side-by-side fours, each four weaving to keep a look behind. Some had the tail-ender do the weaving and allegorically often lost the weaver without realising because no-one else was watching behind. I don't suppose Douglas Bader was the first to use the finger four or four abreast but in May 1941 Johnny Johnson attributes the idea, in 616 Squadron and the Tangmere wing at least, to Hugh 'Cocky' Dundas who suggested it to DB having observed the LW flying style. Some other Squadrons converted to it, some didn't for a while but eventually it was taken up by all of Fighter Command although I don't know of an official edict.

Well, they're definitely quite thick but they wouldn't 'stop one'. :D

It all happens around 37mins in.

If that's a prophylactic you've been sold a bit <cough> short :music_whistling: They were covers made for the job.

It was red sticky canvas tape to prevent general weathering effects on the guns (including icing). Ground crews were always happy when they taxied in with holes blown in them :)

Yes, even that, but at the moment it isn't working (well, I tried in in NTTR up around Fallon).

Well, if the Normandy map doesn't yet have Southern England I'd be happy if a flat generic strip could be added, say 20 miles deep, with just coastline if the map tools will allow us to lay down our own fields for now in ME.

If I am reading things correctly I believe the DLC Maps aren't being updated with DCS Updates and Mission 3 Southern Red CAP references appear to be wrong (~E-W instead of ~SE-SW) https://forums.eagle.ru/showpost.php?p=2916109&postcount=5

What Guide? I had the same problem. It is even easier when the Maps are updated - NOT - so you have to go to the /Downloads/Documentation/ page and get the latest copies of the briefings: https://www.digitalcombatsimulator.com/en/downloads/documentation/ I read somewhere that the campaigns were automatically updated with DCS updates but apparently not. The original map has WP7 >> 290' >> WP8 >> 250' >> WP9 >> 160' >> WP10 which is why the brief "sweep west to 9" then "Sweep N to WP10/CAP West" doesn't work. The current map is now: WP7 >> 270' >> WP8 >> 250' >> WP9 >> 355' ** >> WP10 >> 060' >> WP11 and CAP between WP10 and WP11(all headings approx). ** This is Sweep N to WP10/CAP West and now the briefing makes sense! Oh, and the Southern Red CAP BE references are wrong.

Me too.

Was that the choice - pedals or shoes? :megalol:

Yes but some of us are already struggling with fps and don't want to reduces settings further just to see extensive rail tracks. If sections could be added in ME as targets that would be different.

performance hit ?

If it helps, here's mine. 'Brake Pads'.

Also be sure you have enough spring strength on, I recently adjusted mine after a year or so as the spring had relaxed a little.

I have a chair that locks the wheels when you sit on it. Unfortunately the plastic internal dog-tooth locking soon broke up so I added 'brake pads':- I used cushion floor off-cuts, each 15mm x 6mm x 3-4mm thick and super-glued them under the wheel arches so that when I sit down the pads are pushed down onto the wheels. Works like a charm even though three or four pads have come off (I will glue back on). So if you have vertical movement in the wheels, try that.

FOUND ONE! After weeks of searching I fell over this: http://www.freeapkdownloader.com/apps/remote-macro-keys,1628644/ along with this http://creation-web-dijon.fr/files/RemoteMacroServer2.zip It communicates fine with DCS on individual keystrokes/Fkeys but there is a multi-key glitch being worked on, i.e. it doesn't complete, say, Ground Crew attach ground power, sent as: \;F8;F2;F1 (or #;F8;F2;F1 in UK) It opens the comms menu but doesn't get any further, leaving the next menu on show - probably a timing problem. Developer is fixing this, hopefully only a couple of weeks away. He also plans to allow customising the buttons (shape, color etc). It will be very useful for people that don't want to buy say the CH Controls Manager but have a Tablet (or even a smartphone). You can create and load a separate profile for each aircraft from within the Tablet App so it's easy to switch aircraft profiles in-game. I'll keep the forum posted on the new version when it comes out.

I've had X36, X45 and X52. All considered good value for the money but the support went down the drain with MadCatz. It's getting near that time when I ought to upgrade and would like to find a really good FFB stick but of course there isn't one. Lets hope Logitech can marry their driving wheel FFB to a good stick. Still using the X45 ("re-packaged") for prop control and various switch/button controls alongside the X52.

EDIT: Stop right there. See second post. I've been trying to get my Tablet to send hotkeys to DCS in much the same way as the CH Control Manager does but of course from the Tablet. The most useful PC Server/App I've found is this: http://4pda.ru/forum/index.php?showtopic=248611 It allows custom keys to be defined. It works very well in firefoa and a few other programs but it doesn't like DCS. I contacted the developer who said that it doesn't like some 64 bit programs and he doesn't support it any more. He also said it is open source and "you can fix it yourself if you wish". I do wish but I wouldn't know where to start. Source files are here: https://github.com/pilgr/piHotKeys The question is does anyone out there have the knowledge to get it working with DCS. I suspect it's something to do with the 32 bit Libraries it invokes. If anyone can that would probably be very useful for many guys and gives a zero cost alternative to CHM etc. for anyone with a tablet. Also, it uses a set of hotkeys defined in the file hotkeys.xml stored on the Tablet. It would be nice to be able to select different HTML files from the Tablet for different a/c profiles. Here's hoping...

Wot, no Fallon? :music_whistling:

True. Drifting a bit OT now but it may provide another reference: my 4 monitor ~8.3 MegaPixel panorama plus in-game instruments below runs around 30-60 fps depending on height, location. version etc. Of course it drops to stuttering over Las Vegas but I don't need to go there. Many setting reductions are not immediately obvious to the eye and the panorama plus instruments is as near as you'll get to being 'in the cockpit' without VR (which isn't up to a good enough resolution standard yet or I'd get one and improve the fps). Version 2 runs about 5-10% better than 1.5 on same settings. Specs below.

A bit OT I know but it also affects which servers are available to fly in. There are a depressing number of servers with no-one in them and often at the most just 2 or 3 (I know there are time zones involved). There are a few that are more of a magnet but the thinly spread player base and wide aircraft choice can make it hard to find a server with good numbers and my aircraft of choice at the time. I'm happy with the aircraft choices, just wish more would fly as an online community in good public missions rather than hiding 2 or 3 players behind 20 passworded servers.

.... and I thought SA meant Situation Awareness. Now I know... Simaholics Anonymous. Where's the phone.........

We have the same problem at our museum. We use X52's and the users, mostly kids, are supposed to be supervised by a guide when on the sims. Unfortunately it seems some parents can't read. Ah, well, we only have to repair them a few times a year.

You must be very proud. I volunteer at a museum where this kind of story would be welcomed as 'Oral History'. Sadly there are few left to tell the tales.