Patch Version | | None | | | | | Official Mods (in order) | | None | | | | | Game Play Types | | Only Team Mission CO-OP play is scorable at this time, and MUST be done on an approved GNSF map from our map pack. | | | | | ROE Specifics | TRAINING
Training game type allows the player to go into any type of map for the purpose of training and practicing different aspects of the game play. When reporting training games the only value that needs to be entered on the scoring page (besides game type and players name) is Flight time. For Training game play all other values are ignored, and the player gets points solely based on the time played.
- ONLY GNSF Approved Mods or Patches can be used.
- Any map or mission can be used for training.
- 2 GNSF players per game minimum.
- Players still need to include the debrief.log files and must report games as one report for each flight.
- A player may respawn into multiple helicopters during training.
CO-OP Mission
2 GNSF players per game minimum regardless of game type.
ONLY missions created by GNSF and located on the download page may be used for scoring.
No respawning is allowed unless you are training (jumpinmg in another Helicopter from same or other flight group).
Once the group has started a mission by pushing FLY, no other player can join into that mission. Joining after a game has started by selecting an Available Helicopter (same or different flight) shall not be done UNLESS the flight is still on the ground.
If a player dies during a game he CAN NOT climb into another Helicopter. He is out for the remainder of the Mission. He can stay in the waiting room or exit UNLESS he is the host (Host MUST remain connected).
Players can use ONLY Ka-50 Helicopters (can NOT use any mod to allow other plane types to be flown) for loggable missions. New flyable platforms WILL be allowed when released by the Manufacturer of the game.
Every player enters the mission outcome once the mission is over. If you die you must get the outcome from another player in the game. You will still use YOUR debrief.log file when reporting.
When you enter WR, you will select and available Helicopter and puch FLY ONCE. Once in the briefing screen, wait for the host to call FLY BEFORE pushing the FLY button a second time. The host will call FLY after all players report in and ready.
When all are ready to start, the HOST will hit the FLY button FIRST. All other players then follow when the host calls FLY.
Once in the cockpit, each player will call PIT. Once all are in the Host will ask all to report ready. Once all players report ready, the Host will un-pause the game.
Flight time is the time elapsed from TAKEOFF until your flight ends (crash, eject, dead or land [without taking off again]). Flight time is entered in MINUTES and is calculated for you by the report system from the debrief file.
Your game can only end when you have ejected, died, crashed or landed. A pilot can land for refuelling and rearming as many times as needed at any friendly airport or FARP without terminating the game, but CAN NOT end his game while still in flight.
Flight leader (Pilot #1) will perform ALL queries to AWACs, WHO takes what targets, and all other aspects of the mission planing and execution. All pilots will set the flight ID number to match the pilot number of his plane, and set the COM selector to WINGMAN.
If the host is killed or ejects, he MUST REMAIN CONNECTED and wait for the mission to end. Disconnection of the Host will terminate the game, and shall NOT be done.
Damage and kill points are calculated and entered into the appropriate field in the report form for you by the system.
A Player may leave the game once he dies or lands, UNLESS he is the HOST. If a player must leave during the course of a game, he must FINISH HIS FLIGHT. A Flight is not considered complet unless the player lands, dies or ejects. Leaving the game in flight will result in a zero score being awarded for the game.
REPORTING
You MUST copy and paste the ENTIRE debrief; debrief.log (found in the Temp folder) WITHOUT making any changes or modifications to it. You CAN NOT log a mission without the debrief file being entered into the coverter. Since the system uses the debrief file to calculate what happened, the system WILL NOT accept a mission report without it.
NOTE : The Debrief.log file IS NOT valid until all players have left the game AND the server has been shut down. Attempting to copy your debfief.log file BEFORE the whole game is done AND the server closed will result in an INCOMPLETE log file. To avoid this DO NOT report the mission until AFTER the whole game is done and the server has been shut down.
You must save EVERY debrief.lof file for a minimum of 60 days, and produce it if requested to do so. Failure to produce a requested file will result in JAG action AND loss of points via report removal.
Players are to enter ONE report per flight (one report equals one game equals one flight).
A Flight Time record is kept to acquire flight time badges, and to aid in showing a players play level.
When scoring Mission outcome, the person uses the outcome from the FLIGHT they were in once ALL players in that flight are finished the game.
MISSION OUTCOME
The mission outcome will be the displayed as an in game message DURING the flight, and is what will be used as the outcome for ALL players. This allows players to cash in on any missions they helped succeed at the cost of thier life or plane. The Mission outcome will be the outcome shown by the LAST PLAYER to leave the game (Land and exit or eject / Die). If no players get a MISSION SUCCESS message, then the game is logged as a failure by all.
FRIENDLY KILLS
The following are considered Non Combatant hits in addition to human player and AI planes (friendlies, same side);
- Any House, Office, or NON military structure NOT at the target site.
- Any item NOT classified as enemy (friendly airport etc).
This is determined by the debrief, and the values are calculated and entered for you.
FOR Saitek X52 PRO Users:
There is a file that outputs commands to the flight controler (basically just SAITEK RULLEZ!!). This direct output causes the game to crash when you die, or any time after game start. To fix this problem, this dll should be deleted (it serves no functional use other than to crash the game). The file is called;
lua-direct_output.dll, and is located;
C:-Program Files-Eagle Dynamics-Ka-50-bin-stable- (slashes are shown as -)
| |
