GeoS72

Here is a 2nd set of files that should show when George AI wouldn't lase or fire. dcs fail2Lase-Fail2Fire-2nd time.log DH Fail2Lase-Fail2Fire-2nd time.trk

I used this map for the most recent testing. Test Range.miz

Here is another set of files. George had several failures to lase & fire in a generic Caucasus map MIZ file. dcs Fail2Lase-Fail2Fire.log DH Fail2Lase-Fail2Fire.trk

Here is tonight's issue on my Syria base capture map (played in single player): George AI lased the first target 4 times outside of 8km. George did not lase again but I got a "within range" message. The target data went from ~8400 m to ~7,800 m without the need to lase again. I gave the consent to fire and George AI fired a Lima. I also want to point out that there should have been a 5th time George AI would lase the target based on his earlier cadence. After the target was destroyed, George AI acquired the 2nd target but took a while to lase it. It was well inside 8km and no issue with George firing a Lima. dcs 2024-07-24 Syria.log DH Messeh-4x Lase.trk

Also posted on 7/13/2024: Here is another DCS log and link to a Fast Mission from the Sinai map. I also do not understand why this thread is heavily restricted with file sizes. The link is about 18.5 MB and showcases the problem of firing on the VERY last target, a T-72 MBT. Fast Mission-Sinai-Last Tank No Fire dcs 2024-07-13 FastMis-LastTankNoFire.log Posted on 7/19/2024: Ok, here are 2 sets of log/track files for a test mission in the Caucasus map. I wasn't able to duplicate the problem as we described above. However, I did experience 1 laser ranging event at a range of ~9,900 meters then got no other lase events. After flying towards the target range, George AI gave me an "in-range" at ~7,800 meters. There were no other laser ranging events. This happened when targeting the 1st vehicle on both runs. dcs Test Pilot 1st Target Long Wait-2.log dcs Test Pilot 1st Target Long Wait.log DH Test Pilot-Long Wait 1st Target.trk DH Test Pilot-Long Wait 1st Target-2.trk One more post on 7/19/2024: This track should better show the ranging issue with the first target. George lased target at ~9.6km and then nothing. I cycled his status from MSL to No WAS and then back to MSL. He said target was within range but did not lase at first. The range was at 6.8km until he lased the target again. This problem appears to happen when there is more action occurring in the battle space. So more data is needed. Additionally, this issue is problematic to capture for me. There are days when this bug happens frequently while other days, it's not a big deal. dcs DH Test Pilot-1st Target Range Issue.log DH Test Pilot-1st Target Range Issue.trk

George AI will lase a target every 5 seconds (approx) when outside of 8 km to obtain range information. Inside 8km, the lase logic is delayed to some ambiguous time. This process is very persistent when using the AGM-114L (Radar Hellfire) missile. Furthermore, George AI will not fire even when there is a clear line-of-sight to the target and the helo is within launch parameters. Press "Consent to Fire" all you want; George AI will not comply. I'd also like to point out that after lasing a target outside 10km will also allow the range to falsely count down and then stop. This fake countdown process will continue until the helo is within 9km from a target. What is the link between number of instances George AI lases a target beyond 8km, laser range data countdown beyond 10km, infrequent lasing within 8km, and failing to fire AGM-114Ls after consent was given? One more parting shot: George AI will frequently fail to lase a target. I have to manually cycle between Missile and No WAS modes just to get the George AI to lase a target in a "timely" fashion. Derbroomaster and I flew in the same mission on Jul 13. So here is a link to my track file (much larger than his) and my DCS log. PersianGulf_006 Track File I'd certainly like to see some resolution to this persistent and annoying problem. This issue was originally addressed in this thread: George Wont Fire Any Hellfires More track & log files to follow. dcs 2024-07-13.log Original posted on 7/13/2024: Here are DCS log & Track files from a Fast Mission (creation) that was in the Sinai map. This track should show the number of times that I had to manually cycle George AI from WAS'ing MSL to De-WAS then back to MSL in order to get ranging info. A lot of the time, this range was under 5km. There were also several instances of George AI not firing after consecutive consent to fire orders were given. Fast Mission Tracj 2024-07-13.trk dcs 2024-07-13 Fast Mission.log

First, I'd like to point out that the OP never got any resolution to his problem. Second, others (myself included) believe that it was unnecessary to start a new thread in a different section because the problem was similar. There was no need to start a duplicate thread. Third, if there was a solution then it was not obvious. Standby for a new bug report to document my findings. Cross-referenced bug thread to post problems with George not lasing/firing Lima missiles: George AI and AGM-114L Lasing-Fail to Fire

Well, I'd like to use an electronics term to best describe the resolution to this problem: PFM...Pure eFfing Magic! It looks like the problem resolved itself. Don't know how or why. I mapped the following HOTAS for Left/Right movement and tested in the Caucuses map: WinWing Throttle Ry Axis: Pass WinWing F-16 X Axis: Pass Virpil Rudder Z Axis: Pass* * - this was the original axis that failed; even after several axis tunes. Suddenly, it now works. Maybe mapping to the other axes helped? With each of these axes bound, I was able to use the keyboard commands (A & D) to steer left/right.

Draconus, thanks for the feedback. Which axis did you have bound for steering? I wonder if there is a specific issue with binding rudder pedals for steering. I will have to test it further. All I know and experienced is this: Before this patch, I could use either joy axis (rudder) or key binds A & D to steer a Combined Arms vehicle left or right. Currently, the key bind for accelerate and brake (W & S) work in conjunction with the axis bind for right toe brake. If the key binds were fighting with the axis bind then some unusual movement should be observed. However, there is no unusual movement. The vehicle tracks straight; if A or D is pressed, then no movement occurs. The only time the vehicle turns left or right is when the rudder axis provides the input.

@Glide, this is a hotfix patch. I would bet dimes to donuts that this bug was not fixed. It is normal for the altitude readout to disappear in Transition Mode. It means you are about 1,400 ft MSL. If you switch the HMD to NAV mode, then the MSL altitude will be displayed. Look at like this: that is Boeing's (McDonnell Douglas') way to say, "fly lower!" If you experience the no-fire/no-lase problem, then please post your DCS log and track file.

@Glide, I do not believe there is an altitude problem. I've been up at altitude between 750 - 1,500 ft with a clear line of sight yet experienced the no lasing logic problem. What were the conditions that lead to George AI not firing in your situation? How high was the helo?

@Flappie, You were able to control a vehicle from key command and a joystick axis? The only conflict in my CA controls is the axis bind and key bind for Vehicle Left/Right commands. I removed the axis bind and the vehicle steers with the standard A & D key bind. When I bind an axis, rudder Z axis in this instance, the vehicle will ONLY steer left/right using the rudder axis. NO A & D key would move it. The accelerate/decelerate commands work with the toe brake axis. I can accelerate/brake using either W & S keys or release toe brake on my rudder pedals. A simple workaround would be to remove the Left/Right axis bind. But that does not fix the problem.

Yes, you are correct. The Sinai map has a laundry list of bugs that need to be addressed. One of my other issues is the TACAN channel conflict.

It's disappointing that a) the score is still broken and b) no moderator acknowledgement.

Not to mention, the OP complained about this problem back in July 2022. That's 2 yrs and counting without any solution or acknowledgement.

Rongor, Much appreciate the backup and additional feedback on NAVAIDs. I also noted that Sinai has several TCN stations that do not have airfields. They are stations that will lead you into open desert. Maybe that was meant for future airfield expansion? Who knows. If I may offer a semi-elegant solution for all airfields without a fixed TCN station: drop a mobile TCN unit on the applicable airfield(s). This is great for multiplayer environments. I use this on most of my base capture maps. Basically, my setup is as follows: 1. Create a Neutral mobile TACAN unit (from Ground Unit icon, Fortification, select Beacon TACAN Portable TTS 3030) 2. Press the "Combat" button next to "COUNTRY" to select "ALL" 3. Select a neutral country. I hear that Switzerland is a fine exporter of mobile TCN units! lol 4. Give it a unique Group & Unit name like N.Base Name.TCN.70X 5. In the Advanced (Waypoint Actions) do the following: 5.a. Press "Add" 5.b. Select "Perform Command" 5.c. Select "Activate TACAN" 5.d. Verify "BEARING" is checked. 5.e. Always use "X" for CHANNEL MODE. Y mode is often broken based on my experience. 5.f. Set Channel from 1 to 126. From the Group Name example, 70 in this instance. 5.g. Enter Callsign. I use the ICAO or IATA code for the airfield. It can display up to 4 alphanumeric characters. 5.h. Select the unit's name from the UNIT pull-down menu. 6. Make the asset immortal and invisible in the Advanced (Waypoint Actions): 6.a. Press "Add". 6.b. Select "Perform Command" 6.c. Select "Invisible" 6.d. Repeat process for the "Immortal" function. This neutral TCN station will work regardless which coalition controls the airfield. Using the Invisible & Immortal commands will prevent the asset from being targeted/destroyed by Red or Blue forces (AI or human). It should go without saying that one should pick a TCN channel that is not being used. Otherwise, the TCN receiver in the aircraft will get confused. Would that help in your mission design?

Gentlemen, This is a bug that should be elevated and researched by ED. If you have to constantly cycle between No WAS and MSL just to get George AI to lase the target then that is a problem. I provided several track & log files that could be investigated with the right tools. Even in Wag's video that showcases the Lima operation from the CPG seat, it does not require the cycling between No WAS and MSL. This IS a problem and must be addressed. Period and end of story.

Rongor, Thanks for the additional info on Cairo West. That is just one example to a larger problem with TACAN and/or other NAVAIDs on the Sinai map. I'd really like to see some form of acknowledgement from the Dev or ED. Based on the number of reports of TACAN not working and the silent treatment from the Dev, I doubt this issue will be corrected in the future. But hey, a man can dream, right?

So...after 1 month, is this a dead bug?

No acknowledgement after 1 week. Bumping thread for added visibility. Could anyone else confirm this issue?

No response from @OnReTech or mods yet. Bumping the thread for greater visibility.

This track should better show the ranging issue with the first target. George lased target at ~9.6km and then nothing. I cycled his status from MSL to No WAS and then back to MSL. He said target was within range but did not lase at first. The range was at 6.8km until he lased the target again. This problem appears to happen when there is more action occurring in the battle space. So more data is needed. Additionally, this issue is problematic to capture for me. There are days when this bug happens frequently while other days, it's not a big deal. DH Test Pilot-1st Target Range Issue.trk dcs DH Test Pilot-1st Target Range Issue.log

@Floyd1212, I do not want to drift off topic here. The chief complaint is that George AI has trouble lasing a target and then refusing to fire when in launch parameters. My latest post touches on part of the problem: lasing the target when beyond 8km. In the last instance, I got range info at ~9.8km. Once George shut off the laser, the range data decreased until ~9.3km. Then without re-lasing, I kept flying towards the target then George claimed the target was in range. Suddenly, the range data went from ~9,300 m to ~7,800 m. Again, there was no laser fire to re-range. From my previous experience, George would lase the target approx 5 times at ranges between 9.9km - 8.3 km. The interval at which George would lase is very short at those distances. However, once inside 8km, that frequency suddenly decreases to an eternity. Additionally, George would delay lasing a target when it is inside the 8km range. I've had instances when I'm at 6km and would get within a kill zone of a vehicle because the AI refuses to designate a target until the helo is within 3km. Then to top things off, at that close range, the AI would refuse to fire.

Problem resolved itself over several patches. This thread is closed and photos/files removed to recover file space.

Ok, here are 2 sets of log/track files for a test mission in the Caucasus map. I wasn't able to duplicate the problem as we described above. However, I did experience 1 laser ranging event at a range of ~9,900 meters then got no other lase events. After flying towards the target range, George AI gave me an "in-range" at ~7,800 meters. There were no other laser ranging events. This happened when targeting the 1st vehicle on both runs. DH Test Pilot-Long Wait 1st Target-2.trk dcs Test Pilot 1st Target Long Wait.log dcs Test Pilot 1st Target Long Wait-2.log DH Test Pilot-Long Wait 1st Target.trk