Case

I don't know why squads haven't done that so far. In the 51st we've seen no need for it. Instead we use different means of promoting teamplay, through our GCI weekends and Georgian Incident campaign for instance. The thing with payloads it that they usually aren't included in the integrity check, mainly because the stock payloads for the strikers suck. A few months after FC2 came out a few servers decided that the rearm.lua file could be taken out of the integrity check because it would be plainly obvious if someone cheated by creating illegal payloads, it would either be in the server messages or in the stats for everyone to see. For ERI/LEAVU/GEAR this is different, as there would be no way to tell if someone uses it or not except for when it is part of the integrity check. Then anyone joining would have to have it installed themselves and will have to make the decision to use it or not.

Riptide hit the nail on the head. In a multiplayer environment you want to stop the suspicions. Back in the day there was nothing wrong with ERI or LEAVU, as long as the scripts were part of the integrity check. This way everyone on the server would be running the scripts and no one could complain that someone was using it for cheating, as they all run it. Allowing ERI or LEAVU without checking their integrity will just result in name calling, especially as it only took commenting out one line in ERI to get exact ECM ranging.

Yes, you can make your own payloads, though maybe your payload is already in Wolverine's Payload Mod.

Most likely the AI plane you are fighting turned into the notch and started dumping chaff. When this happens the missile stops tracking the plane and tracks the chaff instead, hence the change in direction (though not the direction at launch).

Must be Panzertard pulling a prank on Etherealn :D Otherwise it may be an issue with ping limits.

Ok, I'll go back to flying my Su-25A then :D

In what situations would you manually lase a bomb to the target? It seems the auto lase option would the preferred one in every case? The only times I manually lase a target is at night in conjunction with the IR pointer and NVGs to make sure I'm looking at the right target. Are there other situations?

That's ok. Feel free to ask any questions on our forums at http://www.51st.org/forums or check our TS3 server at http://www.tsviewer.com/index.php?page=ts_viewer&ID=61407 to see if we are on and drop by to ask questions.

That does not depend on the server, only on what you run. If you run Black Shark and the server list shows you servers then you can enter all those servers. If the server has client slots for Ka-50's then you can select one and fly there. However, you can not select an Flaming Cliffs 2 client aircraft (F-15C, A-10A, Su-25, Su-27, Su-33, MiG-29A, MiG-29G, MiG-29S) from Black Shark. To fly these aircraft you will have to purchase and install Flaming Cliffs 2. In those servers you can fly Black Shark. Based on your avatar I'm even guessing that this is you :)

There is no date set, but we are planning to start the campaign in September. Before that time we need to get the interested squadrons involved and decide on some issues that would involve those squadrons.

Yes, just post in this thread on the 51st forums and tell us with how many pilots you will join and what aircraft you would prefer to fly.

Buon Giorno! No, we start with a pre-designed mission where blue controls the area near Anapa and most of Georgia while red controls the rest of the map. The Georgian Incident campaign is made up out of turns where each turn lasts 3 hours and turns are separated by two weeks. After each turn the mission is updated, units and aircraft that were destroyed will be removed, aircraft that were transferred to other bases will be moved there, and units that moved during the turn will start at their new position in the next turn. Both coalitions will have a General who is in charge of battle planning and the placement, movement and targeting of ground units. This is only allowed when a coalition has the attack turn, which will alternate between turns. During a turn when the the General has the ability to attack he can add and move ground units based on the rules outlined in the operating procedures (see PDF in first post). As such, after each turn the mission will be different from where it started and it will evolve as the campaign progresses. During the winter of 2009/2010 we ran a similar campaign called Crimean Incident. This used Flaming Cliffs 1.12 and we did 6 turns in total and it was a great success. Unfortunately FC2 came out and people stopped flying FC1.12 which meant the end of the campagin. Georgian Incident is the continuation of this campaign, now using FC2.

Try again now, it should be fixed.

Indeed, get a buddy to fly with and do alternate runs on the target area, where one plane attacks and the other one orbits keeping an eye on the target area for launches or AAA.

Hi Petritis, We're looking into this and we'll let you know when it is fixed.

Also be advised that you can do something like: @start /d "C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2" bin\x86\stable\simulator.exe --nopause %1 to provide the path to the executable.

Multiplayer maps of what?

There is away around that only uses three triggers, see this post by Mbot. In your case it would look like: CONTINUOUS // FLAG IS FALSE (1) // SET FLAG (1) SWITCHED CONDITION // UNIT OUTSIDE ZONE (Unit 1, Zone 1) && UNIT OUTSIDE ZONE (Unit 2, Zone 1) && TIME SINCE FLAG (1,1) // CLEAR FLAG (1) ONCE // TIME SINCE FLAG (1,2) // MESSAGE ("Unit 1 or Unit 2 is inside Zone 1")

These are the command line options. There are some interesting options to replay tracks and things like that.

For my stats I made minimal changes to LUA, most of the work is done from the debrief.log where I use LUA to add some more information that I need. So to add to Moa's list of how to improve the debrief.log, the major issue is the lack of information or information being spread across different files. Ideally, I'd like to debrief.log to show: 1. Clients joining the server (name, IP, UCID) 2. Clients entering the server (actually picking a plane) 3. Clients leaving the server (going back to spectators) 4. Clients exiting the server (actual disconnect) 5. For each event, provide the unit type (Su-27, BTR, Molniya)

Good stuff Yoda. You figured out how to make PNG's yourself?

Regardless of unpacking, at some point or another you will have to load the data in to memory. You may want to try to use fancy algorithms, but I always favor the easy approach first and prove that it isn't workable before going for more complex solutions.

No, the PNG generation is separate from LUA. Just use the same setup as what is done in the Tacview LUA file.

If you can write some LUA code to do this I'll run it and generate the PNGs.