Jump to content

hatbuster

Member
  • Content Count

    9
  • Joined

  • Last visited

  • Medals

Community Reputation

1 Neutral

About hatbuster

  • Rank
    Private
  1. hatbuster

    Low CPU utilization & Low FPS

    I just installed Catalyst 13.3B2 and set the prerender limit to 1. Not sure what of those two things did it, but my CPU usage went quite a bit up, spiked over 50%. Not bad on an Octacore. Improve on the threading a bit more and I'll love you, BIS :3
  2. The problem is not the scripting. Or Anti-Hack. It's the Netcode Arma 3 uses. Just like in Arma 2, and unlike other games, the server does not make all the decisions. Clients make these, too. So when the Client says "AND MY AXE". The server is gonna be like "oh, my bad, must have forgotten about your axe" and not do anything about it. That is also why the Netcode was completely rewritten for Dayz Standalone. Maybe Bohemia learns from the experience with DayZ and eventually implements this in Arma 3. Who knows.
  3. @Flash Thunder I have a feeling it's closer to millions of lines! Back to the topic, however: The reason "alpha" is not an excuse for the piss-poor performance is because of they reason behind it: Poor Threading. Threading is hard. But it is core engine work. Modifying the engine gets harder and harder the more stuff you add to it, since you have to redo more code. Thus, this kind of work has to be done sooner and not later. One might even argue that you'd want the prototype to have better threading than we have currently. Blatantly stupid AI? That's fine, that's something you can fix later. Game constantly crashing in MP? Sure, they'll find the cause with the thousands of reports. Indestructible windows? Surely just not implemented yet. But the underlying technology being unable to cope with the scale of the game? No. That's something that should have been addressed earlier. And now we whine about it. Because the more people whine (aka upvote the issue on the tracker), the more pressure we put on BIS to actually do something about it.
  4. Hahahaha. oh wow. Just because they call it new doesn't mean it's new. I bet they worked a lot on it, sure. But you don't get the word "new". By no means is the Disrupt engine built from the ground. It branches from the AC engine. How do I know that? It's easy. A.) It shares a look and feel with AC. Movement works in much the same way, clothing reacts in a similar way, collision is the same, pedestrians act much as they do in AC. B.) The game is close to AC in what it does. It would be a colossal waste of money to build a new engine from the ground up to do almost the same thing. C.) Developing a completely new engine with a feature set this large would take way more time. If they had done that, you probably wouldn't even see any footage of the game yet. Sure, they overhauled the renderer amongst other things. But it's not completely new. They recycled old stuff to make this. And that's good. Because doing it any other way would take far too long and be far too expensive.
  5. You don't create new engines. Ever. Unless you do small-scale projects like minecraft. I agree, however, that multithreading needs to be improved a LOT.
  6. hatbuster

    Major Texture Troubles

    Try setting video memory to "default". I remember reading that "very high" sets it to a fixed value but "default" just uses as much VRAM as possible, and by that possibly exceeding the "very high" setting. If that doesn't work, just flush every time it happens, I guess.
  7. hatbuster

    Strange grass with ATOC

    It renders in the same way for me, I guess the Alpha to Coverage implementation is just not very good. As an alternative, try oversampling! Just disable all AA and set the 3D resolution much higher than your interface resolution. That way you'll get some smoothed edges without any of these weird glitches, at the cost of performance, though.
  8. Hey there, everyone I've noticed a problem with how the game detects the sound system setup. I'm running a 5.1 system and everything is set up correctly (meaning it works with every other game just fine), HOWEVER: I use 2 sound cards: 1.)Onboard for my Headset 2.)Creative XFi Gamer for everything else For the longest time I didn't have more than stereo audio in the game and it was highly annoying, now I found out what causes it: The onboard sound is usually set as standard communications device, the XFi as standard device. That's how it should be, that's how every program knows without me doing anything where to put out sound and from which microphone to record. Setting it like this, however, results in only stereo sound from Arma 2 OA. To get 5.1 to work, I need to set my XFi both as standard AND standard communications device. That is obviously faulty behaviour and I'd be very happy to see this fixed, since proper directional audio obviously makes a huge difference and this fix is in no way rational nor findable on the internet. Thanks in advance HatBuster
  9. hatbuster

    Battleye Virus

    Just disable Avira and update BE, it's obviously a false positive.
×