=VG= SemlerPDX

Since you have a means to fix it, try to reproduce it. I doubt highly that getting into a Bot vehicle in game in and of itself could corrupt game files, they don't have some sort of anti-cheat system governing such things and activities in a match, and a game runs in frames, not exactly linked to however you launched the game (which included the selection of a user account and it's files in a separate location from the game).

↑ Highly recommended https://www.realitymod.com/forum/forumdisplay.php?f=26

muttrah alt -- this is the 32 layer? Is this confirmed to crash upon load? This is important to confirm ASAP as this is a "Starter Map" and will always be one of the choices for the first map following a restart or crash!

citation needed

Added the FIRST rule that appears on the screen to read, "DO NOT USE the vehicles clearly intended for Bots. They will be patched out later - Admins will warn/kick players using Bot Assets" Feedback, revisions welcome. Please also talk to players, warn them, give them a chance to return safely - if they do not comply, we must enforce this rule. Try not to ban for it, if possible, shouldn't be necessary - just make sure they comply. I'll add it to the Rule here on the website as an addendum -- we normally don't have these vehicles available for players, so this rule will cover times such as this when they are available and we need to enforce this.

Yea, I had to bite the bullet and buy another TrackIR TrackClip Pro for $40 -- after that, I treated it like it was made of glass... I take it off and keep it in a box when not in use. Made it wireless so it's easier to use now, but still I keep it in a box and risk breaking it anytime I use it (say a fly buzzes my head, only a matter of time before I snap this little POS in two again). Wish they made it out of the same plastic polymer that my Glock 17 is made from, seriously, I'd pay $80 for something like this if I only knew I could drop it off a roof and still be able to use it for years. I gotta get all my shit set up again, re-read the graphics setup on the BMS forums, great pics of the different settings screens, etc: https://www.benchmarksims.org/forum/showthread.php?29750-Good-Quality-and-Good-Performance-Guide-NVIDIA&highlight=nvidia The most annoying thing is trying to get the damn ministick on the X52 Pro to work... but I think the problem we had before was I had X52 (non-pro) and I think you got the X52 Pro, right, BLuD? If so, that's why the fix that worked for ME did not work for you back in the day. Now that I have X52 Pro, and if that's what you got, whatever fix I get working will also work for you. Same method for both, just different file format for the profile save, that's all. I got some server work to do this week, and I am culling just a couple features from the upcoming BETA test for my next BMS voice control system just so I can get it out there cuz having that work hanging over my head prevents me from feeling like losing myself in games, other projects, etc. After that, I'm gonna spend a lot more time on our various servers, particularly BMS. I want to get some online SOP's for comms and such that we can make simple guides with pics on the forums here, to help new players dive right in to our casual sim-server.

Really wish we had a tracker of some kind to get this information. I check in on the server randomly throughout the day, and could flip a coin as to when there are people flying - sometimes I recognize the names, other times I don't. I'm a daytime pilot myself, when I fly I like to do it between 11am-4pm Pacific US Time, but if we do get some group flights scheduled, I'll find the time to fit in whenever it is. I know that Kav and STARK have been doing some training flights on Saturdays, as STARK learns the sim.

different name on those forums? didn't see it.... maybe just bump the thread if it got lost in the mix

Honestly, at this point, you really should move this over to the Support forums at the Project Reality Website.... You are far beyond all of the basic things we all would try here, and are into the realm where it might be a good idea for the actual PR Devs to understand what is happening for you. This will in turn be able to help others they come across with issues such as yours, or even other users who read your post (and it's eventual resolution). Please check out the pinned topics near the top, these have information that can help and also help them help you: https://www.realitymod.com/forum/forumdisplay.php?f=27

Yes, we are quite aware of this issue. Many design elements of this type were made by a person who considers COOP "too easy" despite the extremely subjective nature of such opinions, a player who plays COOP "good" by knowing all of the meta information most players don't focus on such as specific parameters of AI Bot behavior and spawning locations, and other factors that essentially remove any sort of mystery or immersion into a game focusing instead upon knowledge of exactly how the OPFOR will advance and behave. There were even votes and polls regarding these hardcore changes to a large body of regular COOP players who frequent this website years ago, and they were voted down and many objections were noted. Despite this, we now find the COOP game mode severely weighted to spite the players, in an extreme hardcore re-envisioning of this game mode that the majority of COOP players had not asked for. Most importantly, these changes were not tested with a large body of COOP players for balance and playablity, which is a massive oversight of their designer, to the detriment of you, the players. I only offer these opinions and criticism with a constructive intent, I hope that in time, the COOP game mode can return to a balanced game that is enjoyable with a few small teams or a large server full of players equally, with map layers that respect these numbers in a more tested and favorable manner for the players who actually play the game as it was intended.

It's great to see you around again, brother! I spend way too much time tinkering with things, gotta re-learn a few games myself. Tried to fly a helicopter in Arma 3 and took me like ten minutes to land safely again on the carrier, and barely made that. This place is really great to get away, and to dive into games or projects - bullshit levels often far lower than the real world, on average.

Backup your user profile information and any other such things - uninstall PR, then reinstall it, launch it and run the update, then retrieve your account from your previous installation inside the Launcher Profiles GUI Sounds like something got messed up. If it happens again, you'd want to delete the base 1.6 installer zip file or whatever you used, and re-download it (potentially from the alternate source from the one you used previously) to be sure it was not a problem with the files. Also, crucial standard practice for Windows 10 users: Whenever you go to install new software, first right click on the installer, select Properties, and check the box next to "Unblock" near the bottom (if it exists) before running the installer/setup file for the given program or application. If a program is from a trusted source (every program you use should be in this category, but PR most certainly is) it may be wise to temporarily disable any third party security software to avoid technical issues during installation. Turn them back on before running the program for the first time, and you should be as safe as can be expected. *when it comes to 'untrusted software', some folks will use Virtual Machines to isolate the program from their operating system for evaluation purposes, just an FYI, but if PR was unsafe, we all would have raised hell by now and no one would install/play their game anymore. more info: https://www.realitymod.com/forum/showthread.php?t=149815

More crash dumps and the latest copy of the python_errors log: PRBF2_w32ded.exe_200506_012936.zip PRBF2_w32ded.exe_200506_014933.zip PRBF2_w32ded.exe_200506_043836.zip PRBF2_w32ded.exe_200506_075833.zip PRBF2_w32ded.exe_200506_085054.zip PRBF2_w32ded.exe_200506_125538.zip PRBF2_w32ded.exe_200506_130535.zip PRBF2_w32ded.exe_200506_151803.zip PRBF2_w32ded.exe_200506_152428.zip PRBF2_w32ded.exe_200507_190115.zip PRBF2_w32ded.exe_200507_205051.zip python_errors_v1.6.0.3-05072020.zip python_errors_v1.6.0.3.zip python_errors_v1.6.0.3-05102020-1307.zip python_errors_v1.6.1.1-archive2.zip python_errors_v1.6.1.1-archive1.zip python_errors_v1.6.1.1-05252020-0930.zip python_errors_v1.6.1.1-05252020-0322.zip python_errors_v1.6.1.1-05272020-0658.zip python_errors_v1.6.1.1-05282020-0537.zip python_errors_v1.6.1.1-05292020-0443.zip python_errors_v1.6.1.2-06012020-0825.zip python_errors_v1.6.1.3-06042020-0426.zip python_errors_v1.6.1.3-06042020-0827.zip python_errors_v1.6.1.3.zip python_errors_v1.6.1.3-06092020-0441.zip python_errors_v1.6.1.3-06132020-0722.zip python_errors_v1.6.1.3-06152020-0508.zip python_errors_v1.6.1.3-06192020-1958.zip python_errors_v1.6.1.3-06202020-1919.zip python_errors_v1.6.1.3-06252020-1805.zip python_errors_v1.6.1.3-06292020-2007.zip

If a thing is worth doing, it's worth doing right. But I hear ya, I don't exactly consciously spend 8 hours staring at a screen and fixing things, I start off thinking I'll be at it for a couple hours, then I'll play some games... but then I look up and it's nearly 9pm. Happens all the time. I wouldn't do this if I didn't enjoy the challenge and the rewards of a job well done, but I do have to pay the piper now and then, it's just my lot and I'm perfectly happy - could be much worse. Before all these titanium screws that pop off metal detectors and earn me stares like I'm hauling a bag of MG's, I needed two hands to drink a cup of coffee. Thousand times better these days, just gotta deal with the after effects if I push myself a bit farther than my body and my age dictate. There is no obvious sign post when passing that border, you just find yourself South of it by a few thousand miles and spend half a day or more trying to get back North. I love the distraction of "having something that needs to be done", trust me!! Just gotta communicate sometimes with the team here so you all understand why I might be Mr. Eager one day, then fucked off or grumpy the next. Cheers!

Did that work? Is that the valid solution we should point others to if they have this issue?

@CraB Server has been restarted to last autosave and is now online. Thank you for your report, and your patience!

If you can just give me time to restart the server, I can get it back online. (no worries, just FYSA) You all joining during my restart process is giving me a real time countdown at the server launch screen (RAMP/TAXI/TAKEOFF) of over 5 minutes. Please be patient and wait for me to post up here that it is back online in just a couple minutes. Thank you.

I've been pushing myself too much lately, I am disabled and stay home everyday for a reason, this being a big one - I'll be fine, all things pass - just need to inform you all that I feel my body crashing, today will need to start with taking care of that, and though I want to get a DEV server for FastJack, get my ProCdumps zipped up and shared with the PR Team, etc, I need to cuddle with some ice packs for awhile and see if I'll be able to do normal things today like moving my head or reaching for a drink of water. I only state this here so you understand why I may be online but unavailable (or not logging into TS3 for the day like normal). This happens when I go for a stretch pushing myself while working on my voice control programs, but then no one gets affected when I have that inevitable crash, as I am having this morning. Thank you all for understanding, but hang onto any pity, I'm perfectly fine and will bounce back as I always do with time and personal care. I'm here, I'll respond to urgent issues when I check my PM's regularly until this passes, but this is my life, and it rolls over into VG sometimes though rarely do we have servers that need this level of day-to-day babysitting. COOP is borked, big time, and while some things were tested, it seems not quite as extensively as we would have all hoped - such as no one thinking to toss a smoke grenade in the water, for example. A simple thing in retrospect, but regardless, here we are today. Please everyone continue to be patient as these things get worked out.

To be candid, I had two problems to fix today: reinstall the server and fix the maplist randomizer. Those were our problems today in the most pressing sense. I have been at it since I woke up, and have just completed the public notifications, etc. regarding both issues being resolved. His tool not functioning was a big issue or we'd have COOP up and Mumble up, but maps running consecutive layers back-to-back in alphabetical order. We are finally as 'up and running' as we can be and that was my major personal goal for today, and they were those kinds of things that I couldn't outsource, either. My next job will be to install a DEV server for our in-house VG Members on the PR Team (passworded, of course) as we always have offered for those who wish to work on PR COOP at VG, so glad it's more than just Melon these days, and happy to provide that workspace! Obviously, our servers aren't the only test ground for these things, but the more the merrier. I'll also get the Event server updated after that, as in lieu of upcoming events (which are on hiatus until COOP is stable again) we can have a very simple "fully default and generic" server that we can fire up and try/test anything that has zero fixes applied or otherwise from the base 1.6 + patch updates file set. We can also use this to refer back or even roll back a server to base files for the time we will be helping to identify issues or even work to improve or fix things through the VG PR DEV server that only VG Members on the PR Team will have access to (aside from the Head Admin team, of course). You're first on my mind, FastJack - I won't leave you hanging long, but yea, I do need me that break if you can be patient for 12 hours tops, might get a second wind here tonite, it's only 8pm for me and damned if I can get to sleep before 3am these days. Cheers, brother!

I've repaired the VG Maplist Randomizer. I have changed the names of these files and the actual script to all have the same prefix. This will keep all required files sorted lexicographically (ascending/descending) in a less visually confusing manner than before. Key notes are to only EVER deal with the "disabled_maps.txt" file (again, will have unique shared prefix) -- and I have set the other files to read only to prevent accidental errors. IF we want to change those maps which could potentially become the 'first' map in a maplist, those are picked from the read only file ending with "_starter_maps.txt" and I would appreciate being the only person to edit that file until further notice. NEVER EDIT the maplist.con file -- this is not how we work at VG, so I know we have a very, very short list and this is an odd place with so many eyes here, but I'll just state that no one will ever edit that file. We will only ever add a disabled map to that appropriate file, and await a new update from the PR Team. So, in conclusion, I found the starter_maps.txt file edited and having too few line entries for the actual randomizer system to function in an appropriate timeframe. It is actually rather complex, and while it runs in a matter of a second or two on my new 24-thread Ryzen Beast, it actually takes more than a couple seconds to run on the VG Dedicated Server powered by an Intel Skylake CPU and driven by SSD storage I/O. Talking up to 20-30 seconds at most, often closer to the 10 seconds or less ballpark, and we're not restricting affinity there, like we do for individual game servers. When it is complete, it writes that information to the maplist.con file in a span that could be measured very in few (or most likely, in fractions of) milliseconds. Moving forward, we will obey the SOP above, and we will make sure VG's Maplist Randomizer is modified by me or someone trained in the slightly (understandably) confusing method for it's operation to remain healthy and dependable. Imma take me a long break now. might even go to the range and blast through a few boxes of TMJ -Sem EDIT: ALSO -- we gotta run with default coop.py configuration settings for awhile so we can get the best possible dump file and python error log information to the folks who are working hard to help fix the PR COOP game mode. It's a pain to have certain issues, so please let us know if there is any one value that absolutely needs to be changed for the game mode to even be playable/enjoyable - we cannot go changing every darn kit assignment value just yet, but we will when it is safe to do it down the road, so please advise me of anything crucial so I can bring it up with the PR Team in consideration of requesting to run with it, or even add it as a good/better default setting for the COOP game mode as a whole. This will not apply to many, many custom config settings we normally enjoy, like all servers with their own flavor and flair, but they'd certainly love to know any good 'defaults' for major ones. Cheers!

I know, right? It's almost like people other than you don't live in Lithuania.... then again, I could be some sort of dark wizard .... ya just never know in this crazy world. (just teasin - gotta have fun with that)

I've updated the server to 1.6.0.2 The ProCdump did create a dump file, but uncertain which map/etc. was running. Will need to use file creation time to gleen the details, cross reference with the demo/tracker files which will show what map was running at what time ( http://veterans-gaming.com/demofiles// ) These files are mirrored at SA forums on RealityMod website (SA License Holders and Moderators only, FYI, link won't work for most of you) https://www.realitymod.com/forum/showthread.php?t=149684 PRBF2_w32ded.exe_200502_045242.zip PRBF2_w32ded.exe_200502_205200.zip PRBF2_w32ded.exe_200502_230200.zip PRBF2_w32ded.exe_200503_035504.zip PRBF2_w32ded.exe_200503_074814.zip PRBF2_w32ded.exe_200503_180833.zip PRBF2_w32ded.exe_200504_010155.zip PRBF2_w32ded.exe_200504_194845.zip PRBF2_w32ded.exe_200504_222351.zip PRBF2_w32ded.exe_200505_000200-001022.zip PRBF2_w32ded.exe_200505_001553-002340.zip PRBF2_w32ded.exe_200505_003019.zip PR v1.6.0.3: PRBF2_w32ded.exe_200505_085727.zip PRBF2_w32ded.exe_200505_094306.zip PRBF2_w32ded.exe_200505_095953.zip PRBF2_w32ded.exe_200505_100216.zip PRBF2_w32ded.exe_200505_103705.zip PRBF2_w32ded.exe_200505_104357.zip PRBF2_w32ded.exe_200505_105026.zip PRBF2_w32ded.exe_200505_111838.zip PRBF2_w32ded.exe_200505_112627.zip PRBF2_w32ded.exe_200505_113101.zip PRBF2_w32ded.exe_200505_122841.zip PRBF2_w32ded.exe_200505_130435.zip PRBF2_w32ded.exe_200505_132708.zip PRBF2_w32ded.exe_200505_135854.zip PRBF2_w32ded.exe_200505_143628.zip PRBF2_w32ded.exe_200505_163236.zip Python Errors v1.6.0.0-v1.6.0.3 (before reinstallation Tuesday): python_errors_v1.6.0.1-v1.6.0.3.zip PRBF2_w32ded.exe_200506_000209.zip PRBF2_w32ded.exe_200506_000822.zip PRBF2_w32ded.exe_200506_012134.zip Python Errors v1.6.0.3 (after reinstallation Tuesday): python_errors_v1.6.0.3.zip

Server updated... mumble tested... all is well. Cheers! (gonna go make my coffee and breakfast now... glad that was a quick one)

Glad someone knows about this... been doing this for ten years, not sure that I've ever heard of this issue with our TS3 before. Cheers, Binary!

I've turned on ProCDump with -mm