GeoS72

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

@Floyd1212, Thanks for the tip on checking personal storage space. I did post tracks/logs to 2 short Fast Missions. I was limited to files size so links to download them from my Google drive are provided. I'll try to get another fast mission captured and post my results over this weekend. In the meantime, I sure would appreciate this thread being elevated to the bugs section and/or get some feedback from ED.

@Blackhawk163, I've found it exceptionally easy to duplicate the problem with a full compliment of AGM-114Ls (Limas, aka Radar Hellfire) or with a mix of rockets and Limas. Use George AI to pick up targets and keep him in the "Yellow" (Consent to Fire required). No FCR is required. When I normally fly, I'm loaded up with 16 Limas and 1,200 rounds of 25mm. The gun is WAS'ed to me while George AI has the Limas WAS'ed. If you could run in a similar configuration, then I'll be curious to see your results.

In order to keep the image proportioned, may I suggest a template that is 4000x840 and center the user's image. These files may help in creating a custom server banner. Note: a blank PNG file is between this line and the XCF file. Server Banner-Blank.xcf

@MK84, The image size for the default server image is 4,000 x 840 pixels. It is located in the main DCS Install location here: ...\DCS World\MissionEditor\images\server-image-default.png. You add your own server image from the ME. Click on "Briefing" icon then select the Server tab at the top.

Thank you, @Blackhawk163 for confirming the problem. Now that you could replicate the discrepancy, could you please submit a DCS log & track file associated with a similar event? I'd like to reiterate that these problems are prevalent when firing AGM-114K (radar guided) Hellfire.

No, the problem is not specific to Sinai map. This problem happens on any map. I used Sinai to report 2 different problems; hitting 2 birds with 1 stone.

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. DH Fast Mission-Sinai-Last Tank refuse to fire. dcs.log

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. dcs.log LastMissionTrack.trk

Here is a track file from a Create Fast Mission in the Sinai map with DCS Log. LastMissionTrack.trk dcs.log

@Flappie, Confirmed. The problem is fixed. Thank you very much for addressing the problem!

@BIGNEWY & @Flappie, I'd like to piggy back on @Derbroomaster's remarks. 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 today. So here is a link to my track file (much larger than his) and my DCS log. Persian Gulf 006 Track File link I'd certainly like to see some resolution to this persistent and annoying problem. Would moving this thread into the Bugs section may be more appropriate? dcs.log

@OnReTech, When will the issue with Tacan (TCN) channels be addressed in the Sinai map? I've seen several threads that discuss broken TCN channels. Specifically Cairo West has incorrect or nullified TCN and VOR info. In the screenshot, one can clearly see the Airfield info screen shows SPX Tacan Channel 0X and SPX VOR Frequency 0.00 MHz. There is an additional TCN icon that shows 114X with Station ID BLA. DCS Log file submitted. My track file is too large to attach. Here is one of many threads that also address this specific error at Cairo West. https://forum.dcs.world/topic/328094-cairo-west-vortac-is-broken/#comment-5239541 dcs 2024-07-13 Cairo West TCN.log

Here are the DCS log & track files. The track was from a Combined Arms training mission. Anytime you see the Vulcan being steered left or right it was from the use of rudder pedals. dcs.log tempMission.miz.trk

Yes, I had the same experience!

After this new update, I cannot steer any vehicles using the A & D keys. I can use axes to turn left & right but not the keyboard. Additionally, the key binds are default W for gas, S for brake, A for left, and D for right. There are no conflicts with these key binds. Track file & DCS log soon to follow.