DUST Search - Sticky:Aiming and control system in general

5aEKUXeRJGJ27kCDnDVYak5q wrote:

1. Turning limit. WHY? this is an FPS, not an RPG, I understand you guys have put in the whole turning limit to mimic the orbit/tracking mechnism in EVE so that heavies will "turn slower"... but you have stepped out of your line. The moment you touch basic things like aiming speed, you have stepped on the toes of the FPS players and into the boundary of "too much". This is an FPS first, don't turn it into an "RPG".

Suggestion: (strongly suggested)
abandon the whole concept of "turning speed limits".

Alternate suggestion: (something you could do if you have the time)
have two "cursors", one is without speed limit and will move the camera without delay, but there will be a separate crosshair that controls the gun aim (this will also affect the gun model) will slowly "catch up" within its speed limit to where you are looking at (the first cursor). This way you get to preserve your game design concepts (slow turning for heavies/turrets) but won't make the game feel laggy.
TLDR: control->camera without speed limit, but the gun aim will follow with their own limits. (so if you turn very quickly 180 degree, your camera will turn very quickly without any speed limit, but you will see your gun turning slowly to catch up. If you fire within this catch up period, you will effectively see the gun spraying bullets along a trail as it tries to go to the centre of the camera.

2. Mouse control simulating joystick - just don't.
Mouse users need raw input. Period.
This should be the benchmark you guys should aim to achieve. http://www.youtube.com/watch?v=Ckv95eHdzTY
My point is that you need the LEAST amount of filters/smoothing/whatever be applied to your input.
We want RAW input to camera control, nothing more. This should be a top priority in your game design because this is what allows the FPS skill game to be present in your space MMORPGFPS. You don't mess with the basic FPS mechanics.
The control input to output should be perfectly linear (no acceleration, no smoothing) because this is where the skill game is at. <---this also applies to controllers. take away your smoothing and acceleration bullshet.

3. Framerate / performance issue. This influences the aiming. Fix this ASAP. First you need a high framerate. Secondly you need a consistent framerate.

4. Hitboxes detection. Nothing I can add to, just fix it. How can it be messed up in the first place?


Author	Thread Statistics \| Show CCP posts - 5 post(s)
fred orpaul The Tritan Industries RISE of LEGION 271	Posted - 2013.05.13 01:15:00 - [1] - Quote 5aEKUXeRJGJ27kCDnDVYak5q wrote: 1. Turning limit. WHY? this is an FPS, not an RPG, I understand you guys have put in the whole turning limit to mimic the orbit/tracking mechnism in EVE so that heavies will "turn slower"... but you have stepped out of your line. The moment you touch basic things like aiming speed, you have stepped on the toes of the FPS players and into the boundary of "too much". This is an FPS first, don't turn it into an "RPG". Suggestion: (strongly suggested) abandon the whole concept of "turning speed limits". Alternate suggestion: (something you could do if you have the time) have two "cursors", one is without speed limit and will move the camera without delay, but there will be a separate crosshair that controls the gun aim (this will also affect the gun model) will slowly "catch up" within its speed limit to where you are looking at (the first cursor). This way you get to preserve your game design concepts (slow turning for heavies/turrets) but won't make the game feel laggy. TLDR: control->camera without speed limit, but the gun aim will follow with their own limits. (so if you turn very quickly 180 degree, your camera will turn very quickly without any speed limit, but you will see your gun turning slowly to catch up. If you fire within this catch up period, you will effectively see the gun spraying bullets along a trail as it tries to go to the centre of the camera. 2. Mouse control simulating joystick - just don't. Mouse users need raw input. Period. This should be the benchmark you guys should aim to achieve. http://www.youtube.com/watch?v=Ckv95eHdzTY My point is that you need the LEAST amount of filters/smoothing/whatever be applied to your input. We want RAW input to camera control, nothing more. This should be a top priority in your game design because this is what allows the FPS skill game to be present in your space MMORPGFPS. You don't mess with the basic FPS mechanics. The control input to output should be perfectly linear (no acceleration, no smoothing) because this is where the skill game is at. <---this also applies to controllers. take away your smoothing and acceleration bullshet. 3. Framerate / performance issue. This influences the aiming. Fix this ASAP. First you need a high framerate. Secondly you need a consistent framerate. 4. Hitboxes detection. Nothing I can add to, just fix it. How can it be messed up in the first place? 1)turn limits are fine but should be hard limits not the current scheme of you can always go faster you just have to stick a belt sander under your mouse/fry your DS3 with high voltage w/ sensitivity maxed. Yea I know that its probably asymptotic(not to mention the controler fail limits mean all that would be pointless) but that's the feeling you get and it just feels stupid. 2)100% right! mouse users don't want any thing but raw, we go to extreme lengths to defeat windows and hardware acceleration and input modification, there are websites dedicated on how to get the most raw and therefore the most *reliable* input from your mouse, this is why the mouse, despite its obvious limitations and the plethora of far better/comfortable and more immersive controllers out there, has been the control of choice for PC gaming for so long the reliability and repeatability of the control scheme(its the closest you can get to controlling the game with your mind). As I said above I don't mind turn limits but controller input should mimic mouse movement 100% up to a hard speed limit. 3) yea could use some love but I've dealt with worse 4)is there any chance that your use of instant hit weapons is actually making this worse?? could a non instantaneous bullet speed actually allow you to compensate for the lag introduced by server side hit detection?? honest question I know nothing about it, but I can't shake the thought that bullet travel while it might be more processor intensive might allow for smother game play, ignore me if I am wrong..