Joint Warrior 2: Op Quarterback

[TAW_Blaze]

Anyone else having massive problems with the patch? Non stop warping, 1 FPS when looking at the battle. Utterly unplayable.

[FLANKERATOR]

Looks like 1.2.10 is a no-go.

 

Guys, I've added logs from all the fights as well as pilot scoring up to now.

 

SA points and new rankings are not there yet until final battle is over.

 

Any queries, let me know.

 

http://sa-sim.com/join-warrior-2-104th-and-51st-meeting-in-the-final-again/

[TAW_Blaze]

According to DCS in the live match I got their AWACS. What happened to that?

[FLANKERATOR]

According to DCS in the live match I got their AWACS. What happened to that?

 

According to Tacview, both Spade and you were after the AWACS. You damaged the A-50 first but she was still flying, then Spade finished her with an AMRAAM. Spade got 18pts for the kill, you got 9pts for contributing to it and blue team got 150 pts on the scoreboard.

 

No. And neither do you ....

 

 

:megalol:

[TAW_Blaze]

Yeah I shot 3 slammers into it and then my sparrow got the kill according to DCS. Whatever though, I don't really mind.

[Shaman]

Anyone else having massive problems with the patch? Non stop warping' date=' 1 FPS when looking at the battle. Utterly unplayable.[/quote']

Maybe not non stop but unfortunately yes, all above is happening. Especially something new is huge frame drops.

1.2.10 is broken, and if it is not patched and fixed until postponed date.. I don't think it is wise to go with a final.

[FLANKERATOR]

Yeah I shot 3 slammers into it and then my sparrow got the kill according to DCS. Whatever though' date=' I don't really mind.[/quote']

 

I'm aware that Tacview could generate some discrepancies when replaying a track. This is why I ask you guys to let me know if you spot any inaccuracy in the logs or stats.

 

In this case, given that DCS confirmed the kill for you, then best would be to make it a shared kill and award same number of points to both of you.

 

Edit: database updated and new score is 68 points.

Edited August 10, 2014 by FLANKERATOR

[FLANKERATOR]

Maybe not non stop but unfortunately yes, all above is happening. Especially something new is huge frame drops.

1.2.10 is broken, and if it is not patched and fixed until postponed date.. I don't think it is wise to go with a final.

 

Agreed. I don't think any of the guys flying in the final has a Steam version, so even if the patch doesn't come out before the 23rd, we could still revert back to 1.2.9.

 

I take the opportunity to kindly ask everyone from the red and blue coalition to let us know as early as possible if uncertain for 23 August, so we can offer to other pilots and avoid another postponement.

[JunMcKill]

One question Flanker, when it's the official start time of the match? when the order of start engines is given, or when the first fighter takeoff?, and the game is three hours long isn't it?, everything after the three hours of the official start time is not valid?.

 

Regards,

 

RuSh

[FLANKERATOR]

One question Flanker, when it's the official start time of the match? when the order of start engines is given, or when the first fighter takeoff?, and the game is three hours long isn't it?, everything after the three hours of the official start time is not valid?.

 

Regards,

 

RuSh

 

Hi Rush,

 

Clock starts ticking after both sides call 'Fight is on', after which, fighters are cleared to take off. 10mn later, strikers get clearance to take off as well. Once the 3 hours mark reached, no take off is allowed and all airborne units must disengage and RTB immediately.

[JunMcKill]

Hi Rush,

 

Clock starts ticking after both sides call 'Fight is on', after which, fighters are cleared to take off. 10mn later, strikers get clearance to take off as well. Once the 3 hours mark reached, no take off is allowed and all airborne units must disengage and RTB immediately.

 

Thanks Flanker!

[FLANKERATOR]

Gents from the blue and red coalitions,

 

Here's a reminder to rollback to 1.2.9 for this Saturday battle.

 

1. Back up (rename) your /Saved Games/DCS folder
   
2. Hit 'Start', 'Run', type in CMD and click 'OK'
   
3. Type what's in a red box and change what's in green box to where you have DCS installed, rest will be auto generated.
   

If you need more info, check out SkateZilla's post here.

 

 

- NOT FOR STEAM VERSION -

Edited August 20, 2014 by FLANKERATOR

[Falcon_S]

So? We play tonight but 1.2.9?

[Mustang]

I'm quite loathed to roll back to 1.2.9, i flew in the 104th server last night for just over 4 hours in one session with a full server of 26 clients with no problems in 1.2.10.

 

But if it has to be done so be it, although i won't roll back though right until we're certain the event is going ahead, i want to fly on some public servers this afternoon and 1.2.9 will break that for me.

Edited August 23, 2014 by Mustang

[Falcon_S]

I`m miss stability test on last JW meeting and i don`t know where is the problem. But as Mustang said i fly every day on full 104th server and i dont see any problem.

 

But if it is decided to 1.2.9 ... just wanna to know :crazy:

[FLANKERATOR]

There was a big lack of communication and coordination for this fight. Most of the guys ended up reluctant to roll back to 1.2.9 and I hadn't heard from Maverick to know about the blue team status until today so I couldn't update.

 

At the same time, people were not unanimous about 1.2.10 but at the same time not keen to roll back to 1.2.9 so both teams have decided to stand down and postpone this final fight again until further notice.

 

From my side, I will go ahead and update the rankings and will amend whenever I get the results of this battle.

[USARStarkey]

In the meantime can we do another event in parallel so we dont have to wait on the first on to end?

[Falcon_S]

What is different between 27 people on 104th server every day and 27 people on same server but on JW event? Really don`t want to stop this event until new net code has come somewhere in future?

 

Sorry if I`m not understand problem.

[FLANKERATOR]

In the meantime can we do another event in parallel so we dont have to wait on the first on to end?

 

Yes, better to keep the ball rolling, what are you guys up for?

 

 

What is different between 27 people on 104th server every day and 27 people on same server but on JW event? Really don`t want to stop this event until new net code has come somewhere in future?

 

Sorry if I`m not understand problem.

 

The problem is that 2 weeks ago, red and blue teams tried JW2 in 1.2.10 and reported lagging issues before postponing the final. Also people who were on the servers playing public missions, reported similar lagging problems just after 1.2.10 came out. They described the server as unplayable due to huge lagging.

 

It appears things got better now. Maybe all this past trouble was just due to other reasons not necessarily 1.2.10-related. Maybe some issue with the master server timed with the release of 1.2.10, maybe a temporary issue with the server's bandwidth. As things seem to be rolling smoothly now on exact same DCS build on both servers (51st and 104th), we could have well been barking up the wrong tree.

Edited August 24, 2014 by FLANKERATOR

[JunMcKill]

I had no problem with the 1.2.10 in our server with lots of armor, and playing about 12 pilots, the problem is when someone with a poor connection (above 400ms) get into the server, in this case is a mess. Yesterday flying in the 51st server, came a guy with 3500 ms ping!, was horrible the warping and lagging, we had to kicked him out, but was too late, the server went down five minutes later.

[Buckeye]

Yes, better to keep the ball rolling, what are you guys up for?

 

The problem is that 2 weeks ago, red and blue teams tried JW2 in 1.2.10 and reported lagging issues before postponing the final. Also people who were on the servers playing public missions, reported similar lagging problems just after 1.2.10 came out. They described the server as unplayable due to huge lagging.

 

It appears things got better now. Maybe all this past trouble was just due to other reasons not necessarily 1.2.10-related. Maybe some issue with the master server timed with the release of 1.2.10, maybe a temporary issue with the server's bandwidth. As things seem to be rolling smoothly now on exact same DCS build on both servers (51st and 104th), we could have well been barking up the wrong tree.

 

The lag is definitely better now, it has been pretty much non-existant for me lately. I was a major complainer about it right after 1.2.10 released and caused a ton of lag issues (that ED refused to acknowledge on these forums), but over the last few weeks things have been running well -- or as well as they did prior to the 1.2.10 release.

 

Hope to see the 104th and 51st settle this battle soon!

[FLANKERATOR]

The lag is definitely better now, it has been pretty much non-existant for me lately. I was a major complainer about it right after 1.2.10 released and caused a ton of lag issues (that ED refused to acknowledge on these forums), but over the last few weeks things have been running well -- or as well as they did prior to the 1.2.10 release.

 

Hope to see the 104th and 51st settle this battle soon!

 

Yes, new modules tend to shake up stability a bit, which is understandable, though in this case, my bet is that some other things went wrong and coincided with the 1.2.10 release and this is, in my opinion, what caused all that initial fuss. Aside from few people reporting random crashes, it looks good enough.

[TAW_Blaze]

IIRC if someone joined with very high ping it'd completely destroy the game for everyone.

[MAD MAX]

When we finish this competition?

[FLANKERATOR]

When we finish this competition?

 

104th and 51st are still discussing it. Results from JW2 have already been processed so if this final fight ever happens, it will be seen as a separate battle/event.

 

I don't know if it would be the right time now after the last release when you look at the amount of people complaining. I have personally not updated my DCS yet.