MoppleTheWhale42

Hi, to my understanding, the AGM-65H has no INS. Thus, in forced correlate mode, it uses its CCD for aiming. If this is true, why does the AGM-65H work reliably in forced correlate mode in complete darkness? Is this a bug, or is my understanding how the AGM-65H identifies its target in forced corelate mode wrong? Kind regards Mopple

The initial point handling in ME looks odd to me. The waypoints generated from the initial points seem to be in an arbitrary order in the CDU. They are neither sorted according to e.g. their names, or by the time they were added to the mission. I recently added four more initial points. They showed up in pairs of two, somewhere in the list of waypoints. Can you explain why the TO/FROM setting of a waypoint affects the way the CDI works? To my understanding, the CDI should give me the indication towards a waypoint independent of any other waypoint.

The mission does not contain any flight plan. All waypoints have been set up in the ME as an initial points. Looking into the CDU, I see that it is set as FROM: 86. I can turn the course all 360 degrees. The CDI needle does not move at all. The precision is looking good. The CDU reports a FOM of 1 for INS, EGI, and BLD.

Since several weeks, the CDI does not always work correctly, when steer point is selected as reference. Sometimes the needle sticks to the edge of the HSI. The attached screenshot shows the issue. I am flying heading 180 and the steer point is a little to the right of me. As I have set the course to 180, the CDI should indicate that the course is a little to the right. However, the CDI sticks to the very left of the HSI. I have added a track, depicting the issue. What may be a bit special, is the high number of initial point objects in the mission. HsiIssue.trk

Hi, in the remarkable document "Hog Basics: RAF Bentwaters Tactics Guide, 1982", there is a description how two A-10s can enter a circle, where they turn opposite to each other around a common point. The author states: "Entering the circle is relatively easy. Lead calls “circle” and turns hard into the wingman for about 135 degrees. The wingman waits until the lead’s nose passes him and then begins an easy turn into lead. Once the wingie starts his turn, the lead reverses back into the wingie, and the circle is formed." Honestly, I do not understand how this should work. Does anyone understand the concept, or, better, has practical experience? If yes, could you please post a drawing or a tacview recording? Thank you and kind regards Mopple

I fully support this request. This functionality is available in the real A-10, has been requested so often, and it appears to be simple to implement.

I feel that the problem has become worse since some weeks. If you have several main battle tanks standing on a street, then you can be pretty sure that the Mav ignores all the tanks and locks on the streetlamp. No problem, if a Mav sometimes accidentally locks on a streetlamp, but actually it seems to prefer streetlamps to vehicles.

Thank you very much for the many valuable replies. Looks like I didn't remember correctly and that my expectation was too high.

Yurgon, thank you for the quick answer. Don't you think that this is new behavior? This behavior prevents us from circling around a target, and I am pretty sure that worked in the past.

I am flying at 12000 ft above sea level and have a target on sea level on my 3’o clock position in 9 nm distance. My targeting pod is installed on my right site and therefore has perfect visibility on the target. Nevertheless, I cannot fire the LASER. I need to roll slight to the left, i.e. away from the target, to be able to activate the LASER. As soon as my bank angle is 0, or I roll to the right, the LASER goes off. I have even unmounted the AIM-9s to ensure that nothing is blocking the LOS of the TGP. I am pretty sure that this is new behavior, as this prevents to circle around a target and be able to LASER the target.

Thank you guys for this very interesting discussion. As a bottom line, I would say that it is not worth to program the wind into LASTE, but to rely on the A-10 to measure the wind. Regarding the difference between geographic north and true north, this depends on your location and, as the magnetic north pole is wandering, it also depends on the date. For the Caucasus, the difference is about 6 degrees. On the graphic, you can see the difference back in 2015 for the whole world.

I was testing the LASTE wind correction, and therefore I have set up wind in the mission editor as follows: 33 ft, 22 kn 0° 1600 ft, 52 kn 6600 ft, 34 kn 52° 26000 ft, 18 kn 325° Temperature on ground level 20° C. I flew 10000 ft AGL and dropped an MK-82 in CCRP mode. To my very surprise, the bomb hit with an accuracy of 2-3 meters. I repeated this several times, approaching the target from different directions. I always got very accurate hits. Then I added wind correction in LASTE. I entered Height 00; 180°; 22 kn; 20 °C Height 02; 180°; 54 kn; 17 °C Height 07; 232°; 34 kn; 7 °C Height 26; 145°; 18 kn; -32 °C Again I dropped an MK-82 from 10000 ft AGL. Now, the bomb missed the target by > 10 meters. Thus, I am either doing something wrong, or LASTE is doing some auto wind correction. What's your experience?

You make the mark point your steer point and then slave the TGP to the current steer point (China hat aft long).

Ich finde die von der IBM-Demo erzeugte Sprache ziemlich gut: https://www.ibm.com/demos/live/tts-demo/self-service/home

When you put the TGP in standby mode, then the optics turns back, so that it is covered. This is correctly displayed in any view of the pilot. However, it is incorrectly displayed in the F2 view of other pilots. I.e. another pilot, using F2 to watch my A-10, sees no difference between my TGP being in air/ground mode and my TGP being in standby mode.

No idea. Whenever CNC showed up, I could delete the SADL target.

Hi, can you please add the possibility to delete mark points? As far as I know, the real A-10 supports this function. I think I have seen a thread for this topic, but could not find it on the wish list. Kind regards Mopple

I have made several more trials and most of the time "CNTCO" comes up and and I can delete the target, so the answer from Yurgon is definitely correct. However, sometimes, after hooking "CNTCO" does not show up and up to now I could not figure out why.

Thank you for the answer. However, after hooking the target, CNTCO does not show up.

Hi, after receiving a target over SADL, I confirm "WILCO" and destroy the target. Now I am ready to get a new target assigned, however I still have the previous target in the TAD. The problem now is: If the new target is close to the previous target, then I cannot distinguish both targets on the TAD. Therefore, I want to delete the old target before receiving a new target. I can unhook the old target, but could not figure out how to clear it from the TAD. Do you know a solution? Kind regards Mopple

Hi, have positioned some SA-18 between some trees. When I approach them I see the SA-18 without any trees in the TGP of the A-10, when I am 26 miles away. Only when I come closer (~20 mi), the trees are also rendered, hiding the SA-18s.

I am wondering how exactly DCS maps between the two-dimensional x and z coordinates and longitude, latitude. According to documentation, the x-axis points towards north and z points towards east. Thus, I would expect that if I increase the value of x and leave z unchanged, then the latitude increases and the longitude does not change. However, this is not the case. On the Caucasus map for example, I get the following longitude/latitude for the given x and z values. Caucasus: x= 0, y= 0, z= 0, lat=45.129497, long=34.265515, height=0.000000 x=100000, y= 0, z= 0, lat=46.029375, long=34.285897, height=0.000000 As you can see, the longitude is also increased, although the value of z did not change. The other maps show a similar behavior. It looks to me that x is not exactly pointing to north. Can anyone tell me how exactly the coordinate transformation is done within DCS?

Hi, please find attached an ACMI file, where a single BTR is destroyed by a single CBU-105 dropped by an A-10. Tacview-20210908-003515-DCS-ClusterBombTest.zip.acmi

Hi BuzyBee, I am glad that you liked the question. Here is another one, this time I am trying to trace back hits from cluster bombs. When I drop a cluster bomb (here a CBU-105), the bomb shows up as the secondary object of my plane: <Event> <Time>45.11</Time> <Location> <Longitude>56.5492761</Longitude> <Latitude>27.2261811</Latitude> <Altitude>4341.05</Altitude> </Location> <PrimaryObject ID="11"> <Type>Aircraft</Type> <Name>A-10C Thunderbolt II</Name> <Pilot>Moppel</Pilot> <Coalition>Enemies</Coalition> <Country>us</Country> <Group>Aerial-1</Group> </PrimaryObject> <Action>HasFired</Action> <SecondaryObject ID="12"> <Type>Bomb</Type> <Name>CBU_105</Name> <Coalition>Enemies</Coalition> <Country>us</Country> <Parent>11</Parent> </SecondaryObject> </Event> The next event is that the BLU-105 comes into existence: <Event> <Time>83.92</Time> <Location> <Longitude>56.2419409</Longitude> <Latitude>26.1718273</Latitude> <Altitude>-2.25</Altitude> </Location> <PrimaryObject ID="13"> <Type>Bomb</Type> <Name>BLU-108</Name> <Coalition>Enemies</Coalition> <Country>us</Country> </PrimaryObject> <Action>HasEnteredTheArea</Action> <Airport ID="ICAO:OOKB"> <Name>Khasab</Name> </Airport> </Event> Here is my first question: How can I find out that the BLU-105 (ID=13) is related to the CBU-105 (ID=12)? Then, when the skeets hit the targets, I see that the targets get destroyed, but I can neither trace back to the BLU-108 nor to the CBU-105: <Event> <Time>109.58</Time> <Location> <Longitude>56.5777276</Longitude> <Latitude>27.2675555</Latitude> <Altitude>10.77</Altitude> </Location> <PrimaryObject ID="6"> <Type>Tank</Type> <Name>BTR-80</Name> <Pilot>Ground-1-5</Pilot> <Coalition>Allies</Coalition> <Country>ru</Country> <Group>Ground-1</Group> </PrimaryObject> <Action>HasBeenDestroyed</Action> </Event> From these "HasBeendDestroyed" events, is there any way to trace back to the airplane, that dropped the cluster bomb?

In my experience, that's what happens, when the TGP is in area or point tracking mode, and you fly high-g maneuvers. I do not know whether this happens with the real TGP as well. What I do to prevent this: If I have to fly aggressive maneuvers, or fly away from a tracked target, to which I want to return, I put the TGP into the INS mode. This way it preserves the location it is aiming at.