p.s. I mean not noobs with kbm, i mean best players, they always better coz easy type of controls.

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?

some news would be nice.

The hotfix did not fix anything for me, using an IBM Keyboard and a Logitech Performance MX mouse.

Reading this thread, I get the same headaches I got when reading the SP cap threads.

The pounding headache caused by terrible solutions looking for a problem that doesn't exist.

The best solution to the SP cap problem was to not have a cap at all. If someone wants to grind all day, fine. That person is working hard for their rewards. But we had countless theorycrafters making up the most convoluted schemes imaginable, just because they want to keep dedicated players from gaining an advantage via their dedication.

Now, again, we have tons of people chiming in with more solutions in search of a problem. Cap it this way, gimp it that way, separate the the gun crosshair from the viewport! That's a lot of code whose only purpose is to attack people who choose a certain input device.

Much like other whining posts, these posts miss the obvious truth: If X is clearly superior, everybody would be using X.

Keyboards and mice combos can be had for $20 dollars, and everyone's PS3 has USB ports. So why aren't more people using this little "I Win" button?

But furthermore, assuming the KB/M is a superior controller choice(many top players would disagree), why punish the player who wants to work hard and master it?

This is just another example of people who don't want to put effort in the game trying to cripple those who want to improve their performance.

The real solution for this is to give players a proper control panel for input. Acceleration curves, joystick deadzones, bindings, turn speed, etc. Let everyone customize their own variables to maximize their effectiveness with their controller choice.

Any other solution will just result in more attempts by CCP to tweak the controls on the behalf of players, and more threads in response to the changes because, surprise, one size does not fit all.

The hotfix did not fix anything for me, using an IBM Keyboard and a Logitech Performance MX mouse.

Reading this thread, I get the same headaches I got when reading the SP cap threads.

The pounding headache caused by terrible solutions looking for a problem that doesn't exist.

The best solution to the SP cap problem was to not have a cap at all. If someone wants to grind all day, fine. That person is working hard for their rewards. But we had countless theorycrafters making up the most convoluted schemes imaginable, just because they want to keep dedicated players from gaining an advantage via their dedication.

Now, again, we have tons of people chiming in with more solutions in search of a problem. Cap it this way, gimp it that way, separate the the gun crosshair from the viewport! That's a lot of code whose only purpose is to attack people who choose a certain input device.

Much like other whining posts, these posts miss the obvious truth: If X is clearly superior, everybody would be using X.

Keyboards and mice combos can be had for $20 dollars, and everyone's PS3 has USB ports. So why aren't more people using this little "I Win" button?

But furthermore, assuming the KB/M is a superior controller choice(many top players would disagree), why punish the player who wants to work hard and master it?

This is just another example of people who don't want to put effort in the game trying to cripple those who want to improve their performance.

The real solution for this is to give players a proper control panel for input. Acceleration curves, joystick deadzones, bindings, turn speed, etc. Let everyone customize their own variables to maximize their effectiveness with their controller choice.

Any other solution will just result in more attempts by CCP to tweak the controls on the behalf of players, and more threads in response to the changes because, surprise, one size does not fit all.

CCP Wolfman - Can we expect a fix for Tuesdays downtime we desperately need it with the "full release"/planetary Conquest !

CCP Wolfman - Can we expect a fix for Tuesdays downtime we desperately need it with the "full release"/planetary Conquest !

A RESPEC OF SKILLPOINTS IS NEEDED BECAUSE OF UNDOCUMENTED APPLICATION OF THIS CONTROL SHENANIGANS AND MOUSE BECOMING USELESS IN SLOW TURNING DROPSUIT CONTROL.

The artificial turning speed cap makes most of the suits unplayable with twitch mouse. As a heavy, I need to hold back my aiming speed at 1/4 of my normal aim speed I have been refining for 20 years. If I aim fast with the mouse, the movement is registered as much slower. This design is frankly idiotic, but that's not my point in this post.

Because of this failure to communicate in advance these changes so that I would have known to spec into tank (where twitch speed aim is not used), I want a respec of all skillpoints.


When you want to go about fixing this, either revert back to Chromosome control scheme, or remove artificial dropsuit turn speed limits. The turn speed limitation is not a good game design mechanic. It adds nothing that would not be more simply and beautifully added by making a broader spectrum of dropsuit run and strafe speeds. Balance dropsuits by their run and strafe speed, not by the turning speed. This is not a mechwarrior game.

Now read this and respond, do not be offended by the harshness. You developers scammed me out of a PS3 purchase and multiple merc packs on multiple accounts which I would never have even given a thought to, had I known dust will drop its mouse support in release build.

1. We are looking at doing re-balancing of our AV weapons. One of the topics, which also seems to be showing through on this thread is to keep a decently long enough range on the forge gun, but also look at the damage decay variable over time on it, optimal ranges, etc. Because agreed, that it is a very potent anti-vehicle weapon and it's not exactly something that is easily countered with countermeasures (see next point). We also don't want the forge gun to be nerfed to the point of feeling ineffective, so a direct reduction of damage output across the board is not going to be the simple answer there.

ccp i have not played in the last 3 days do in large part because of the aiming problem so think we can get some info seeing as tomorrow is the 14.

Hi,

In answer to the question on the mouse sensitivity - it's being worked on currently. With the help of the forums we have identified the key issues and we hope to deploy a patch that resolves these concerns very soon.

As for keyboard remapping, we are working through a list of prioritised tasks and this feature is among those. At this moment in time we are utilising all available resources to deliver a smoother Uprising experience.

* After some investigation we discovered that the sensitivity input curve being used by the mouse was incorrect. Despite new settings being present they were not being used. This issue requires a code update to fix and that is something we are working on as we speak. We will let you know when that is ready (this issue does not effect DS3 users).

* Related to that we found a bug with the mouse sensitivity input curve that is being used which resulted in some weird spikes when changing sensitivity. This occurs at settings of 20 and 100 and will be fixed once the above issue has been.

Don't forget that for each Mouse User, there might be multiple Eve accounts to be sold to, i know i run 3 Eve accounts on my PC and PC users pay a monthly Eve fee where as F2P people usually stick to F2P without even buying boosters.

If i had tried this game with this control scheme vs Chromosone, i would most likely not have returned to Eve and not bought 5 merc packs for my boosters.

I also convinced a couple of other people to do the same, in the end they will lose around 10 Paying Eve accounts & 3 payed Dust accounts by loosing the 3 Dust accounts due to Controll issues.

And i doubt we aren't the only ones.



Also touching this subject again, if you want to play like a couch potato and not be in any way competitive with other players that have fun, only when playing they competitive, its is entirely your choice but we should not be bubble wrapped, taped down to the floor, blindfolded, gagged and shoved up some spikes from the rear up, just so you can keep playing on your couch and compete with us.

This game was advertised to come with KB/M support and well since uprising it doesnt.

Hi guys,

WeGÇÖve just finished testing a further update to the aiming systems and we will be deploying this to you today. This time the changes are primarily focused on improving the DS3 controls but there are some little tweaks for the mouse in there as well. I have decided not to explain what has actually changed (yet) as I donGÇÖt want to influence your feedback. I will fill you in once youGÇÖve had a chance to play with them and shout praise/abuse.

In other control related news:

* We are looking in to whether or not the DS3 acceleration to max rotation speed is respecting the actual settings (thanks Sete Clifton for noticing there might be an issue here).

* After some investigation we discovered that the sensitivity input curve being used by the mouse was incorrect. Despite new settings being present they were not being used. This issue requires a code update to fix and that is something we are working on as we speak. We will let you know when that is ready (this issue does not effect DS3 users).

* Related to that we found a bug with the mouse sensitivity input curve that is being used which resulted in some weird spikes when changing sensitivity. This occurs at settings of 20 and 100 and will be fixed once the above issue has been.

Cheers

CCP Wolfman

Hi guys,

WeGÇÖve just finished testing a further update to the aiming systems and we will be deploying this to you today. This time the changes are primarily focused on improving the DS3 controls but there are some little tweaks for the mouse in there as well. I have decided not to explain what has actually changed (yet) as I donGÇÖt want to influence your feedback. I will fill you in once youGÇÖve had a chance to play with them and shout praise/abuse.

In other control related news:

* We are looking in to whether or not the DS3 acceleration to max rotation speed is respecting the actual settings (thanks Sete Clifton for noticing there might be an issue here).

* After some investigation we discovered that the sensitivity input curve being used by the mouse was incorrect. Despite new settings being present they were not being used. This issue requires a code update to fix and that is something we are working on as we speak. We will let you know when that is ready (this issue does not effect DS3 users).

* Related to that we found a bug with the mouse sensitivity input curve that is being used which resulted in some weird spikes when changing sensitivity. This occurs at settings of 20 and 100 and will be fixed once the above issue has been.

Cheers

CCP Wolfman