How exactly would LoS calculations be based on your internal clock?

I know the rnd() function is based on your internal clock but I thought that the LoS function appeared to act randomly. I wasn't aware it actually was random.

Collision date and height should be available client-side. By pressing 'L' you show collision areas so obviously that date is present client-side and it would be impossible to draw the terrain without knowing the height.

The exact format could be different and in this case it would need to be converted which could take some work but all in all I don't see how it would be a large addition.

In addition to that I'd rather have an indicator that was sometimes out of sync then no indicator at all. Even with an out of sync indicator you eventually develop a better feel for the system and when it does hit and when it doesn't. Without an indicator this would be much harder.

To clear things up. LOS is not based on your internal click, I was using it as an example. Where the server and the client run their own code. The "Server" time you see is not the real server time. That I would like to see resolved.

^^ this ^^

That's exactly what I mean.

A visual indicator saying: If you shoot right now you're going to miss because you don't have LoS. Or: If you shoot right now you may hit because you do have LoS.

If you don't manage your movement and attacks around it you'll fire wasted shots. It won't stop your auto-attack. It will merely change colour and nothing more. If you decide to ignore it then things will be as they are now.

But if you're smart you'll press space bar when they turn cyan to temporarily cancel your attack and then push it again when the marker goes green again.

As to the lag comments, what does it change really? If I zoom in 100% to nearly 1st person view and use that to manage my attacks I'll still have the exact same problems when lag hits of it looking like I can hit but still missing because we both moved by the time the package hits the server.

Hell, the exact same thing can happen when looking at the distances on your landmarks. If you have lag then they won't be right. Does that mean we should remove the distances and replace them with: "Very Near" "Near" "Kinda Near" "Kinda Far" "Far" and "Very Far"?

If you have lag then information on your screen will be incorrect, regardless of this change. You'll still lose your locks when working near max lock range, you'll still miss even though everything looked like it would hit, you'll still die even though it looked like you had just enough armor left etc.

All this change would do is make it clear when exactly you're on one of those "Turrets don't work here" slopes without wasting tons of ammo while moving around to find that single spot that does work.

All it does is add a visual indicator for the LoS mechanic. Just like we have a visual indicator for the range mechanic ( the distance on your landmark screen ), a visual indicator for having something locked and a visual indicator for being locked. I don't think they make the game easy or even easier. They just make the game sensible and a lot less frustrating.

Or you the player could look to see if your shots clear maybe? Just saying... its not hard.

This is basically why I suggested it.

There's a handful of situations where there currently just aren't enough visual clues to whether or not you'll hit. If you're in one of these you can of course just try and see. So you miss and you move around a bit, but often the terrain in which these situations happen isn't confined to a few square meters. It's a larger area, so once again you're in the situation where there aren't enough clues as to whether or not you'll hit.

It's not about missing your shots. It's about it being clear why your shots missed. Sometimes when you see 95% of a robot it's still not enough and you miss. Yet sometimes when you see less then 75% of it you still hit.

It's like using module when you have 100 Accumulator and getting the error that you don't have enough yet when next time it cycles and you have just 50 Accumulator left it goes off just fine. It's frustrating not because the module doesn't go off, but because you're just not sure when it will and when it won't go off.

Well there is a slight desync between your clients and the server probably.

A lot of the time I have a second character in tow and it will look like they just ran through a plant. So there is certainly a difference between where the client shows a character and where it really is.

Maybe once you enter combat the server updates position more often and more precisely, but it wouldn't surprise me to find that the hit-or-miss on the obstacles was due to desync as Shadey said.

If this is the case, and they can't 'fix' the lag, then there should be some kind of LOS indicator or players with better internet will have an advantage.

They seriously need to work out their line of sight system. It doesn't really involve skill at the moment it mostly involves luck. I'm not talking about that hill that's in between you and the enemy, yes you're sure to hit that, but sometimes you have a clear shot but you plow the ground. Clearly the given the inefficiency of the current system Pelilstal is the way to go.
Unless you like to play turrets online. Once you find a spot where you have a clear shot (after having wasting three quarters of your dps on grass), you stand there immobile, and it turns into a battle of who has the best tank.

Edit: Spelling; Tourettes online and others.

I'll edit for spelling.