Forum Rules 07/06/2016
Prohibited topics include, but are not limited to: Piracy, drugs (including cannabis), pornography, religion, racism, sexism, homo/trans -phobic content, videos and images showing violent death or serious injury, ‘spam threads’, hacking & griefing (endorsement thereof), religion, politics, etc. Prohibition may be suspended for some threads if they are found to be suitable by the Moderation (such as scientific debate).
If there is doubt, the Moderation Team can decide whether a topic is considered illegal. §5 Attitude towards Squad and the Development Team
As per §1 and §2, keep in mind to be respectful and reasonable, not only towards all users of the forum, but also towards the Squad Team and towards any ideas and content and the game itself. Criticism is welcome, but if it is not constructive and/or if it is offensive, the Moderation may need to step in. Please refrain from posting if you are upset, angry or drunk, or you may be punished for things you wouldn’t have otherwise written, which is not in anyone's interest. §6 Language & Legibility
Please post only in English. Non-English content (including non-legible content) may be removed. If you see someone posting in another language because s/he apparently does not speak English, please report their post - if you can, you may reply in their language to explain their question, but please do translate their and your message so it can be reviewed by the Moderation. ‘Hiding’ insults in non-English posts will be punished harshly. Posts written largely in ‘leetspeak’ or full of spelling / grammatical errors may be treated like non-English content. This rule does not extend to PMs. §7 Forum structure & Search
Please ensure when posting a new thread, that the thread is located inside the correct forum section. Check all forum section titles to judge where your thread should belong. Threads created in the wrong forum section will be moved or deleted.
Before posting a new thread, please make use of the forum search to find older threads about the same topic. In doubt, it is recommended to rather post in an existing thread, unless that thread is years out of date. However, do not bump old threads without adding a new question / answer / insight that wasn’t in that thread before - use common sense. §8 Thread Titles
Please name your thread appropriately; the subject title should sum up / explain the content in the thread. If you fail to name your thread properly (such as ‘Hey!’ or ‘Check this out!’ or ‘Help!’), we will either rename or lock the topic. Repeated offense may lead to infractions. The practice of using CAPITALS only in your thread title is not allowed and will be edited or the thread will simply be deleted. Strange or abnormal Unicode characters should be excluded from thread titles for the sake of being distracting and unnecessary.
§9 Thread Capitalization
Please ensure that your post is not in all CAPITALS, as this is not allowed. Any threads posted in all caps will subsequently be removed from the forum. Repeated offenses may lead to infractions against your account. This practice is not approved or accepted here.
§10 Images in posts
When posting images, mind the following restrictions:
.gifs will be allowed and may be removed by Staff if deemed necessary.
Maximum size for images is 1280x1024.
Do not include more than ~1 large image per paragraph of text, unless in image collection / announcement threads. Link to further images.
Consider posting thumbnails. You may post a few more images per post if they are reasonably small, the details are for the Moderation to judge. §11 The use of BBCode
It is allowed to use the BBCode in your posts. Over usage is not allowed. You may use the Bold in a reasonable manner but not for the whole text body. You may use the size feature but in a limited reasonable manner. You may not use any of the additional fonts at all. Color may be used to high light a point but again, not for the whole text body. Moderators will be watching for misuse and will edit when required without giving notice. Continued disregard for this rule will result in Moderator action in the form of warnings. §12 Complaints of Server/Admin Abuse Reports of server/admin abuse will not be posted publicly. All reports concerning this type of behavior should be place in the appropriate sub-forum. http://forums.joinsquad.com/forum/241-report-server-admin-abuse/ All posts made outside of this area will be be removed. Section II: Reporting & Moderation §1 Reporting Posts
There is a Post Report system in place. If you notice a post that violates forum rules, simply use the exclamation mark icon below the users avatar image to send a report to the Moderation. We will then review this post. Your report will not be made public and cannot be linked to your person by anyone outside of the Squad Team. You will not be punished for using the Report system even if the report was false, unless you repeatedly abuse the system to spam it.
Do not ‘report’ posts by replying directly in public to them. In case of spambots, this prompts them to respond in turn, spamming the forum further. This also fuels flame wars and arguments. §2 Reporting Moderators
Moderators are subject to the same forum rules (and some additional rules / exceptions). If you think that a Moderator has treated you unfairly or is otherwise breaking forum rules, please PM the Lead Moderator or any Administrator. Do not accuse Moderators in public, the Squad Team will treat every complaint seriously and it is in our interest to discipline or remove Moderators who are known to break forum rules. §3 Respect Squad Team members and Moderators
Do not ignore or argue against Admin, Moderator or Dev instructions on the forum. If you have a complaint, as per §2, please inform the Team in private. You are expected to follow orders given by the Moderation, Administration and Development Team, and it is necessary for smooth running of the forum to respect their decisions. Being stubborn or ignoring warnings will lead to harsher punishments - however, we do not tolerate Moderator / Admin abuse of power / privileges, so do not hesitate to inform other Team members if you feel treated unfairly. §4 Bans and multiple accounts
If your account is temporarily or permanently banned, do NOT create another account. Bypassing a ban will result in further action, and a permanent ban of all of your accounts.
You are not allowed to have more than one account for any reason. If you share an internet connection with another user who has their own account, it might happen that this account is incorrectly identified as a secondary account - please get in touch with the Moderation or Administration to resolve such issues.
Search the Community
Showing results for tags 'trackir'.
Found 5 results
I am very much looking forward to the development of helicopters and I know many other people are. However, once they are introduced to Squad, I would very much like to see TrackIR v5 and Joystick control available with helicopters as it would be an easier approach for getting used to aircraft. Though it will take more time and resources, I ask that the developers take into consideration my request for introducing these with helicopters and are making it one of their future goals. I use a Logitech Extreme 3D Pro and TrackIR 5 Headset clip for my setup.
Hi everyone, first of all: sorry if I opened this topic in the wrong forum, didn't know where to put it. Mods please move accordingly – thanks! I was looking for a solution to use the roll axis of my TrackIR for leaning in Squad. After searching a bit on the internet I stumbled upon FreePIE, which is a free alternative to GlovePIE, and essentially allows for programmatic access to and redirection of TrackIR input data via Python scripting. I then quickly wrote the following generic script which allows for binding of TrackIR axis input data beyond a given threshold to keys. I use it to bind my TrackIR roll axis to the keys "U" and "I", which I in turn then bind to "Lean Left" and "Lean Right" in game (Lean Toggle OFF). The key bind only gets triggered if the axis input data is either below -50 or above +50 respectively – which equals to a deadzone of 100 in the center of the axis. Key binds, axis and thresholds can easily be changed to other people's likings. I don't know if this is of interest for anyone but thought I might as well share. The code can be found in this GitHub Gist, but I'll simply paste it here as well. Feel free to use it and ask any questions you might have here. EDIT: I changed the script to allow for an arbitrary number of axis - threshold - key combinations. # FreePIE TrackIR AxisToKey## Author: loenze (https://github.com/loenze)# Bind axis value beyond given threshold to key.## I wrote this for leaning in Squad,# but the script should work in any game with any action.## SQUAD forums discussion: http://goo.gl/mVh6E7## To configure your key binds simply add config lists with the according parameters# to the AxisToKeyConfig list at line 31. You may add as many as you wish there.## AxisToKeyConfig = [# [trackIR.roll, Key.U, -50],# [trackIR.roll, Key.I, 50]# ]## This example consists of two bindings for the TrackIR roll axis.# If the head is tilted to the left beyond a value of -50, the U key will be pressed.# Likewise for tilting to the right beyond a value of 50 and the I key.## Possible axis values are: trackIR.x, trackIR.y, trackIR.z, trackIR.pitch, trackIR.roll, trackIR.yaw# Available keys can be found here: https://github.com/AndersMalmgren/FreePIE/wiki/Reference## To find the right threshold values for you, you might want to turn on debugging for# FreePIE's Watch window by uncommenting line 77.# CONFIGURATION# Add lists consisting of [axis, key, threshold]AxisToKeyConfig = [ [trackIR.roll, Key.U, -50], [trackIR.roll, Key.I, 50]]class AxisToKey: def __init__(self, axis, key, threshold): self.axis = axis self.key = key self.threshold = threshold self.type = 'pos' if threshold > 0 else 'neg' def press(self): keyboard.setKeyDown(self.key) def release(self): keyboard.setKeyUp(self.key) def over_threshold(self): if self.type == 'pos': return False if self.axis < self.threshold else True else: return False if self.axis > self.threshold else True def update(self): self.press() if self.over_threshold() else self.release()AxisToKeyBindings = [AxisToKey(*c) for c in AxisToKeyConfig]class Debug: info = '' @staticmethod def read(binding): Debug.info += """Axis\t""" + str(binding.axis) + """Thres\t""" + str(binding.threshold) + """Key\t""" + str(binding.key) + """Status\t""" + ('PRESSED' if keyboard.getKeyDown(binding.key) else '') + """ """ diagnostics.watch(Debug.info)def update(): for binding in AxisToKeyBindings: binding.update() # UNCOMMENT FOLLOWING LINE FOR DEBUGGING #Debug.read(binding)if starting: trackIR.update += update
So DevilDogGamer put up a video about EyeX which looks interesting and seems like something we could use in Squad. I'd definitely want a way to suppress the tracking so I could look at different spots on my screen without changing my view, but this has real potential I think. At $100 it seems to be reasonably priced as well.
So I have been using FaceTrackNoIr for awhile now on flight sims and games like Arma 2 & 3. In terms of immersion this is right up there for me with VR without the massive paywall. Also adds a cool edge to combat when you can look over your shoulder without disengaging the enemy. Just thought it would be cool to have support in my new favorite tactical shooter :) Lemme know what you guys think.
Will Squad support any types of VR? Coming from being a full time Arma player I really would like to know if I can or will be able to make use of my Track IR when playing squad. I believe this is crucial to be able to look left and right and not be so horse blind when playing shooters. Any information would be appreciated!