habe was im Inet gefunden was das Setup und connecten des BMS DF betrifft:

Setup BMS
Setup BMS for the 1st VFW
by
Demo
Published on 09-11-2011 04:14 PM

F4-BMS Multiplayer Standard Operating Procedures
Before You Can Fly:

Before you can fly online with us in BMS, you MUST do the following (we will check):
Ports
Forward port UDP 2934-2937 and ports 9987-9989
Anti-Virus / Windows Firewall
Disable your anti-virus and turn off Windows Firewall
BMS Config File
In your Falcon BMS folder -> User folder -> Config Folder -> Open the file Falcon BMS.cfg with Notepad
Add these lines to the top of the config file (copy and paste) then save the file:
set g_bShareMpClouds 0
set g_bMessageStatistics 0
set g_bEnableRakNetPacketLogger 0

The “set g_bShareMpClouds” is required for all pilots because of that feature causing connection issues. The other two are optional but recommended because they result in saving very large text files and take up hard drive space. Do not edit anything else in your config file. After adding the lines above, save and close the file.

Notes:
You can use this tool to check if ports are ok: PORT CHECKER UTILITY

To use that application to test your ports:
Be sure BMS is not running
You need to have at least one other user to test your ports with you
Both of you launch F4PortTest.exe
Exchange your IP and enter it in the label "To IP" (for example, I would enter another pilot's IP here if he was checking his ports with me)
Enter your callsign in the *Message* section
Push to "Send"
If your ports are ok the other user will get a message with your callsign in it. Both users should do it. The host of missions will require you to send him a message to check ports before we fly.
Teamspeak/IVC/Communications
Make sure you are not using voice activation for Teamspeak, and make sure your Teampseak push –to-talk is not the same as your IVC Comm1 or Comm2
Make sure you have a key binding to mute your Teamspeak mic to ensure you don’t transmit on both TS and IVC.
Multiplayer Connection SOPS

1. Prior to beginning the connection process, the Host will direct the rest of the pilots to the TS channel he/she has reserved in the ATO.

2. Prepare to Fly - Before you fly online in any simulator, make sure you sure all of your hardware is ready to go and you have done a quick test flight in the game. For example, you make sure your flight stick profile is loaded (the push-to-talk is setup for IVC or Teamspeak depending on the flight), your Track IR is loaded, etc... Then go into BMS, click on Setup => Controllers and make sure they are set up and function properly. Then go launch one of the training Tactical Engagements (i.e. Basic Flight) and make sure everything is working. Once you confirm everything is operational, you can back out and you are ready to fly.

3. Be on Time - If you sign up for a flight, be on time and be ready to fly (you've already done the required step above before the scheduled flight time). Please remember to respect other member's time. They may only have a few hours to get their flight in, and if someone holds up the flight, they may have to drop out. This applies to the Host of the mission as well.

4. Connection Information - The Host will provide the mission IP, the IVC IP (if you are using IVC), the theater, and the connection bandwidth. At the 1st VFW we use a minimum of 200 and a maximum of 512 for client bandwidth with 256 being ideal. We will use 256 for all our standard flights. In our tests, exceeding 512 or using a bandwidth below 200 caused connection issues. The Host will set his connection bandwidth to 80% of his upload speed (you can test your connection at speedtest.net). The sum of the client's bandwidth cannot exceed the Host's bandwidth setting. For example, if the Host sets his bandwidth to 1,000, he can only host 5 clients maximum at 200 bandwidth (5x200 = 1,000). The Host enters 0.0.0.0 for the "Connect to IP" address section and 127.0.0.1 in the "Dedicated IVC Server" if he is also hosting the IVC. If he's not hosting IVC, he would enter the IVC host's IP under "Dedicated IVC Server". Clients enter the mission IP in the "Connect to IP" section in BMS and the IVC IP under "Dedicated IVC Server". It is important the clients enter the bandwidth in the "Bandwidth" section and press enter to make sure it was entered. If you aren't using IVC, uncheck the IVC green boxes and only enter the Host's mission IP and bandwidt

5. Connection Procedure: Host - If IVC is going to be used, the Host launches the BMS launcher, then clicks on IVC Server. This will open a black window. The Host then launches BMS by clicking on "Launch". Once in the game User Interface (UI), the Host enters 0.0.0.0 in "Connect to IP Address", enters his bandwidth, and then enters 127.0.0.1 in the "Dedicated IVC Server" section. The host reviews the information is correct and then clicks Connect. BMS will minimize to the task bar while it launches the IVC client, then he clicks back on BMS in the task bar to get back into the User Interface. The Host then says "Comms are Up" and that lets the clients know it's time to connect.

6. Connection Procedure: Client - If IVC is being used, the clients launch BMS by clicking on "Launch" and enter the mission IP address in the “Connect to IP Address” section and enter the same IP (if the mission host is all the IVC host) into the “Dedicated IVC Server” field. Clients do not need to connect to IVC before launching BMS. When you click connect, BMS will minimize while it launches the IVC client and you simply click back on BMS in the task bar to re-enter the BMS UI.

7. Text Check In - Once in the Comms window, pilots must perform a text check in. This is simply entering a number for how many clients you see in the Chat Lobby/Comms window after connecting. For example, if you see 5 callsigns in the Chat Lobby, you enter "5" to let the other clients know you see them. This is a legacy Falcon procedure that is used to confirm all pilots see each other.

8. IVC Mic Check - Once a pilot enters the Chat Lobby, he should perform an IVC mic check. This is done by pressing and holding F1 or F2 to transmit. For example, “Demo mic check on IVC, how copy?”. The Host will reply if he hears you “Solid copy Demo 5 by 5” or “Lima Charlie” (meaning loud and clear). If a pilot has issues with communicating on IVC in the chat lobby, he will have a limited time to try and resolve the issue, so be sure to test your IVC before flying online!

9. Entering the Mission Screen - Once everyone has entered the Chat Lobby and a text check-in has been performed, the Host will bring up the mission. The Host will make sure all the settings are set to realistic and allow external views. Once the mission is up and the Host has stopped the clock, he will say "Campaign/TE is up" which means the clients can enter the mission screen. If there are more than 10 people in the Chat Lobby, it's required to enter in Chat Lobby order. This is done by looking at the list of callsigns in the Chat Lobby and going in that order. The first pilot on the list says "[Callsign] is committing" then once in the Mission Screen and the client has stopped the clock he would say "[Callsign is in, clock stopped]". Then the next pilot in the list would do the same until all pilots are in the mission screen. No changes should be made while clients are entering the mission screen. It is very important to note that only the Host should edit steerpoints and flights, and only Flight Leads are allowed to enter the Loadout/Munitions screen.

10. Assigning Comms/Radios – If using IVC (which is the standard at the 1st VFW), the Mission Commander must assign VHF (Tac or Victor) and UHF (Uniform, Area, Broadcast) channels for the flights. VHF or your Tac frequency will be for your flight. Meaning each flight will have their own VHF channel to communicate with each other on. Then all flights will share the same UHF frequency so you can communicate with other flights. The only exception is that during the ramp start, each flight will have their own back up UHF channel. This process will be described in greater detail below. But basically the Mission Commander will say something like the following:
Let’s say there are 3 flights (Cowboy, Falcon, and Lobo) – (I’m using fake frequencies):
-If I was the Mission Commander, I would say Cowboy ‘s Tac will be VHF preset 1 or 138.05, Falcon’s Tac will be VHF preset 2 or 138.40, and Lobo will be on VHF 3 or 140.50.

-Then I assign the UHF channel that we will share… “All flights will be on their assigned Tower frequency (UHF 15) and UHF preset 3 or 297.50 once airborne

-Then I need to assign back UHF channels for the ramp start – “For the ramp start - Cowboy will be on back up UHF 6, Falcon will be on back up UHF 7, and Cowboy will be on back up UHF 8”

It’s very handy to write all this down so be sure to have a pen and paper ready.

11. Briefing(s) - The Mission Commander will give a mission overview, assign flight channels (IVC and Teamspeak) and then the pilots will switch Teamspeak channels and discuss their individual flight strategies. Each flight will conduct a flight briefing on their own channel in Teamspeak and plan the flight. Once your flight is ready, your Flight Lead will say "[Flight Callsign] is ready to brief" over IVC using F1 or F2. Once all flights have said they are "Ready to Brief", the flights will then give a concise briefing in takeoff order (the first flight to take-off gives their briefing first) using IVC. So, this means flight briefings and planning will take place over Teamspeak, and the entire mission briefings/broadcast briefings will be done over IVC. The only information you need to pass on to the other flights during the briefing is what altitude your flight will transit out at, your overall strategy, and any other important information the other flights need to know. Briefings have the word “brief” in them because they are supposed to be concise, so don’t waste time telling the other flights what type of munitions your flight is carrying or any other information they do not absolutely need to know. If you are not in the mission screen before the briefing, you are not permitted to fly. So don’t be late and don’t waste time asking if there’s an extra seat.

12. Entering the 3D World - The Host should always set up the mission to be within 5mins of the first flight's take-off time to ensure they clock doesn't have to run at x64 for extended periods of time. But once all the briefings are completed, the Mission Commander will perform a Ready Check and Systems Check, and all the Flight Leads will check with their flights to confirm they are ready (over their own private TS channels) and broadcast "[Flight Callsign] is ready" when they are ready. The Systems Check is making sure all pilots have entered the Setup page of the UI and tested their flight sticks, throttle, etc… to ensure they are working properly. Once everyone is ready, the Host will say "The Host is committing to RAMP/TAXI/Takeoff" and that lets all the clients know it's time to click commit and select Ramp, Taxi, or Takeoff depending on what the Host said. For this point on it's a good idea to keep comms to a minimum.

13. In the Jet Cold Jet Radio Check In – Once in the cockpit in the 3D world, you will do the following.
-Turn the Power on in the jet
-Turn the volume knob of Comm1 all the way up
-Turn the UHF radio on by setting it to Both & Preset
-Ensure you are on the correct back up channel
-Check in using Comm1 (ALT+1)
-For example “Falcon 1-2, checking in”

Then once all pilots have checked in on the assigned back up channel in your flight, then Flight lead will have you start up your jet and continue the ramp start. At some point during the ramp start, flight lead will direct you to switch to Up Front Controls/assigned VHF channel.

http://i585.photobucket.com/albums/s.../UHFBackup.jpg
14. Fly the Mission as Fragged - From this point on the mission should go on as planned. If a pilot gets shot down or crashes, he/she is not allowed to re-enter the game. Do not ask if you can re-enter the game even if there’s an extra A.I. jet. We strive for realism in the 1st, and therefore, when a pilot is down, he is down. After a pilot is shot down, he/she must exit the game and wait until the mission is over for the debriefing. With the exception of the Mission/IVC Host, a pilot is not allowed to stay in the 3D world switching views. If you a pilot has a CTD or controls issue, he will be allowed one opportunity to re-enter after letting the Host and/or Mission Commander know about the CTD. Multiple exits and re-entrances into the 3D world can also cause problems so under no circumstances are pilots allowed to re-enter the 3D world more than once. We understand things happen, but we have to maintain online stability for the other pilots and therefore you must respectfully back out if you have a second CTD or issue.

15. Debrief – After the flight, we will conduct a debrief. We do not hold back on our debriefings. Debriefings are used so we can be better virtual pilots. Therefore, if you made a mistake and you know it, call yourself out on the mistake. If you saw a mistake another pilot made or something he/she could’ve done better, bring that up as well. Just make sure you are respectful in the way you suggest areas for improvements. Pilots should not take offense to constructive criticism. You may be doing something you didn’t know you were doing. If you disagree with a statement, wait for the pilot to finish speaking then you can explain why you did what you did. But again, always be respectful. Our briefings are always a "what we could have done better" debrief. The debriefing will not be each pilot telling us each step of their mission over and over again. You can give us a brief overview of what happened during the flight, but only cover the important events and lessons learned. Please do not give a debriefing like “We took off, headed towards steerpoint 2, climbed to 25,000, etc…”. Only cover the important stuff. The debriefing is used to discuss how you thought the flight went, tactics that were successful/unsuccessful, brevity, etc... See the Classroom section of the forum for more details.

16. MOST IMPORTANTLY… HAVE FUN! – We try to strive for realism and we do enforce SOPs, but at the end of the day, this is all for fun. So if you’re not having fun, let us know so we can help. And if you have a suggestion to improve our SOPs, please let us know. We are always looking for ways to get better and do things better at the 1st.

OTHER NOTES BEFORE FLYING

Before flying:
Have a pen and paper. There are a lot of frequencies, tacan channels, IPs, etc... that you will need to know. Pen and paper is very helpful.
Test your hardware... do a quick test before a flight and make sure everything is working. Trust me, this will make your flying so much better because you'll never have issues with a stick or something not working.
Make you enter the bandwidth and hit enter - If you don't enter the bandwidth, we will get in the pit and not have any models or textures on the ground.
Only Flight Lead enters the munitions/loadout screen and/or edits steerpoints - This is so we don't cause problems with syncing everyone up or loadouts. Technically all ships in the same flight should have the same loadout. But this is up to the mission commander.
TE/Campaign Hosts - When you host a mission or TE, try to save the mission with the clock about 5 mins before ramp start time (25mins from takeoff). This ensures the clock doesn't have to be on X64 for a long time.
Radios:
Back-Up UHF - This is the frequency you will check in on when entering the pit. Each flight will have their own back-up UHF.
Tower Frequency / UHF 15 - This what everyone should set the tower to... UHF preset 15 in their DTC. Remember, this is the frequency you should be on for UHF when doing your ramp start (after the check-in on back up UHF frequency). Flight lead will tell you when to switch to the UFC (Up Front Controls) and check in on your assigned UHF/VHF.
Area/Group/UHF (or Uniform) - This is the frequency that all flights in the same package will share once airborne. Generally we assign these as UHF 6-10. You will switch to this frequency after getting takeoff clearance and taking the active runway. Remember that if you ever switch you UHF frequency that you broadcast it over UHF so other flights know you are making the change.
VHF (Victor) - Each flight will have their own VHF channel. This is the frequency that you use to communicate within your own flight.
When giving radio info - Be sure to include the preset channel and the frequency. That way if they have trouble getting you on the radio, they can switch to the frequency themselves... in case their presets got messed up.
Ramp Start
When you get in the pit. Don't make a "in the pit call" or text check in. Don't start your jet until talking to flight lead on back up UHF and he tells you to start the jet.
Simply turn the power (electrical power) on in your jet. Turn Comm1 volume knob all the way up. Switch the UHF radio to Both and Preset. And change the back up channel to you assigned back up channel (using the channel knob).
If you have problems getting the radios up or anything. Text your problem SHIFT+T so flight lead can help you.
Once you are on the UHF back up radio, check in "Falcon 2-1, checking in". Flight lead will wait until all pilots check in before telling you to start the jets.
HERE IS HOW YOU SET UP THE BACK UP UHF RADIO WHEN GETTING IN THE PIT
http://i585.photobucket.com/albums/s.../UHFBackup.jpg
You will remain on the the back up radio while starting up the jets. When you get your jet started, tell flight lead you have a good jet "Two, good jet". Once Flight Lead hears everyone has a good jet, he will make the call to switch to UFC and check in on your assigned Victor. You can do this two ways... 1.) If you have your UHF/VHF channels set as the default in your DTC (Data Cartridge), you simply need to use your DTE page on your right MFD and click Load (you can do this while your left MFD is doing the FCR bit test). After your DTE loads, you will automatically be tuned into UHF 15 and your assigned VHF (if you set them to default by checking the default green box next to the channel in your DTC). 2.) You can manually enter in the frequency for the Tower on UHF and your assigned VHF. So after flight lead tells you to switch to Victor, you will do another quick check in. "Falcon, check in Victor 1"... "Two, checking in".... "Three, check in..." "Four, checking in"... (Flight Lead) "Copy, all Lima Charlie". Now you proceed with your ramp start.
This is the green default box I'm referring to above UHF and VHF:
http://i585.photobucket.com/albums/s...3-31-58-23.jpg
http://i585.photobucket.com/albums/s...3-32-12-77.jpg

This is the DTE page that you press Load on:
http://i585.photobucket.com/albums/s...3-33-32-46.jpg

And that will tune my radios to exactly what I set as default... notice it matches my DTC default settings above.
http://i585.photobucket.com/albums/s...3-33-44-24.jpg
Flight Leads need to broadcast their taxi calls. For example if I had a four-ship, "Tower, Falcon 1, flight of four, ready for taxi". Then press T to get the tower menu and select Ready to Taxi.
IVC
When using IVC, make sure you wait for the mic "click" after someone transmits before responding. It's easy to step on each other.
Make your calls clear and concise. Don't hog up the radio.
If you transmit something and let go of the transmit button, wait until the other pilots respond before transmitting again. We often will transmit something then forget to add something and transmit again which leads to stepping on other pilots.
Lights
When you get in the pit, turn your wing/fuselage lights on and set to flash. Leave landing light and strobe off.
When aligned and ready to taxi, turn on strobe and landing light.
When holding short preparing to takeoff, set the lights to steady
At fence in, lights out
At fence out or air refueling, or on weapons range, lights on.
After landing and clearing the active runway... lights back to flash.

Nicht schlecht Para... wir werten auf die deutsche Übersetzung von dir

Wie schon öfters geschrieben, bin ich voll davon überzeugt, dass hier EINE gemeinsame verbindliche Prozedur vorgegeben wird. Vieles von der Liste ist richtig, manches leider nicht ganz...stay tuned

Haben heut ein weiteres Problem gefunden und auch die Lösung dazu. Wenn einem der Falke crasht oder man Ziele etc nicht findet sollte man unbedingt nachsehen ob man das richtige Battlefield hat. Is nen anderes eingestellt kann man zwar connecten udn auch mitfleigen aber der Falke wird extrem instabil und auch Ziele etc. sind teilweise einfach nedd da.

bisher nur Korea ....aber bei benschmark...arbeiten sie daran...

Zitat von Deamon

Stelle ich die Trimmung wieder auf die mitte geht es wie von geisterhand wieder auf vollen anschlag nose Down
wie gesagt ich mache nichts ( Weder am Stick noch am Schubregler , oder Tastatur )

habe auf meinen Cougar zwar die Trimmung drauf ( Pinky Switch + Coolie-Hat 1 )

Vieleicht habt Ihr ne Idee woran das liegen kann oder hattet einer von euch auch schon das Problen
Das war auch der Grund warum am Dienstag mein Flieger abgeschmiert ist

Warum sich deine Trimmung verstellt, weiß ich nicht und kenne bei mir das Phänomen auch nicht. Wenn aber die Trimmung immer wieder automatisch auf Vollanschlag läuft, gibt es Abhilfe, wenn der Trimmreset auch nicht helfen sollte, hast du den probiert? Sollte das Phänomen trotz Trimmreset weiter bestehen, dann trimme zunächst in die "Vollanschlagrichtung", obwohl sie dort schon steht und dann zurück.

Gruß

Nik

Auch bei mir trat das Trimmproblem auf, hatte zu der Zeit noch den X-52. Am Stick kann es also nicht liegen.
Mir fiel dabei auf, dass es immer dann auftrat, wenn ich die Trimmung nicht stufenweise veränderte, sondern die entsprechenden Tasten gedrückt hielt. Trim- Reset brachte nichts.
Ich meine mich zu erinnern, dass ich das Problem durch die genaue "Gegenteilmaßnahme" geregelt hatte, schiebt z.B. die Trimmung automatisch nach links, halte ich die Tasten für die Trimmung nach rechts gedrückt. In Kombination mit mehreren Trim- Resets war es dann erledigt.
Ohne TrackIR war es auch recht schwierig, die Trimmanzeige zu überprüfen und dabei den Vogel in der Luft zu halten, also auf mind. 20000ft. gegangen und dann das Ganze für 5-7 Sekunden bearbeitet, um dann wieder aus dem Fenster nach dem rechten zu sehen...

Gruß
Corran

hatte das selbe Problem...habs wegbekommen,, in dem ich für die Trimmung andere Tasten zugewiesen hab..

gruss Jaws

Bei mir gings nur dann, wenn die Trimmtasten über das Spiel und nicht die Saitek Software programmiert waren. Aber seitdem läuft es problemlos. Sollte trotzdem mal wieder ein Problem auftreten, dann hatte ich einfach wild am Trimbutton und Reset herumgedrückt bis es ging.

Corran hatte dazu gerade eine Lösung, den Trim button IN GENAU DIE Richtung drücken, wo das Flugzeug hinzieht, dann in die Gegenrichtung und dann halt Reset oder sonst was...Da ist noch was bei BMS zu machen.