Multiviper.com
Site Navigation
 
 Home

 Community
 Forums
 Downloads
 coppermine
 News
 Topics
 Stories Archive
 Submit News
 Links
 Web Links
 Web Links
 General
 Content
 Top 10
 Infos
 Your Account
 Profile
 Private Messages
 Search
 Your Account

 

Multiviper.com Server
Donations
 
HELP KEEP OUR SERVER/WEBSITE ONLINE!
Make donations with PayPal!
Donat-o-Meter Stats

September´s Goal: $120.00
Due Date: Sep 30
Amount in: $0.00
Balance: $0.00
Left to go: $120.00

Donations

 

Event Calendar
 
September 2010
  1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30  

Birthdays
Concerts
Exhibitions
Fairs
Meeting
Other
Topics

 

User Application/Login

Hello! Welcome as a new member of this website!
To apply for a membership you will have to agree with our Terms of Service.

Multiviper.com - Terms of Service

MULTIVIPER CAMPAIGN SERVER / TEAMSPEAK SERVER STANDARD OPERATION PROCEDURES [SOP]



Table of Contents



SECTION I WELCOME TO MULTIVIPERS

SECTION II REGISTRATION ON FORUMS

SECTION III CONNECTION AND REGISTRATION ON TEAMSPEAK

SECTION IV CONNECTION TO CAMPAIGN SERVER

SECTION V CAMPAIGN SERVER ETIQUETTE/RULES

SECTION VI TEAMSPEAK ETIQUETTE/RULES/KEYBINDS

SECTION VII DO'S AND DONT'S

SECTION VIII SERVER ADMIN RESPONSIBILITIES ON MVS

SECTION IX PILOT RESPONSIBILITIES ON MVS

SECTION X SEVER DETAILS

SECTION XI EXTRAS



SECTION I WELCOME TO MULTIVIPERS



Welcome new pilot to Multiviper's. A Viper, is an F-16 pilot, and Multiviper's, is an online community, a collection of pilots from The United States, Canada, Brazil, UK, France, Norway, Denmark, The Netherlands, Mexico, Turkey, Greece, Australia, Sweden, South Korea, South Africa, Spain, Singapore, Portugal, New Zealand, Japan, Germany, and other countries from all over the world. The Multiviper community of pilots is here to Fly Falcon 4.0 Allied Force in a Multiplayer setting with coordination between pilots, both inside the individual flight and between flights of aircraft. This coordination exists while an entire war, is fought below us in the skies, in a continuous simulation of aerial combat operations in a simulated war. We are also here to learn things about the F-16, and other military aircraft of aircraft in general, learn about the simulation, as well as share our knowledge with the new crew of pilots that make an appearance here daily. We are also here to make friends and enjoy each others ideas about how to create and execute missions. This is a place where everyone can have input about what's happening in the campaign that ties us all together. In order to best do these things, we have taken the time to develop what we call the SOP for pilots on the server.



These are a set of Standard Operating Procedures we follow, and that we would like you to follow, as well, while flying here. Falcon 4.0 Allied Force is a sophisticated simulation of modern aerial warfare. There is a lot of information available in both the manual and the forums that will help you get up to speed. While flying the simulation, in multiplayer, you are basically a fighter pilot. You need to be able to react to both tactical and strategic considerations as well as handle your aircraft in the performance of your mission. The level of depth and complexity of the simulation can make for both frustration and hard feelings for and from the other pilots who are here to fly just like you when pilots don't follow the SOP. In addition, because of the level of complexity of the sim it is not without bugs just like other software programs, and we have to try to do all the things we can to minimize the software end of problems. Nobody likes planning for 10-30 min just so the program crashes to desktop.



We ask that you be courteous as well as friendly to other members and work to coordinate as a team. As you progress from novice fighter pilot as well as flight members you can learn to plan missions and become an aerial mission task/planner. You can become a flight leader, or an element lead. As you log more hours and accrue additional flight experiences, learn what works well and what doesn't work, and if you'd like to commit time, effort, and energy to helping keep Multivipers the best place to fly Falcon 4.0 Allied Force on the web, you can be promoted to Sever Admin and help share the responsibility of leading flights, tasking/creating missions, and coordinating or directing the campaign.



Also, due to the nature of both the MULTIVIPER site and the ALLIED FORCE simulation, the general minimum age to fly on Multivipers is 17 years of age. However, pilots down to 15 years of age will be considered for membership on an individual and case by case basis. Falcon is a serious and complex F-16 combat flight simulator. It is highly recommended for pilots new to multiplayer Falcon that, at a minimum, they fly all the training scenario missions before signing up and flying online; especially if they do not have extensive experience flying Falcon as a standalone program.



SECTION II REGISTRATION ON FORUMS



Registration on the Forums is Required



To register:



Enter into your web browser http://www.multiviper.com

Click Register, read the SOP then choose Agree

Enter Username, Email Address, Password, Confirm Password, enter the Confirmation Code

Click Submit

Once you have completed your initial registration, update your profile with all information possible. This is a requirement of membership at MultiVipers. At a MINIMUM you MUST have the Location and Age sections filled out.



SECTION III CONNECTION AND REGISTRATION ON TEAMSPEAK



The communications software used on MultiVipers is TEAMSPEAK. If you don't already have the program, head over to the Teamspeak homepage and grab it.



Part 1: Connecting to the TS server -



Start TS

Click Connection,

Click Connect

Click Local Address book

Right-Click on any spot inside the white area under Local Address book, add server, clone server, delete server will come up, choose

Add Server, then

Type Multivipers in the Server Name area, then

Click on the Server Address bar and enter ts11.DARKSTARLLC.COM:8925, then

Type your nickname or callsign as you wish it to appear on teamspeak, make sure this is the same one you will be using in the sim. For example, you might choose MVS-CODER, then

Click the Anonymous button DO NOT ENTER user name or a password as you WILL receive an ERROR!!, and finally

Click Connect at bottom



If you followed the above steps you should now be sitting in the Unregistered Pilots Lounge on MVS TS. Continue reading the SOP and a SA on TS should be by soon.



Registration on Teamspeak is also Required. To register you must first be allowed by a Server Admin to register. In the rare event that there are no Server Admins on Teamspeak at the time you show up just hang around, one will be by, skip the teamspeak registration steps and go register on the forums. Before you even bother with this, make sure you can fly here by testing your upload and download speeds. To do this go to Speakeasy.net then click on a city name on the right side, then wait for it to perform the upload and download speed test, and give you your results. As long as your speeds for both upload and download exceed 128 up and 256 down you can fly here no problem. If they don't you'll have to explore any other options you have in regards to an ISP that will allow you to connect at the speeds supported here. Confirm these speeds with the admin that allows you to register.



Once allowed to register by an admin

Click Self,

Click Register with Server,

Enter in a Login name and User Password, write them down on a scratch piece of paper

Click Register when done, then

Click Connection,

Click Connect

Click the circle next to Registered,

Type your Login Name and User Password as you registered them, then

Click Connect when you are done and if you did it all correctly you should end up coming back into the Multivipers Teamspeak Server as a Registered member.



SECTION IV CONNECTION TO CAMPAIGN SERVER



--->READ AND UNDERSTAND THE FOLLOWING BEFORE you attempt to connect!!



--Step 1--

If you have a Router...

You must forward ports 2934 and 2935 for both UDP and TCP.

You should also assign a static IP address. For details on how to perform either of these actions visit Portforward.com

If you have a firewall...

You must either disable your firewall completely, or enable Falcon to function through your firewall. For details on how to do that see your Firewall specific manual.

Once your connection is properly setup you're ready to connect to the Multiviper Campaign Server.



--Step2--

Open Falcon

Click Multiplayer, You will then see Multiplayer at the top.

Click Internet, Here you will see the list of Internet Servers at the top. This is where your server entries will be listed once you input them. To Input a server type the relevant IP (either the Primary or the Backup depending on which one is active) into the Custom Server Address bar. Make sure you include the dots (.) Once this is finished click add on the left, then the listing will appear in the list. Select the Listing, click keep on the bottom to enable it's appearance the next time you start Falcon.



--Step 3--

BEFORE you attempt to make connection make ABSOLUTELY sure your connection speeds while connected to MVS are always at a MINIMUM of 128 upload 256 download. Also always be on MVS Teamspeak Server so you can receive instructions and coordinate with other pilots. With the latest patches from Lead Pursuit we ask that you connect one setting below your tested speeds.



NOTAM: A new issue we've seen that we hear Lead Pursuit is working on is an issue only experienced with routers. Occasionally the server part of MVS seems to lock client IP's. Whereas, these same people with routers have made no changes, and are able to connect to other people. Yes the problem is real. The solution is to change your internal IP address, example original ip 192.168.1.100 changed to 192.168.1.105 seems to correct the problem. If LP doesn't know why this occurs you can bet I don't either I just know the fix we've uncovered, please don't ask me about this anymore. If you do however get your internal ip changed and still have issues please let an Admin on TS know and we'll try to diagnose you.



SECTION V CAMPAIGN SERVER ETIQUETTE/RULES



-Always Connect at one setting below your actual connection speed, at a MINIMUM 128/256. This is to insure a smooth flight for not just yourself but your fellow pilots. Always have your firewall set properly as well, either off or on but enabled for Falcon.



-You need to test your connection speeds occasionally, to do this go to Speakeasy.net then click on a city name on the right side, then wait for it to perform the upload and download speed test, and give you your results. As long as your speeds for both upload and download exceed 128 up and 256 down you can fly here no problem.



-Don't adjust any of the Priorities Tabs inside the sim, they don't work except for the PAK's and we would rather you not adjust these because it can upset the balance of the campaign.



-Don't Create/Modify Packages. Fly them as fragged in the ATO. If you need a custom package please ask a Server Admin.



-Do not stay connected to the server if you are going to be idle more then 5 minutes.



-->The use of a control stick for primary flight control is required. Other flight enhancements such as rudder pedals and Track IR are optional, but recommended!



SECTION VI TEAMSPEAK ETIQUETTE/RULES/KEYBINDS



-->You must be on Teamspeak and in communication with the other pilots in order to be flying, or logged into the campaign server. Do not stay connected to the server if you're going to idle more then 5 minutes.



-All pilots on TS need to take care of not interrupting flight comms in progress. When breaking in, wait for a clear break in the flow of comms in the local flight channel, identify yourself so we can have you clear channel if we need to and state your need right away. This is in the flight channels, in briefing or the pilots lounge you can interrupt if needed, sometimes pilots will forget to clear out of here, so either move the pilots, if you’re a sever admin, or just go to another channel. Lets try to keep the unregistered pilots lounge for getting pilots registered and cleared to connect on the server.



-If you go Away From Keyboard (AFK) for more then 15 seconds make others in the local Teamspeak channel aware of your need to leave your computer for a moment so they don't keep trying to raise you on comms over and over.



-Teamspeak Keybinds are required for campaign server flights. You must have the ability to increase and decrease your reception volume of teamspeak communications so they can be adjusted in flight. You must also have a broadcast key which you will use to communicate to other flight channels.



SECTION VII DO'S AND DONT'S



* Do Check in with flight leads, on teamspeak, and secure permission before joining a flight that is already in progress or in planning.

* Do Connect at a minimum 128 upload and 256 download speed

* Do Change your pilot name and Callsign, in the logbook to the same thing you use in Teamspeak

* Do Maintain formation to the best of your ability unless ordered to do otherwise.

* Do Learn Brevity. The purpose and execution of brief coded and uncoded transmissions used to maintain clear communication as well as good situational awareness.

* Do perform your role in a flight, lead or support. 1/3 are leads, 2/4 are supports.

* Do have FUN, and enjoy the the life long friends you will make.

* Do grab a beer before going up on a flight.



DON'T

* Don't Ever Connect with a firewall improperly configured.

* Don't Ever Connect with speed settings less than 128up/256down.

* Don't connect to the server if the speed test shows that you are not capable of sustaining the speeds indicated above 128U/256D.

* Don't connect to the Falcon Server without being in Teamspeak.

* Don't Ever Give the server password to another person. If you need it ask a Server Admin. Only Admins are authorized to give it out.

* Don't Adjust Mission Priorities Tabs or Mission Pak's. Contact a Server Admin if they need adjustment.

* Don't change munitions in the munitions screen, without a directive from your flight lead to do so.

* Don't Lose sight of your wingman (use your MFD's).

* Don't make a habit of falling out of formation.

* Don't Shoot down other friendly Aircraft intentionally, (fastest way to earn a life-long ban)

* Don't Create/Modify Packages. Fly them as fragged in the ATO. If you need a custom package please ask a Server Admin.

* Don't Move The Ground Troops. That is the job of the Server Admins.

* Don't attempt to reconnect to the server more then three times without contacting an Server Admin for assistance.

* Don't repeatedly join and then leave flights, this causes server instability, and can eventually cause a crash.

* Don't use the exterior views excessively, it lags the server.

* Don't keep problems to yourself, address problems with the server, mission, pilots with respect and to a Server Admin and we will try to fix them.

* Don't cheat or fly unfair, using unfair advantages such as being in blue side flight channel, and flying red. This can lead to your lifetime ban. So fly fair, or don't fly here.

* Don't fly suicide missions. Think about what you are flying, where and when. We can't count on re-supply. Some squadrons don't get replacement jets.

* Don't roll back the time on a package unless you roll the time back on the entire package. This eliminates single FAC/escort etc. flights going on suicide missions by themselves.

* Don't take a package up and hop out of the jet when you are out of ammo. You are expected to fly it home and land it.

* Don't Fly sober.

* Don't enter the RED AIR side of the campaign. Only authorized pilots may act as aggressors. (See: Aggressor Group Notice on forums)



SECTION VIII SERVER ADMIN RESPONSIBILITIES ON MVS




Server Admins are here to keep things flowing smoothly on the campaign server.



As a Server Admin your primary focus should be on flying and ensuring smooth flights, and tasking missions if you feel so inclined. As an SA it would be helpful if you'd answer new pilots questions as long as they've tried to look it up in the manual or if you feel like giving a bit of training. It would also be helpful if SA's would lead flights if there is a shortage of experienced/skilled pilots able to do so.



Server Admins also should no longer be responsible for making sure of the registration or connection of new pilots is secure. This is now the responsibility of new pilots as designated in the SOP. You are free to direct new pilots to test their connection speed or verify that firewalls are down, if you suspect a problem and please do attempt to diagnose a connection setting, if necessary. Improperly set connections are still a concern but less so then when we first started. Server Admins are required to assist in registration or setup of new pilots.



Server Admins should recruit the guys that are on Teamspeak that you'd like to fly with and take charge of the seating process to get pilots into seats as quickly as possible, once pilots are seated, expedite the selection of munitions as well as conduct a preflight brief. Keep the briefings short and encourage questions and discussion before making ready to click fly. It is especially important to have the plan worked out before entering the jet. If multiple flights are going to be part of a package with supporting roles they should be included in the planning process.



Server Admins must, before clicking fly, remind all pilots to click on the green line in the frag order and click fly, then select either, ramp, taxi, or takeoff.



Server Admins leading flights should take up skilled/intermediate pilots on the more dangerous flights have them take the support role, keeping the rookies in lesser risky missions until their level of skill is such that they can be reasonably expected to survive and thrive in a more dangerous mission.



Server Admins are expected to connect at a minimum 128 up 256 down and with their router/firewall properly configured.



Server Admins are to be held to all rules set forth in the SOP.



SECTION IX PILOT RESPONSIBILITIES ON MVS



Registered Pilots are here to fly and learn about the sim. You are also here to communicate effectively both in the planning process as well as the execution of the mission. Generally registered pilots are expected to fill the support roles in a four ship flight, that's the number two and four, in a two ship flight, the number two, until they have the skills to lead other pilots in combat. There are times where you'll be asked or want to fly element lead or flight lead and this is fine as long as you feel comfortable in the role. Of if no Server Admins are around where you'll want to fly lead. You are clear to do so as long as you believe you can bring the aircraft back.



Registered Pilots must be able to communicate both on local and broadcast in teamspeak. You are expected to be able to do this at any time.



Registered Pilots must not adjust the priorities tabs in the simulation 2-D map.



Registered Pilots must click in on the green line in the frag order once after joining a seat in a flight and again before clicking fly, and selecting either ramp, taxi or takeoff.



Registered Pilots must NEVER GIVE OUT THE SERVER PASSWORD.(DOING SO IS A BANABLE OFFENCE) If you need it ask an SA. Anyone caught giving the password via the forums will be subject to the same discipline THIS INCLUDES ADMINS.



Registered Pilots must comply with instructions given by the server admin with regards to the server.



Registered Pilots In a mission are expected to comply with the directives of your flight lead or admins to the best of your and your aircrafts ability. Any situation impeding or preventing you from complying with a directive must be communicated to your flight lead as soon as a directive is given. Also make your lead aware if you lose sight of him visually, or if you're low on fuel, or if you’re out of weapons, have a damaged aircraft or any other situation that requires communication of important facts. If you're unsure that another flight member should know something then its better to say or ask and be told, to be quiet, then to keep it a secret. If and when using broadcast communication, keep it short. Generally only the flight lead of a flight will be communicating via broadcast. Also consider using the text chat if conditions permit. It's actually how all communication was done at one time in the sim between pilots and it still works well in some situations.



Registered Pilots are expected to remain clear of the munitions screen for the entirety of the planning process. If you need to see what munitions you are loaded with, click the green line in the frag order to update your munitions, and then click briefing on the bottom, your load-out will appear in green. Your flight lead may clear you to adjust your own munitions. To do this, again click on the green line in the frag order, then click munitions, make sure only your name appears in gray, click on the other flight member names, to change them from gray to black, once yours and only yours is gray, choose your load out, when done, choose Ok, then communicate to the rest of the flight that you have finished.



As Registered Pilots you are welcome to participate in all aspects of the sim at your own pace.

Registered Pilots are expected to connect at 128 up 256 down and with their router/firewall properly configured.



Registered Pilots should use the same callsign on teamspeak as they use in the sim and vice versa. Stick to one callsign all around, also set your pilot name to the same one in the logbook.



SECTION X SEVER DETAILS



-- Server name: Multiviper's Server

-- Server IP address: Check with Server Admins or on TS

-- Campaign detail -- Check with Server Admins or on TS



Description of server

Windows 2000 Server

Dual 2.4Xeon

2gigs Server Ram

10k rpm SCSI Drives

Internet Bandwidth 6144/6144

Dedicated Host Mode only



SECTION XI EXTRAS



Due to the wide range of people from around the world, and IAW International Flight requirements, the STANDARD language required for all pilots to utilise on MultiVipers is ENGLISH. It is requested that all members who intend to fly on MultiVipers have a good level of understanding of the English language so that everyone is able to have an enjoyable time flying on the server. We have an expectancy of Level 4 Understanding as defined in the ICAO Language Standards (The same level at which airline pilots must communicate) See: Here for more information.



If you are having problems or don't like the way something is set please send me email at jayoung@gmail.com or inform me either here or on teamspeak. I will listen and try to accommodate you the best I can..



Need a callsign look here: Callsigns



If you have bugs or issues that need to be addressed please post here http://www.multiviper.com



Currently MV's admin staff doesn't have a stance on modifications to the game in any way and are strictly of our own decision.



If the server goes down and does not return in about 10 minutes please send email to falconprocess@hotmail.com with the subject line of falcon. You must only put falcon in lower case in the subject line nothing else this will send a SMS message to my mobile phone and alert me of the problem. Please coordinate with other people on Teamspeak as to who will send this message so I don't get 10 of them at once.



Thanks

Multiviper

jayoung@gmail.com

And the Entire Multiviper Staff



**PLEASE NOTE**

1. ALL PILOTS ARE TO ENSURE THAT THEIR "SIMULATION" SETTINGS IN THE UI MATCH THE SERVER SETTINGS. THE REQUIRED MINIMUM SERVER SETTINGS ARE:



A. SKILL: ACE (97)

B. FLIGHT MODEL: ACCURATE

C. AVIONICS: REALISTIC

D. WEAPON EFFECTS: ACCURATE

E. AUTOPILOT: 3 AXIS

F. AIR REFUELING: EASY

G. PADLOCKING: ENHANCED



2. ONLY Server Admins are authorized (in accordance with Current Campaign Rules) to make changes to the server regarding Priorities settings, ATO taskings and Ground Force movements.



3. ONLY Flight Leads are to make changes to waypoints and/or weapon load outs for their respective flights.



4. CURRENT CAMPAIGN RULES: Please refer to the Campaign information page on the Teamspeak server for the rules governing the management of the current Campaign.



Changelog

------------------------------

Current version: (Rev. 13d) 09 Aug 2009 - MVS-OzCougar

(Rev. 13c) 10 Apr 2009 - MVS-JPClarke

(Rev. 13b) 31 Aug 2008 - MVS-JPClarke

(Rev. 13a) 13 Aug 2008 - MVS-JPClarke

(Rev. 13) 16 Jun 2008 - MVS-JPClarke

(Rev. 12) Jan 2008 - MVS-OzCougar

I have read and agree to abide by these Terms.
Yes
No

Your Account ©
Powered by Nuke Evolution theme designed by effectica.com

Spambot Killer
multiviper.com

PHP-Nuke Copyright © 2006 by Francisco Burzi.
All logos, trademarks and posts in this site are property of their respective owners, all the rest © 2006 by the site owner.
Powered by Nuke-Evolution.

[ Page Generation: 0.15 Seconds | Memory Usage: 3.9 MB | DB Queries: 33 ]

Do Not Click