Jump to content

George can't find targets


Gunfreak

Recommended Posts

I made myself a mission, it's a long hall some 30 minutes flight, along the way there are several enemies.

I got shot at by some infantry, even tho I looked right at were all the tracers came from he wouln't lock on when I asked him.
Later a Shilka and some Infantry are in the way. I know exacly where they are, after many tries he locks on to the infanty, But there's a lot of trees, so I'm unsire if we hit, the Shilka is right next to the infantry but he could not find it. Even when I see the TDAS has the shilka right in the center, I don't get the options to choose it. or "save" it. 

i7 13700k @5.2ghz, GTX 3090, 64Gig ram 4800mhz DDR5, M2 drive.

Link to comment
Share on other sites

  • BIGNEWY changed the title to George can't find targets
  • ED Team

Please include a track replay example. 

He is finding targets for me just fine and engaging, a track is the only way to see what is going on for you.

It maybe a line of sight issue so readjusting your position maybe needed

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

3 hours ago, BIGNEWY said:

Please include a track replay example. 

He is finding targets for me just fine and engaging, a track is the only way to see what is going on for you.

It maybe a line of sight issue so readjusting your position maybe needed

The Shilka was in the  open, as I said the TADS looked straight at it. 

The track is to big, to upload, not that it would help, as I had flown for like 25 minutes, so I assume the track would just show the apache crash after som 5-15 minutes.

i7 13700k @5.2ghz, GTX 3090, 64Gig ram 4800mhz DDR5, M2 drive.

Link to comment
Share on other sites

  • ED Team
34 minutes ago, Gunfreak said:

The Shilka was in the  open, as I said the TADS looked straight at it. 

The track is to big, to upload, not that it would help, as I had flown for like 25 minutes, so I assume the track would just show the apache crash after som 5-15 minutes.

The tracks I have been looking at seem ok, if you want me to check attach it or link it. 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

I have seen something like this as well. Although it only happens to me if I do a cold start. If I use a hot start it works fine.

System: MSI Z370 | i7 8700K | 32GB DDR4 | RTX 2080Ti | TM Warthog | Logitech Pro Rudder Pedals | Oculus Rift S

 

 

Modules: FC3 | UH-1H | SA342 | Spitfire | AJS-37 | F-5E | A-10C | M-2000C | AV-8B | F/A-18C | F-14 | C-101 | F-86F | MiG-21 | MiG-19P | MiG-15 | F-16C | JF-17 | L-39 | Mi-8MTV2 | KA-50 | Christen Eagle II | Yak-52 | Bf 109 K-4 | NTTR | Normandie | Persian Gulf | The Channel

Link to comment
Share on other sites

10 hours ago, NineLine said:

Please supply a track and we can take a look.

I'll try to get a track, does not see that it happens every time though so I have to try for a while and see if I can get it to appear again.

System: MSI Z370 | i7 8700K | 32GB DDR4 | RTX 2080Ti | TM Warthog | Logitech Pro Rudder Pedals | Oculus Rift S

 

 

Modules: FC3 | UH-1H | SA342 | Spitfire | AJS-37 | F-5E | A-10C | M-2000C | AV-8B | F/A-18C | F-14 | C-101 | F-86F | MiG-21 | MiG-19P | MiG-15 | F-16C | JF-17 | L-39 | Mi-8MTV2 | KA-50 | Christen Eagle II | Yak-52 | Bf 109 K-4 | NTTR | Normandie | Persian Gulf | The Channel

Link to comment
Share on other sites

Is your acquisition set to FXD or TADS? I mostly see my cold started AH64 setting ACQ to FXD what could imply (I don't exactly know how George works) it only sees target in a limited LOS. I manually set my ACQ tot TADS everytime after a cold start and have no problems with George picking targets.

AMD Ryzen 7 5800X3D, MSI X570 Tomahawk, 32GB G.Skill F4-3600C15D @ 3866C14, ASRock Taichi 7900XTX, HP Reverb G2, VPC WarBRD-D & Thrustmaster F16 Viper & F18 Super Hornet, Thrustmaster Warthog Throttle.

Link to comment
Share on other sites

26 minutes ago, Marco Schaap said:

Is your acquisition set to FXD or TADS? I mostly see my cold started AH64 setting ACQ to FXD what could imply (I don't exactly know how George works) it only sees target in a limited LOS. I manually set my ACQ tot TADS everytime after a cold start and have no problems with George picking targets.

Haven't thought of that, I will try that and see if it helps. Thanks!

  • Like 1

System: MSI Z370 | i7 8700K | 32GB DDR4 | RTX 2080Ti | TM Warthog | Logitech Pro Rudder Pedals | Oculus Rift S

 

 

Modules: FC3 | UH-1H | SA342 | Spitfire | AJS-37 | F-5E | A-10C | M-2000C | AV-8B | F/A-18C | F-14 | C-101 | F-86F | MiG-21 | MiG-19P | MiG-15 | F-16C | JF-17 | L-39 | Mi-8MTV2 | KA-50 | Christen Eagle II | Yak-52 | Bf 109 K-4 | NTTR | Normandie | Persian Gulf | The Channel

Link to comment
Share on other sites

13 hours ago, NineLine said:

Please supply a track and we can take a look.

Here is a track file. However after doing some testing now I got it to work sometimes as you can see in the track file, but the times it does not work might very well be caused by something I do wrong. Also tested with and without setting ACQ to TADS and leaving it at FXD.

 

Link to track file: https://www.dropbox.com/s/xiyi5xdig0u6f90/AH-64D George.trk?dl=0

System: MSI Z370 | i7 8700K | 32GB DDR4 | RTX 2080Ti | TM Warthog | Logitech Pro Rudder Pedals | Oculus Rift S

 

 

Modules: FC3 | UH-1H | SA342 | Spitfire | AJS-37 | F-5E | A-10C | M-2000C | AV-8B | F/A-18C | F-14 | C-101 | F-86F | MiG-21 | MiG-19P | MiG-15 | F-16C | JF-17 | L-39 | Mi-8MTV2 | KA-50 | Christen Eagle II | Yak-52 | Bf 109 K-4 | NTTR | Normandie | Persian Gulf | The Channel

Link to comment
Share on other sites

I should also mention that the mission was flown in VR so although I was not always able to see the target menu displayed in my VR headset I do not know if it was displayed on the screen or not.

System: MSI Z370 | i7 8700K | 32GB DDR4 | RTX 2080Ti | TM Warthog | Logitech Pro Rudder Pedals | Oculus Rift S

 

 

Modules: FC3 | UH-1H | SA342 | Spitfire | AJS-37 | F-5E | A-10C | M-2000C | AV-8B | F/A-18C | F-14 | C-101 | F-86F | MiG-21 | MiG-19P | MiG-15 | F-16C | JF-17 | L-39 | Mi-8MTV2 | KA-50 | Christen Eagle II | Yak-52 | Bf 109 K-4 | NTTR | Normandie | Persian Gulf | The Channel

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...