#3 - Several ideas popped up - ie,

1. the alternate primary sphere can be delayed until 1-2 seconds become arming. If the bullet hits any surface, it'll merely bounce off.

2. start alternate the primary sphere small, then scale up over time.

#2 -

coz it's unarmed - when it's suddenly armed, it'll hit the mothership because it has a significant sized hit sphere. While this may be really good for simulating a flak hit, it's meh when it comes to travelling across the length of the mothership...

I'll need to think of another solution.

actually lol i'm going to hav a big problem with this particular flak ammo ...

coz already there's a solution to delay its collision active state - ie, by 300ms ... so once fired, it doesn't hit the mothership immediately.

BUT ... at certain angles it can go THROUGH the mothership (coz unarmed)

P.S. each barrel fires independently, and is destructible, rendering the particular turret inoperable. Will show more in its animated form this weekend.

It animates almost exactly like the good o chicago piano

Moreover, losing a barrel doesn't cause the destruction of the entire turret. It merely disables (temporarily) the turret partially or fully from being able to fire. That's until the new barrel respawns...

Therefore, since the system is already there - might as well use it to add a bit more depth to the game. Turret gunners MAY in the future request for the turret barrels to be replaced or upgraded to fire more powerful ammunition types...

The mechanics for barrels to be an independent "ship" object was made because it's just a flick of a switch - either way it had to be a ship object because only ships can "recoil" - not meshes - at least not coded that way.

P.S. for those who doesn't know what's a Chicago Piano - it's a term given to a ww2 1.1 inch AA guns installed on carriers like the USS Enterprise (CV-6).

P.S. The shake does NOT affect ur aim; nor does it shake distant objects in a way that is distracting... notice that the reticule doesn't shake?

Btw everything is off here. Reticule’s off. Aiming’s off. Firing doesn’t trigger a recoil animation when it should. Will need time to figure out.

so for my upcoming game, there'll be some context sensitivity when it comes to input ... hopefully it'll address the latency issue without the need to turn off V-sync ...

game's name is gonna change too :( but yeah ... thanks for the conversation.

but if u ask me - while it's legit for players to call it latency, they also have to recognize the unnecessary amount of load they're putting on their GPUs just for this ... actually this is ok until devs get blamed for poor optimization DUE to this ... lol

it depends on how the input polling is being done ... if the devs or the game engine puts it in the variable execution loop then the more it's called, the more "sensitive" the input will feel because it's acted upon almost every possible call

V-sync typically limits this call to the refresh rate.

for the discarded frames scenario... if it's 300 fps over a 60hz monitor - u'll only see the progress every 5th frame ... the rest are discarded, means u r actually seeing jitters but the high fps makes u think it's smooth. Just turn on V-sync and u'll see WHAT's smooth.

but back to input latency - i could set my thread to sleep for 5ms per poll, but whether or not the game engine can pick it up is another matter.

If u turn off V-sync, either, the extra frames rendered as discarded OR they tear onto ur screen; ironically disrupts ur sniping...