TobiasA

To be fair, most of the stuff they do is pretty good. It is mainly the F-16 that suffers from long lasting bugs that don't get fixed for months and then something new comes and breaks stuff that worked. The A-10 for example is pretty fine, and the Hornet as well. And DCS as a sandbox is doing pretty well too, even if there are flaws.

This is really unrealistic as the maverick would run out of coolant before you are even close to the target, and it would do so on the A-10. On which boresight was never necessary. And it is about the same offset as not aligning because you usually have to lock targets very close. I understand that you see it this way though. But... These threads will continue to pop up as long as the system software quality is as low as on the F-16. They rework one thing that worked and screw up the hole SOI/SPI concept on the way in without anyone noticing before releasing. I can totally understand the frustration about that.

There is no way to help with boresighting mavs as of now. Best is to not boresight them at all, this way they will point to about the same direction. At least somewhere. This thread is more or less useless, the initial posting is far away from constructive feedback and there is no way to boresight mavs as of now. So there won't be any help either. There are many cool things in DCS, boresighting mavs is none of these. It never worked as it should, and even if it worked, the handoff never did, especially on movers. Let's just see if they fix it some day. As of now, I'd be totally happy with bugfixes. I don't need new functions when half of the stuff we have still has major flaws.

The manual is wrong here. MODE 1 will break the lock of an AI MiG-29 on your 12 o'clock outside of approximately 25nm. So either the manual is wrong or the implementation is wrong. Also, the selection of the band should determine whether your radar is jammed or not, while it currently doesn't really do this as it seems. All of it is wip, and I don't write this with a negative tone in mind.

The A had a single monochrome MFD, and the radar had a considerably lower range. It wasn't bad though, but used mainly for navigation as it didn't carry AIM-7. The FCS was different, less thrust but also less weight. Turning off datalink and GPS and entirely relying on dumb bombs will probably get you close. As close as you get without modding DCS. However, many A in europe got a MLU upgrade, bringing many features that the C had, like two MFDs and AIM-120.

Any comments on this issue?

Thanks a lot!

A huge thanks to you! Question: How do I see in the document that it is no longer hemligstämplad? Just curious. Do I see it at all? Edit: Ah, wait, if it is available in riksarkivet then it is no longer hemligstämplad, I guess...

Finally... I managed to recreate the issue. It happens when you switch in and out of MRM override with a lock still present (or maybe not even necessary to have a lock?)- in that case, the elevation will get stuck. Attached is a shorter track than the original one. RWS_no_altitude_control_short.trk Mind that I have an axis mapped as altitude control.

That sounds like it was a controller issue and then got closed.

Now we have a track

That doesn't solve my problem though.

This will change to TWS, changing to RWS is done by 2x TMS down short with no lock.

I am using DTC, you need to let the mission run in realtime until the dtc upload is finished.

When returning from TWS by double-bumping TMS down, the RWS mode will have its scanning altitude (elevation) stuck until you "bumb" the scan range by moving the cursor to the side. Returning to TWS by TMS right long will regain control over the scan altitude, bumping back to RWS will leave you unable to control elevation. This doesn't happen always, but I have been able to reproduce it in a test mission. After shooting down the last enemy plane (mission is 4 minutes in total), the altitude control is locked to what you had when you exited TWS. I am using an axis to control the elevation. You can see the altitude jumping back to -99/-99 when going back to TWS and coming back to the "old" altitude range when going back to RWS. When bumping to a 60 degree scan volume, I regain control over the radar antenna elevation and I can move the elevation around again. This has been bugging me for a while, and I finally managed to recreate it. I hope the attached track makes it possible to see why and how it happened. It may be the case that it happens when a lock is dropped because the target leaves the scan volume or is destroyed. RWS_no_altitude_control.trk

Post- designate has been buggy for a long time now. It is worse for some bombs (CBU-97) and less bad for others (Mk-84). It also gets worse if you pull out of a dive after designation. They will go anywhere along the bomb fall line. CCRP will work just fine, but CCIP is not usable right now in most cases because the post designate does not work as it should.

First of all, thank you for taking the time for a detailed reply. The thing is not that we do not appreciate the work going into the F-16. It is... It happened in a lot of the recent patches that saw relevant changes for the F-16 that you take the F-16 for a spin after a bigger patch, and something big is broken. You literally do one single ramp start, and something is off. We went for a quick training like we always do, just a short trip to the range, checking if everything works or if things have changed. I usually take LGB, but this time we went with mavs, LGB and JDAM and out of these, only the JDAM worked. After getting the TGP to work, which took quite some time. And that is getting really frustrating, especially since it is no longer called Open Beta. I am not raging and ranting, but in some of the patches, it makes me wondering about how such problems can pass the internal beta test. And I would really appreciate it if we could get a more reliable platform, and things that already work don't get broken two updates later. That being said, I know that the 16 is still early access. But I would appreciate it if there would be more bugfixing (like fixing post- designate CCIP) and less new bugs, especially on features that didn't even see a change. It's not some new feature, or that something behaves different. It is that things completely stop working. And that's just sad.

Strange, I flew several minutes and it remained dark until I enabled master arm., two times. It happened after rearming with the TGP already present and powered. I will try to recreate it.

Plus, it seems to not come back to life until you enable master arm. Which is not correct.

If you rearm with the hardpoint still powered on, the same seems to happen.

Yes, and in some cases, Master Arm has to be on to power on the TGP.

CBU-97 will fall really long in post- designate CCIP, or do not release at all. Edit: This seems to affect other weapons as well, just not as much. CBU-97.trk

Does this apply to normal startup as well?

Do not have the gun cross above 10 degrees on the pitch ladder unless your sink rate is really low. At no point should it ever exceed 13 degrees AOA, especially when carrying HTS, TGP or heavy ordnance on the inner wing hardpoints.

That is probably another bug. I never tried repairing so I haven't tested yet.