dorianR666

1994

it appears the problem remains

its a VR thing, difference between eyes. your vid, i assume, is not VR given its camera movement.

Even if it was within seeker FOV, its nonsensical for the missile to think the target suddenly teleported 5 miles away right before impact. ED needs to implement range/speed gates and proper target movement prediction in memory mode, or we'll keep seeing this.

100 views. No one knows? Ive never seen it in the old A-10C and i havent found any indication in documentation that there should be multiple Z markpoints. Ive seen it twice in the new A-10C though. So I guess this is another bug in the A-10c upgrade.

Please read my post. It doesnt work in Minhad, because you used warehouse functionality in Minhad. It works in Dhafra, because you did not use it in Dhafra.

I know why that is. You see, you used the cursed warehouse functionality: When i removed the warehouse file from your mission, it began to work: DO NOT USE THE WAREHOUSE FUNCTIONALITY. It doesnt work. It never worked. Avoid it entirely. Whenever you use it in a mission, that mission file becomes incompatible with DCS after an update (or rather, after every time ED adds a new weapon to DCS). It breaks then, as you can see in the first screen shot with the empty lines in the table. DO. NOT. USE. WAREHOUSES.

you want to post that here: https://forums.eagle.ru/forum/529-a-10c-the-enemy-within-campaign-30/ there is a forum section specifically for enemy within

Hi, i was flying a singleplayer mission, me and 1 wingman. At the end of the battle, this is what my TAD looked like: There are 3 markpoints Z. Why? Is it done per weapon type? When I stepped through the markpoints (as STPT source), only the bottom left one was selectable. How do I understand this situation?

How do I make the wingman follow orders? This time he even seemed to turn on target. I have alse been receiving "RTB" when I tell him to rejoin sometimes, though he does rejoin, so thats just a radio response bug.

A-10C wingman is still broken Put SPI on target (via TGP), SPI broadcast on, tell wingman to attack targets at SPI - "affirm", 3 seconds pause, "rejoin". ED, for gods sake, fix this please.

the old logic was that when you are locked/fired at, all 4 lights activated and you couldnt tell from which direction you are being attacked from. the new (correct) logic is that only 1 light activates, in the proper direction.

Bump

That cant possibly explain why tadpole doesnt work. Neither can it explain why ADI fails if EPU was already running before main generator loss. If ADI was one of the "various systems on the AC and DC bus will fail", then it shouldnt be running at all after main generator failure, yet it is, so that cant be the explanation. The problem here is that it appears that power is lost to components like ADI and INS for a fraction of a second and then regained again. Which would be understandable if EPU switch was at Norm, since it takes a while for it to engage - but this still happens with EPU already engaged before the generator loss! See my third post. Please review this again.

this never worked, and was reported already many times before whats funny is that civilian traffic cars actually are illuminated by map's light sources.

When you slave a maverick to particular coordinates, you need ownship coordinates from INS to compute the angles to which the maverick seeker should rotate.

I cant replicate your issue. Zooming in and zooming out, coordinates are correct and not changing. My cursor was on TACAN beacon 57, marked with red arrow in screenshots. I had to switch into the "Stereo" screen layout, I dont normally use it. I use two screens, but not as "Stereo" setting. Instead, my normal configuration displays 3D on left screen and MFCD exports on right screen. In that case, the editor bug doesnt happen because the editor is displayed only on left screen (and right is black). Stereo configuration is probably fairly uncommon among players. However because the problem doesnt exist in my DCS, its possible you are running an old version. Are you on latest OB? I am.

yeah, its been reported many years ago but not much is being done about it. most unfortunate, because perhaps half of the campaign missions packed with paid modules (a-10c in particular) utilize this function and often became unplayable when it fails. i dont expect it to be resolved. more of a warning to fellow mission creators.

might be because INS drift is buggy in hornet. one system may take it into account, another may not. jf-17 had a very similar problem. navigation symbols did have drift, gps bombs targets did not.

an annoying bug when in FUNC mode, pressing the buttons on UFC should not type corresponding characters, and instead enter the CDU page inscribed below a button. this works for all buttons except SPC. FUNC with SPC causes both actions - switching to WPINFO page *and* typing a space character. this is incorrect. func.trk

MIDS terminal may be running, but that doesnt necessarily mean datalink symbology should start appearing on pages. Perhaps they shouldnt appear with D/L off. We will need a word from ED I suppose.

*extrapolation of last known location, direction and speed of that track. It used to fly to last known location at some point in past and it was very useless In my experience, if you keep STT until the last moment, it never happens. In TWS though, i keep seeing it all the time.

another track attached, showing some of the symptoms OP mentioned. in particular, HUD attitude ladder and attitude director indicator are messed up. notice that i moved EPU switch from Norm to On, and waited for the green light indicating EPU is running. only after that, i shut down the engine. still, even tho EPU was already running the whole time and thus electricity source was never lost, INS and ADI both got messed up. f16_epu_ins.trk

track attached, but showing different symptoms than OP - tadpole stopped working. im switching steerpoints but tadpole is always within velocity vector. f16_epu_tadpole.trk

ive seen this too. running on EPU messes up lots of things. but only sometimes.