=36=Witcher

So... I'm following the discussion even though I don't use VAICOM, but I'm really interested in the whole project (as Home Fries surely knows :)) Being a Software Engineer when outside of the cockpit, I can't help but reason about the whole code base. I know we're about to hit the "critical mass" of the script, so I think that the time for a major overhaul is coming. Now... for sure, TARGET scripts are not meant to be THAT module, and what Home Fries achieved here is quite impressive IMHO. Nonetheless, we need room for further improvements. So, here's my first thoughts: I think we should find start to branch the scripts according to... something. I don't know exactly what the best way do this can be, but the first thing that comes in my mind is to split the code base between Cougar and Warthog base. I think this should help split the code base pretty much evenly, and would also help reduce the complexity. What do you think, Home?

Yep, it's folded in the right part of the cockpit, just below the screwdriver above the INS. Click it to reveal.

Totally normal. The yellow contact is not an actual contact, but rather the last known position of the contact before the radar lost it. The contact will continue to move on the radar according to the latest known course and speed until you manually dismiss it with the VTB Theta Up switch (where you also see the RAZ indication).

No, you're not :) If disk space is not an issue, here's the direct link to download the OpenBeta: https://www.digitalcombatsimulator.com/en/downloads/world/beta/ It will install alongside the release version, and you can fly with both of them. There's also a way to switch your current version to OpenBeta, but I don't have the instructions at hand right now. It's a simple process anyway, you'll find it quickly. This way you will only have one DCS version, but the OpenBeta is updated more frequently and it has more features than release (i.e. Supercarrier and JF-17 modules just to name two). Most of popular multiplayer servers are on OpenBeta, so if you are interested in flying online you really should consider it.

First things first: are you on OpenBeta?

Maybe it doesn't matter, but I wouldn't use time compression on a track to demonstrate a bug, since it may change the simulation behavior. Also, I would record a new track with the latest version, just to show that it's still there.

The video is from 2018, are we sure something didn't change since? Also, are you using DCS time compression?

How many feet above ground?

Theta Up

Please tell me you're not trying to compete with the 2000C against Falcons and Hornets :D

I think his point is that 0.5nm in after 40nm is too much. I honestly have no idea whether it is too much or not.

Here's the difference, both from the cockpit and outside view

Uhm, I remember them to be different in brightness and "cone". I'll try in a few minutes and report.

NOT FUNCTIONAL means that the control (there are others as well) is not implemented in the simulator. You can interact with it but it has no effect.

Woah, completely forgot about that, I'm sorry. However, there's a reason why: still at page 133,

Nope. And by the way, there's no such thing as "runway heading" and "glide slope" in the INS.

I think he means the fact that the texture pack can't be used in multiplayer servers with integrity check.

Well, I guess it's handy to have the contact on the VTB to check the interception course. But I agree, I would also love to hear from other people

Magic slave to radar has been there for years, and is in fact what you are saying: bring the Magic seeker to lock the radar contact and have a "double lock" (i.e. the triangle). But it's not something new, at all. It's the opposite of what we had already: you can now turn a Magic lock to a radar contact, obtaining the "double lock" again. Using the VTB switches you can "create" a radar contact manually by entering its position, course, speed and altitude. To do that, click on "DEB" (top left switch of the VTB), change the data you need with the other switches, and then "FIN" (again, top left switch of the VTB). I think it's used to do air interception with radar off, when you have an AWACS/GSI directing you to the contact.

Yes, radar slave to magic is also here. Same key binding.

It's the first button of the top row in the left MFD. OSBs are numbered from 1 to 20 rotating clockwise for each MFD.

Do you mean CCMs?

Ok! Be sure to read the updated manual, it should have all the new stuff. Latest version is 1.1.1, you already have it in your DCS World\Mods\aircraft\M-2000C\Doc

Yes, and that's fine. IT DOESN'T have to happen. I showed you the Boresight on purpose: the Magic patterns are completely separated from the CCM modes. The symbol next to "MAG" in the HUD now shows the Magic pattern, NOT the CCM mode. The CCM mode is shown with the circle around the gun cross if it's Boresight, or a dashed line for vertical or horizontal mode. In Stable, instead, the symbol next to MAG on HUD shows che CCM (so again, Boresight, Vertical or Horizontal), just like the screenshots you showed us. But those are radar modes, not Magic search patterns. We don't have Magic search patterns on Stable.

We're exactly on the same page instead: I asked you about MAG/MAV because if it doesn't change on the PCA it means it's not going to change in the HUD either. Moreover, what you are showing in the screenshot are not the Magic search patterns, but they rather look as the pre-update CCM modes, and that's fine since you're showing the Stable version. In the OB, with the Magic patterns, you see an horizontal or vertical double-headed arrow, no circles and no |--|. Any mods installed? EDIT: This is what you're looking for in the latest OB: