Project Reality Forums

FFG wrote:You want the bomb to continue to the target without the laze on the target? lol no

Ever heard of inertial navigation backup?

He wants it to basically go back to where you can kill the spotter and it doesn't matter.

No. Like Fuller said, no sticky lases anymore and the bomb would only continue on its last trajectory. LGBs in PR generally take quite a while after being dropped until they are going on a straight trajectory towards the lase, so the bomb would only hit the target if the enemy fails to suppress/dispose of the spotter earlier than right before the bomb impacts.

This is still a long way from before, where someone could get sticky lased, dispose of the spotter right after, but a jet could drop a bomb many seconds later and still get a hit.

DogACTUAL wrote:Ever heard of inertial navigation backup?
No. Like Fuller said, no sticky lases anymore and the bomb would only continue on its last trajectory. LGBs in PR generally take quite a while after being dropped until they are going on a straight trajectory towards the lase, so the bomb would only hit the target if the enemy fails to suppress/dispose of the spotter earlier than right before the bomb impacts.

Fairly sure the engine won't allow this. Also, doesn't really seem fair, might as well just go back to old sticky laze system.

Are you sure it isn't like this already? I got killed while spotting for a bomb on the way a couple of rounds ago and my medic confirmed the bomb hit the proximity of the target.

PatrickLA_CA wrote:Are you sure it isn't like this already? I got killed while spotting for a bomb on the way a couple of rounds ago and my medic confirmed the bomb hit the proximity of the target.

Yeah from what I recall, the projectiles should just keep going straight (operating with whatever gravity/propulsion they have) unless they suddenly lock on to someone elses' laze in a different area which would make it seem like they went "crazy" when the spotter died.

Can't confirm though.

Tested it two times, from what i can see if the lase dispappears the bombs go ballistic again. LGMs seem to continue on their last trajectory though.

[R-DEV]Psyrus wrote:Yeah from what I recall, the projectiles should just keep going straight (operating with whatever gravity/propulsion they have) unless they suddenly lock on to someone elses' laze in a different area which would make it seem like they went "crazy" when the spotter died.

Can't confirm though.

Bombs have gravity so they will start falling short if laser disappears. Missiles usually have no gravity so they will continue to the last location of laser.

[R-DEV]Mats391 wrote:Bombs have gravity so they will start falling short if laser disappears. Missiles usually have no gravity so they will continue to the last location of laser.

That makes no sense. Bombs have gravity during all the trajectory, guided or not. Or are you talking in-game gravity?
Anyway, once a bomb follows a stable trajectory, if the laser input disappears, a inertial guided system takes over, guiding the bomb to the last laser position. This system accumulates error with time, and obviously, can't correct the target's movement. So it's pretty much like the current setup, but more realistic, and it punishes targets that don't move after disposing of the spotter (which is the reason why you'd mount it on a bomb).

Now, I'm unsure about the state of the art of the PR implemented LGBs, but since an inertial gyro system is old and cheap, I suppose all in game bombs have it. Newer bombs could have a gps inertial back up instead, having more precision for the passively guided part of trajectory.

agus92 wrote:That makes no sense. Bombs have gravity during all the trajectory,

Bombs have missile logic. They were implemented when laser targets were mostly static.

Now, I'm unsure about the state of the art of the PR implemented LGBs, but since an inertial gyro system is old and cheap, I suppose all in game bombs have it. Newer bombs could have a gps inertial back up instead, having more precision for the passively guided part of trajectory.

Bombs have missile logic. They were implemented when laser targets were mostly static.

hmm,

what about low-tech bombs having TSLaserGuided logic and high-tech bombs TSWireGuided logic?

[R-CON]Fastjack wrote: hmm,

what about low-tech bombs having TSLaserGuided logic and high-tech bombs TSWireGuided logic?

You should not listen to Alon when it comes to BF2 code
Everything that wants to track laser targets needs TSLaserGuided, but BF2 only has guided missile logic. That means once a bomb tracks it becomes a slow missile to BF2 so in theory it can fly upwards. Also while tracking a targets physics get suspended. Since usually bombs are dropped from high up these things are not really a problem.

[R-DEV]Mats391 wrote:That means once a bomb tracks it becomes a slow missile to BF2 so in theory it can fly upwards.

Not just in theory

[R-DEV]Mats391 wrote:You should not listen to Alon when it comes to BF2 code
Everything that wants to track laser targets needs TSLaserGuided, but BF2 only has guided missile logic. That means once a bomb tracks it becomes a slow missile to BF2 so in theory it can fly upwards. Also while tracking a targets physics get suspended. Since usually bombs are dropped from high up these things are not really a problem.

Understood. Then, after losing laze the bomb should still keep guided missile logic, BUT, with an increased error (as in probabilistic deviation to last know laze). Do you implement error already with current laze, or the bomb goes straight to the target?

To quantify the error: according to wikipedia source's (https://www.globalsecurity.org/military ... -specs.htm), modern bombs should have a 50% chance of hitting a 30m circle with fall times of 100 secs or less (which I don't feel like calculating, but I'm pretty sure that's waaay higher than when the jet sees the laze in PR).

There's no error in missile mode

Could there be 2 kinds of lases on the littl bird with rockets, as the spotter lases and then when the pilot(me) moves the chopper from still(static) hovering, the spotter's lase aslo moves as the lase tracks the mouse's movement at that time, really becomes hard for the pilot(me) to know where is that the spotter meant after the pilot(me) moves the chopper.

1.Static lase (which one put stays there for a definite period of time; like the GLTD uses)
2.Dynamic lase (which moves actively with the cursor)

Thanks!

So i recently had a pretty good round as a spotter on khami lasing moving mec vehicles in and around the city on their way to the objectives (i was in an elevated position). My lases led to quite a few AAVs, APCs/IFVs, trucks and tanks being destroyed.

The new system effectively nerfed 'defensive' lasing capability, like routinely peeking up behind cover for a split second and lasing a FOB or vehicle that is aware of your position.

On the other hand it also really buffed the 'offensive' lasing capability, when the target is unaware of the spotter and/or moving.

Overall imo opinion lases got effectively nerfed a good bit, since most of the time your target will spot you sooner or later if you keep looking at it and moving vehicles on most situations disappear from line of sight too quickly for the jet to react.

But i still wouldn't have it any other way than the current system just for realism's sake and for the ability to keep guiding bombs.

It seems that to be most effective with the current system one has to find an elevated position with a good vantage point that is hidden/unassuming and try to have as little exposure time as possible.

DogACTUAL wrote:since most of the time your target will spot you sooner or later if you keep looking at it

Then only laze when your jet and/or heli is ready.

You don't laze a tank all the time do you?

Yea, now that you don't need to keep trying to make it stick, just pop up when you need to.

sweedensniiperr wrote:Then only laze when your jet and/or heli is ready.

You don't laze a tank all the time do you?

Here, just for you, since this statement keeps popping up:

Previous lase system minimal exposure time: 1-5 seconds (pop up, lase and make sure it sticks, hide again; time varies with distance)

Current lase system minimal exposure time: 8-20 seconds (pop up when CAS says it is inbound, wait for bomb drop, then wait for impact; time varies with CAS drivers ability to estimate correctly when to lase and spotter potentially needing to watch the target before lasing to make sure it is still there, otherwise the CAS exposes itself for nothing looking for a lase that isn't there)

Yea, no.

DogACTUAL wrote: Current lase system minimal exposure time: 8-20 seconds (pop up when CAS says it is inbound, wait for bomb drop, then wait for impact; time varies with CAS drivers ability to estimate correctly when to lase and spotter potentially needing to watch the target before lasing to make sure it is still there, otherwise the CAS exposes itself for nothing looking for a lase that isn't there)

As it should be.