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 'sdk'.
Found 12 results
I downloaded the Squad SDK(Epic Launcher) today and after 3 hours of initialization and loading, I got an error at 96%. This is so much frustrating. I couldn't have the chance to read or screenshot the error as another error followed it said "out of video memory" and the graphics driver crashed horribly. The display didn't recover and I had to restart PC. I don't know what's the issue here. I read in a wiki SDK recommends a minimum of 16gb ram but I don't think that would cause graphics driver to crash. Can you please mention the hardware recommendation for the SDK specifically because I think I'm lacking many things to run the SDK successfully. At least mention the HDD space and Graphic memory requirements. Current configuration: AMD FX-8320 @ 3.5ghz 8GB DDR3 RAM GTX 1060 6GB 100GB free space in HDD 550watt PSU
Hi all, "Squad SDK Unreal Editor" on UE 4.16.3 Windows 10 on MacPro newest Model 16GB UE is initializing quickly towards 73% where it spends a few minutes on shader compiler work, after that it goes quickly up to 95% where it spends around 20 minutes on shader compiler. At some point it finishes this work and CPU use drops to a few % with the only task left running "Unreal Editor" without any shaders or other apparent processes. It stays that way for hours until task is ended manually. I have turned off everything in Windows i could find in settings that might interfere. Any ideas ?
Hey Squaddies! It's time for a quick Modding 2.0 development update! Progress has been going well since the initial modding release, so we figured it was time to show off some of what's coming up next. First off, the Modding SDK UI has been completely redone (by an actual designer this time!). With their help and a fresh copy of the PSD of the new SDK UI, we went straight into implementing the update. It turned out like this! As you can tell, the tabs on the left the UI for the Modding SDK have all been moved to one window. No more multiple tabs on the top bar! Every action you need for modding is now in one convenient window. Sharing Mods We've scratched the old Steam Uploader and wrote a whole new one from scratch. (This one gives more errors than "Something went wrong."). We've also removed the need to have to pick an "Output Directory" when you are cooking your mod. By default, the system will now pick a valid path for you! We've also removed the need to have to click both the "Package" and "Upload" button. If you just click upload now it will perform the "Package" too. The "Package" button now is exclusively for people who don't want to upload their mod to the Steam Workshop. Editing Mods You are now able to edit your mod's information through the UI after creation. No more having to go through your modinfo info file and change all of the information and hoping you don't break anything! This new UI is probably 90% done. All the work that is left to do is small but important: fixing button sizes, handling really long strings, handling edge cases, etc. This should definitely come out with Modding 2.0, or maybe even earlier! Modding SDK Internals SMI Files Modinfo.smi files have been destroyed and replaced with your .mi files. No need to worry though, as soon as you load your mod in the Modding 2.0 SDK, your mod's SMI file will be upgraded to the new format. The main reason for switching file formats is Modding 2.0 doesn't require nearly as much data to be stored locally as the previous method. Steam Workshop Images Your mod's Steam Workshop preview image now lives inside of your mod's project folder. This was changed to prevent this reference being lost and then not knowing why you can not upload to the Steam Workshop. Cooking Mods As mentioned above, you no longer need to pick a package location. The Modding 2.0 cooking system will by default pick a good path for you. The first place it tries is your mod's project folder. Sometimes this doesn't work due to various issues (No space available, The pathname is too long, etc...), so cooking will continue to walk up the Squad folder structure until it finds a valid path. If it can't find a valid path (which is unlikely), you can still specify a cooking directory. Example Modding 2.0 Project Structure In-Game Mod Downloads Finally! This what you've all been waiting for, right? We're happy to report that progress is going well on getting in-game downloads working. This is proving to be a much larger task than originally thought, but steady progress is happening! As you can see in the GIF, mods can now be downloaded while the game in running with no problems. This test case is performed during the game is booting up, since we are doing a lot of CPU heavy stuff then: Current Work Currently, work is focused on getting the mods that are being downloaded while the game is running to be recognized by the game. This is quite a bit of work and will be taking up most of my time for the rest of the month, as the engine is not set up to accept PAK files mounted in the middle of the game. Offworld Out.
So I just downloaded the SDK and I've been trying to start it for a while, but the application has been sitting at "loading... 83%" for more than a half hour. Is this normal? I've tried restarting it twice with no effect. Edit: the unreal engine process is maxing out both my CPU and RAM usage, could this be a problem?
This is mainly for the Devs. Due to my C: drive dying i've had to re-install windoze and consequently the SDK as well - all 38-odd Gig. - which sux some because now i have to re-copy all my work back into the Mod folder - ok, takes time but not so bad. Except that just after re-installing windows the windows update 'helper' helped by breaking windows, so i had to re-install again - this was just afte re-installing SDK and everything else. Even trying to point "Install" at the existing SDK returns an error that the install folder must be empty - so everything must be deleted before you can install. This may not be such an issue for those outside Australia and that's fine but here we have rubbish internet compared to the rest of the world - and it's a pita doing such big re-installs. So my question is this (and it may very well be an Epic's thing not OWI's, i get that but i have to start somehwere), is there a possibility for adding into the Launcher a way to point "Verify" at an existing SDK install so i don't have to chew through nearly half my 100Gb monthly quota and lose another 2-3 hrs in doing so? Cheers!
Thought i'd start a thread for any SDK issues, problems and for update info/changes. Starting from the SDK update in September 2017. Couple questions to start off: 1. after the update i have now only 4-5 maps in the Contents - is this right? were the other maps removed for a reason? 2. can we expect any form of change-log, even rough, for each update?
Name: "Tresenka Border" Landscape: Alpine Climate: Cold Alpine in the higher area closer to the airbase and cold, wet, muddy forests in the lower valley. Dense forests, small water canals, muddy dirt paths, one main highway. Setting: Tresenka Border takes place in a fictional setting along the border between Russia and a country at war. Fighters from the warring country continuously use the river and mountainous terrain to cross into Russian territory aswell as making use of old WWII trenches. However as fighting has intensified in the region, Insurgents have pushed through the border-crossing while Russian forces' increased security will now be on the defensive to protect it's military installations and small civilian population in the region. This battle will take place in a clash near a military airbase just outside of the border between the Russian Federation and Insurgent forces. Factions: Russian Federation vs Insurgents Design Plans: Large scale map designed for Infantry, Transportation, Light Armor and Heavy armor fighting in a heavily forested area. High vantage overwatch military installations, some bunkers carved into the mountains, Radar stations. Custom buildings and assets also planned. Inspirations: Battlefield 2 , Project Reality, Altai Range (Battlefield 4) for setting, Damavand Peak (Battlefield 3). Screenshots: (link) First Rough Pass Update 1 Update 2 - Lighting and Environment Note: This is my first creation using Unreal Engine 4 but i'm so excited and determined to complete this map . Terrain textures were pretty hard for me to get right and natural looking. I'm on my third pass so far so the snow capped mountains are indeed a work-in-progress . Update: Worked on the mountain side and terrain a bit more. Check the album above for screenshots! Feedback and Suggestions are greatly appreciated!
With the annoucement of the soon to hit SDK how about some community price funded mapping contest? Maybe the dev´s could set the rules of time and what the base thing has to have to be accapted and use an extra mapping contest donate paypal account for everyone who wants just to donate some price money(of course without any reward). It would not be much in the end I guess but I think that would get a few people in the mood to start and build something great. Any opinions?