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) 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. Section II: Forum Signatures §1 Signature Dimensions
To avoid clutter, please make sure your signature (if you choose to have one) does not exceed the following size limit: 350x150 pixels. Your signature may consist of images, user bars and text elements, as long as the total size does not exceed 550 x 200 pixels. A small tolerance will be given, but any signature larger than the limit may at any time be deleted without prior warning. If you are not sure whether your signature is acceptable, please PM a moderator. §2 Signature Content
All rules of section 1 fully apply to your signature. We will remove signatures or parts of signatures without notice if they violate the forum rules, and infractions may be given. §3 Animated Signatures
Please refrain from using animated .gifs as signatures, they distract and clutter the forum. Section III: 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 'artillery'.
Found 12 results
Insurgent Artyillery Calculator /u/r4ff4_ello an me wrote a little python script for calculating elevation (in keystrokes 'W') and the angle to target for the insurgent arty truck. It is not a bot nor does it press something for you, its just a calculator which uses grid referencing and some school geometry, have a look: Insurgent Artillery Calculator Web-Version Grid-Reference Version Code: https://trinket.io/library/trinkets/9d405e92ee Just input the grid-scale, position of artillery and target with easy grid referencing no more counting and just one angle output. Be advised the elevation data is for 80ms Keystrokes so if you want to reproduce it use our keyboard macros! Changelog: v5: - now on par with mortar-version - added web-version v4: - updated for the coming new map grid (A1 K1-9 SK 1-9) - attempt to fix angle calculation in quadrant 3
Squad Mortar Calculator As promised here is an mortar calculator script. Use grid-referencing to input position of mortar and target to get elevation (Milliradians) and Azimuth (Angle in °). The link provided works on your smartphone as well. Please provide feedback and ideas for further improvement. Web-Version Python-Version Features: Calculate Azimuth, Elevation and Distance based on mortar and target position. Infinite sub-setting like A1K7K7K8K9 for cruise-missile precision Interpolation for elevation-steps Description: Refer to grids like this: C2-KP5-7 = C2K5K7 A1-KP5-5 = A1K5 or A1K5K5 D12-KP3-9 = D12K3K9 1. Input Mortar-Position 2. Input Target-Position 3. Dial "Elevation" and "Azimuth" into mortar interface 4. Enjoy! Visual Guide: Changelog: Credits: XXPX1, loff Other versions: By XXPX1 By bravo2zero By loff You can find a version for the insurgent artillery here:
As someone fascinated with the concept of indirect fire, I am eagerly awaiting the introduction of static artillery. In my opinion having FOB deployables such as Howetzers and mortar pits could greatly improve the game. Not only would it add to the combined arms goal of Squad, but would help turn FOBs into key map objectives for players to attack or defend. Another thing I would like to see is a manual approach to aiming said artillery, following the trend of the Rocket Technical. Instead of gunners just clicking a map, have them experiment with the angle of elevation and orientation. This would promote communication with forward observers and keep the crew from getting bored. So what are your thoughts on FOB based artillery and when do you expect it to be implemented?
He everyone, I had a quick question regarding the implementation of the mortar system in game. Is there already any word from the devs regarding what it will look like? Other then the already existing speculations that it will be pretty similar to what the mortar system looked like in PR. And is there already word out on what the ETA for mortars is? Also. Merry Christmas and a Happy new year.
Aniallator posted a topic in General DiscussionIn my experience rocket artillery can be effective in the right hands (I've been on both the sending and receiving ends of this), but that generally speaking, it's ineffective. I think the reason for this is that people usually employ it strategically rather than tactically. 90% of the time I've seen rocket techies they're bombarding a flag/FOB, which is ineffective unless the rocket techie is coordinating with friendly squads that can rush the flag/FOB the moment the bombardment ends... which is hardly, if ever, the case. All the enemy has do to is wait for the bombardment to end, then they can resume defensive positions and revive anyone who went down. If you're unable to coordinate with friendly squads, or those squads are unable to position themselves to employ the aforementioned tactic, a more effective utilization of the rocket techie is using it defensively as an area denial weapon, rather than offensively against static enemy positions. A good example of this is Kohat v2, where whoever controls the hills near the flags controls the flags. Using rocket artillery to deny the enemy the hills, if successful, would allow flags to be held or at least held for longer, and would if nothing else buy time. Keep this in mind next time you use a rocket techie.
YuriIsLoveYuriIsLife posted a topic in Feedback & SuggestionsI think we need a thread exclusively for artillery brainstorming. On the Squad FAQ, it's stated that "In the long term we plan to always have maps of all different sizes, allowing server admins to choose the kind of maps they wish to run." In the first maps, we can assume that the devs had almost exclusively infantry combat in mind. So we can also assume later maps will be larger to accommodate vehicular combat. I think I may have found a viable solution for self propelled artillery for the big and rich US and Russian forces. In the long term we plan to always have maps of all different sizes, allowing server admins to choose the kind of maps they wish to run. US Forces: The M1129 Mortar Carrier. The M1129 is a Stryker Chassis with an M121 mortar which is just an m120 mortar modified for vehicle use. It has a range of 7,240 meters. It can also carry an M252 mortar (5,935 meters) and an M224 mortar (3,490 meters). Russian Forces: TOS-1A and/or 2S31 Vena. The older TOS-1 has a range of 500 meters to 3,500 meters. The newer TOS-1A has an increased range of 6,000 meters. 2S31 Vena: The 2S31 can fire mortars at a max range of 7,200 meters.
Make the commander the most diserable role to play! I played a lot of bf2! And it was so boring to play commander. Squads didnt follow orders and you didnt really have a big impact on the game except from eternally spotting enemies. I'm confident SL's Will follow orders (in Squad) but its not really a big adrenaline rush to have 3 otter Guys on your comms channel, and seeing Dots on a map. Solution? Make the commander awesome! Reinforcements: I suggest the commander should impact spawn timers on vehicles, it can be done in 1 of 2 ways as i see it. 1st: prioritizing respawn timer rates e.g. your 1st priority gains a 2x respawntimer boost, 2nd 1.5x and 3rd 1.2 (what ever). - If no commander boost rates could just level out on all vehicles 2nd. simply buying vehicles like building fobs. though with a maximum so you can't have 2 or 3 mainbattletanks or whatever. This way the other team wouldn't know if they are going up against an armored force or a fast-moving recontype force. - If no commander is chosen a standard picking for a balanced force is chosen. (my favorite) being in charge of reinforcements gives the commander a greater strategical impact. I think we all agree mainbattle tanks shouldnt respawn right after being destroyed. Vehicles should be cared for and valued highly. The squad should cheer when destroying enemy vehicles... knowing they wont see the fckr again for a long time. Offmap assets: Commander is in charge of all offmap assets: Artillery, UAV's (small videofeed of whats going on atm), drops and.. piloting planes! Helicopters belong on the map. Planes do not! We Will miss out on the brute force of a plane haulning over the map in 12 seconds If their speed is to fit into gameplay. I hate missing out (see the link, you can't fit this into a game where an airplane takes off and land on a 8x8 km map). Let the commander call a plane into the A.O and have him pilot or Gun it when dropping a JDAM on an enemy compound or shooting down a helicopter bugging your squads. "Air support incoming 3 minutes" Would be a nice information to relay to your squad mates. And this would give the commander some hands on experience. Even just 30 seconds, two or three times a game, not looking at your map would make a big difference for playability. making airsupport this way, would also make it a lot easier for developers I believe (not an expert on the matter). Comms: The commander should ofc talk to the SL's and not the squadmembers, to hold a chain of command. on his map he should be able to tap into one squadleader and only talk to him. He should also have direct comms to all vehicles, making vehicles a team asset, not a squad asset. Again by tapping into their comms on his map. (sidenote on vehicle kits) Maybe pilots and drivers, except humvees and the like, should not be squadkits. but instead a separate "squad" operating only under the commander. So a squad as one unit can be deployed by a team-helicopter/apc without having a member driving back to base to not lose the vehicle. This would also emphasize the importance of vehicles, and caring for them. Typical BF to drive to the front and leave your vehicle.. I dont want this. Conclusion: Offmap assets like planes and artillery should be very rare, and therefore it is important to give the commander a busy gameplay revolving around strategy and comms. since he has the role of tactical air command, artillery battalion, executive officer and if you listen to me: pilot/gunner and company commander (reinforcement wise). he SHOULD have enormous impact on gameplay, the biggest impact of the team! He should feel the resposibility of the SL tenfold. people don't go SL because it is a big responsibility - and for the same reason people wouldn't just go commander to mess around. - and YES mutiny/voting should be an option. sorry about the rant, I had so much on my mind :D what do you think?
I've seen quite a few suggestion and question threads regarding when mortars will be introduced to the game, but what I'm more interested to know is how people are expecting these indirect fire weapons to affect gameplay, and also how in-depth people want the mortar system to be. The reason I've created this discussion is because I've seen a lot of excitement from some people for the eventual arrival of mortars, but I've also seen a lot of complaints (especially in-game) about grenadier and LAT explosive 'spam'. So if people are getting annoyed by small explosives like what's present, then mortars will give them an unpleasant surprise. I personally don't get irritated by the current amount of explosives going off in any given skirmish, and expect mortars to be a nice addition to the game. In terms of depth I'm not interested in a mortar system that requires me to get out a calculator, but want something a little more complicated than a system like Arma. Also, keep in mind that land vehicles will be out well before mortars arrive, which means responding to them will be quite a bit easier than if they were released today.
it would be super awesome for conventional forces to have the MLRS. with UE4 and the devs' amazing skills--thats nirvana, lol jk but u know. for balance/gameplay i imagine it being something like the first one spawns 20 min into game, only 1 in play at a time, respawn time is 20 min, is very slow, takes a good time to "set up" and fire, is defenseless within 1000 meters, 1000 meter minimum and 2000 meter max range, if MLRS then no mortars, cost the team a lot of tickets when killed, requires commander order (?), takes a lot or supply points to re-arm (...), but is fucking beast! tactically MLRS would need to be escorted into combat by armored support with IFVs and such i imagine. gunships, mortars, area atttack ("metaweapons") counter MLRS. supply trucks might follow for for armament and repair. would require its own squad(?) Russian US
I would love to see the effects of arty and mortar fire in the dirt, it could also provide a little cover in an otherwise hard approach. Sure, it's not a gaping chasm, but if you lay your sweet little ass down in it you might just avoid collecting a bullet with your face. Is it easy to implement? is it taxing on our wee little cpu's? is it possible? was it planned anyway?
Upon hearing the average size of future maps would be around 16km, an idea popped into my head. What if there were some sort of artillery battery implemented in or near each team's base? These batteries would be immovable Each battery would consist of 2-4 artillery pieces Types of artillery could be howitzers, rocket launchers, or even long range mortars The team required to operate these batteries would vary depending on the kind of machine (i.e. howitzer would need a gunner and a loader