S77th-GOYA

Not affordable for every country. Some countries can afford all they will need.

A reminder that the deadline for requests is just a couple of hours away.

A couple of well placed main battle tanks might break people of that habit. :smilewink:

To change approach direction, set the wind to blow toward the direction you want to approach. If it doesn't change, increase the wind velocity. (post more)

In general, most new online pilots don't scan as actively as they should. Maybe it would be better if you posted what you do and what happens when you do.

Welcome to LockOn Community Exercise Red Flag 2008. This thread is an information thread only, just as last years threads. It ill be designed to disseminate information to the community about this mission LOCERF 08-3. Please post your questions etc over on the 159th forums found here: http://www.the159th.com/forum It will continue to be the official spot for all planning etc. Please be advised that the LOCERF rules have been amended and can be viewed here: http://www.the159th.com/forum/viewtopic.php?t=3387 LOCERF 08-3 DATES: The next mission will commence at 0500 zulu on 31 May 2008. If you are interested in participating in the next RedFlag please PM me no later than 14 May 2008 at 2300 zulu. You must include in your post: Number of Slots Requested The type of aircraft you request (for example 3Sqn requests 4 Su-25t's and 4 Su-33's) If you do not PM me with this information then you will not be considered for the next mission. __________________ All Lonewolf Pilots: Please PM with the same information. Unless you have already done so, you will be required to pass a checkride in order to participate in the mission. __________________ The number of pilots that will participate in this mission will be limited to what is considered maximum for server stability. IF YOU REQUEST A SLOT IN REDFLAG YOU MUST BE ABLE TO FILL IT!!!!!! In the past we have had teams who decided to leave or pull out of the mission at the last moment. Please be considerate of your team mates and realize that you are hurting your entire team by not showing up. This also includes briefings etc, make sure you represent your squad and yourself well and attend scheduled briefings and the mission. S!

As I recall, from the initial release to the release of the last patch and every patch release in between, there has been a chorus of ED's customers giving constructive criticism about various flaws in the modelling of LO. Nobody is bemoaning the fact that ED didn't get it right the first time. The problem is that they STILL haven't got it right and there are only a few of us clinging to hope that there will be another patch. Your reference to the ET and "common sense" is arguable. But the main thing is that ED did something about it, unlike other aspects of the modelling. Who said anything remotely involving cars? The main point there was that you don't have to write code to see that something is modelled incorrectly in a sim. And no one that paid money for the product should be expected to keep quiet about its flaws. GG, I know you, probably more than anyone else, have given ED results from your research and testing. I hope ED never responded to you with, "We haven't seen you attempt to write a flight sim ... let alone attempt to 'get it right."

Bumping a necro-thread just because it was a very good re-read. :-)

Post a track. My testing says the 15 is faster than the 27. F-15 - 1371 knots - Mach 2.386 MiG-29S - 1382 knots - Mach 2.406 Su-27 - 1330 knots - Mach 2.316 All speeds achieved at ~36,200 feet, clean configuration, just before all fuel consumed.

1. If you know that you will not fly the entire mission, please do not participate. 2. Yes 3. Because a "dead" pilot serves no valid purpose in the channel. Yes, unless he is the only English-speaker. 4. -50 за небоевую потерю/дисконнект 5. This rule has been abolished. It may return if staff considers it necessary. Regarding 3 There is no problem with listening. There is a problem with speaking. If it can be arranged that a moderator can mute a "dead" pilot in teamspeak, perhaps this would be an alternative. Most moderators do not currently have admin privileges in the usual teamspeak servers. Regarding 4 It is unfortunate that anyone gets a disconnect. During the event, the staff cannot know the circumstances regarding each disconnect. To be fair to all, we must be "unfair" to those whose connection was unwillingly dropped. If we begin to readmit pilots after disconnects, there could be problems with pilots improving their situation by disconnecting. We do everything within our power to provide a stable server. There was only one disconnect in the last event.

These are the amended rules. As a courtesy, I am posting them here for your translation. Rules for Exercise Participants (Mission Dependent) When prompted, connect to the mission server, but do not hit "FLY" until your flight is called by a moderator. - There will be no respawn except for mishaps prior to “point of no return”. Combat losses are not recoverable at any time. - Once in the server, you may taxi but do not fly until permission has been granted by a moderator. - Fighters may only land at their starting homeplate. - Bombers may land, refuel and re-arm at their designated FARP, but may only change loadout at homeplate. - "Point of no return" occurs at 20 minutes after permission to fly. If you are not in server by this point, you may not fly. - Anyone landing at a non-approved airfield must exit the server and will incur a disconnect penalty. If the non-approved airfield is behind enemy lines, it will incur a combat loss penalty. - No ECM macros or print screening. - Vulching is allowed. - Stock loadouts only (unless otherwise authorized) - Maximum allowable ping = 500ms. If forced to exit because of high ping, no penalty will be incurred. - Missions are 3 hours long but plan your day for a 4-4:30 hour flight. - If you are shot down, exit the game server immediately. A 200 point penalty will be incurred for anyone still in the server 2 minutes after the log reports their “crash”. This penalty actually applies to any condition which mandates an exit from the server. (unforced crash, landing at a non-approved airbase, terminally stuck on the grass, etc.) An additional 500 point penalty will be incurred after 5 minutes and the offending party will be banned from the next two LOCERF events. - Any condition which mandates an exit from the server also mandates an exit from any TeamSpeak channel with active participants. If a flight/channel has only one English speaker, he is exempt from this rule. - Only bomber pilots may change their loadout. However they must declare their intention to do so while parked at home plate in a parking area. (NOT a taxiway) At this point a moderator must confirm your parked status and grant approval to exit the mission. - Any disconnect after point of no return and prior to a moderator declaring the mission complete will be counted as a loss. - While unenforceable, using F11 is against the spirit of LOCERF and forbidden. - Obey moderator directives at all times. Scoring System -50 points for a non-combat loss / disconnect -100 points for combat loss of aircraft other than A2A. "Combat" is defined as caused by enemy action -200 points for each friendly A2A kill -50 points for each friendly A2G kill (will count toward enemy objective, if applicable) +130 points for shooting down an enemy Fighter Aircraft +150 points for shooting down an enemy Strike Aircraft The mission specific objectives will be scored on a percentage basis. For example, if an objective is worth 2000 pts and a team completes 43% of that objective, they will be awarded 860 pts.

I agree that all participants should have the rules available to them. I will also agree that any future changes to the rules must be announced in a easily found place. I do not agree that it is the responsibility of the LOCERF staff to make them available anywhere other than the LOCERF forums. I'm sure you do not want a Babelfish Russian translation of the rules and that is all I could provide you. I know that some of you speak English quite well and could provide an accurate translation. As for my presence in this forum, don't expect it to continue indefinitely. Recent circumstances made me feel it necessary. I was a pilot in CA so I saw the same things you saw there. I was a pilot in LOCERF 08-1 and saw the same things you saw. I then became administrator of LOCERF and wanted to make sure you knew that the problems that plagued 08-1 were not normal. Also, from what I see in this forum, thoughts that I had hoped to convey to the whole Russian speaking contingent were not being relayed to you by your representative. Lastly, and perhaps most importantly, I've seen that this community has insulated itself from the other groups involved in LOCERF. Obviously, language has some part in this but perhaps some of this is based upon lack of trust. From the previous community events that I mentioned, I can see a basis for distrust. I've seen some posts here that show that some of you felt cheated in 08-2. I felt compelled to show you that the event was scored fairly and the scoring system was not a secret. But there certainly was a breakdown in communication. We can overcome this.

A few folks have expressed their desire to see the scores positive rather than negative. That can be easily accomplished by replacing a penalty for losses with an award for the opposing team. The thing I would like to determine is how A2G performance is weighted against A2A performance. Personally, I feel A2G should carry much more weight because of its importance in winning a war, however, the importance of survival cannot be diminished. I'm thinking that a value can be assigned to each aircraft on a team and that value used to determine the total value of the A2G objectives. Of course, some "wiggle room" will be in place for uneven teams.

They are a great bunch of blokes. The best bomber pilots in LockOn... :music_whistling: :D

The scoring system to be used was provided to DarkWanderer 5 days prior to the event. For those with access to the 159th forums, this can be confirmed here: http://www.the159th.com/forum/viewtopic.php?t=3442

I can not grant access but I will notify the administrator. Which name did you use? 300? =300=Ruff?

Yes. Unless you fly in an organized event.

If it goes as planned, the next mission start time should be 0500 or 0600 GMT. Next 1400GMT and next 2100GMT again. It occurred to me that many of you have not seen my apology for the lack of one Su-25T for RedFor. It was my mistake. I confused the number of MiGs with the number of 25Ts. I should have referred to my notes but I didn't. I should have asked another moderator to check the mission but I didn't. There is no one to blame but myself. I apologize to any of you who were caused problems by my mistake.

Copied from the discussion at the 159th forums. Again I ask that the pertinent points be translated. In 08-2, six pilots disconnected after landing at a friendly base and received no point loss. This will change. The loophole for avoiding a penalty for a disconnect will be eliminated. Although discussions in this thread have softened my opinion about deductions for errant missiles/weapons, my opinion is still that this should be eliminated because: A - It is intended to curb spamming of missiles. I don't believe that problem exists. We are forcing medicine on the healthy. B - Running out of missiles is its own penalty. We force fairly long flight times and running home to rearm is not a quick task. C - If spamming begins to be a problem, this rule can easily be reinstated. D - We are not here to be accountants. We fly and fight. The price of achieving an objective should be measured in fallen comrades, not money spent. E - It is a pain in the ass to score. Regarding scoring and the discussion that softened my opinion on this matter, if an automated system can be implemented (and I'm confident that it can) maybe bonuses can be awarded for getting a kill with a less than stellar weapon. But deciding a value for weapon/target could be a problem too. 08-2 kill totals by weapon R-77 = 10 AIM-120 = 10 R-27ET = 8 R-27ER = 3 R-27EM = 1 AIM-9 = 1 Cannon = 2 R-73 = 0 R-60 = 0 Victims of AIM-9 and cannons were all strike aircraft. This does not take into account how many of each weapon were released. Opinions?

:) Thank you.

Could someone translate this please? Babelfish fails miserably.

We have pilots from all over the world. The flight times are rotated so that a particular region is not constantly inconvenienced. It is unforunate that flight times are sometimes very late or very early for pilots but it is unavoidable and it is a result of attempting to be fair to everyone involved.

:thumbup: Я признательн

Someone please translate. Rules for Exercise Participants (Mission Dependent) On game day, connect to the mission server, but do not hit “fly” until your flight is called by a moderator - There will be no respawn - Fighters may only land at their starting homeplate. - Bombers may land and re-arm at their designated FARP, but may only change loadouts at homeplate. - “Point of no return” at 20 minutes after takeoff. If you are not in server by this point you do not fly. - Fighters only allowed to use home bases for re-arming, refueling and repairing. - Landing at other airfields is prohibited. If you land at an airfield behind enemy line, it will be counted as a loss. - No ECM macros or Print screening. - Vulching is allowed. - Stock Load outs only (unless otherwise authorized) - Max allowable ping = 500ms - Unless an emergency, use proper runway approach and landing headings. - Missions are 3 hours long but plan your day for a 4-4:30 hour flight. - Insure that Enemy/Friendly skins are dissimilar - If you are shot down, leave the game server immediately - Only Bomber pilots can change their loadout. However they must declare their intention to do so whilst at home plate. At which point a moderator will confirm your parked status. - Even if you are confident of your teams victory and the ability of your machine and connection to handle the stress of LOCERF missions, leaving early will be counted as a loss. - While unenforceable, using F11 is against the spirit of LOCERF If you land at an airfield behind enemy line, it will be counted as a loss. (In other words, getting the $hit kicked out of you in POW camp and donating your aircraft to the enemy is not a desired end result). -If you land at a airfield behind friendly lines (other than those designated for refueling and rearming for your airframe) it is not considered a loss but you must leave the mission and can't respawn. -50 points for a player that has disconnected prior to mission completion. (This includes those that have disconnected due to being shot down.) -50 points for Combat loss of aircraft. "Combat" is defined by being shot by either ground or air. -10 points for each weapon launch that does not hit its intended target. (ARM's/Mavericks that get shot down by AAA or SAM will not count against your point total) -100 points for each friendly kill +30 points for shooting down an enemy Fighter Aircraft +40 points for shooting an enemy Strike Aircraft The mission specific objectives will be scored on a percentage basis. For example, if Primary is worth 1000 pts and a team completes 13% of that objective, they will be awarded 130 pts. DarkWanderer was aware of these rules and this scoring system. Please be aware that the scoring system is being reviewed and changes will be very likely. Please contribute any ideas you may have regarding changes in scoring. Also, it has been said that I "promised" that Russians will be given their first choices for aircraft in the next event. I did no such thing. The following are excerpts from my messages to your representative. and then later... With the Russian pilots not flying as a single large group in future events, the task of assigning aircraft becomes much easier. I don't expect any difficulties in giving each of you your first choice. But I want to make it clear to everyone that I did not promise to do so.

Laugh while it still seems funny. :mad: