Kuky

Then I have no idea

Hm, that to me looks like your monitor playing up. Have you checked settings on the monitor, does it have some game mode, hdr mode etc? If yes, try turning it all off.

Nah, thats not it, not in the quick mission I tried this and where track is from, anyway... the targets are on coastline flat area so maybe few m difference at most, which should not be the cause of it. My guess is, looking at that screenshot of HUD, that aiming reticle and line are shifted above horizont line, I think the top of the line should be level with aircraft line, not anove it, and if you shift that line down to the aircraft line on the HUD the aiming circle comes right above the area where the bombs actually hit. EDIT: ignore the crossed out part, I realised what I wrote and thought was the issue, makes no sense so just ignore it Yes, good point

ah-huh! Bingo! You're right, changing the option then restarting DCS makes it change appropriately.

You are right, I just tried the 256 option for the mirrors and they still look exactly the same as with 1024 (or 2048) resolution. The option does indeed seem to be "stuck" to highest value.

Come on man...

Here also...

Another issue I found was that when switch is in ALL position (to drop all bombs of the same type at the same time) in case of KMGU bomblets canisters only 12 of them drop from 2 inner canisters at the time, so in order to drop more of them you have to quickly press the weapon release button again and again in order to release 12 more, then 12 more again etc. I believe these canisters should drop whole 96 bomblets in one go (which is perfect for targeting columns of vehicles in straight road) and when the switch is in ALL position it should drop them all from all 4 canisters... but it doesn't. KMGU deployment.trk

Beside the cannon on the MIG-29A Fulcrum module being bad I can see that deployment of bombs (all kinds) is extremely bad as well, I have tried RBK, KMGU, FAB & ODAB (or maybe the last one has a different name, I can't remember now but its not relevant to this issue) and all of them drop way too short of the aiming point on the HUD... I mean all of them, all the time. I thought maybe its the map issue somehow (maybe terrain elevation is off on some maps) so I tried Caucuses map also and I can see the same thing. FAB500 deployment.trk

Yeah... what you gonna do? I bought at first 2x 1TB M2 drives thinking 1TB would be enough for DCS... within 1 week it was... well full So I bought another 2TB M2 drive for DCS and moved it all over, now with 1 new aircraft module (MiG-29A Fulcrum) and I am trying out the South Atlantic map (which is pretty good I must say so I intend to buy it once I have bit of money left again) I am again down to ~850GB left on this 2TB drive. So, solution to your "problem" is just uninstall modules you no longer use, aircraft and terrains and you'll save on space and DL data when DCS gets updates.

This shadow should not be visible as its a shadow cast on ground underneath the shelter structure, but its however visible on top of the shelter structure. It goes away once full shadow is visible (second screenshot)

With these shelters I think you need to have 2 separate objects as top of shelters, the higher one on which the land texture and grass/shrubbery is on and lower one, the underside as shelter ceiling, which needs to be lowered so that grass/shrubbery is not visible through it

I am seeing cannon piper being offset to both left and right (I guess depending on turn/bank) in both Radar CC and IRST Vert mode

I think both the radar and IRST don't need to wait whole scan area to be completed in order to get a lock, it should depend on in what area the target is in. If scanning starts on top and goes down then its logical that if target is on top of the scan area to be scanned and locked earlier than target which is in bottom of scan zone. I don't think the IRST VS locks too quick, I think that radar CC mode locks too slow.

ah good catch... so then this is not just TDC being displayed wrong, I wasn't sure if its just HUD TDC symbology wrong or radar mode is wrong, but you're right, this then confirms that its actually in wrong radar mode altogether.

I honestly can't tell the difference between option 3 (1024) and 4 (2048)... maybe in other aircraft (like in FC3 MiG-29) it makes a difference, have a look at the 2 screenshots with the 2048 and 1024 option

Thanks for the tip however I don't see mirrors resolution an issue for me as now with new MiG-29A module mirrors look good even at 1024 settings but just for the heck of it I will try this out also

Please see attached track (and screenshots) where I am engaging an F-14 with R-27ER, I select B Radar Mode (High PRF) for high rate closing targets and radar keeps lock until missile impact, I fired the second R-27ER (just for heck of it, as target was already hit) and after the F-14 crashes into the ground, and radar lock is dropped, I notice on HUD that TDC is long, representing the D (Low PRF) receding targets radar mode and not the one I had selected on weapons panel. Incorrect Radar PRF Mode after loosing lock.trk

Eh... not all landings are good, especially when after engagement you end up with 1 damaged engine and then you're trying to land on very short runway, adding to problems drag chute when released rips off on release which does not help with breaking and stopping the airplane

soooo.... will this get support for MiG-29A Fulcrum module any time soon, or any time at all?

Yes, track replay is indeed broken so no use of them ATM, however you can see in screenshot where I was shooting at, the cannon aim and where the tracers went... the cannon computation is completely off for the MiG-29 right now. I can't use aiming and firing at non-manoeuvring target as judgement for accuracy (not that on its own) and even then I find that aim is off a bit and cannon rounds overshoot over the target so I have to aim at the bottom of the target in order to get hits. The cannon should be accurate and not this bad (for example look at accuracy of aiming piper in the F-15C... that thing is like a sniper, compared to it MiG-29 is like shotting with a bow and arrow.

Cannon aim is definitely off, here is a track that shows it clearly In screenshots, the two labelled as '1st Aim and Shoot A/B' show cannon aim reticule very off to the right of the F-15C but the tracers/bullets go very far off to the left of the F-15C And in screenshots labelled as '2nd Aim and Shoot A/B' I aim to the front of the F-15C and some bullets hit the back of it (and I score some hits) So clearly there is big discrepancy in aim reticule of the cannon on the MiG-29 and this is definitely a bug MiG-29 Fulcrum-A Cannon Aim Innacuracy.trk

Oh, its been reported already... good (but looks like we'll need to wait for this to be changed for a while) Thanks

Just remembered that also this could be due to monitor features like Gaming HDR and some other enhancements, which my monitor has too, all of which I disabled because it was giving me inconsistency in image brightness, something like a flicker, so maybe if you have monitor that has these features try turning it all off.

Hm, maybe you have bit of hardware issue (video card or monitor, maybe even the cable between the 2)? On something slightly different, my dcs runs pretty smooth but yesterday I was setting up VoiceAttack so I set dcs to non full screen, smaller than monitor native resolution, and after switching back and forth between the applications I noticed dcs getting very stuttery even while I had vsync 120 fps which was weird, I thought maybe because I had 4 Mig-29a in the mission it overwhelmed my video card but turns out it didn't, I restarted the pc and after that it was smooth again in the same mission. So I don't know, maybe theres bit of memory leak or something when dcs switches from one view to another as it did with me switching from dcs to VoiceAttack? Maybe try a different cable first, I'd also check if possibly video card is running too hot, running out of vram... anything like that... even changing settings in dcs... computers can have tons of things causing issues and most of us here know this. Good luck in finding what causes it