=VG= Acro1

Guys I'm sorry, I have to give my absence on the last minute. Within the last few days I suddenly booked a skiing trip, won tickets to Madrid and got a new girlfriend, and now I'm racing around to get my shit together   I cannot make it this time, but will look forward to the next one!

Please take a look at this server crash report form. The answer sheet has been set to zulu time, so if a report is made immediately when server crashes, we can track the necessary information from the server logs. I've omitted questions about faction and previous map cuz we can easily track those from the logs as well. Feedback is welcome ^^!

Report form: Click HERE

Report collection: Click HERE

4 hours ago, =VG= TEDF said:

1.6 sneaking around

Is it reeeeeeeaaaaalllyyy though?

Can I volunteer for UAV just to get some inpromptu Arma 3 co-op footage without actually participating in the mission  ?

4 hours ago, =VG= Fastjack said:

Why not both? 

Because confusion Tomatoes are technically fruits, but due to their usual usage and the volume at which they are consumed/processed, they are considered vegetables by law in most countries. This is the best way, since they are optimally regulated, subsidised and taxed based on this usage behaviour.

Similarly, if we call this bird a Trans helo then the pilot's priority is transport and supplying. He must drop CAS activities and respond to trans calls ASAP.

On a map with a big-ass Chinook and considering that the Griffon has only gunner seats, it's superior role as dedicated CAS is evident.

But as said: Not both because we don't like confusion . We can't have some ppl punished for stealing and some not, but you know that already.

1 hour ago, RizlaQc said:

yeah no teamkill for me ........

Yeah keep dreaming Added! Go look!

Kokan has many flat fields that the enemies cross constantly. This is where a good Griffon CAS team can do real damage and halt an attack. Even if hovering high and far for safety, you can just pick off the blips. (After checking map, duh)

As mentioned, the bird has only co-pilot and doorgunner seats. The damage it can do as dedicated CAS far outweighs the logistical / transport role it ever could. Kokan has plenty of vehicles and transport isn't very oftenly called in general.

There needs to be a ruling, so that everyone (or at least the vast majority) acts accordingly. Having a 'neither CAS nor trans' bird is only going to cause confusion and frustrated honest players. This is why for ease and maximum effectiveness, the 'soft' consensus is that the Griffon is a CAS asset.

For reference: We are talking about the Griffon CAS helicopter on Kokan Alt.

It's one of those few grey area assets that have characteristics of both. As you mentioned, it's a Trans bird according to game files ( I believe it has a small crate as well?) but it is called 'Griffon CAS'.

90% of players I know including =VG= have agreed that Griffon CAS is a CAS helicopter. There's no 100% set-in-stone reason other than 'it just works well that way'. Similar to how French VABs are considered humvee-type assets despite having more seats and the ability to request kits from them.

Kokan Alt benefits more from 1 trans Chinook and 1 CAS bird with guns in the sky than it would from 2 transport helicopters. That's a large part of the reasoning behind this.

21 minutes ago, =VG= Kavelenko said:

A more telling statistic would be the type of weapon used to TK and the distance.

Disregard CAS chopper kills, too many idiots standing next to armor.

@=VG= Kavelenko If I remember correctly your favourite was bouncing nades, with about 30-odd self deaths from your own frag

11 minutes ago, =VG= SemlerPDX said:

This list would benefit from some aggregation, some time played metrics, etc.

Hit me up and I'll gladly compile a list

Have you been naughty or nice in the land of PR:COOP? Santa sees everything! If you ever thought about how quickly those teamkills rack up in a year, wonder no more. Find your name and  in the list below. If your name is not on here, tag me in a comment and I'll look you up.

Shoutout to @SSgt. HaterOneActualfor coming up with this idea!

KEY NOTES:

- Playtime per person varies greatly, and not everyone was here for the entire year. Remember this when comparing yourself to others .

- PR teamkill logs can be finnicky, so these numbers are accurate with about 5% deviation.

- This is the number of TKs between 01/01/2019 00:40 and 12/31/2019 23:45

Takeaway: This seemed like a fun idea but note that this is no celebration. Accidents will always happen, but let's at least halve these numbers in 2020, shall we . Shoot hoes, not bros.

#teamkillawarenessmonth

=== TEAMKILLS PER PLAYER===

.SUGAR. 425
2EZ 115
2Polev 13
43rd DannielsCz 264
45th Golden_Days 733
=AMPHETAMINE= 75
=VG= Bejaki 5
=Ro= .Blizzard. 129
=VG= 0100011000101 257
=VG= 22..12 153
=VG= Acro1 110
=VG= Asquirrel 80
=VG= BinkleDinkle 77
=VG= Deathdealer 434
=VG= Fastj@ck 40
=VG= Kavelenko 161
=VG= Keed 169
=VG= M823us 17
=VG= Melon_Muncher 15
=VG= Orracis 18
=VG= Rotblut 18
=VG= Ryan.TT 144
=VG= Sausag3 23
=VG= SemlerPDX 11
=VG= Skitalez 309
=VG= STARK58 201
=VG= Vanillapop 34
=ZF= Honeybadger101 153
Agenteta 55
Alucardednoc 421
Avaga 214
BLYAT Meaww 304
Banditbhbf 28
Batmeme 88
Beachdog[PL] 55
Bugti47 189
CNJ CodeNameJonathan 31
Carkidd 83
Chickenjason123 24
Condrad 290
CptHawk 120
Crustysock 65
Dagger61 25
Daniel75 295
DarkCeltic 33
Dr._Phil_Perlmutter 23
Eurostep 129
FPSGeraud 40
Fiester 53
FinWeirdo 289
Fishsticks 112
G0nz0 36
Ger-man 178
Grizzly.Wilson 58
HTCY Kuro212 126
Hellcruizer 322
Hoops-320 46
Hsc20 227
InchPincher 57
J4SON 203
JCLA3114 11
Jarvin 31
JohnnyTightLips 69
Johnny__Rico 127
Karamara 178
Kemerovo 440
Kiddcar 74
Knifer 4
Legionnaire93 31
Lon-Nolan 114
Lonewolf-PR 161
Lowkey95 316
Magnum-{FR}- 90
MixedArsenal 110
Necrodude 75
Nexwizz 271
PFC. Blackburn 124
PWNED-Life 5
PaloAlto 51
PissBlitz 4
Ranger>>>12<<< 329
Rev Cyanide_CN 24
Risiko94 32
RizlaQc 131
Rokk 37
SSgt HaterOneActual 143
Saharian 79
Sgt. Dragon 157
Skirmisher 195
SoftBullet 14
Spartanish 148
SpessNL 32
Spoden 112
Stainburger 190
Stormtruppen 41
TABARNAC 412
TBF deadxangelqc 25
TRYbol 34
TimeTooTock 74
UA Evgneniy 371
Vipy TSMNF-Viper 64
Volod.41 1473
Warghost 164
Whiskey-Mike 305
Wolfsschanze 37
X0R 250
Xenalite 396
Z.Silva 95
Zviking 122

Thanks for the amazing work you keep up here, have a fiver on me!

Thanks for the effort lads The entire team had fun working together in what must be some of the best cooperative matches of the past months. I've got some bloopers on tape and Ramiel was an incredibly fun duck hunt! Can't wait for the next one.

A few notes for next time perhaps:

- Remember the roadblock bug

- NEVER let Hellcruizer drive anything motorized again.

Shoutout to the volunteers and the good work of everyone involved. The whole team had an amazing time!

12 minutes ago, Kuro2712 said:

Alright, thank you for the quick answer. Seeing the standard server suddenly crashing and seeing the event server still locked made me worried for a moment. 

Server password is

vip

all lowercase!

2 minutes ago, Kuro2712 said:

It's already the time and the server is still locked, can only specific people join?

Setting up some final details, we'll get there shortly ;)! Thanks for your patience!

The map bug research file is now view-only to the public. Those who want to contribute, DM me your gmail address or test data to be submitted.

Click here to view the research file.

Semler has the spreadsheet, I backed it up and released it as editable by all, for now. We'll limit the access to those who have any business with it. They're all devs or administrators so I trust they know how to handle data, and if something goes sideways we'll just roll-back the data.

I don't think iFrames are worth the hassle here.. It's taken Semler and me some back-and-forth tweaking to get the PR admin time schedule to fit, and the research file is way bigger and has many separate datasheets for map testing, hypotheses etc.

 I think it's better to keep a URL to the file in a sticky post, and I'll limit writing access to those who need it. Devs and testers who want to join the bug hunt can DM me their gmail address and gain access.

Welcome back to the team @MOKUM! Hope you enjoy the campaign as much as ever.

Do fix your TeamSpeak push-to-talk though, please. I was on the verge of reporting you as a troll when your music was blasting incessantly in the Welcome channel .

You know I could have helped you if you didn't ghost me on PM , right ?

Did you end up going for the rod or the claw idea?

EVEN MORE SAAAAAALT??!?

The guy really doesn't care much about life, does he .

In my testing at JTG:

Bijar Canyons STD, flying IDF:

Could go oob east, west, south, any combo. No crash. Tried in jets and helos.

Khamisiyah STD, flying US:

Could go oob east-west, no crash.

East/west oob and then south while still oob: no crash.

Flying south oob first: crash.

I've never seen the server files, but this sounds like perhaps the OOB mechanic checks if a player is oob already before executing the rest of its code, to avoid running the script multiple times.

Again, I have no access to those server files yet so I'm purely hypothesizing based on my coding knowledge.

@=VG= ciro Do we run Procdump or Procdump64? Both come in the download you specified.

Lads, can we please take a chill pill nobody is doing statement vs statement, no personal attachment is involved. This is a thinking pool, not a debate. Let's focus on the essence and not jump on our horses if someone disagrees. We strive for the same goal . There will be enough to read through as is.

12 hours ago, =VG= ciro said:

https://gaming.stackexchange.com/questions/358024/project-reality-bf2-flying-south-out-of-bounds-crashes-the-coop-server-whats

 

Nice one fella!

Thanks Though I don't think many answers will come, I'm keeping tabs on that page. Never know if something good comes out of it!

@=VG= SemlerPDX Does Realitymod provide you with the necessary files once you become a contributor? I'm submitting an R-CON application somewhere today.

30 minutes ago, 0100011000101 said:

This morning at work, I've tried something ...
even if that is a bit of a dickmove, I tried to crash empty (!) servers. Unfortunately, I did not find an empty deployment server that had air-assets, otherwise I would have tried it as well. When I create a local game, whether deployment or coop, the server stays alive. but in coop I could crash blackhound and jtg when I flew in the south of the map but doubles PRTA server does not crash! I flew there on operation archer 2 times in the south and only died, the server remained stable.
is this map dependent or does prta have a solution to the problem?

Funnily enough, I tried doing the same thing on our own server since it was empty this morning. Driving and flying south in Khamisiyah STD caused no crash with either helo, jet or humvee. I tried local games too and had no crash either.

6 hours ago, =VG= SemlerPDX said:

The server was even freshly installed and given a week without any serious VG modifications to any configs aside from PR Admin assignments and the maps to make it COOP.  When the server demonstrated the "fly south bug" crash more than once (on more than one map), we were fairly certain the bug resides in the game.  Melon has personally poured through pages of code chasing any lead as far as it would go, to no success.

Is there a way to publicize the respective files so we can have a look at them?

2 hours ago, Xenalite said:

Can we resign people from CAS if we know that they are notorious for flying south and crashing? It's probably a worse disruption to the server than people TKing in main.

While this could fix an acute situation, I do think resigning people 'before the crime' is  a situation we best try to avoid. How many incidents before someone is 'notorious' ? It will take several days before every admin knows that player X is a southflyer, and several days again if we decide to give them a second chance at flying. Half of the admins will resign them on sight, half won't. This will cause a lot of confusion and create an unfair feeling towards many pilots. Even the best of our aviators hit that southern edge once in a while, and when this goes unpunished it widens the unfairness gap. The people who are notorious south-crashers are usually also disruptive in other ways (stealing, bad communicative behaviour,...) and are already being dealt with. Unfortunately, the only fair and effective solution to this problem, IMO, is fixing the bug.

Many new pilots join every day, with decent flying skills, that end up flying out of bounds because they didn't know of this issue. We must continue our efforts to make those players aware so it doesn't happen again. Most of them have good intentions, so we must give them that chance.

I fully understand your idea though and in theory it looks great! Unfortunately though, these are still human players, and humans have their flaws.