=VG= 0100011000101

try to create an offline accout and see if it works with it. do you have multiple sound or graphics cards? have you ever been able to play pr on this computer? do you start the game in admin mode? firewall and antivirus software you could also switch to off and try if it works. but turn back on afterwards !!! in the launcher there are options to delete the cache and all other settings, which you could also try.

Negativ. its only in our hands i think. I do not think that it really interests someone at deployment (but cant blame anyone for it)... it seems there are not too big problems with the bug, otherwise you would read something in the forum. and JTG has mostly 0-2 players ...nobody cares. we should continue to analyze his behavior and try to find a way to neutralize or move around him. there is different behavour! local crashes a lot less than online. deployment apparently too. maybe we should play a few more rounds bf2 again ... etc. So it can really be that we can never do anything about it, but it can also be that Kavelenko tomorrow by accident finds out that they do not crash if something else cross the border in the south before or whatever...

lol. then lets try out if a tank can crash the server if he got "wings"^^

I would also see it that way, but then the server would not crashing immediately at the first map. after a restart the cache should be empty..., if you play kashan std then, the probability is very high that the server crashed. I think that we can never fix this bug. BUT: because the server not always crashes we might find a way to limit it, defuse it or even bypass it ... I now assume that this error also occurs in deployment but there very rarely happens because not so many newbies have the opportunity to immediately jump into a jet. but if I start three times kashan std on an online server then i have an average of 2 crashs but once i can fly in the south ... why? what is different? why is the error local much less common than online? If you can answer these questions, then maybe you can develop a strategy on how to avoid it. the only thing I can imagine right now is that it has something to do with the memory management. When I play pr on a computer with 16GB I get the memory.dll error much later than when I play pr with a 4gb computer. and these times are always similarly long. So if I open a sever local I use 16gb ... but if the vg-server but only has 4gb then this could be the reason why the error occurs more often. i have the hope that it is a stupid combination of several events. So something like that just someone in the north also flies out of the map or similar ... I would also try the days if there are maps that are uncrashable or if all maps crash. another thing that I still want to try: try to crash kashan 3-5 times and then compare the individual trackers of the games ... so where are the enemies, what kits were used , where are the individual units, in what condition are they ... maybe you can find out something. or we play muttrah 24/7 ... that rarely crashes ;p Of course it would be really cool if we could do that for a few days / weeks. So not only for me, but for handful of players who want to test things and dont have the possibility. the bug is so rare on local that it's hard to test there...

@WarGhost: https://drive.google.com/file/d/1oIXSVcuP6ImOExBwknpYM2mb6bzbSrn1/view?usp=sharing the 1st armored division of the mec Air Force in action ;p can not we just replace all the jets and choppers and fly only with vehicles? then there are enough crashes but not of the server

but pls dont close this thread. if there are still ideas, observations or attempts it makes sense to leave this discussion open ... In any case many thanks to all who helped and to melon for finding this bug. maybe we should set up volod on the bug and he just kills this fu**ing noob ;p

^^ no. i cant delete it or edit the size. pls try it for yourself...sorry.

if you have NO write permission, it might be useful, so that all your ideas can be included but only certain people can edit. but I really thought flying ^ ^ if you are on the edge and use "!fly name 1000" then you fly quite a long time ... and if you then turn the cannon of the tank you can change his direction a bit ... On a local-server it works, but unfortunately I have not enough rights to use !fly on our server. that would have to do a headadmin or we set up a testserver where you have more rights. look at your mails... I think that everything is unchanged. probably the only thing that has been adapted is the kit-restriction. but the server-admins can say that more precisely. I can try it, but I think there you can not do any map-votes and then it will be hard ...

only air-assets are crashing the server. I could not crash with jeeps and tanks. at airassets it does not matter what you take. tranport (chennok and chopper), attack helos and jets are crashing. but most of the time I tried transporthelos. The server crashed at mountains just like when it's flat. I even crossed the border on foot and there were no crashes. it think it has something to do with air assets itself. So vehicles of all kinds, on foot or parachute jumps could not cause crashes. what you could try if the server crashed when a tank flies. but !fly works only upways ... let's see if you can fly a tank to the edge ^ ^ These tests have been done so far but I could not find any patterns in it: list below.

what do you mean by that? with cap mark you mean the flag itself? at kashan and jabal, the most southern flags are blufor. and there the server crashed no matter if we took flags or not.

more SALT! ...and even more SALT!^^

Thats all;) 2,3 MB

it didnt crash...there are working on the update i think.

if you go to deployment-->create local, you can join this server with another computer in your network. but i have tried it 3 times now and it wont crash...

Great job binary, so if i'm not mistaking, we can do the test on local server ? That would be great. im not sure...i tried it again today and the local server wobt crash anymore... it is about 1:35 or so ... If this happened to me again I would say yes, otherwise it might have been another PR bug. ^^

During testing in the last few days I had the feeling that the server did not crash at all once you have successfully flown over the south edge. So once I was over it, I could fly with all the jets and choppers over the southern edge again at any time and nothing happened. I tested this way: mainly, I flew along the border of the map in all directions with two different choppers or jets, and then in the south ... because the other edges do not crash and the crash itself does not matter if I flew over another one before, I would stop this because it saves a lot of time. and I have more and more the feeling that it is map dependent, but it does not always crash ... there are some maps thats crashes more often, but there is no real pattern. So far, I think all crashs are on STD maps. at least according to the listing... I have tried to crash local server. that was very strange. right at the first attempt (kashan std) there was a south crash. after that I tried it at least 30 times, but did not crash it anymore. there was still one crash when loading map but not a south crash. I still wonder, what is different in the south than in the west, for example? Something must be different there, otherwise it would not happen ^ ^ I also tested two maps on blackhound DEPLOYMENT but there were no crashs. I did not find any STD map there but mostly AAS (and AA INF). it will be hard to test this in deployment. @ head-admins: is it possible to clone the vg coop-server and lock it with a password? so that we can study the crash at vg? ^^otherwise I will banned soon at JTG and with admin commands and possibly even rcon-commands you can try more and you are more efficient. if that's possible, would it be possible to change it to a deployment server for a short period of time? so we can try out if its a coop or pr-wide bug?

i dont know^^

I joined pr somewhere feb 2017 and I do not know it without crashing. but that was not nearly as much as it is today. but we also had more maps ...

on the JTG server you can do a map vote... if you are alone on the server you automatically win the vote... so you can switch between two maps and try again and again. that would be really good. if that works, you could also enable mapvote and assign a password ... so others can test it. alternatively you could perhaps only on this server give individual people admin rights so that they can try out.

ok, me again...thats why i wrote that before^^: does the bug really happen only in the south? on which servers? coop and deployment or just coop? do the server configurations differ? what else is the difference? eg 32 / 64bit, teamswitch on / off, anything ... which logs can we see? also over a longer period of time? to see for example which maps before that ran, when the server was restarted, which team was played, which commands were used, are there other game mechanisms that can crash the server? What is different in the south? on code-side, on the map, in the circumstances, ... Sometimes the server crashes immediately at the border of the map and sometimes you can fly further ... why? is it possible to set up a sevrer to provoke crashes and to try things out or is that associated with a lot of work? if so, how easy is it to test all allowed settings? I have the impression that it has become more recently. why is that? what changes were there? why do some servers not crash or rarely and others often or always crash? is it better after a restart? for how long? what makes it vulnerable? if deployment is not crashing, why? what are the differences in map, config, etc ... are the bots to blame? Why? what happens when you turn a map around? is it really not possible to generate the bug locally? is the earth really flat? ^^ what existing information is still available? Where? I would ask more of such questions ... and there are many sub-questions. and probably everyone has many other questions to contribute. please move this into the new thread;)...

since this bug seems to be very hard to identify, maybe it makes sense to moderate the discusion a bit. So it would be nice if we do not let trivia, unconfirmed, contestable have entrance into this search. perhaps a diskusionsthread and one where we carry the knowledge together? I have the feeling that pr here and in the other communities has the problem "old against new" (at vg not in a hard way). The veterans know everything and the newbies have no idea. On the other hand, the newbies thinks then the old gentlemen are caught in their game system and invotaions are categorically rejected ... short story long: I think we have to tackle this down on several levels on a very professional way and should include everything possible. We should try to approach it from the programming side ( if you can. ) as well as from the playful side and from the theoretical side (making/collecting logs). if you can not find it in config files or anywhere else we can try to find it by using logical exclusions. and everyone who plays a lot can do this... even if we do not find it, we may find a way to avoid it or move around it. I think that's really important because it takes 90% of the game fun and population and gets worse and worse. And that reduces the quality of the server very much. but if we discus it exactly as in the thread before, then because of the length many things get lost and in a time no one knows what was on page 2... but both, narrowing down and sharing knowledge are important. I think it would be nice if we could do at least 2 threats. one strictly modierte where no discussion is allowed. You can post logs-fils and listings there. confirmations at best with source, refutations, officials, etc. and a thread in which one can ask questions, discuss and sometimes become offtopic and evaluate. Of course, all other suggestions are also welcome. I'm just scared that we will never find this bug if we continue to do so as we started it. including me. but it is also important to continue to exchange as we did before. does that still make sense? ^^ sorry for highjacking again...you can delete this post. I just wanted to say that before you creating a new thread.

Now I feel with you ^^ I do not take that personally and I do not feel attacked and did not want to attack fastjack personally. but it does not help if we always talk about "possibly", "maybe", "I heard". and since this misinformation paralyzes very much and it is not helpful to speculate in this case but facts have to be researched, it was important for me to put it right. broken, at the end and totally frustrated, I now go kill some bots. let's see ... maybe I'll do it like the birds and fly in the south

sure. every time I say that it is not only vg concerns, someone says that it seems so only a vg problem or it is not clear. and that is really silly now, especially since I called the server on which it is provociable and have given instructions how to prove it quickly. but instead of convincing, it is better to question it. I do not suppose it's personal either, but if you're completely overheard, you'll be LOUD !!!!! ;p but i am chill...^^ you are welcome: https://drive.google.com/file/d/1bvnRK_T5y_Ksnehx2OovlchK_bbD9F-r/view?usp=sharing in the first 5 seconds you can see on which server it is. if the server crashed nvidia unfortunately stops recording. but you can still see the "connection problem" and no it was not my connection ... the server is crashed. edit: If anyone has a youtube account he is free to reupload it. Unfortunately, google probably does not get an instant view ... or I'm too stupid for that.

the next one who writes something like this gets a reallife-tk! ;p go to the JTG server. run kashan. fly south ... and your question is answered. I dont lie. it did not happen once, but EVERY TIME! again for all: the flying-south-bug IS A COOP PROBLEM. NOT ONLY VG IS AFFECTED BUT AT LEAST TWO OTHER SERVER !!!!!! then he is lying or he has not tried enough server or JTG has changed something after his statement. Of course it can also be that I hallucinate. since it is now statement against statement: try it yourself. try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself.try it yourself. form your own opinion or we will not get any further here. but theoretically debating whether it is so or not makes no sense ... try and share experience!