Wow, you guys are still banging on this?
The lack of response after months and 1000's of replies should be a huge clue that they aren't interested in fixing the problem.
The fact that there are exploitable config options that would be dead easy and seriously take minutes to fix (they already filter "dev_console", "novid", etc, adding an entry to the filter would be trivial) still in the game should tell you how motivated their programmers are.
I personally got tired of waiting and lucked out on a cheap system. The real rub is, Apex isn't CPU bound at all, the only time it taxes my CPU in any way is with lots of particles/physics happening. How do I know this? The CPU I now have is an Intel Core i3 3225 dual-core, which is actually 20% below their stated min. spec, and the game runs great. Power wise, the i3 is almost exactly equivalent in power to my previous (unsupported) quad-core CPU that didn't support the unneeded instruction set.
You're seriously kicking a dead horse here. Based on their reaction time to fixing the bugs for those who can run the game, it's going to be a loooooooooooooooooong time before they even consider removing the requirement and possibly having to optimize their code somewhere. Like I mentioned above, adding a simple string to their config filters to prevent ACTUAL EXPLOITS is already too much for them to handle.
