Get a new PC. Anything below GTX 1090 is trash

How nice of you to write nonsense. To bad the developers did not know about the GTX1090 when they launched the game in 2014.

Originally posted by schwollenheit:

How nice of you to write nonsense. To bad the developers did not know about the GTX1090 when they launched the game in 2014.

Facts hurt man, I'm sorry. I own a GTX 1060, & it should run this game with little to no problems, but for some reason it just can't load certain files, especially particular files in ROBZ that I can't pinpoint. What sucks even more is that these Vertex-errors can happen at any given time, especially during multiplayer. For example: The map loads, & it gives you the vertex error as soon as it finishes. Even worse is when the crash/vertxbuffer Error occurs in the middle of a multiplayer game, which I understand is absolutely infuriating.

The most help I've seen the developers give is "lower your graphics" or "Deactivate the mod", yet, you & I both know we shouldn't have to. Whats even more pathetic is that my old Dell Laptop(Which was a potato) never got those kinds of errors, which is Ironic. THIS game should be able to run better on a GTX 1060 Nvidia(The new PC I use now), but nooope. It will run smoothly in terms of framerate, but will crash at some point. Wheather that be as soon as the map loads, or a middle of a game.

I'm going through the same problem you are right now. The devs ceased supporting "low" end PC's awhile ago. Keep in mind they update the game constantly. I think not to long ago they gave the game another update which damaged it further. Overall, ROBZ is extremely unstable as of late, its why a lot of people are putting MOWAS2 on the shelf and moving to Call to Arms. Believe me, I don't agree with them in any way. I personally believe they should fix this issue, rather than giving it a cold-shoulder.

Overall, in conclusion, this is more of a Windows10/Microsoft issue. Microsoft, for some reason, doesn't like Asus or the GTX 1060 or below, so its locking certain files and refusing to allow the user to fix it...yet for some reason, it grants more freedom to garbadge Dell laptops. It really only supprts GTX 1080's & 1090's. So unless somebody gives this problem more attention, it will be unresolved.


((PS: I noticed this error in particular gets ignored on a daily. And the one's the do get answered are usually consisting of the Dev's(Basically) saying your PC sucks & that you should lower your graphics. I even saw them lock a thread over it. I personally think they just want a richer playerbase with ultra high-end PC's that can cash-in more money for DLC's, so they're starving out assistance to players with "inferior" PC's, because they're less likely to buy said DLC's. It sucks, but thats bussiness for you. Overall the devs are not bad people, I just don't agree with how they handle the new influx of errors.))

I do not think the developers would be able to make the game work on 1090 either. Either you know how to, or you do not. Crying for more capacity is lazy programming. Look at what the guys that coded Quake had to work with. They had to churn out maximum with limited resources.

Quake made the programmers into diamonds on those platforms.
1090 and above only creates coal dust programmers.

Originally posted by schwollenheit:

I do not think the developers would be able to make the game work on 1090 either. Either you know how to, or you do not. Crying for more capacity is lazy programming. Look at what the guys that coded Quake had to work with. They had to churn out maximum with limited resources.

Quake made the programmers into diamonds on those platforms.
1090 and above only creates coal dust programmers.

We'll just have to wait and see if a solution comes up. But for now, its best to gamble and HOPE that you don't crash. That's what i'm doing.

same problem, the game was working on my old potato pc, but not on my new gaming laptop

Originally posted by tiennou:

same problem, the game was working on my old potato pc, but not on my new gaming laptop

Turns out it's a RAM and coding issue on the dev's end. If the game detects any sort of inconsistency, it just out-right crashes instead of bugging out or lagging, of which it can do both of but not very commonly(It prefers to just die or desync).

It's an older x32 type-game that suffers from the same issue as Oldrim(OG skyrim.) It can only handle so much before it overloads from the ammount of data being processed.
The only way to prevent it is to lower your graphics. If the game doesn't agree with your PC that's just the way it is; It doesn't matter how beastly it is. It's not your fault and there's really not much else you can do about it.

can it be with dx11? What inconsistency can it be? adding some virtual memory can be a solution?