=VG= SemlerPDX

Also highly recommend APEX to anyone who reads this... A3 without APEX is just an A3 program waiting for you to eventually purchase APEX

It's nearly a non-issue. All things stated for factual reasons about facts. You'll never run into a static issue cleaning - just don't blow the thing apart or suck up something important!

PRO TIP: Don't suck -- blow! https://www.amazon.com/Compucleaner-Durable-Plastic-Electric-Pressure/dp/B07RKYWBD2 Regarding what was said above, all points thoroughly made, the takeaway should be that static can be a concern regardless of suck or blow, canned or vacuum pressure. Yet, until there is a better way to remove dust buildup from impossible to reach areas, there is greater risk by not cleaning. It is the lesser of two evils. I had my own in-home PC Fix-it business called "PC Field Medics" for a number of years, I was my own "Geek Squad" of 1, and cleaning the computer was the first ten minutes of any 1-hour reset job. I used to roll with disk images of current Windows installs, would offload their data, flash their HDD with the image, replace their drivers, programs and data, and get out in less than an hour in most situations. Even carried a case with so many types of RAM, so I could "boost" most any system while I worked on it. I had NEVER had any issue with static damage due to cleaning hundreds of computers out in the real world. That being said, a few simple SOP's can ensure you don't "blow it" by increasing potential for damage: First, turn off your computer. Do not unplug it, but turn off the switch on the PSU (power supply). This will not disconnect the ground your computer and case have established already. Next, ground yourself and try to remain grounded during the procedure as you hold the plastic cleaning device (of any kind). This is achieved simply by touching the metal case anywhere as you move it while blowing/sucking. Next, tape down all case fans using masking tape or any tape which leaves no residue behind and is easily removed yet strong enough for the task of taping down the case fans. This is to ensure that during any sucking/blowing, they do not spin up and explode due to overspeed. You may want to wipe the areas you are about to tape if they are dusty themselves. Curl over the end of the tape on itself to give an easy handle for removal when done. Finally, NEVER touch the tip of the cleaning device to any computer component during the sucking/blowing process. This can ensure the only potential for static buildup is from the movement of air itself - and on that note, don't hold it in one position for a long period of time, motions should be swift and the entire process brief. Dry air = more potential for static -- observe higher caution in those situations. If you must brush a component, ground yourself and then touch the part to ground it to you while you brush it. Touch your brush tool to pull static from it, moisture from your hand or breath can help dissipate and discharge buildup for these very brief maneuvers. If you were so overly concerned with such things before powering back up, providing a break after your task, perhaps grabbing lunch for a couple hours is likely enough time for most any *minor* static buildup anywhere to naturally discharge by at least half. When numbers are already very tiny and quite possibly within tolerance margins for these parts or components in question, this becomes more and more of a non-factor. Again, IT pros clean, PC users everywhere clean, and our parts are not popping off like 7.62mm rounds tossed in a fire... All we can do is minimize the potential for damage and definitely avoid things that very much will cause damage such as sucking/blowing case fans past their rated tolerance levels for overspeed causing them to explode and shoot plastic into the computer potentially damaging other components. *edit: obviously, the mention of compressed air in the post(s) above referring to "Canned" air for cleaning computers, which has a component to minimize moisture when discharged as directed, in bursts - compressed air from a compressor like those used to fill car tires or power tools is a big no no for blowing out computers due to the unchecked moisture and difficult to regulate air velocity.

It is a limitation of the game which forces us to make such rules. There can only be so many squads, and we have discussed this one to death (perhaps not publicly) with regards to locked dedicated logistics squads and/or those with 2 squad members only. You'll have to forgive the blunt "no" - it is as gentle as one could hope, given that we have been over this before and our hands are tied by both our goals and intentions for our COOP Server as well as the game engine itself (as mentioned, only so many squads can be made, and since player count is dynamic, we won't allow special rules when lower population because if/when it increases to higher population, it would be an imposition to then tell certain squads they must disband to allow for others to be created - and that's just one example of this can of worms getting spilled out everywhere). Thank you for understanding.

Somehow missed this reply until just now... That's very awesome, man!! Well done! From the outside, some of this stuff seems very hard to get into, but literally just diving in and playing around with the bits and some tutorials / videos is the best way! (Stuff is cheap as hell, too - if something fried, it's like losing a lunch, not a monthly rent payment like our computer parts )

(very awesome graphic, man! )

Event Viewer will have logs of what happened most likely, again, that's where to look. Also, not sure how you are monitoring, but you should be actively logging - HWMonitor from CPUID tools has this option - so you can view what occurred even if you have to restart or were not watching it actively. Actively watching it would only tell you "that" it went black, which could be useless except for noting the time so you can cross-reference this with your HWMon logs and Windows Event Viewer events.

lol - no worries! It's all brand new and we're still working out all the promo info to make sure everything is clear. That's on me, and I have much work to do. Basic rundown: VG Army (and VG Air Force) are open public clubs that anyone can freely join. Known members or those who post up a short into to let us know who they are are given the "Member - Enlisted" group, functionally not much different that standard "Member" group, but first step to further membership roles. This one section of the VG Wiki on the topic spells it out nicely: https://veterans-gaming.com/wiki/information/vgclan/advancement/#Member Groups (just don't worry about the applications at this time)

Not to take this off topic, but there are errors and events logged, you just need to know where to look. These would then be used to determine if it was an operating system issue or a hardware issue such as power delivery. That's where I'd start, for sure. If left scratching my head, I'd do stress testing and monitor thermals to be sure it's not related to that - I could get that behavior from a multicore CPU by improperly attaching a cooling device, where everything would be fine unless the CPU ramped up usage for extended periods which would lead to throttling and eventually a hard crash/shutdown to protect the chip. Keywords to google on this would be 'Find crash in Windows Event Viewer' and/or 'CPU-Z stress test' and/or 'memtest memory testing'. If the Event Viewer research shows an OS or driver related cause for these shutdowns, you should consider running some windows tools to check out your OS:

Well, let me know. No one is actively using the VG Event Server daily and you could have a better learning environment (even if just joining the server yourself to see if something works, then shutting it down again and tinkering with code and navmesh). Sometimes the final things like running a mission/game in a dedicated environment vs a local environment can present their own set of challenges, and we're happy to provide the tools for you to finalize your work and learn the end parts of map/mission building. Of course, if any of our team had a PR Event to host, we'd have to put your work in a side folder for a Saturday (and possibly a few days in the week prior for that event mission testing) but as I said, activity on that server is not 24/7 so you could make use of it the rest of the time to tinker and learn. Also, @LangMaster join the VG Army already, geez! You look naked without Enlisted tags, you've been a friendly regular here for a very long time and we'd love it if you started down the path towards membership groups, even if you didn't want to be part of the VG Clan we still like that we can recognize our long time trusted regulars with the Officers Group membership role, and joining the VG Army (and the Enlisted Group) is the first step towards that.

If or whenever you are ready, I'd be happy to give you access to the VG PR COOP Event Server for you to run your tests. You'd upload missions through TCAdmin web browser based control panel which provides access to the levels folder, and then you'd adjust the maplist.con as needed yourself cuz I'm a lazy fuck and not gonna do your work for you lol. Server would be behind a password, of course, and we'd ask that you run tests which have time/duration announced here on the website (can't leave it online 24/7). *Tests don't need to be announced with a full week or two advance notice as we recommend for standard gaming events, you can literally just use this thread or the chatbox on the front page to announce a new test period anytime, even multiple times in one day for more than one test. Let me know! We're all behind you!

What?! No trolling the players! Seriously though, if you don't mind my constructive criticism, random IED's in video games are often invisible or damn near and can be detrimental to playability if not used with caution by the game designer - unless you want players to drive at 5MPH everywhere. A2 INS SOAR never had them. There is a reason MRAP's exist and realistically one might assume that whatever army BLUFOR is part of would send stealth helicopters to an MHQ would also provide IED survivable MRAP-style vehicles when IED's are a known threat in an AO.

True TBF he never takes soldiers away from the front, he never leads an asset squad just to drive a tank and "to hell with the other squad members", and he plays for the team. We enforce communication, and we can deal with any problems if they arise on a case by case basis like we always do.

@=VG= .Blizzard. This is nothing new! You are where I was about 8 years ago - it happens to members who spend so many thousands of hours playing. When chasing the dragon of that perfect match where everyone is working together, new players or those who don't cooperate so intuitively become a frustrating hinderance, like a mental block that makes one question how they ever tolerated unskilled or new players in the past. It doesn't mean you are a bad person for not being welcoming to new players, or too impatient to lift up and train the endless waves of newcomers month after month, year after year. It's rather some kind of feeling we all get at times where we just want the endless training of others to end at some point so we can rest assured that everyone will know how to play as expected, that the game will be so finished that no new systems or bugs need to be worked out and that changes are no longer needed, when in reality it is a journey not a destination. Just remember: PR COOP is a 'doorway' at VG, but COOP gaming at its finest is the actual 'building' of VG and it has many rooms - from Arma mil-sim to BMS flight-sim and all the survival and FPS and strategy games we also play with the friends we make over time here at VG. Small crews of good friends form, play the ever-living-hell out of a particular game, and (hopefully) remain here as friends and playing other games together when bored of what is commonly most everyone's "first game" here at VG. No worries, no need to be overly critical of those things we move on from ... managers are well aware of areas they are working on ... but it's true that after a time, players gain the optics to see things for what they are, the magic dispelled and looking up the sleeves to see all the hidden cards there. Ignorance is bliss, but it fades. Even within a single year, the types of players change with different influxes from one country or another, and in a sea of FTP modern PC games it is amazing that PR holds the player base it does and still hooking new players as old ones move on. Don't spoil the magic too much for the new guys, let them have their fun as much as possible. The battle to wrangle the players into the COOP style of communication and teamwork is an ongoing one, a battle some of your peers are still fighting here on the VG PR COOP server and requiring all the support we can give them (even if only moral). We all keep trying to fix or improve the negatives that may appear in time through updates or patches, something that new players have patience for, but understandably our seasoned vets may become increasingly despondent and just eventually move onto other games. Fortunately, this is exactly why we don't ONLY run Project Reality COOP at VG, having the larger goal of creating a military PC gaming themed home online for cool people around the world and not tied to the lifespan of just one PC game. We can bring the COOP style of gaming we enjoy so much into any game we play and it makes it 1000% better every time.

Just a reminder to new VG Army members - we typically assume most members play PR COOP, but if we all don't know you from the games as a long time regular, please post up to say Hello and let us know what you play here! We just started this new membership path, and it seems the best route so that we don't accidentally award Enlisted group/ribbon to a semi-automatic bot preparing to fire off spam rounds in the club forums. We are glad to have you all - a simple reply from standard website members including what you like to play here will be rewarded with the entry level Enlisted website group!

Whatever you can do is awesome! Keep up the great work man!

Okay - slow your roll cowboy. You just jumped to 1000% during a mere discussion about the rules, drawing some line in the sand as if we asked you to spend your time joining each and every squad to be sure they have a mic, and if not, resign them. NO ONE SAID THAT! You are good people, we all know that. Be good Admins and make sure that our server is not disrupted by squads with no real leader. There are OBVIOUSLY exceptions, as BLuDKLoT mentioned, "...when the server is slow then we tend to be more lenient about certain rules but as a standard for a full server this shouldn't be the case." As an Admin here, you must be aware of these nuanced exceptions, and when NOT to go gung-ho on every single perceived rule violation like a man on a mission. Take time to evaluate what is required, how the entire server is running, how many players and how many squads, who is doing what and whether it is detracting from or adhering to the spirit as well as the letter of our rules. There are a finite number of squads that can be created in any given match. The rule is very clear that if no-Mic (non communicative) Squad Leaders are taking soldiers away from the front, are absorbing too many players with mics that can and should benefit from a properly lead squad, THEN you should evaluate the situation, and if it is detracting from the goals and intent of our cooperation, teamwork, and coordination based gameplay, then they should be resigned. If some single rando no-mic SL is running around the front lines with a couple squad members, and then the rest of the server is filled with proper Squads being lead by SL's with mics or communicating properly, then who cares about that single rando SL and his no-mic squad .... but if we have a deficit of players due to those players being part of multiple no-mic SL Squads, it would be wise to enforce this rule to get the server back to how it was designed to run: A handful of regular players (with mics) leading Squads of various types for players with (or without) mics to join.

I'm not sure that follow would work for edits, that is typically for things like comments or reviews, and VG Wiki database doesn't have those things. And YES - if people were getting notifications for every edit, it would be MADDENING. That's not exactly what the VG Wiki is for - would be better to make any kind of announcement post to redirect attention to a new rule, as we've done in the past with the changes to the 'No Smoke' rule (now that bots cannot see through certain smoke) Thanks @=VG= Acro1 for taking care of that update.

Fixed

Players are jacking the MHQ and moving the spawn point when they should not? My very first proper script for Arma (2) was for this exact thing. I added some stiff restrictions for being able to move it. Might need to do something like that for the MHQ in this mission...

Are we all talking about the same thing here? How is this new GUI hurting your ability to fly between buildings, an action that is performed with the GUI closed and hidden? I was under the impression that we were discussing the elements on the GUI not being stretched to the wide-sides anymore, and also the mini-map not being transparent when brought up to view, and the fake DoF effect of blurred perimeter when ADS or using a rifle scope. I just don't see where that is related to flying and sense of scale in 3D... apologies if I've missed something.