Davee

:lol::thumbup:

RTFM! :)

Gun convergence was fixed according to RAF doctrine. It initially was set for 400 yds Battle of Britain but was subsequently changed to 250 yds. However, some senior pilots had their mechanics change their personal convergence to closer ranges - 100 yds. Tracer worked as a guide to aiming but with .303 calibre it burned on the way to the target and was depleted at longer ranges thus losing some effectivemess. What is more important was the loadout. A mix of some tracer and ball early on but after the BOB, incendiary ammo such as the DeWilde was introduced and included in the belting. NOTE: With the DeWilde it is IMPORTANT to ensure that there is a flash on impact with the skin as this was the main way in which it ignited. It is not a tracer but used contact to become molten and penetrate hot. It was extremely effective. It resembled small orange sparklers all over the target. For the .303 they tried AP but it proved innefective as it would only penetrate the skin and not have enough energy to damage underlying components. Therefore withdrawn from service!! But, please explore the loadout of the 20mm Hispano cannons because that was another issue. With the larger shell, AP and incendiary did extroadinary damage. Sound: The sound of the .303's is similar to "Heavy fabric being ripped" Quote.

Just a question - doesn't a dark comms menu mean that you don't have the correct frequency selected on the radio? Not sure on this.

:thumbup: (moot)

Nothing to do with procedures. Please read the posts again carefully. :)

Are you sure? Never thought of that. :)

Me as well! I spent hours yesterday trying to sort this out - it appeared to update (from the start menu), then when I ran the program it wanted to revert back to the previous version. I also got the "update not available" when I again tried to update to the latest from the start menu. I then deleted the program, re-installed completely fresh and got the exact same problems. Finally, I renamed the OpenBeta folder in the saved games and launched the program. Voila it worked. I then copied over my config, missions, kneeboard files to the newly created OpenBeta folder.

Works for me. Just a thought - is it possible that you have another locked keypress being sent by your HOTAS? For example: Shift, Ctl, Alt key or perhaps a toggle switch transmitting at the same time you press backslash key?

+1 The aircraft does not bleed speed very much with throttle closed even at slight nose down and when a mild turn is made the airspeed drops very quickly. Also, when in landing configuration and the flight marker within the brackets, I noticed that with a slight touch of the throttle the response is jerkish and shows on the HUD as if the POTS are dirty. However, I have HAL sensors and they work clean in all other situations.

+1 Plus a better shutdown sequence of sounds.

:thumbup: Just to add, when the engine received damage, the exhaust ports involved skipped the firing order or belched smoke. The damage model of the engine is linked to the graphics engine. Leaning out of the cockpit is a markII eyeball confirmation of the issue.

In another currently available SIM that is based upon the BOB, you can see the exhaust glowing but more importantly, you can see the exhaust flame change colour from orange to blue (clear in daylight) when the engine is running properly. (mixture) Also, you can see the flame dancing between the different exhaust ports in the correct firing order. That to me is really emmersive especially in the evening/night missions.

Does "Bitchen Betty" sound like the "Swedish Chef"? :)

I took some time last evening to search Youtube for Spitfire startup sequences and discovered several variables by different pilots and different variants of the Spitfire. For the most part, any differences I found seemed to be related to pilot personal preference and were minimal. Two however caught my eye - one involving the magneto switches and one the engine cutoff lever cockpit left side. Initially WAGS showed the pre-start check ensuring that the appropriate systems were off. Standard procedure for all the video I saw. (safety). Regarding the cutoff lever - WAGS showed the lever full back and then forward as the engine turned over - most startups did indeed show the lever in the back/off position during the priming and electrical sequence. It became clear to me that it was off in order to prevent a premature engine turnover should something be pressed that shouldn't be pressed. But . . . . the only difference I saw was that the lever was pushed forward just prior to ignition rather than during ignition. Potato/Potahto. In general terms, WAGS procedures appear to be similar to most of the vids I saw and any differences were minor - for example: after priming, WAGS had the primer pump pushed in but not locked. Vids showed pilots leaving it out and then pushing it in and locking after everything was warmed up. (leaving it out was in case it had to be re-primed during a difficult start and also appeared to be for visual reference that it was still unlocked.) Again - no biggee! Lots of interesting stuff to see there. I'm really looking forward to this magnificent mix of art, science and technology.

:smartass::thumbup:

Excellent, now if WAGS would hold off on startup sequences until Mr. Grey approved them . . . . . . :)

Not sure whom you are referring to but if it's Cripple - he's dead-right with the controls issues. Spit dedicated enthusiasts would see these issues right away and then watch the fireworks. Hope they are corrected before initial offering.

:thumbup:

They also resolved this in earlier variants with Mrs. Shilling's orifice.

Just curious why you wouldn't use a "Press/Release" command? MapKey(&Throttle, MSU, PULSE+'q'); //description MapKeyR(&Throttle, MSU, PULSE+'q'); //description or as in my example below for radar management. //RADAR MGMT - VIEW ZOOM// MapKey(&Throttle, MSU, '-'); MapKey(&Throttle, MSD, '='); //MapKey(&Throttle, MSP, ); not in use. MapKey(&Throttle, MSR, DX4); MapKey(&Throttle, MSL, DX6);

Study up on propeller pitch and rpm's . . . . :)

Yup, Saves everyones time if you read the manual first then Chuck's guide second!

Yes, I have it mapped to my throttle trim button as an alternate press. Before landing, I reset the trim. The light goes out and there is no warning buzzer wheels down.