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 'memory'.
Found 14 results
I've noticed I'm not the only one to experience this and I can only imagine what the cause of the issue is. Ever since v11.1, virtually every single round I play I end up having a VRAM crash with the error stating I don't have enough memory to allocate textures ect... PC specs are I7 3770k at 3.4Ghz GTX 980ti 6Gb 16Gb DDR3 Corsair RAM Windows 7 I was not getting this issue before, and have even lowered the graphics settings to try to fix this issue to no avail. Some details that are important are: Preload texture streaming is OFF. Distant shadows OFF. AO/lense flare/Motion Blur is OFF. Settings on epic, lowered to high I still get VRAM crashes. Resolution is 1920x1080 even though it is lower than what I was playing before this update (without issues.) Tried SS at 1.5, 1.25, and OFF... VRAM crashes on every single one. The crashes seem to happen especially when I ADS or use Binoculars to zoom in, and also immediately upon dying (like instantly as I die I get the crash) I have cleared cache, I have set sound quality to low...everything except reinstall the game, which I am going to do tonight. As I said, I have only a bad guess at what the issue is and that guess is a memory leak. just now ran a STAT UNIT during startup and in a real round on a server. Results are as follows - stable 9.4 ms for GPU on main menu. 15-30 ms for GPU in-game, with random spikes up to high 90s that last just an instant. Not even sure what this means but figured it may be important. Any help or information would be much appreciated, I have 1100+ hours in this game and truly love it, but this is absolutely unplayable. Why boot up the game when I know I can't even play a round without crashing? Just isn't worth it and I've spent hours trying to fix this on my own, including a full dusting of my PC.
is there a memory leak in A11? Ever since I started playing A11 a few days ago I noticed a problem: it starts using 6gb, then 8gb, then it eats all of my 16gb, it`s so bad I cant get to play unless I restart the game (usually after 1 hour of gaming) is anyone else having this issue? I ask because I suspect the problem may be in my computer, since I havent played lately A10
I seem to only get this message when I have Squad cranked up at epic settings. I have had Squad since v9. Never had an issue until it was updated and now since v10, I keep getting this crash on epic settings. As the title says, I have a GTX 1080 paired with i5 Skylake CPU and can't fathom how this is happening. I play at 1440p resolution and also have 16gb of regular RAM. Does this happen to anyone else? It has only happened to me playing this game. Lowering the settings to high seems to help it.
Bash posted a topic in Software SupportLast 3 days I have not been able to launch squad. Tried every step of a clean install on multiple drives to no avail. After researching on the forums I found the same issue persisted for awhile when people were CLOSING the game. This issue occurs when I LAUNCH the game. I get the "Loading" screen but after it fills no splash screen with the "Squad" logo. 32GB's of RAM never even bumps. Windows Event Logs doesn't show any additional information about this specific error. Any help would be greatly appreciated! FYI mods I am aware of the following similar posts that contain no working fix: http://forums.joinsquad.com/topic/13222-the-memory-could-not-be-written/ http://forums.joinsquad.com/topic/12349-memory-could-not-be-written/ http://forums.joinsquad.com/topic/13064-expected-not-an-issue-squadexe-the-memory-could-not-be-written/?hl=memory http://forums.joinsquad.com/topic/13064-expected-not-an-issue-squadexe-the-memory-could-not-be-written/
Windows 10 x64 12gb ram 4gb video ram on a 970 i5 2500k SSD is fine for space No page file I get a windows popup after about 2 hours of playing squad saying im out of memory (doesn't specify video or main ram) and that I need to close programs, it offers to close programs automatically and the one time i clicked that it closed squad. If I ignore the error and leave the window open I can carry on playing, if i click cancel it pops up again a few mins later. Watching the GPU ram it sits full most of the time while in squad. Regular ram is not even close to maxed. Anyone got similar/ideas to fix?
Ive just bought the game on steam summer sales and when i was launching the game the loading window showed up and it was loading but when it was loaded 100% this error popped out: Squad.exe - Apllication Error The instruction at 0x00007FF7E7281345 referenced memory at 0x0000000000000000. The memory could not be read Any fixes for this?
Hi today i was playing squad as usual, and had to get off, i then exited the game normally, through the in-game screen. Everything was working from here and went on with my day. When i came back about 2 hours later to start playing some more, the error popped up: https://gyazo.com/65fc40abd7c754cc795b7095a65ae9c3 and i haven't been able to load up the game at all. Any help would be appreciated, thanks in advance!! Btw i have tried uninstalling, and reinstalling; along with verifying game cache, trying to run the game through the system files without steam, uninstalling and reinstalling the EAC software too, still to no prevail.
WorstNoobEVER posted a topic in Software SupportHi Just after the preload (before the actual game opens fullscreen), game crashes and send me 2 error messages one after another. First one : http://hpics.li/c0cb55d (translation : the instruction at 0x0007etc uses the memory adress 0x0007etc. the memory state - or the state of memory maybe - cannot be written) Second one : http://hpics.li/d50336b and yeah, the title of the window is : application exit unreacheable I tried to close Steam and reopen it, it won't work. What should i do ? Thanks
Hey fellow squadlings, I recently started getting a strange error. It started happening after I upgraded my CPU from i5 to i7, and both before and after updating the drivers on the new CPU. whats strange is that on my old CPU, the i5, I would never crash, and would play for hours at a time, whereas now, on the i7, I seldom get more than 5 minutes of gameplay before my game crashes. While it does crash every 5 minutes or so, it does also run more smoothly in that short time. That is, it runs at a higher framerate and enables higher graphical settings. Anyone know of any workarounds? I just want to iterate that the crash bug occurred both before and after I updated my drivers, and also that my video card is a GTX 550 Ti. My RAM card is 8GB I'll paste the error message below: error file:d\g\pipelines\owi-squadrelease-a-8\U\Engine\Source\Runtime\windows\D3D11RHl\Private\D3D11Util.cpp][Line:176] Unreal engine is exiting due to D3D device being lost. (Error: 0x887A0007 - 'RESET')
Fresh install of the latest build has been fine (within reason, alpha etc.) for a few days, now i'm constantly experiencing crashes after about 20 seconds loaded into a map with the following error: System specs: i5 3570k, 8GB Ram, R9 390 8GB gfx, 2560 x 1440 res - up to date drivers etc. this is repeated running the game on ultra and high. Quick google and the error message is a UE4 error rather than windows, so found this old thread: The VRAM pools had not been set up as stated in that post so i inserted those into my defaultscalability.ini which has not solved the problem. This is the log file output from the last crash: [2016.12.29-15.02.13:083]LogHAL:NoLogging: [2016.12.29-15.02.16:560][ 25]LogScript:Warning: Script call stack: Function /Game/UI/UMG/Map/SQ_RoleList.SQ_RoleList_C:Construct Function /Game/UI/UMG/Map/SQ_RoleList.SQ_RoleList_C:ExecuteUbergraph_SQ_RoleList [2016.12.29-15.02.16:863][ 27]LogD3D11RHI:Error: Direct3DDevice->CreateTexture2D(TextureDesc,SubResourceData,OutTexture2D) failed at d:\g\pipelines\owi-squad-release-a-8\U\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Texture.cpp:434 with error E_OUTOFMEMORY, Size=2560x1440x1 Format=DXGI_FORMAT_R16G16B16A16_FLOAT(0x0000000A), NumMips=1, Flags=D3D11_BIND_RENDER_TARGET D3D11_BIND_SHADER_RESOURCE [2016.12.29-15.02.36:471][ 27]LogWindows: FPlatformMisc::RequestExit(1) [2016.12.29-15.02.36:471][ 27]Log file closed, 12/29/16 15:02:36 I've reached the limits of my technical understanding/ability, so wondering if anyone has any bright ideas? Ta
Hi there, I tried to load up the game today and I have been having some issues with it. 1) Start the game from steam 2) game loads initially fine 3) plays intro 4) loading screen comes up with controls 5) presumably after 4) is done, an error comes up with the following Squad.exe - Application Error The instruction at 0xfd69c559 reference memory at 0x00000004. The memory could not be read Click on OK to terminate the program. Has anyone come up with this error before? Thanks, LK Edit1) Crash logs [CrashReportClient] bHideLogFilesOption=false bIsAllowedToCloseWithoutSending=true
Other than fatal errors, I also crash a few times a day while getting the following message: The instruction at 0xfeeec414 referenced memory at 0x12f98a40. The memory could not be written. Click OK to terminate the program This appear to be happening regardless of what i was doing at the time. please advise EDIT!!! : This happened twice today, both times it happened when i was manning a stationary dushka
Hey Guys, Definitely considering purchasing the game (probably even helping out with the Kickstarter) however my computer doesn't work too well with other games such as Insurgency (although I can run games like ArmA III on lower settings with a decent frame rate). I'd just like to know how this game would work with the specs I have before decide to buy the game: Processor - Intel® Core i7-3632QM CPU @ 2.20GHz Video Card 1 - Intel® HD Graphics 4000 Video Card 2 - AMD Radeon HD 7730M Memory - 8.1 GB Operating System - Microsoft Windows 8 (build 9200), 64-bit Thanks!