FPS and enemy accuracy

Fill me in on this, what was the issue before? Enemies ended up in effect being more accurate on low frames such as consoles rather than high frame rates set ups such as pcs? or visa versa?

I think that had more to do with the unreal engine and how it worked if memory serves correct. From what was previously said on the old forums, frostbite doesn't have that as a "feature", thus this game will be even easier for the PC scrubs of the world. 

You guys already have it easy enough with your mouse+keyboard and easy reloading cancelling.  Not to mention all the hacking that goes on from nothing but a bunch of awful cheats that use RHA.

Playing on 100+ fps anyone 😀

For those who don't know: In Mass Effect 3 when you were within line of sight of an enemy they would update where they were shooting with your new location every 15 frames. This didn't change regardless of what your FPS was, meaning on consoles which were capped at 30 enemies updated their aiming 2 times per second.

If you were a PC player playing at 60 FPS, they would update 4 times per second making them considerably more accurate. As you increased your framerate above 60 they got even more accurate.

In general a lot of engines tie things to the framerate because it's a convenient thing to use that doesn't change as drastically as the last thing we used which was CPU cycles(doing that is why playing older games on your modern PC might make them go 50x faster than normal speed).

I have to imagine that Frostbite probably uses framerate for a lot of the same things as well, although it's possible they added in additional code to make the frame interval dynamic so that rather than simply update every 15 frames it alters how often it updates based on your FPS in order to maintain the same number of updates per second on the AI accuracy.

Well for one thing you can use your mouse to look around as you are running, which you can't do on consoles.  It's nice.

Technically you can do this on consoles too, it's just very difficult without practicing daily finger yoga

With my right hand, sometimes I would move my use my middle finger to shoot/use right bumper while I moved my index finger awkwardly over the A button (sprint), and used the thumbstick normally to look around while sprinting. But yeah, most of the time it's just too impractical

Fortunately there is a solution for that.

Meh, we've had this discussion before. PC has much better controls.

I would be interested to know if cloak is more effective since enemies re-evaluate targets more often at higher fps.

While the enemies updated your location every 15 frames, the AI routine to re-evaluate targets was on the basic AI code and happened at the end of each action they took. In most cases, it would happen after they finished firing their current burst of ammo at you.

The issues with cloak's invisibility not working reliably is because of a few other factors:

1. Enemies will continue to shoot at the location where you cloaked.
2. If no other targets are present, the enemy will just cheat and look at where you are anyway. This cheating ignored both line of sight and cloak.
3. Enemies could hear you if you moved too close to them and start shooting at the location where they heard you.
4. Because of the re-evaluate code I mentioned above if you cloaked at the start of a burst fire against you, you would still have the entire burst fire shot at you and they would know your location until it ended and the re-evaluate code kicked in.

In general it wasn't really that much more effective on PC. The re-evaluate code might have triggered slightly faster after the current action finished since AI routines were checked each frame, but it would be a difference of 0.033 seconds vs 0.016 seconds.

This was just mean but I lol'd

Wondering if controls will be like in MEMP or DAMP.DAMP was almost impossible to play with K/M for me.

Well, badly designed games/engines do anyway. The proper way to do it is to tie the logic (physic, rendering, game updates) to the timing and have specific framerates set for each. Rendering runs at 60 FPS, physics at 10 FPS etc. and when a new frame is calculated, you apply the changes based on time passed since the last one.

Seriously, tying sh*t to the effective framerate on modern-day hardware should warrant a high five in the face. With a chair.

Thankfully, most engines and games do it the proper way by now with the odd exception every now and then (looking at you Need for Speed).

edit: Just to make things clear - I'm not saying UE3 is a bad engine. While I haven't used it much myself, I'm fairly confident that it provided proper frame timing for the devs to use. This one's almost certainly on Bioware, not Epic.