Operation "Blue Flag" - 24/7 PvP Campaign - ROUND 2

[Esac_mirmidon]

Not following the rules is one thing. Make a note to admins and this guys will be banned.

 

Beeing a noob NEVER could be a reason to not be included in this FREE-OPEN campaign.

[zaelu]

My eyes are in tears from the smell of onions. Seriously. They say putting water over them makes the effect less annoying.

 

I observed that the fighters spawn with something above 20% fuel that should be enough for a quick intercept for an elite squad that defends a AB. Fueling to 50% would take far less than fueling to 100%.

 

Me and my friend fueled our Su-27 to top last night (Twice) and we had very nice chats about all kind of stuff while the crew were busy. Elite ftw!

 

Relax a bit... it's not only a game... it's a non elitist intersquad war from the beginning (look at the number of lonewolves).

[Scharfi]

7 Lives are still too much in my opinion. :/

We should reduce them.

[gregzagk]

Hey all!

 

A small update of the current server status and some AAR (Connection statistics) of the second round:

 

 

3rd Round Preparation

Since the end of Operation's "Blue Flag" Round 2, we are working on some new features and fixes that we will present on the 3rd round.

 

Feedback on the forums was really important & helpful.

 

The server is currently running a stress test session since Friday and will remain open until we will be ready to announce the official start of the 3rd round.

 

Please keep reporting issues on the forums.

*At this point I would kindly ask again to use this thread specifically for the campaign and not for debates that are already open in other threads of the ED Forum. It really helps when we won't have to search through many posts for a report like Tello did previously about a possible issue for the AI's.

 

The current changelog of the 3rd round is available here : http://www.buddyspike.net/news/m/34326321/article/3506641/page/1

 

On other news we upgraded our website recently ( layout and content ) and started the polls for the best Red & Blue Pilots of Round 2 (LINK: http://www.buddyspike.net/nominations ).

 

The winners will earn keyrings with the Operation "Blue Flag" logo.

 

 

2nd Round Overall Connection stats

 

Start date : 11st of September 2015

End date: 22nd of September 2015

 

During the 2nd round, a total number of 1503 DCS World pilots connected to the server. (unique id's)

 

A total number of 9296 connections occured resulting an averege of ~6 connections per pilot during the 12 days.

 

The player limit on the Server was set to 60 clients per session.

 

On the next chart you can see the Red & Blue pilot numbers flying on on the Server during the 12 days of the Campaign.

 

 

 

Earlier today we reached the 400th registration on "Buddy Spike" website.

Thank you all for your participation so far and we hope that more of you will enjoy the upcoming events.

 

See you in the Server :)

 

Greg

Edited September 29, 2015 by gregzagk

[TaliG]

edit :doh:

Edited September 28, 2015 by TaliG

[Sweep]

Hahahaha!

 

LOL! Jeffrey (who was on Blue,) is on the Red MVP nomination list! :megalol: :thumbup:

[ScAvenger001]

I'll just remind that since round 2 is over, we are in a mode of test.

Server restarts can occur and we are trying to maintain consistency as much as we can during this test phase so you guys can still enjoy it.

 

I believe what happened in this case is that the server crashed prematurely to the normal restart and right after your capture, this simply caused the status of the capture not to be saved yet.

 

This wasn't a crash, it gave a "mission restarting" message and everything, it was just ten minutes early and didn't record the FARP capture.

[xcom]

did the mission restart for you immediately or did you get kicked out?

[gregzagk]

This wasn't a crash, it gave a "mission restarting" message and everything, it was just ten minutes early and didn't record the FARP capture.

 

After new mission restart how did you check that the FARP was not captured? Through the DCS F10 Map or the gadget ?

 

After the mission restarts it needs 20 minutes to repair units and it will get your side's units repairs.

 

Greg

[SpeedStick]

My whole reason for taking part in this is the more difficult setting, and hence the immersion. Needing more coordination, communication ect. If I'd wanted unlimited life, 10 sec startup and taxitakefoff, I'd join ANY other server.

However I support whatever you decide

[gregzagk]

My whole reason for taking part in this is the more difficult setting, and hence the immersion. Needing more coordination, communication ect. If I'd wanted unlimited life, 10 sec startup and taxitakefoff, I'd join ANY other server.

However I support whatever you decide

 

No worries if you don't see anything from Xcom, Crash or me it's not official :)

 

LOL! Jeffrey (who was on Blue,) is on the Red MVP nomination list! :megalol: :thumbup:

 

LOOOL :D Sorry about that.

 

Due to the mistake Jeffrey will receive a keyring anyway.Thanks for letting us know.

 

Greg

[Oznerol256]

Can we get a percentage cut off for closing airports and farps, so that we dont have to kill every last unit? It seems like there is always some vehicle hidden by the other team or bugged somewhere where we can't see. Just close the objective if there is only 1 or 2 enemy units left. Maybe it can be done by programatically killing the last objectives. Since the units respawn in waves they shouldn't get killed again as soon as spawn.

[HiJack]

400 registered! WOW NICE. Can we have them all in one server at the same time soon please! :D What a furball that would be!

Edited September 28, 2015 by HiJack

[ScAvenger001]

did the mission restart for you immediately or did you get kicked out?

 

When the mission changed, DCS crashed to the main menu for me. So, "kicked out" but that's just as likely to be a problem on my end.

 

After new mission restart how did you check that the FARP was not captured? Through the DCS F10 Map or the gadget ?

 

After the mission restarts it needs 20 minutes to repair units and it will get your side's units repairs.

 

Greg

 

PAK6 intel report listed the FARP still as red after the restart. When we sent another strike package to the FARP the respawned ground units attacked our A10s. The FARP was definitely red after the restart.

[gregzagk]

Can we get a percentage cut off for closing airports and farps, so that we dont have to kill every last unit? It seems like there is always some vehicle hidden by the other team or bugged somewhere where we can't see. Just close the objective if there is only 1 or 2 enemy units left. Maybe it can be done by programatically killing the last objectives. Since the units respawn in waves they shouldn't get killed again as soon as spawn.

 

Hello. This should be improved as the enemy team can't move anymore units.

 

So if there are any units placed wrong near the assets please report the Airbase, City or FARP to take a look.

 

1.5 Open Beta

Fortunately ED announced that they are ready to release 1.5. As we want to assist on the open beta phase our initial thoughs are to move the stress testing there once it's out.

 

Depending on the results our main goal remains to release the 3rd round there with some additions that we were waiting for.

 

Stay tuned :)

 

Greg

[HiJack]

1.5 Open Beta

Fortunately ED announced that they are ready to release 1.5. As we want to assist on the open beta phase our initial thoughs are to move the stress testing there once it's out.

Perfect! :thumbup:

[Darkwolf]

In wa, do ou expect tanks to sit in the open ? DCS is already ridiculouly empty of any ground clutter compared to real life.... are you really expecting a defense brigade to stay on apron and be like " hey shoot me ? "

[Gaanalma]

Perfect!

[xcom]

When the mission changed, DCS crashed to the main menu for me. So, "kicked out" but that's just as likely to be a problem on my end.

 

DCS crashed does not necessarily mean that you were "kicked out", it means either your DCS crashed and the server went on running, the server crashed and in return because the mission is heavy your DCS also crashed or mission restarted on the server and your DCS crashed.

 

I believe what happened is that DCS on the server has crashed before it was supposed to be restarted and as I said to you before, this is probably the reason why the capture was not saved.

[xcom]

Announcement:

 

BuddySpike now owns a domain - BuddySpike.net.

This means the old BuddySpike website is now available at the above domain, please update your bookmarks ;) (Although the old URL should still work).

 

Thanks to the donations we have been receiving we are able to start pushing this forward and get more events, more prizes and eventually get better stuff back to the community!

Thank you all for believing in this project, your constant tests, feedback and ideas are always welcome. We will continue building and creating multiplayer events for the DCS community, with all the help you are all giving us, it is making it a lot easier!

 

So a big THANK YOU to all of you that take your time to donate, test and give us great feedback!

 

SALUTE!

 

BuddySpike Team - Greg, Xcom, Crash.

[ScAvenger001]

DCS crashed does not necessarily mean that you were "kicked out", it means either your DCS crashed and the server went on running, the server crashed and in return because the mission is heavy your DCS also crashed or mission restarted on the server and your DCS crashed.

 

I believe what happened is that DCS on the server has crashed before it was supposed to be restarted and as I said to you before, this is probably the reason why the capture was not saved.

 

I think we're saying the same thing, that my losing connection to the server is non-indicative. But I really don't think the server crashed ate the capture, because the "restart" message displayed for everyone and it happened 30 seconds after the capture.

 

That said, my understanding is that the capture event would be recorded more or less immediately? Rewatching the video, the capture message appears at 04:27, the "mission restart" message appears at 04:53, the huey's clock stops ticking (presumably due to the mission being closed server-side and the simulation halting) at 04:59, and the recording ends (due to the game closing itself) at 05:21. Since the capture message is apparent to the other clients, the server must still be alive at that point, and I'm pretty sure the restart message is also triggered server-side so it's very probably still kicking at that point as well.

 

Also, oddly, it gave me a "welcome back" message when I initially landed at the still-red FARP.

 

In any case, there's more than 30 seconds between the capture and the mission end.

 

Here's how it went, and then you'll know everything I do:

 

[gregzagk]

I think we're saying the same thing, that my losing connection to the server is non-indicative. But I really don't think the server crashed ate the capture, because the "restart" message displayed for everyone and it happened 30 seconds after the capture.

 

That said, my understanding is that the capture event would be recorded more or less immediately? Rewatching the video, the capture message appears at 04:27, the "mission restart" message appears at 04:53, the huey's clock stops ticking (presumably due to the mission being closed server-side and the simulation halting) at 04:59, and the recording ends (due to the game closing itself) at 05:21. Since the capture message is apparent to the other clients, the server must still be alive at that point, and I'm pretty sure the restart message is also triggered server-side so it's very probably still kicking at that point as well.

 

Also, oddly, it gave me a "welcome back" message when I initially landed at the still-red FARP.

 

In any case, there's more than 30 seconds between the capture and the mission end.

 

Here's how it went, and then you'll know everything I do:

 

 

Well this happens when you are stupid... :doh:

 

Sorry mate totally my fault. Checked again the mission file and saw that we had uploaded a test version in which the minutes were wrong... Should be ok in the next version.

 

Thanks again for reporting. Keep it up.

 

Greg

[ScAvenger001]

Sure thing :)

[gisuck]

LOL! Jeffrey (who was on Blue,) is on the Red MVP nomination list! :megalol: :thumbup:

 

I voted for Jeffrey! :lol: :thumbup:

[xcom]

I think we're saying the same thing, that my losing connection to the server is non-indicative. But I really don't think the server crashed ate the capture, because the "restart" message displayed for everyone and it happened 30 seconds after the capture.

 

That said, my understanding is that the capture event would be recorded more or less immediately? Rewatching the video, the capture message appears at 04:27, the "mission restart" message appears at 04:53, the huey's clock stops ticking (presumably due to the mission being closed server-side and the simulation halting) at 04:59, and the recording ends (due to the game closing itself) at 05:21. Since the capture message is apparent to the other clients, the server must still be alive at that point, and I'm pretty sure the restart message is also triggered server-side so it's very probably still kicking at that point as well.

 

Also, oddly, it gave me a "welcome back" message when I initially landed at the still-red FARP.

 

In any case, there's more than 30 seconds between the capture and the mission end.

 

Here's how it went, and then you'll know everything I do:

 

 

Your assumption is wrong, the capture is recorded immediately, but not saved immediately.

So either it was a server crash or a mission restart because of Greg test file mistake, in either way it is as I told you before the event did not save.

 

You can keep arguing on how this works, but I wrote it so believe me when I tell you :)

Edited September 29, 2015 by xcom