Sheikh

A VERY nice person gifted it to me. Muchos Gracias Gordo!!

Cyprus is not an area of a contention in the current Levant theater, nor is it a combatant, and it only has several British military bases on it, the British base at the Sovereign Base Areas of Akrotiri and Dhekelia, as well as several outlying encampments for supporting those bases, The Famagusta base is currently inactive due to that area of Northern Cyprus being under Turkish control. Sooo... unless you want to control the Turkish controlled area or launch from there, something that is very unlikely given the current state of affairs in the Levant, Cyprus isn't really worth including in the map.

thanks

In the Controls menu for the F15 it lists these two commands, so I slaved them into my HOTAS,but no matter what radar mode I'm in, or what missile I have selected, the selecting the Next aircraft or previous aircraft seems to have not affect on the targeting order when the missiles are launched. Is this a bogus Command set, or does it actually have a function in DCS? Also, 'Auto-lock nearest aircraft' Doesn't seem to have an affect either. Thanks.

Methinks thou doth protest too much...

Beta is not to make it broken The whole point of Open Beta is to check that things are fixed, and getting better, not to find the fubar's. When an 'update' actually makes a module less usable, that's a step backwards. It also shows that ED didn't do any QC on the module to see if they could discover if their patch had disabled something or not. DCS wide we had illumination problems for the last week on almost every aircraft, including stable FC3 planes that don't need much in the way of tweaking. This weeks 'fix' addresses almost all of those illumination issues, but with proper QC before release they would not even have occured Some of us may sound like petulant 2-year olds, others sound like the Curmudgeon in the Cul de Sac who tells kids to get off his lawn. But we ALL suffer, probably needlessly, due to coding errors from ED, most of which is probably not even necessary to go near. I, too, am very tired of the wonky things that happen, like the elevation foible from the last 'fix' on the TDC, or the RWR warning that should have never existed. It seems that with all the 'coders' that ED employs, you could set aside one guy per airframe to thrash it and check for these little foibles before the update is released. It SEEMS like that would be the case. If I was involved I'd have at least some dedicated testers doing nothing but checking things for compatibility. Since this is apparently not the case, it points to a severe problem with ED's business model, which is ingrained from the top down. The way to stop all this is to just not fly, not participate, and not buy. ED will get the message very quickly. But no one is willing to do that. I've solved more than one problem in my life by throwing it back at the guy wanting me to check it out and telling him to fix it himself. Suddenly peoples attitudes change when they realize they do not have you over a barrel. I can go back to the F15 any time I want, and I do it a lot. The F18 will eventually come around. But at least I have a backup plan.

Registration Name: Sheikh Squadron: TAW 33rd TFW "Death Rattlers" Country: USA