• Content count

  • Joined

  • Last visited

About DaiaBu

  • Rank
  1. Thanks beginna. Link to my latest log file: http://s000.tinyupload.com/?file_id=72338842725051782838 And to the .dmp file: http://s000.tinyupload.com/?file_id=06557334621385887743 I will forward all of the above details to the Squad support email and link to this thread. Many thanks for your help
  2. Oh, apologies - just after posting this, I see someone else has posted a thread with almost the exact same symptoms as me: http://forums.joinsquad.com/topic/28355-crashing-with-no-error-message/ Should I instead just forward all this to the email in that thread ([email protected]), along with my log files? Perhaps if this is affecting other users there might be something to investigate for the devs. Apologies if I've broken the rules by posting a similar issue, not sure how I missed the other thread
  3. Hello all, Bit of an odd one this. Whilst playing this morning, my game crashed back to the desktop, but there was no error, or any sign that it was going to crash (freezing, stuttering, etc) - it just closed down instantly and with no warning, as though I'd hit Alt+F4. I had probably been playing about 20 minutes or so. I restarted no problem, and rejoined the same server. All seemed well, then after about another 10-15 minutes, exactly the same thing happened. I restarted again and cleared my app data (haven't done that since the update). Joined a different server, and was able to play for a good couple of hours, so I figured it was just a data issue. But then, about 10-15 minutes into an Insurgency round of Chora, it happened again - just as the SL was throwing an incendiary into the cache in front of me. I have kept the log file from the second time it happened, and from the most recent time. In both cases, it appears to have been a fatal error relating to "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address...." I am running an overclocked CPU, however it appears to be completely stable. It's done a couple of Prime95 runs with no issue, and the temperature maxed out at 70 degrees while playing - warm, but nothing to worry about, and it hit higher peaks while running Prime for longer periods with no issues or errors. If it's of any relevance, the first crash happened on Chora, and the second was Logar Valley. Between those crashes I played full rounds on both Operation First Light and Narva - I only mentioned that in case perhaps there's an asset in the desert maps which might have caused the failure. Anyone have any ideas? I've saved the log files in case they are any use. Below are extracts from the final part of each log where the Unhandled Exception was recorded. Happy to share the full log files if needed. System specs: CPU: Intel i7 3770K 3.5GHz (OCed to 4.2GHz @ ~1.170v) GPU: Radeon RX480 RAM: 8Gb Kingston DDR3 @ 1600MHz Mobo: Asus P8Z68-V Running on Windows 10 64bit @ 1920x1080p. Performance is generally good (~50FPS) Using ReShade with a SweetFX filter, but have been using this for months with no adverse effects. Any help appreciated. First occurrence: Second occurrence:
  4. Suggestion speed limit key

    I think you might have misunderstood the OP. He's talking about the ability to better control your own speed on the fly, by capping it at a maximum - not capping the speed of every vehicle in the game permanently at walking pace. At the moment, using a keyboard key to accelerate, you are either accelerating at full throttle or not at all. If you want to drive at less than maximum speed, you have to keep "pulsing" the accelerate key, but that's hardly realistic and rather irritating. The OP is suggesting that it would be handy to have a way to cap your speed at a given maximum, so you can roll forward at walking pace even when holding the accelerate key (W), making it easier to provide rolling cover for infantry, for example. Red Orchestra got around this by allowing you to have an incremental throttle in the vehicles. Hold the key down and the vehicle starts to accelerate, but take your finger off the key and you stop accelerating but keep moving. If you want to decelerate, you hold the brake until the speed drops to the desired level. It meant you could better control your vehicle speed, rather than having only a digital on/off control for what should be an analogue, gradual input.
  5. Graphics look colorless / dreary

    I also found that Squad looked a bit "washed out" at times, so I installed a ReShade/SweetFX preset which has improved the vibrancy brightness of the colours. I did the same with Rising Storm 2. Both are much prettier games with SweetFX in my opinion
  6. AK74 vs M4/16 Recoil

    I hope so too. I've found the same thing with the AKs - the sights being so far away feels very weird and makes shooting (especially at any sort of distance) quite difficult. It applies to all sights in the game, it's just not as much of a problem with the M16's red dot.
  7. Hi all! Been playing this game for a couple of months now, and really enjoying it, so decided it was time to join the community, sign up on the forums and stick my two pence in The game is fantastic so far, so good that I often forget it's still in the alpha stage. And seeing the trajectory the game is taking, it's kind of hard to think of any meaningful suggestions. However, I wanted to share a couple of small things in the hope that they might get picked up. These are by no means big changes, but little things that I think might make general communication and usability easier from my personal experience. Compass Heading The compass is essential for communication in this game as we all know, for spotting enemies. My only suggestion is - can we make it so that your current heading is offset slightly above the rest of the compass bar? At the moment, the current heading is slightly larger than the rest of the bar, however in the heat of a firefight when trying to call out an enemy vector, I sometimes find it a little difficult to recall the current heading with only a quick glance. If the heading was raised up slightly, I think it would help draw the eye that little bit quicker. VOIP Indicator When someone says something over radio, or voice, then their name appears in the bottom left hand corner, so you know who's talking. The problem is, as soon as they stop transmitting, the indicator disappears. This isn't always a major concern, but a few times I have been in the situation where someone says something and by the time I've looked to see who was speaking, the indicator has disappeared from the screen. Obviously in real life, this isn't a problem, as you're likely to be able to identify your squad mates by their voice alone; but in a game where you are often playing with people you don't know, I think it would be handy to know who said something without having to ask them to repeat themselves. My suggestion is, rather than the indicator disappearing immediately, have it fade out slowly. It doesn't have to stay long - just a second or two after they've taken their finger off the transmit key, which gives you a fraction of time to flick your eyes down and check who spoke. In addition - I'd also suggest adding an indicator to the names above each player. Last night I was in a game where I was following 3 or 4 other players as we entered a compound. They were all in front of me, so when one spoke, I couldn't tell who it was without looking down. If there was also an indicator on their name, I'd be able to tell who was talking without taking my eyes off the centre of the screen. I know these might sound like trivial changes, but I often think it's the little details like this which really help with the immersion and make your interaction with the game feel a little more natural. First post, so be gentle. I go by this name in the game, so I guess I might see (or already have seen) some of you on UK servers