• Content count

  • Joined

  • Last visited

Community Reputation

79 Excellent

About Snapjaw

  • Rank
    Only two days away from retirement
  • Birthday 24/06/89

Recent Profile Visitors

283 profile views
  1. If you're really unsure you could just buy it, game for an hour solid and then return it if it is terrible. Or you could just pirate it and pay the developers if you go past the 10 hour marker and still enjoy it.
  2. Every other ARMA community I have been involved with has a formal application, an interview and an extended evaluation period. This is to make sure people actually stick around, can point their gun the right way but most importantly are amusing to play computer games with. FK doesn't have this. Instead, FK offer priority during missions that literally can't hold the players interested in playing. The only requirement for this is to consistently display good attitude in a way that is transparent and recognized by senior members. Why the need for transparency? Because there was a literal uproar over the suspicion that some people received these due to favorbility. Personally I think it would be nice if people could receive it due to word-of-mouth from other players; but that is apparently a minority opinion. Why regular for tags? Because its managable to be dependent on a nice person that doesn't fully know every system. Reversely its a gamebreaker to deal with a douchebag that knows every system inside out.
  3. Personally I use it to mark positions as well. Sure looks a lot better than what I used to do, which was to use items found in a sushi shop.
  4. Added now. Didn't think about it. That was my inspiration. Thought about binding forward to one of the rotor pedals, then figured I might just bind it to a key instead.
  5. As many of you know ARMA doesn't have an inherent auto-move key. This means that if people want to move in a controlled manner (e.g. in formation, head on a swivel) their hand will assume a pretty uncomfortable crab position to reach for the ALT key. Naturally many will forego either the formation or the awareness if the patrol is of any extended length, or moan extensively about it. A similar but less pronounced problem can be felt whilst driving extensively in a slow-moving convoy, as continously straining your index finger whilst relaxing the rest of the hand can feel rather uncomfortable after some time. For those of use without a handy-dandy macro keyboard I attached a simple script. If you're one of those people that dislike running random executables from the net, I provided the source code as well, which you can run if you have AutoHotKey ( ) installed. It binds ctrl+q to auto-run; and the auto-run stops the minute you hit W. As such you don't have to worry about auto-running into a landmine because you couldn't find a way to stop. The rules, BattleEye and Bohemia seem to have no problem with this item. But should it be a problem feel free to delete this thread. In regards to discussion; do you believe this to be useful, pointless or even game breaking? Download AHK from auto-run.ahk
  6. Intro and purpose TrackIR tracks for head movement so that you no longer need to use the ALT key; or in the case of a chopper - your POV hat, to look around. It is however extremely expensive for the rather simple thing it provides; so this is a guide to do it yourself. All in all this DIY probably costed me less than 20$. In other words less than APEX on sale. So I figured it was worth it. This is a very rough guide to everything as it would take me a solid weekend to write down all the details. Depending on time and interest I'll update it with more detailed info regarding how I did it. So lets get started. In order for this to work you're going to need several things: Tracking software to make sense of it all A web camera with IR capabilities An attachment with IR diodes (lamps) Configuring your software Tracking software to make sense of it all Download FaceTrackNoIR ( ) and take it for a spin. You will be using the PointTracker tracker source. You will use this software as you build everything else; to make sure that your camera works and that your circuitry holds. More details about optimally configuring it is found later in the guide. A word about the FaceAPI (aka facetracking with a webcam and nothing else) FaceTrackNoIR is actually a collection of different ways of tracking and conveying the data. One of the things that you might want to test is the Tracker Source > faceAPI. This tracks your head with no fixed points using a regular webcam, but comes with several drawbacks. First off it is ridiculously slow. 30 FPS is the most you will get out of it. Secondly the technique is very unstable. You will end up having to use a massive amount of smoothness (frames to decide where your face is), thus making it even slower. Thirdly it is extremely bad at recognizing anyone with a beard or glasses. If it still is enough for you; that is definitely the easy way out as the procedure described in this guide requires a fair bit of elbow grease Web camera with IR capabilities So this is the first big hurdle and in itself requires three things: A webcamera without a IR blocking lens Some sort of IR pass filter Craftmanship Personally I settled for the PsEYE ( ) webcamera, which is one of the few that is able to achieve 90-120 fps (compared to the standard 30 fps). The downside is that it was meant for playstation and not PC; so I ended up paying a grand 3$ for Windows drivers. I felt like they deserve it; but if you're really strapped for cash you can most likely find a free option. Secondly, the camera had to be dismembered to remove the IR blocking lens. Most cameras has this, as picking up IR from the background wrecks the image. There are a few resources for this, for instance Do note that this makes your webcamera completely useless for everyday use, as the IR-cancelling lens also sets the focus for the image. Finally an IR pass filter had to be attached. This to make sure only IR would be picked up at any decent level. You can achieve this by cutting out a diskette and placing it inside your webcamera. Due to the low quality of such a thing, and the expensive nature of proper IR pass filters; I personally just bought an IR cover lens and attached it ontop of the camera. An attachment with IR diodes (lamps) You will need: A couple of IR leds ( ) A resistor of about 20 ohm A usb cables Either wires, or another usb cable Some office supplies to put it all together If you have wires; great. Otherwise scavange the first usb cable. A usb consists of four cables. What you want is the black and red cables, as they're used to send 5v. The other two are useless. Open up the end of the second usb cable. The red one is the 5V, and the black one is ground. Make a small circuit with your resistor, leds and and the second usb cable. You're aiming for something similar to this Attach the circuit to your office supples in some way. Most likely you'll be attaching your cabling to your office supplies as you go along. Put your attachment together. Attach it to your headset by some means. Personally I used velcro tape ( ) so I can remove it when I don't need it. End Results: Configuring your software Once everything works there is plenty of things to try to get right, but the most important ones are the PointTracker tracker source > Settings > Camera > Point extraction; PointTracker tracker source > Settings > Camera > Model > Model Dimensions; and the Curves. All of these are very dependent on how your attachment ended up looking, how far you are from your screen, and the light conditions of your gaming room. I attached my configuration here. You should likely only need to fiddle with the three items mentioned in the previous paragraph ( armaLoLight.ini ). If you went my route with the PSEye drivers you will end up with something called CL-Eye Test. Options < Video Capture Filter of this software lets you manually set the Gain and Exposure. These two together with the Point Extraction mentioned above really sets how receptive your device is to IR. Naturally you want it to pick up as little as possible (to avoid interference); but if you go too hard FaceTrackNoIR might end up losing track of your device. If you're like me and sometimes have the sun directly behind you, it's a fine balance.
  7. Played it before, could be up for it again; depends mostly on time.
  8. Launch the game with the mods but disconnect from the server and join the VR room. Get a feel for all the stuff. There are metric tons of weapons, uniforms and extras. Play with the stuff you will end up using. e.g. the M136 launcher, the grenades, bandages, radio etc. Save a basic loadout of what you consider acceptable gear Take a look at the vehicles. In particular the russian ones (BMP, BMD, BRDM, BTR an ZSU) since that's mostly what you'll be fighting With ARMA it's ironically those that played for several hundred hours that considered themselves barely passable and those that downloaded the game a week ago that think they're hot shit. Befriend the former and ignore the latter; because no, memorizing the top speed of a Ural going down a 20 degree incline is not a requirement to play.
  9. The layout is such a jumbled mess that I don't even know what I name I am supposed to assign each vic according to the author. But lets go with the most intuitive then, which is top name is top vic. BRDM is a BTR? Never heard it since they're never used, but sure. BTR is a BMP? Literally the last assessment was 'Everyone calls everything with russian plating and wheels a BTR'; in what realm does this take place? BMP is a T-90? Not a "MBT" or "Tank" like literally everyone mis-refer to them as.
  10. Feel free to post your rank as well. Mostly because having a superstar and a prospect I in the same group isn't fun for anyone. Personally I'm shit and I used to hover around Challenger I.
  11. Depends on a lot, I usually end up calling people by name. On average though: Blue: LATs and riflemen. 2iC in yellow so people can keep track on shacktac. Red: AR, AAR, medic and SL. Medic in green so he sticks out when people aren't looking at shacktac. This thread gave me inspiration though, so I'll try to use colours for two-man pairs (unique + rifleman) and see how that works out.
  12. 1st Mission Bravo Lead Zeus: @Sarissa Really enjoyed a convoy mission, which is a first so that must say something. Sorry for dropping the ball on the M113; had consistent problems making out what people were saying during the mission so all I got was "MTAR ... M1". Will fiddle with my audio during the week. Platoon: @Digby Tatham-Warter Really good job. I honestly believe the subdivision of tasks and the very clear instructions regarding convoy behaviour helped a lot in making sure that people did not end up goofing about. It became a little bit confusing at the point after all squads and regrouped at Plt HQ; amd one could really feel how much of an impact that had on people. Stellar stuff. Squad: @Cyico @Drett @Lyecer @NeilZar @seami @Sebbe @Silberjojo @ThatWalder @Wafflefox I felt like I ended up with a very solid squad that inspired a lot of trust and as such didn't need any babysitting. Mount up times were great, positioning during attacks were great, vision was absolutely stellar. Even the silliness that was the initial mounting up after briefing was handled maturely. Also, really good driving by @ThatWalder and @NeilZar . Would trust the vic to you any time of the day.
  13. And here I was thinking it was because the mortar asset, which was only included due to popular demand; took a shot from a position the mortar team itself requested; and by pure chance happened to hit the target. The suggested Open up on the first checkpoint, Drive through the biggest town in map, Leave mortar team behind; next to a BTR, Bumrush the target and fail, Have remaining forces extract for 15m before realising it isn't allowed, Finalised by Have a random trooper by pure chance find the dead body of the president, Barely make it to the extract on time Seems to suggest that pretty much everything but platoon lead was the deciding factor.