Theduncanizer

For admin, do you mind to move my earlier post/ merge it here? https://forums.eagle.ru/showthread.php?t=275176

I can confirm the bug is present as well in Persian Gulf and Nevada. I should have actually used PG for the videos, bomb goes straight to the other side of the hill :D

It works both creating a markpoint from the hud or tgp, and after that selecting that as steerpoint after changing the dts to hot

That might be the issue, but if you try it, you just need to switch from dtc to HOT if you create a markpoint on the target, select it as steerpoint, and It works perfectly, even without the jtac giving you any accurate number. If the dts was not accurate the workaround i mentioned shouldn't work.. The other question is, IRL i know airplanes like the av8 feeds target elevation from the most precise source (tgp for example when you create a lock), shouldn't the A10 do the same?

I didn't make any spi to avoid possible sensor interaction faking results, i just red the elevation, tgp remained in Atrack. All i had set was steerpoint as spi. I didn't make a video this time, all the results match the hypotesis. Releasing active pause didn't generate any change in simbology, all the drops were offset until target elevation is forced in instead of dts.

Hi A10 yoda, all the test were filmed flying QNH. The behaviour you quote is correct, but the ALT SCE switch apparently is not implemented in the DCS model(It;s an old post but i din't see it in any changelog, if you have any info would be amaing:https://forums.eagle.ru/showthread.php?t=82199 ). I made another video trying out your suggestion: 1st drop, inducing a qnd error setting a random value 2nd drop, setting the correct qnh 3rd drop, selecting DELTA from the ALT SCE switch 4th drop, selectin RAdio from the alt sce switch. All impact are on the same spot, showing all these parameters do not affect the DCS model (contarly to the real airplane behaviour) For the 5th drop, i used the tgp to gain correct target elevation and input that value in the LASTE via the HUD, the solution moved exactly on the previous impacts, same spot where the 5th bomb impacted (so the ballistic as expected remains unchanged).

Not a problem man, nothing taken personally! I love this sim and I believe everybody that uses it deserves a perfect experience. Please post your results, meanwhile let's wait for other feedbacks!

I might have found something useful. Every time we input a different value than DTS on the HUD, we are basically changing the Target elevation fed to the LASTE for its calcoulation (as theorised). Also the value limit is comparable, -1000 to 20560 in the game compared to -990 to 16380 in the A10A document, probably cause by different suite version). On the real airplane, there is a LASTE subpage in which you can select various tgt elev for different steerpoints, but that is not simulated in DCS so was kinda tricky to prove on documents. The question of the why the ccip is not spot on on DTS, but it becomes when forced (even leaving the tgt elev that appears once you select it) still remains. Maybe unaccurate terrain rapresentation in the sim on real dts data or vice versa? Also, although not necessary for operation, should a SPI feed tgt elevation (3d point, but in our sim we just use it to cage other sensors)? I think the latter could only be answered by a hog driver or a developer from ED.. ccip tgt elev laste.pdf

Sorry i made a video but is before i red the comment. Even with a steeper angle still is inaccurate on dts until forcing the target elevation on the steerpoint.

I will try and post the results. There is a thing i still cannot explain, and it's easily replicated. Fly at 3000 ft towards a waypoint, select mk82 profile and you will see the dotted pbil. ( also works with gun pipper). Now manually select an altitude from the ufc and set it higher than your current altitude, the ccip solution will disappear/get crossed. If ccip relies only on its own sensors, that shouldn't happen.

fixed on today's update: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.5.6.49718/

I made this track quickly. Wpt alt 6500 ft, tgt elevation 1650. First pass: only ccip mk82 selected -> long Second pass: tgp spi (confirmet on hud), DTS -> long Third Pass: Markpoint created out of spi and selected as steerpoint/DTS-> long Fourth pass: same as 3rd, but forcing steerpoint elevation of 1650 -> perfect hit The three long impact are really close to each other with similar time of fall. Notes: I left TGP as spi generator for the last pass to show how the current steerpoint altitude influences the drops regardless of SPI. The altitude that was set on the hud was the standard changing from DTS. I would also like to clarify that i meant CCIP needs some elevtion data, usually taken from DTS, but that should be able to be overrided by SPI and it's confirmed is overrided by a manual stpt altitude. Also worth of a note, TGP alt and standard altitude after changing from the DTS agree. ccip.trk

According to what you said, how do you explain the fact it is influecenced by current steerpoint altitude if it's supposed to be completely independent? CCIP needs to know a target elavtion somehow, then uses as you said altitude/spd etch to calculate the pbil and impact point. Elevation data can be provided through different means, one should be SPI. Maybe you didn't notice as when you in the sim you always have a steerpoint select regardless, and if the alitude ot that point is close to the target one, you have a working system. Reference for A10 usaf manual, TO 1A-10C-1 at page 1-434 reads: The CCIP Mode uses EGI, CADC, target elevation, and stored weapons information to compute the impact point for forward firing and free-fall ordnance. It allows selection of various modes, weapons, target elevations, and fuze times. A pipper and reticle continuously display the impact point for selected ordnance. The information is displayed on the HUD, and includes symbology for CCIP guns, moving target indicator, BATA display, CCIP bombs, Minimum Range Staple (MRS), Desired Release Cue (DRC), and Projected Bomb Impact Line (PBIL). The only way that you can use CCIP without having to input target elevation is when you select the Radio Alt as altitude source, but it is not simulated as far as i know (only BARO, no Delta or Radio) Source: TO-!A-10A-34-1-1 on page 1-25 (attached, just above LASTE 4.0 note) As also the ED manual reports, the 10C usaf describes the SPI as: (1-391) SPI. The SPI is defined as the point in three-dimensional space that the system uses as a unique reference for other functions, such as weapons delivery, off-board transmission, and sensor slaving. A sensor can define the SPI only when it is the SOI, but once defined, the SPI is not necessarily confined to the SOI. For example, a change in SOI does not necessarily mean that the SPI changes. A SPI is always present unless there is an error condition such as a failed CDU. Incorporation of Datalink allows transmission of the SPI off-board. For a detailed description of SOI, and SPI, refer to TO 1A-10C-34-1-1. Obviously i don't have other publications out of the one i quoted above, hence why i am asking here if there is a correlation of the spi elevation and target elevation fed to the computers to calculate the PBIL, having observed a correlation in the simulator. CCIP.pdf

Hi guys, I noticed a weird behaviour with the ccip delivery. Regardless of what is your spi generator, when you create one, it looks like LASTE keeps the current steerpoint elevation for the delivery cue. Easy to replicate: fly at 3000ft to a wpt/mkp/stp that has an altitude higher than 3000ft, get a spi and still no drop cue as the computer will still be thinking that your target is above you. From the manual at page 400: A SPI is a 3D point in space that the systems use as a shared reference location to cue weapons, aim sensors and send over the datalink. This is a key component of the A-10C and helps you to locate targets with onboard sensors (Targeting Pod, Tactical Awareness Page, HUD, Maverick and AIM-9), then cue weapons and slave sensors to it. The default SPI is the steerpoint. Once a sensor has been set as the Sensor Of Interest (SOI), the sensor may designate the SPI. Once a SPI has been defined, the SOI can change without changing the SPI. The current SPI generator is always indicated in the lower left corner of the HUD. The system is always tracking a SPI with the current steerpoint being the default SPI (such as when the aircraft is powered). The exception is if the SPI is commanded to steerpoint but there is no valid steerpoint because the CDU is not available. My work around is to create a markpoint on target and set that point as steerpoint, changing elevation data from DTS to manual (seems to be more accurate on targets in mountainous areas), but from my understanding that shouldn't be required as the spi, as 3D point, should also feed the target elevation for the release cue. Any light on the matter would help!