Unit responsiveness and visual accuracy

from AshesoftheSingularity Forums

So... hey, any chances we may have increased responsivness from units in this game or is it intended for them to have such a delay before reacting to your orders and starting off with so little acceleration?

I get it fits with the magnitude of each ship even though they look small from afar, but don't you guys believe it may be a bit overcompensated at the moment? specially for the smaller ones and engineers. Oh, boyt, engineers can sometimes be phsically painful to watch walking aound at the very start.

 

Also, a bit related: I've noticed there's a discrepancy between shots visual representation and their actual hit detections. When a unit fires, the damage is dealt a little after the projectile leaves the unit but considerably earlier than when it really hits the target. It not only creates a visual discomfort as it makes for harder learning of unit's damage dealing potential. It's very hard to determine the amout of damage being delivered by each shot.

4,064 views 3 replies
Reply #1 from AshesoftheSingularity Forums Top

You are right, multiple threads have been created on this subject, and ive supported for increased responsivness in every single one of them,

 

About the discrepancy, from what ive noticed its more the actual shot or projectile taking time to do damage rather than it doing damage before it hits.

Lazers for example, in theory a unit should already be dead but its being targeted by 10+ lazer units, its only after awhile that it receives damage and explodes.

Turrets, they shoot their projectile, the projectile hits, and only after awhile will you see the hp for a unit decreese on the tooltip.

Im not sure if this is a latency issue? or some kind of performance trick to help in rendering explosions and unit deaths. But whatever it is this seems to create an overkill issue on a lot of units, which is something armies and meta units dont even manage properly, and i doubt they will ever will.

 

 

TouchTasks - Access tasks with ease on Windows touchscreens.
Reply #3 from AshesoftheSingularity Forums Top

When long press has been bound on a button for a secondary function, you cannot have the button act on press, and it has to be delayed to release to prevent the primary function occurring when the secondary function was intended.

 

When the camera pan controls are changed to MMB to pan, the RMB long press secondary is no longer needed so the behaviour could be changed for clicks to register on press.