ensure no inhibits present George AI and AGM-114L Lasing and Fail to Fire Problems

[Floyd1212]

48 minutes ago, Derbroomaster said:

I was under the impression giving a time would help with fast-forwarding to the appropriate time the incident occurred.

It does help, a bit.  It's like giving someone directions to drive somewhere and then take Exit 30.  Knowing it's Exit 30 means you can slow down and be prepared to look for it when you pass Exit 29.  But in this case, there is still a bit of a drive before you are even close.

Actually, this is all a moot point as I watched the track again and gave it a little longer and the track ended with nothing happening.

The track ran from 5:03:00 to 5:39:40

Edited December 5, 2024 by Floyd1212

[admiki]

7 hours ago, Derbroomaster said:

Do you have an example of this topic you'd like to share? If not, you may not understand the frustration a lot of us are feeling as we constantly provide reports and examples.

Both Floyd and I are not getting paid to do this, we are trying to help people with issues.

Take a look here how to report a bug:

Emphasis being on it being a short as possible track.

If you are hunting a bug, don't take your sweet time around the cockpit, plan your mission before you get into cockpit and execute that plan as fast as possible.

We can't just jump in time in tracks, and speeding it up introduces all sorts of weird crap.

So, I spent 45 minutes of my time watching you faffing around on F10 map (well, I didn't, since I just let it play out and was doing something else).

Then, according to track, you crashed about 25 minutes after takeoff.

You took another bird and crashed it about 7 minutes after takeoff.

You are correct, track are somewhat bugged after they go over an hour.

So, can you understand my frustration?

[Floyd1212]

That's what I get for playing it at fast speed then, as I didn't even see that activity.

Short tracks that get directly to the problem is what is helpful.

[admiki]

18 minutes ago, Floyd1212 said:

That's what I get for playing it at fast speed then, as I didn't even see that activity.

Short tracks that get directly to the problem is what is helpful.

Once in cockpit I sped it up since you said he had about 160 clicks to targets.

According to track he had no waypoint, was flying with hover symbology, spent about 10 minutes in cockpit after each crash.

Once track got to his stated time 04:33:30 I bugged out.

[GeoS72]

This problem still persists. The issue with capturing GeorgeAI behaving badly in a track file is also a concern. I play almost exclusively in the multiplayer environment. With that, the track files are large and the time taken to reach a target can be a while - 20+ minutes.

The problem of GeorgeAI lasing when he wants can be mitigated by using a mixed Hellfire loadout (e.g. 3 RF + 1 laser missiles per pylon). The AI will habitually lase from 10,000m down to 8,200m every 15 - 20 seconds (maybe longer, it's been a while since I timed it). Then he will take a lunch break at ranges under 8,000m; lase whenever he feels like it. To combat his lunch breaks, I long press left on the AI wheel to cycle between RF and Laser Hellfire. That kinda helps to put him back on track. He will often double lase the target when switching between Laser and RF missiles when using this technique.

I want to make this clear: The GeorgeAI lasing problem still persists. By no means is my workaround a permanent solution to this on-going problem. It is a field-expedient remedy to a problem that can be resolved above my paygrade.

[Floyd1212]

Keep in mind there is different laser behavior needed for Limas vs. Kilos.

The Kilo needs a constant laser for the missile to track the target and be guided in. The Lima needs a few seconds of lasing the target to get the positional data loaded into the missile, then you can stop lasing — and George does.

Sometimes this can be a pain if you want to switch to a different target but the missile already has the data for the first target. You have to switch to Kilos and then back to Limas to get George to lase and capture new data.

If you keep flying around without shooting the Lima, I think George will clear the missile and re-lase the target to get fresh data. This sounds like the behavior you are describing.

EDIT: The complaints about George not lasing in other threads were primarily when engaging with the gun, but that issue seems to be much improved as of a few patches ago. 

Edited July 9 by Floyd1212

[GeoS72]

Floyd, et al:

GeorgeAI still misbehaves with all conditions being met: good line of sight, altitude, and constraint box within limits.

The point to make: this problem still persists after 1 year of the initial complaint. Any improvement to the AI logic is small but also not advertised. Case in point: months ago, I discovered the AI ability to swap between Laser and RF missiles. I believe it coincided with the addition of Target Zoom function (Long Press Up in the AI wheel). That was not advertised in change logs. You would think that adding this new capability would be showcased in a short video; nope! Hell, I would have welcomed the change if it were mentioned here (as an example).

I'd be more than happy to host a day/time on my server to demonstrate the shortcomings of GeorgeAI; this way all invited guests can see with their own eyes, collect data, and dissect that data. DM me for details.

[BIGNEWY]

3 minutes ago, GeoS72 said:

Floyd, et al:

GeorgeAI still misbehaves with all conditions being met: good line of sight, altitude, and constraint box within limits.

The point to make: this problem still persists after 1 year of the initial complaint. Any improvement to the AI logic is small but also not advertised. Case in point: months ago, I discovered the AI ability to swap between Laser and RF missiles. I believe it coincided with the addition of Target Zoom function (Long Press Up in the AI wheel). That was not advertised in change logs. You would think that adding this new capability would be showcased in a short video; nope! Hell, I would have welcomed the change if it were mentioned here (as an example).

I'd be more than happy to host a day/time on my server to demonstrate the shortcomings of GeorgeAI; this way all invited guests can see with their own eyes, collect data, and dissect that data. DM me for details.

I would suggest waiting for the next patch, if you still have issues after you will need to provide short track replay examples. 

thank you