Dagger71

Yes. that is correct. I Did not put in the right order.

It will also retract with flaps at auto, under other circumstances.

Auto flap setting work according to Gs, AOA and speed and also controls speedbrakes. As KFTGB you would only use full/half settings when taking off/landing. There may be some emergency procedure detailing the use of non-auto setting, but for normal flying, keep it auto.

Also the speedbrake will retract under certain circumstances which doesn't happen with the A10C. "Speedbrake EXTEND–OFF– RETRACT. The speedbrake is mounted between the vertical stabilizers. It is controlled by a throttle mounted switch. Airborne, when in the AUTO FLAPS UP mode, the speedbrake automatically retracts above 6.0 g or above 28° AOA and, when not in the auto flaps up mode, below 250 knots. The speedbrake will automatically retract if flaps are extended unless the speedbrake switch is held aft. The speedbrake extends with the flaps HALF or FULL so long as the switch is held in EXTEND. The speedbrake can be commanded to extend to any intermediate position but will retract fully with a momentary forward press of the speedbrake switch. The speedbrake operates normally on the ground."

although I don't really disagree with what you say, MP in DCS is still a small percentage of overall player base. It's just the way it is at this point.

This isn't a multiplayer bug either. It happens in SP.

ok re-read and duplicated. Thought you were referring to in-game labels. To be honest I think it's been this way since day one...possibly to avoid clutter??

check your keybindings. Sounds like you have a duplicate.

Of course not. The only visible liveries will be the ones loaded in the MP mission. Hoggit PG server has some really good desert skins, but only those who download them will see them.

No there has been an immense amount of confusion regarding this. It's a lot more complicated than I can explain on a game forum without a massive amount of studying the subject again. Even yourself in was confused. Maybe someone with a bit more recent hands on experience can do it better than me. I say Shagrat evolve in his understanding once I made the statement about the SPI actually only being a snapshot of the output from the sensor. So when I say the TGP SPI is contantly calculated... technically this isn't completely true. The LOS was already calculated and when one press make SPI, it takes a snapshot of this point. As the LOS moves, it gets updated and the SPI takes this new dataset. The CDU does not know what any SOI was looking at .01 seconds ago, but when you "create a SPI" it will save this point and what sensor created it until you slew to a new position, generate a new SPI, the engines are shut off or if some severe damage happens/ But again I think this is more advanced SPI understanding that will lead to probably about 10 more pages of back and forth so I don't think we should really get into it.

Yes absolutely. this is much better to ask questions then to make unsubstantiated claims. The TGP tracks the moving vehicle through several methods, might be using Gaussian mixture mode, which uses the camera sensor to detect differences in contrast, pixels and other criteria and uses calculations to determine if this object is indeed moving or is just background noise. So when the TGP is in track mode (think of it as auto-slewing) the SPI is not really looking at the vehicle, but through it to the spot on the ground that it calculated through the center of the LOS as discussed before. As the vehicle moves, the LOS moves, therefore a new SPI calculation is made. The margin of error between the actual SPI location and the center of the track point (vehicle) is completely negligible when it comes to using conventional bombs. Not to mention using the laser to get a more accurate SPI It is possible newer versions of airborne surveillance can also implement some sort of instant volumetric calculation to get a more precise point, but I am unaware of such. Volumetric calculations take time and lots of data to be processed, usually taking a few days just to map up a small area of land.

Here is another interesting fact. If you take an A10C operating out of Afghanistan and fly it in a remote Island of Antarctica you will NOT be able to generate (create) a SPI because it will be missing vital DTS, data and map package information.

But the SPI IS in fact a saved 3d point "in a database or similar." When TGP is SOI and not generating (making SPI), nothing you do with it is recorded on any level. The moment you do TMS FWD LONG, onboard sensors and processors create the SPI ( a large amount of calculations in a microseconds) that the LOS points to on the ground. When the TGP slews, those calculations are redone and continue to get done until you stop moving the SPI, then it remains a saved point. Like mentioned before it is a snapshot. Remember what I mentioned about the TGP pod glass aperture could be covered up in black tape and it will still be precise since the lightening pod nor any sensor does not actually use the video to generate the SPI. It is there for visual cue. When switching from say TGP LOS SPI generator to the HUD TDC as SPI, it is actually a NEW and completely different set of calculations used to determine the SPI. This calculation of SPI is not something that even could have existed 40 years ago.

I didn't invent anything. Even Shagrat knows this now. Did you look at page 400 of the manual? It is also in DoD manual. So the line of sight is technically an unobstructed line between two points. Draw it from the center of the TGP cross hairs to the ground that it is point at. That point on the ground represents the SPI. Do you understand my laser pen example? I think that might be the easiest way to understand. The SPI always remains with the sensor that is generating (making) it. If is HUD SOI that could be the middle of the TDC or a CCIP, depending on submodes used.

It's referring to the TGP LOS that is SPI. Think of it as a laser pen. I can point it a wall and generate (make a SPI). Its not really the Pen that's the SPI, but the end of the LOS that is. But If I am using a laser pen, eyeglasses that emit a laser and a laser clipped on my shoulder, it's easier to say "The pen is now SPI" instead of the dot created by my pen is now SPI.

Bingo!!

I'llgive an example on LOS and how it works in relation to the TGP and how it generates (creates) the SPI (I've worked on surveillance UAVs using similar technology). Whether TGP uses Digital Terrain Elevation Data (DTED) or any other format, It can do this: 1 Slew the TGP, ) and zoom it in while the glass on the pod is covered by a piece of paper (so you can't actually see what it's actually looking at). 2 Do TMD FWD LONG (Set/make/generate SPI) 3 Do China Hat forward long (Slave all to SPI) 4 Look at the MAV screen 5 Take the paper off the the glass The TGP and MAV will both be looking at the exact same spot!!!

That's not what I asked. If 2 planes fly with the same WP entered, but mid flight one changes the WP coordinates, do you still say they are the same waypoints??

and neither is the HUD TDC a real box in 3D space. IT can however be the SPI!

What does that have to do with changing Waypoints?????

It's been like this then entire time. He's the Bill Murray of the Warthog forums!!!

The LOS is NOT imaginary! As Shagrat explained to you, it ends at a specifically calculated point on the ground!! It is calculated using INS GPS, gimbals among other critical components. Can you guess what that point on the ground is called??

What is system level? Are you refering to the flightplan???

I'm so glad you are catching on! Listen to this man Quigon!

Without the LOS there is no SPI.. The LOS focal point generates (creates) the SPI. You have a fundamental problem with understanding how the SOI "generates" (meaning creates) the SPI. look up page 401 of the manual. it will explain. Just as I have for the past 12 pages!!!