Jump to content
  • Announcements

    • Merlin

      Forum Rules   07/06/2016

      Introduction   The Squad Team reserves the right to edit, update, add and remove rules at any time. Applicable rules extend to the PM system. Your PMs are private, but the Squad Team may be informed about unacceptable PM content by the receiving party.   Section I: Posting Rules   §1 Show Respect This community can only work if we all respect each other. To that end, it is imperative that any time you engage with another user, either directly or indirectly, you show them respect with the content of your post. In particular refrain from flaming, insulting, abusing, taunting, racism, and other similar types of actions towards other forum users.   §2 Attitude & Behavior Poor attitude and behavior are the most common ways a negative / unsafe environment is created and perpetuated. As such that kind of behavior will not be allowed on these forums. Please be mindful of this rule when posting personal positions and opinions regarding topics which could be considered contentious in nature. As a rule of thumb, keep your posts civil in nature, and refrain from making posts that are likely to incite arguments and create a negative environment. As a privately hosted web forum we reserve the right to maintain an environment that we are happy the majority of our players are comfortable with.   §3 Swearing While we will not strictly moderate every little swear that occurs, please try to avoid excessive bad language. The moderation reserves the right to remove rants and unsuitable content at any time.   §4 Illegal Topics
      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 'rangefinder'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • OWI Official
    • Announcements
    • Progress Updates
    • Frequently Asked Questions (FAQ)
    • The Official Squad User Manual
    • Development Tutorials
  • International
    • Supported Languages
  • Game
    • General Discussion
    • Questions
    • Feedback & Suggestions
    • Media
    • User Created Guides
  • Support
    • Software Support
    • Hardware Tech Support
    • Website Feedback
    • Bug Report Form
  • The Community
    • Introductions / New Players
    • Teams & Clans
    • Events & Leagues
    • Wiki Development
    • Modding
  • Game Servers
    • Game Server Info & Support
    • Game Server Feedback
  • Off Topic
    • Off-Topic Discussion

Found 2 results

  1. Making FTL unable to determine range presented in a13 is an incomplete solution. A12 algorithm was: 1. FTL sets marker 2. FTL reads range to the marker A13 algorithm is: 1. FTL sets marker 2. FTL asks SL to set a marker on top of his own 3. SL marks on top of FTL marker 4. FTL reads range to the marker Does it require more teamwork? I guess. Something like quick event for medic and someone he is trying to revive, then need to do it together successfully, then revives is successful. More teamwork as well... Does it make finding range to target harder? I guess. If SL is aware of issue, it's +2-3 seconds, but same result. Although as a SL I don't really appreciate such minigame. I'm not sure what exactly is trying to be archived with removing rangefinder from FTLs, but to make it complete, SLs should give up their ability to see range to the marker as well instead of playing minigame "SL, marker my FTL marker". Or another way is removal ftl marker UPD: For full picture it's interesting to compare more similar features: 1. Squad marker (attack, observe, etc) + FTL marker 2. SL marker rangefinder + FTL marker rangefinder 3. Map contact marker + reinforce, resupply, etc markers All of them increase effectiveness of operation and lead to decrease in squad communication. Elimination of them lead the game to be more hardcore and "encourages players with excellent eyeballing/map reading/teamwork/etc skills". In that sense, Squad marker makes my job as squad leader pretty dull. All I have to do is to press hotkey on my mouse, get squad marker in the middle of my screen and scream "Marker" in the comms. I engage something? Marker. SL, where to go? Marker. SL, where to spawn? Marker. SL, which track to take? Marker. I mark before, during and after engagement, I barely ever have to call direction, everyone from my squad will find the marker on their compass and determine relative direction better than I could ever do with words. How is it in principle different from FTL rangefinding? Thinking of it, makes me want to play without this feature, but I know how effective it is, so while it's enabled, if you don't do it, you are in disadvantage.
  2. SVD Sniper - Guide

    Hello, just thought i'd post a little bit of help on how to aim with the SVD as this is difficult for some people in squads i've been in. First i'd like to point out that i put my FOV to 80, in order to better see. My mouse sensitivity is at 35 ingame, and i highly recommend putting your sensitivity even below that if you are trying to hit at 600-800m. Here is some illustrated instructions as to where to put your chevrons when aiming with the SVD currently ingame. If the stats for the SVD changes i will update this. At ranges up to 100m your bullets will hit at the top of the first chevron, and so you should aim with this. http://i.imgur.com/atuh2vw.jpg At 150m your bullets will hit inside the first chevron. So you should keep the top of your chevron at the top of your target and the bullet should hit inside that chevron. You should probably not attempt headshots beyond this range. http://i.imgur.com/qJUA7qG.jpg At 200m your bullets will hit quite close to the bottom of the first chevron, at this range i would place those chevrons on the shoulders of the target if possible, this should give you a neck/upper chest shot. http://i.imgur.com/P3jovr3.jpg At 300m you should still place the chevrons on the shoulders of the target, the bullet should hit right in his chest. http://i.imgur.com/s6t9B6H.jpg At 400m you should aim with the second chevron, this is a bit of a tricky range, as the bullet will land between the top of the second chevron and the bottom of the first, i place my second chevron at the lower stomach of my target at this range for a chest shot. This is probably the maximum range of effective engagement if you don't have 4K monitor or a low field of view. http://i.imgur.com/s6t9B6H.jpg At 600m you aim with the second chevron, it should land pretty much right at the top of it. http://i.imgur.com/308oTMl.jpg At 800m you are pushing it even if you have clever settings the sway will make it difficult to hit here. But if you attempt it, you should put the bottom of the second chevron on the shoulders of your target. http://i.imgur.com/ghhxOHQ.jpg Sadly the range finder is not accurate at the moment, but it can give you some indication if you adjust a little bit, at 200m the target should fit inside the 300m mark, but be outside the 400m one. This seemed to be true aswell at longer ranges, with the 800m target fitting inside the 900m mark. http://i.imgur.com/Tckz7w1.jpg I hope the SVD will be updated in the future with an accurate range finder where targets fit inside their marks. And a clossed scope, that behaves more like an overlay, the PSO scope that is modelled ingame has an eye contact cushion, and you're suppose to have it all the way up there, so it shouldn't be an open scope where you can see around it. This would also make it easier to use, as the zoom that you see would be greatly enhanced. I hope this was helpful to someone.