• Content count

  • Joined

  • Last visited

About Skul

  • Rank
    Squad Leader
  • Birthday

Profile Information

  • Gender
  1. Nah, man. Squad is a game of innertia(momentum), teamplay and skills. Proper FOBs, ammo crates, repair stations matter the most, then teamplay, then personal skills, like reaction and such. If you have, like, 8 FOBs on the map, you have your grenadiers on ammo crates spamming enemy flags(grenadiers are 100 times better artillery than mortars, no joke, no sarcasm, they are better, don't use mortars at all). And you have your vehicles on repair stations on the overpowered positions spamming enemy with infinite ammo, it doesn't matter how skilled your enemies are(how fast they react, dolphin dive or shoot towards critical body parts). If your enemies don't abuse ammo crates, repair stations, spawn points and all of that meta stuff, you're going to win by using game mechanics, unless enemies have very good FOBs, ammo crates and repair station themselves. But yeah, if your enemies play with kdr 5 even after you placed all of that properly, then you deserve to lose. But it isn't a problem of a game, it's a problem of a team and players which have scissors instead of hands and sawdust instead of brains. The thing is, I never saw anyone(I played enough matches myself) to play a proper-proper Squad yet, when a team is working as an mechanism: But we'll get there. Well, then the team isn't good enough to stop this player and this team deserves to lose. When both teams are good, it is very easy to stop these 1-2 highly skilled players. There are tonns of grenades, grenade launcher, rpgs and all of that. If a team can't stop 1 player(which is all by himself without his squad) with their whole Squad, then this team deserves to get stomped. Simply saying, Squad is about git gut or git rikt. And I love that this game is about it.
  2. Yes, that's one of the worst things that can happen to a game nowadays: when skills actually matter, you can't just jump'n'shoot with deagle or sniper rifle and still randomly get kills. I haven't seen as bad game as Squad(where so many skills actually matter at the same time simultaneously, and RNG almost non-existent and definitely non-relevant) since BF2 days. I mean, how dare they implement a game mechanics with so high entrance threshold / skill border(since BF2 days) and biggest skill gap(since BF2 days) between scrubs and skilled players, which encourages big time skilled players(aka nerds and no-lifers) and punishes very badly noobs, scrubs and lamers. They should make so random game mechanics, that any random noob from CS/CoD/Cattlefield/ArmA/anyothermainstreamseries should be almost as good as nolifer with 2000 hours in Squad, just as Valve did in CSGO.
  3. You mean, like, getting revived in 3 seconds after literally getting RPGd in the face 10 seconds before? When you say 'realistic' you mean things like that one, right? This game is awesome but has nothing to do with realism or anything like that. And it is a very good thing. I am more into games BF2 alike(Squad is very BF2 alike): revives, vehicles, grenades, sprint system, health system, heal system, move system, game mechanics and a lot of other things. What does that even mean? What's your point? You go try to take a vehicle and be actually effective with it. Well, if you have read patch notes, actually knew this game, or at least read my previous posts, you would know that there can be only one heavy AT in a team even if you have 46 players in your team.
  4. I like this one. It makes optics hard to use, unlike in other games. And once you're able to master it(and yes, you can master it), you can rock on it, just like in good ol' BF2 days.
  5. @beginna, nice, thanks. I've read that it compulsorily and forcibly enforce users to use latest drivers. Can I use older drivers if I install Experience? Never really used it myself because of ADs, registration, additional services and processes in the system...
  6. Did you actually count it? I personally did, on Firing Range(when you actually know that other vehicle starts with 100% HP left). And it does match to the numbers in that spread sheet. It's like when there is a scientific proof of Earth being in a form of ellipse but then you come and say:"From what I've seen while traveling is that Earth is flat".
  7. Try 372.90 NV drivers and 16.300.2311.0 AMD drivers depending on your video card.
  8. Why are you providing videos from real life? Squad has nothing to do with RL. It is an arcade-ish hardcore teamplay-oriented video game. Randomly getting behind a vehicle with instakill weapon has nothing to do with teamplay, hardcore or arcade. It is just lame and casual, that's what it is. And before someone said something about instakill machine guns on vehicles, I am against it as well. Instakill weapons is an unofficial antonym of skill. You should be able to hit enemies at least 2 times if you didn't hit them in the head. When I wrote my previous comment it was 3 Tandems per team. And it was very easy to shoot at big distances. Now, of course, HATs are kinda balanced, with mines and IEDs, and all of that stuff, I like it, it is fair now. Well, you're right about them, but it isn't a story about me.
  9. I would recommend to use Driver Display Uninstaller to properly uninstall your current drivers first: It is pretty easy to use, just follow instructions on the website.
  10. Just found this based on your crash log: It is probably a hardware/driver problems. I would start with downgrading my driver version. Recommended AMD driver ATM is 16.300.2311.0: [GPU_AMD] // From OR-27051 as of 8/4/2016 is 16.300.2311.0 7/18/2016 (Crimson Edition 16.9.2) SuggestedDriverVersion="16.300.2311.0" // From OR-27051 +Blacklist=(DriverVersion="==15.300.1025.1001", Reason="Crashes with Paragon content using more recent GPU features") // 14.301.1001.0 - are the AMD drivers that seem to be causing crashes when we try to compile a compute shader. +Blacklist=(DriverVersion="<=14.301.1001.0", Reason="Crashes with Paragon content using more recent GPU features") I think I would start with 16.300.2311.0. If problem continue to exist on this driver, I would probably install next driver which goes after 14.301.1001.0 and would try them one by one, one after another till the recommended 16.300.2311.0 version. While also trying to fix this problem using other methods... Make sure you have your video card plugged into 16x PCI-e. To do that you need to open manual of your motherboard and see which PCI-e is/are 16x and which are 8x/4x/1x. Or sometimes they mark it on the motherboard itself. Make sure both 8-pin connectors have good connection with a video card. Sometimes people get this kind of problems because of dysfunctional PSU. So if you have multiple PCs, try changing PSU. I would also try switching RAM to other slots and connect different pieces by themselves(one a time). I personally sometimes get similar errors in Squad when I overclock my RAM too much(same with VRAM). Do you have anything else plugged into PCI-e slots? Disconnect all hardware and software devices you can and try to play Squad like that. You want as little amount of variables in your equation as possible. I would also try to downclock core and memory clocks on the video card. Maybe increase voltage by 1 step. Sometimes even something wild as changing from HDMI to DVI or changing any other type of interface to any other type of interface helps. The thing is all of these techs is a one big glitch. Problem can hide anywhere, sometimes it is even refresh of your monitor xddd. Good luck!
  11. Just another wild guess, launch task manager(or any other process manager), open Processes or Details tab(depending on version of your Windows) and close all programs which could have overlays or anything like that. Turn off antivirus and firewall. Try to close as many programs as you can. Perfectly you should have Steam and Squad running, everything else which didn't come with Windows should be closed. I had similar problems as you in different games(including Squad). And often it was this program which was trying to hook another program and bullshit like that.
  12. @Nikko B, yeah, that's a very nice idea. Never thought about it myself.
  13. In a9 all of my screenshotting software stopped working. So far I tried MSi Afterburner, ShareX, Dxtory, Greenshot, Fraps, Overwolf, PlayClaw. Programs themselves work in all other games. But right after I updated Squad to a9, it stopped working properly. Different programs give me different results when I try to make a screenshot in Squad: MSi Afterburner says Screenshot captured but doesn't create a file in needed folder: When I try to use Dxtory, literally nothing happens when I press a button, same with Fraps, Overwolf and PlayClaw. When I try to make screenshots using Dxtory and Greenshot, it makes files with black rectangles(1920x1080) instead of screenshots. But sometimes randomly it does make proper screenshots. One more thing worth mentioning is that pretty much all other functions of listed above programs work in Squad. Overlays of Afterburner, Fraps, Overwolf and PlayClaw work in Squad. Video recording of Afterburner, ShareX, Fraps, Overwolf and PlayClaw also work in Squad. The only function that doesn't work in Squad is screenshots. I can't use Steam, because Steam overlay affects my FPS in Squad. Problems with overlays, making screenshots and recording videos started the moment they implemented EAC(a6 point something or whatever). And this time screenshots stopped working after the update of version of EAC. I'm pretty sure this problem exist because of EAC blocking access of these programs to the Squad. I don't know how to launch Squad with uninstalled EAC(it doesn't allow to start the game with uninstalled EAC) to test if it is actually a problem with EAC. Anyone knows any screenshotting software which actually work in Squad? Do any of listed above programs work in Squad for any members who read this?
  14. There is a log when your game crashes now: When you press on click here to view directory, it will open a directory with log files. If you post Squad.log here in text(hidden under the Spoiler, obviously) and post all files from that directory(CrashContext.runtime-xml, CrashReportClient.ini, Squad.log, UE4Minidump.dmp), then just maybe someone will be able to help you with your problem. You can also post text of files located at %localappdata%\Squad\Saved\Config\WindowsNoEditor. Post files in text hidden under spoilers and files themselves. It will take some time to do all of that but that's what you want to do if you want your problem fixed. I would also install another version of Windows real fast on another HDD and tried to play the game to see if problem still exist on clear version of Windows.
  15. Make sure you have your speakers set as default: And also make sure that when you press Configure you have "Stereo" chosen: Do you have USB headphones or you're using your built-in sound card? Describe your sound system.