Forum Rules 07/06/2016Introduction 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 '12.1'.
Found 2 results
Hey soldiers, We've been working on getting the most heinous issues beaten in Alpha 12 and we're happy to present the patch notes for the hotfix! This update addresses a number of issues, but first and foremost would be the slow/no load issues that popped up with Alpha 12. That's not all, though: there's plenty of tweaks and fixes for everyone. Let's check 'em out: Patch Notes Systems Large number of optimisations to foliage and UI texture sizes and streaming in of textures. Optimised audio assets and sound cue variations in order to have a much lower memory profile. Reduced individual .PAK file sizes by breaking the large content .PAK files apart into smaller chunks, which speeds up loading into the game as well as installing updates from Steam. As the file structure has been changed, this patch will be quite large. Performance optimisations to the Squad Leader order widget. Performance optimisations to the main menu map. Removed player collision interaction on infantry ammo bags. Tweaked the first person offset to closer match where the head and eyes are in third person when leaning left and right. Unified the sub role drop-down interaction style across all role selection modes. Increased Steam connection timeout from 60 sec. to 120 sec. Updated layering of icons on the map. (Top to bottom: Spawn Points, Infantry, Vehicles, View cone, FOB Radio, Capture zone flag, Deployables, HABs, other Map Markers) Vehicle Gameplay Turret damage has been implemented to all closed turrets. Should a turret take damage, the damage will be passed on to its parent vehicle. In addition, if a turret is below 50% health the turret will begin to suffer a penalty in its maximum turn speed. The more damage taken, the more severe the penalty. Stabilised turrets also suffer by having its stabilisation disabled below 50% health. A cracked screen will appear when turret health is below 50%. Repair tools will be able to repair its health up to 25%, requiring vehicle crews to take their vehicles back to a repair station to restore full turret functionality. Open turrets like MAT-V .50cal turrets or Technical DSHK are not affected by this change. WSAD keyboard controls now can control traverse and pitch of all vehicle turrets with the exception of the KPVT, NSV-T, PKT turrets, and open turrets. Fixed an issue in the physics code gear mapping preventing the 6th forward gear on vehicles to work correctly and made sure RPM thresholds for shifting out of neutral gear are being respected, making driving up slopes in first gear much more manageable. AT-4 HEAT projectile set to use Heavy Anti-Tank type damage. Increased AT-4 HEAT armor penetration capability from 350mm to 500mm. This is a temporary placeholder change to the AT-4 to give the US and GB factions an infantry HAT weapon system. When the actual GB and US HAT weapons are implemented, the AT-4 projectile specs will return to their original "light/medium" AT role. Damage tweaks to guided missiles and rockets: Trucks: 1 TOW to instantly kill, 1 HAT to burning, 2 LATs to burning MATV/BRDM-2: 1 TOW to instantly kill, 1 HAT to burning, 2 LATs to burning BTR, MTLB: 1 TOW to burning, 1 HAT + 1 LAT to burning IFVs: 1 TOW to burning Slightly decreased .50cal's armor penetration capability at medium (100-800m) ranges. Made unarmored vehicles slightly more resistant to 25mm/30mm Autocannon High Explosive ammunition. Increased Heavy Anti-Tank rocket armor penetration capability from 630mm to 900mm RHA penetration. Light Anti-Tank standardised to 320mm RHA penetration. Simplified armor distribution on the BRDM-2. Tweaked camouflage netting on the M1A2 Abrams woodland cannon to not be as visually obtrusive from the gunners point of view. Reduced armor thickness on the M1126 Stryker. Increased carrying capacity of Logistics Technical to 1400 points. Simplified the collision mesh and distribution of armor on the T72-B3 hull slightly. Increased coverage of heavy front turret armor on the T72-B3, but added a weak spot where the base of the gun attaches to the turret. Tweaked BTR82A's 30mm turret armor, introducing a weak spot where the gun connects to the turret, but buffing its overall frontal armor. Removed physics kickback on all 25mm/30mm autocannons and the KPVT when firing. Decreased overheat penalty on BTR/MTLB 30mm and ZU-23. Infantry Gameplay Narrowed L85A2/L22A2 and M4 series ironsight front post for better target visibility. Lowered ammo point cost of LAT weapons (M72A7, RPG7 HEAT, RPG7-V2 HEAT and RPG-26) from 50 to 40. US and British HAT roles have been set to 2 per team, one frag grenade added to their inventories. Reduced deviation on the RPG-29. Unique Identity: Continued from the A12.0 release, weapon behaviour and handling has been tweaked in several ways to improve response and give each weapon family a more unique identity, as well as improving the effects of attachments like foregrips and UGLs. Unique Identity: All weapons have received a pass based on their caliber and barrel lengths. E.g., the AK-74 and L85A2 families now have less recoil than the M4 family. Focus Sway (ADS, focused) has been reduced. Weapon Sway (ADS, non-focused) has been reduced. Foregrips now decrease vertical recoil but increase horizontal recoil. Underbarrel Grenade Launchers now decrease vertical recoil but increase Weapon Sway (ADS, non-focused). Light Machine Guns and General Purpose Machine Guns have received a recoil and sway pass similar to Rifles in A12.0. Fixed some issues related to bipod deployment. Removed suppression ability from knives and pistols. Reduced all types of Sway on Binoculars - they should be more accurate and easier to use now. Map Tweaks & Fixes RAAS/AAS ticket gain/loss for flag changed: When a flag is capture, capturing team gains +30 tickets and losing team loses -30 tickets (was +20 and -40). This change is in combination with the reduction of overall ticket counts, so overall rounds will be slightly shorter, but rounds that have a lot of movement along flags wont end as suddenly. Reduced Counts on all AAS/RAAS map layers: Tallil, Yehorivka - 350 Tickets. Basrah, Belaya, Chora, Gorodok, Kamdesh, Kohat, Narva - 300 Tickets. Fools Road, Kokan - 200 Tickets. Logar, Mestia, Sumari - 150 Tickets. Reduced ticket count for Skirmish map layers to 100 Tickets (from 150). Reduced ticket count for Invasion map layers to 150 Tickets for Attackers/600 Tickets for Defenders. Fixed various Maps having incorrect map descriptions on team select screen. Fixed Main Base flipped vehicles for: Kohat AAS v1, Basrah Invasion v2, Fools Road RAAS v1, Mestia AAS v1, Mestia AAS v2, Mestia RAAS v1. Fools Road RAAS_v1 moved Fortress flag to OP. Fixed RU Main Base resource pool on Gorodok Invasion_v2. Fixed crashing on Jensen's Range Skirmish v1. Fixed incorrect flag setup Kokan Invasion v1. Fixed some map layers having incorrect faction descriptions and faction insignia. Added Vehicle depots further down the valley on Kohat RAAS v1 for faster logistics for both teams. Fixed incorrect CP names (Mohd Zai & Bahadur incorrectly labeled) on Kohat AAS v2. Fixed odd ammo caches on Logar INS v1. Fixed floating road segments in the north-west part of Mestia. Fixed lighting on Mestia AAS v2. Fixed Staging Zone boundary issues on Mestia Invasion v1 and Invasion v2. Fixed ambient visual effects on Tallil Skirmish v1 and v2. Fixed ambient wind audio not playing on Tallil Skirmish v1. Fixed map naming on Tallil Skirmish v2. Fixed US Main Base resource pool on Tallil Skirmish v2. Fixed Insurgents DShK Technical not being accessible on Al Basrah RAAS v1. Fixed missing materials for several assets on Chora. Fixed floating house forcing players to vault to get to the staircase on Kamdesh. Fixed Aircraft Bunkers culling too early on Tallil. Fixed incorrect collision setting in Protection Zone preventing players from leaning in Main Bases after the Staging Phase ends on all Tallil layers. Fixed trees and other foliage on roads, smoothed out areas with jagged terrain and tall lumps on Gorodok. Fixed collision and scaling issues by removing offending assets on Yehorivka Bug Fixes Fixed a crash when a Squad Leader attempts to invite a player who has disconnected. Fixed damage issues on several vehicles (including both tanks) caused by bugs in turret setup, mesh collisions and decoration configuration Fixed being unable to move the camera in the FV510 commander seat. Fixed missing turret turning sounds on a majority of vehicle based turrets. Fixed T72-B3 fragmentation rounds dealing no damage to infantry on non-direct hits. Fixed low-health/bleeding post-processing screen effects not playing during ADS. Fixed UB-32 Rocket Technical's ammunition being treated as if it was an emplacement. Fixed dead players not showing as dead in the Squad list UI. Added a check for 'foliage.LODDistanceScale', to force exit the game if players modify this value to hide the foliage similar to the other .INI checks. Fixed extra apostrophe in the deployment confirmation message when spawning on rallies. Fixed mines not playing an explosion effect or sound when a vehicle drives over them. Fixed some team based mismatch issues relating to Roles and force revert of your role to default when it becomes unavailable. Fix emplaced weapons not usable by other team when a player is shot out of it. Fix emplaced weapons having incorrect bounds leading to weapon models disappearing occasionally. Fixed main menu music not looping. Fixed zeroing on the 300m and 400m settings for the RPG-29. Fixed zeroing on the M4 series Red dot sight and M150 Optic. Fixed Neutral Technical DShK spawned near Village on Al Basrah RAAS v1 cannot be entered by either team. Fixed a number of statics either having missing collisions or missing textures. Fixed stationary SPG-9 doing slightly more damage than technical-mounted variant. Fixed some vehicle explosions showing broken explosion animation effect. Fixed vehicle wreck collisions being desynced from their visual wreck model. Fixed the FV510 Desert variant having a non-charred wreck model. Fixed snow on Belaya not producing snow related interaction sounds. Fixed Vehicle Driver UI RPM indicator showing incorrect values. Fixed an issue where a selected but now locked role inside a drop-down list forces an unusable UI state. Fixed Map & Team info mismatches in team select. Fixed first person view being offset after leaving emplacement when entering an emplacement while freelooking. Fixed Insurgent Radio ammo limit, now increased to 20,000. Mmm, those gearbox fixes speak to the logiboi in all of us. Get patching! We'll see you in-game! Offworld Out. Edit: This post has been updated.
Karm has sent out the word that public playtesting is commencing another round for Alpha 12.1. Be advised that the Squad - Public Testing app is already in your library and is a full Squad install for testing purposes. Careful with your bandwidth limits! Check under the "Custom Servers" tab if you don't see a testing server available. BIGGEST CHANGES: Large number of optimisations in foliage, UI, textures and audio which should result in less memory used Vehicle damage has been tweaked and fixed. Some vehicles would not take damage as intended, and armor/damage values have been changed for balance. Vehicle gearbox has been tweaked a bit. Driving uphill should be less problematic. AT-4 damage has been increased. Weapon handling changes: sway has been reduced, recoil has been tweaked. Several layer balance tweaks WHAT WE NEED FROM YOU: Feedback on memory-related issues (loading times, hitches, server loading timeouts). Is it better than A12, the same, or worse? What issues still remain for you? Please post this feedback in the #bug-reports-a12 channel on Discord: http://discord.gg/Squad