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 'alpha 7.7'.
Found 1 result
Read the full Changelog on our front page HERE! UPDATE 7.7 Hotfix (15 October 2016) We are now pushing a version Alpha 7.7 hotfix release, here are the changes: Fixed crashing in Squad's custom full auto sound and voip sound code relating to sound rendering in Unreal Engine 4.12 being asynchrounous now. Fixed a crash related to gunshots not having an audio device under certain circumstances. Fixed some issues with sound concurrency, causing certain gunshot sounds to cut out. Fixed exploit relating to FOV. Made a minor fix to deployable placement logic so you cannot place deployables on a roof from the ground. EDITED FOR CLARITY: You can still place deployables on a rooftop when you are standing on that rooftop. Added code so server admins can view the framerate of their servers in the scoreboard. Fixed distance delay on certain explosion sounds. Fixed an issue where the camera changed to third person on exiting a vehicle in single player Jensen's Range. Fixed issue where vehicles get bogus rotations after destruction (e.g., sideways vehicle wreck). Fixed an issue where players lose mouse input in the main menu / map. Updated the Ural wreck collision. UPDATE 7.6 Hotfix (30 September 2016) We are now pushing a version 7.6 hotfix release, here are the changes: Fully disabled Valve Anti-Cheat on servers as it is not currently used (Squad uses Easy Anti-Cheat). This is to resolve issues where certain players were unable to connect to servers. Fixed the bug where vehicle drivers are unable to see any players around them after driving a long distance away from the location they entered the vehicle. Added a fix for a rare crash relating to visual effects. Added a number of additional performance measuring code markers to aid developers with working on Alpha 8. UPDATE 7.5 Hotfix (19 September 2016) We are now pushing a version 7.5 hotfix release, here are the changes: Fixed a client side crash relating to effects code in the engine introduced following the upgrade to Unreal Engine version 4.12 Fixed some possible memory corruption which may have been leading to crashes relating to the initialization of the console on startup. Fixed a rare server crash in vehicle claiming code. Pulled in a performance fix for Alpha 8 using a much faster method for drawing nametags. Note that in order to facilitate this, nametags will now be rendered through walls for nearby friendlies. Performance improved on the maps Op First Light, Kohat, Sumari and Logar by fixing improperly sized terrain textures. Fixed soldiers being invisible in local play on Jensen's Range, a bug introduced in a performance fix for alpha 7.4. Fixed an exploit relating to users tweaking their FOV outside of acceptable ranges. Increased the starting velocity for the spectation camera from 2.5 to 15 meters per second. ---- UPDATE 7.4 Hotfix (13 September 2016) We are now pushing a version 7.4 hotfix release, which contains: Fixed the round start crash and a number of other crashes, all caused by the improper deletion of physical materials in memory. Pulled in a performance fix developed for Alpha 8 relating to the rendering of other people's character meshes. Fixed up the deployable repair station blocking lean and deployables. Made reflection spheres not appear in game. (As an aside, we would like to assert that reported sightings of UFO's in squad are *completely* unfounded and baseless!) Made the wire fences at the fool's road train station penetrable. Fixed not being able to enter certain tunnels at the Fool's Road hilltop. Fixed players not being able to drive vehicles into the fortress on Fool's Road. Fixed the Sumari AAS 3 flags being cappable by 1 person. Fixed the Sumari skirmish layer cap zones being too high in the air. Fixed some road and spline bugs in Chora. Finally, please note there is at least one other moderately occurring crash that we are still aware of and actively investigating. ---- UPDATE 7.3 Hotfix (31 August 2016) We are now pushing a version 7.3 hotfix release, which contains: Disabled async loading as an attempted fix for loading related crashes, and possibly a number of other crashes & bugs. Added an attempted fix for a crash caused by a specific effect emmiter. Added fixes for materials and material settings on a number of maps to prevent a specific type of crash. [This means a very large download for this patch] Removed an unused analytics plugin as a fix for round start stuttering. Updated the Easy Anticheat SDK. Updated turret bounds to avoid them popping out. Fixed some ambient sounds on Sumari and Kohat. Removed a number of unused materials. Fixed errors with two fence materials. Fixed an improper texture size which was causing a small loading delay. Increased the max data cache size as an improvement for both Squad and Mod developers. Cleaned up unusued references to trace channels without actual properties which were causing log spam. Cleaned up some orphaned break points in Blueprints as a reduction of log spam. ---- UPDATE 7.2 Hotfix (19 August 2016) We are now pushing a version 7.2 hotfix release, which contains: Fix for physx crashing [The most common crash currently]. Added a workaround in vehicle physics assets for a deeper bug in physx. Fixed a common crash caused by a landscape material issue. Fixed a crash related to vehicle seat code. Allowed sounds shorter than 10 seconds to be loaded async on map load as a fix for some of the stuttering issues players have been seeing. Fixed a number of issues with collision meshes on environment objects. Removed unneeded landscape hole material from Operation First Light. Disabled ribbons in effects for time being to negate a memory leak. Optimized tick rate on effects. (ie not realtime). Removed a few trace messages in the source to reduce some log spam. Made an adjustment to the trace channels and presets used in vehicle collisions to accomodate another vehicle fix. Pushed a simple collision setup for the radiotower, moving it from complex to simple collision, which should stop it from crashing people. Foliage Cvar exploit fixes. Added some ambeint sounds to Yehorivka and Sumari. Updated default unbound binding text to "None" from "QWE". Checked all collision assets for physmat assignment. Added wheel effects on ural. Reduced wheel effects to 4 on all vehicle types. Assigned wreck meshes to "block all". Increase m2 yaw to 30 degrees from 25. -- Note: There is a known camera bug when exiting vehicles including stationary .50 cals in the Firing Range. Simply enter the admin cam (Shift + P) and exit the admin cam (Shift + P) to reset the 1P camera. The bug does NOT happen in multiplayer. -- Server Admins: Update your map names on your server rotation file!!! We renamed the maps to better identify them. "Logar" "Logar Valley AAS v1" "Logar Valley AAS INF v1" "Logar Valley INS v1" "Logar Valley INS v1 Night" "Logar PAAS V1" "Jensen's Range" "Kohat" "Kohat AAS v1" "Kohat AAS v1 INF " "Kohat AAS v2" "Kohat INS v1" "OP First Light" "OP First Light AAS v1" "Chora" "Chora AAS v1" "Chora AAS v2" "Chora PAAS v1" "Chora INS v1" "Chora AAS v1 Night" "Chora AAS v1 INF Night" "Fool's Road" "Fool's Road AAS v1" "Fool's Road AAS v2" "Fool's Road AAS v1 INF" "Sumari" "Sumari AAS v1 INF" "Sumari AAS v1" "Sumari AAS v2" "Sumari AAS v3" "Sumari ITC v1" "Sumari INS v1" "Gorodok" "Gorodok AAS v1" "Gorodok AAS v2" "Gorodok AAS v1 INF" "Yehorivka" "Yehorivka AAS v1" "Yehorivka AAS v1 INF"