@Ronnie21093 imagine developing a proprietary software, paying a shitton of games to support it to hurt your competition, only to later drop support for it and have those games run like shit on your latest hardware
@Meemoo :cirno_stare: Why. There was no reason to drop support. It can't be that expensive on the cards (for a technology from the 2000s). Quite a large number of games used it. Who benefits from this? Marketing's already hit the bottom of the barrel on these things turning into personal heaters, why refuse to publicize ditching a tech that's so integral to some games? Gets worse by the day. :cirno_laugh:
@Meemoo@Iffine Oh fucking God, I just realized something. Good fucking luck running Arma 3 on this thing. Arma 3's physics engine is PhysX. :cirno_laugh:
@Meemoo@Iffine Never played Crysis, tbh. Also, tbh I don't know if Arma 3 uses a GPU or CPU version of PhysX, but I imagine it is CPU based due to Arma 3 being heavily CPU reliant.
I also have no idea about what kind of PhysX version Mirrors Edge and Borderland 2 uses. Do you have any idea?
@Meemoo@Iffine Alright, so it seems Mirrors Edge and Borderlands 2 use a GPU based PhysX while Arma 3 uses a CPU based version. Unless they fucked up THAT terribly that even CPU based versions of PhysX are fucked, Arma 3 should still run on that thing. :doge_laugh:
@Ronnie21093@Iffine oh you meant that. The games run a GPU based version yeah but if the GPU doesn't support it then the CPU bears the load but the games are poorly optimized in that front (again, to allegedly fuck with AMD) so you get the same result as the video
@Meemoo@Iffine I'm on an AMD CPU and GPU and Arma 3 works fine for me. Only time I get lag is when BEEEEEG stuff is happening, and usually even NVidia players also get hit with lag :doge_laugh:
Also, have you ever seen any Arma 3 videos where someone gets "Arma'd", which is being sent in a random direction VERY RAPIDLY? Yeah, that's the game's PhysX having a hiccup in calculations :doge_laugh:
@Meemoo@Iffine If you're curious, how it works is that PhysX is set to calculate the physics in cycles. Every once in a while (especially on servers) it will make a miscalculation in regards to where an object (vehicle or player) should be and the speed of said object. In most cases it will try to correct this by moving the object forward or backward a bit to where it *thinks* it should be, but on occasion it throws out such a high number that you're suddenly doing a tactical insertion to the other side of the map via flying vehicle or you're part of the Arma Space Program due to PhysX overcorrecting :doge_laugh:
@Meemoo@Iffine It is :doge_laugh: They *have* tried to fix it before, but it's just such a fundamental flaw in the physics engine that it is practically impossible to fix without rewriting the entire engine. They eventually gave up and made an achievement for having it happen to you :kekw: