Vakarian

This is an old bug, reported couple of times already IIRC

Everything is here

It was only marked as reported literally on the post above yours.

@cfrag Thanks a lot man, you helped me find a bug in my solution... It had actually worked all along, and I have been blind in the script I've been working on. So there is no point for this topic, error was as it is most of the times, in front of the screen

Thanks for the miz file, I will test this out later tonight when I get home. I don't remember from the top of my head how large is that circle of influence around the airfield, it might be that you are still inside so you got the land event.

Instead of focusing on the gauges, look at the indicator showing total amount of fuel. Gauges only show specific fuel tanks and it's kinda irrelevant to begin with. If you want to know quickly total amount of fuel, look at the number indicator.

I'm making a little app to track my flight time and I noticed than when I suffer some battle damage and manage to land the aircraft (fixed wing or a rotary) in an open field DCS Scripting engine doesn't register is as a landing as no "land" event has been fired. This ofc extends to any landing that's not Airbase, Ship or a FARP and is most noticeable in helicopters as you can land them practically anywhere. In the current documentation, land event has following attributes { id = 4, time = Time, initiator = Unit, place = Object, subPlace = 0 } I guess that the problem is that the "place" is not an object when you land on an open field, but it would be really nice to get this event fired even if the "place" object would be nil or something like that. It is quite sad that I can't track my flight time in this regard as I have my takeoff time, but no landing time as DCS hasn't registered I ever landed

Yeah, nozzles were straight back the whole time. It's like it did the whole VTO procedure (regarding how slowly IAS was increasing) and after transitioning to forward flight it just jumped to that point. Weird

Jesus, try to keep the camera still Btw, notice how IAS keeps increasing steadily the whole time after the lineup, while the aircraft seems stationary. This is definitely a bug

Seems like my comments might have missed the point as I probably forgot to say some things I had in mind... Sorry for that. My underlying point was that as the owner of Cougar MFDs I do not see the point of upgrading to this as the price is just to high for the marginal benefit. That being said, I'll probably still do it anyway . The current owners of Cougars probably won't see this as something awesome, and someone that has neither will look at them both, start to compare and will probably get to same conclusion I did. I mean, what some of you guys commented is true, I do understand why they need to set the price they do because they do it in low volume and are not mass producing it. But, as a customer I really don't care about that. Sorry if it's too blunt, I just think that everyone will think for themselves to get the best stuff they can for the least amount of money spent and I don't see these Apache MFDs as a way to do that. TC Multifuction box on the other hand seems to hit the sweetspot (both pricing and functions available) and that is the product that I would definitely buy if I'm not already deep in building a Harrier UFC myself.

Well yeah, Cougars are not something I'd say are the pinnacle of latest tech, but let's be honest, it's a button box, nothing else. If a button gets registered when I press it, I really don't care if it's an el cheapo no-name switch beneath, ALPS, Omron or even an OTTO switch behind it. It's a button, nothing else. It's a frame with 28 buttons on it, just formed in a logical shape to accomodate better muscle memory. Now, with the Apache MFDs, we have a bit more buttons and a 3 extra encoders (I presume those are encoders, might be wrong) placed in a slightly bigger frame. Now, I don't think that the size of the frame matters as much in the terms of the pricing, it's a plastic after all and at the first glance looks 3D printed. PCB can also be done fairly cheaply from jlcpcb or any other manufacturing. So, 3 extra encoders, 4 extra buttons and a larger frame result that there is a product that's more than a double of price of a single Cougar MFD and a tad more than a price of the both of them. TM Cougars (Kit of 2 frames) TC Apache MFD x2 56 buttons 64 buttons and 6 encoders 80 USD 200-240 USD That's why it's a hard sell for me

While this is tehnically true, I really struggle to justify that I should pay 200-240 USD for two of these when I can get 2 TM MFDs and I get practically the same thing minus the encoders for ~80 USD. I really doubt that in total 6 encoders justify that price. If they would sell 2 of these for 150-180 USD, then I'd give them a shot.

It's not hard to make them dynamic just on its own. What seems to be the problem is that each livery from different wings had the numbers on different places, different fonts,... That's what makes it more complex than usual when you have XY liveries, but the numbers are on the same place with same font. IIRC HB did comment on this a while a go on one thread when the question was similar to this one

Hmmm, I've never noticed this for the ground units. I know that contrails can disappear when they are a bit farther and you look at them from a random position, but I didn't encounter this issue with ground units or aircraft

Would adding hydraulic damper help alleviate some of these issues? I think I've seen it done somewhere but failed to see any conclusion

You do realize that the graphics play such a minor role in a simulator, right? I mean, would you rather have a little rough around the edge models with near 1:1 FM, or blyatiful models, but FM like press up, go up?

Yeah, thanks for addition. That's another thing that's different if you do it in air

Try do think about it a bit, it's not really hard to deduce why it has been like that

IIRC Kneeboard doesn't get updated when you do it in the air, only on the ground. CAS page gets updated regardless

Fixed it for you

Sorry for late reply. Other than Tacview and SRS, I have T-45 and ZeDim static pack. I've disabled both, ran the track file again and I still experience the issue. Then I ran repair with those mods still disabled and that didn't help also... Then I reloaded the mission, placed couple of units on helipad to test and I found out a weird thing. As seen on a new track file, at first I loaded the mission, selected the aircraft and went straight to F9 view of the ship. Rotated around it multiple times and the units were visible. Then I went to A-10, put TGP on the ship and the units disappeared from TGP view. Went to F9 again and then the units on the ship were visible only from certain angles. Posting a track and the video I've recorded showing this bug. ifvsDisappearingV2.trk

Ok, well, then post a track so we can see the issue. Having wrong elevation in the system is one thing that comes to mind when the CCIP pipper is showing "wrong" impact point

What is your target designation showing? Gun pipper takes the target designation point elevation to calculate proper impact position. If that designation is on wrong location (i.e. not where you are about to shoot) and the elevation of that point is different, that would be the reason why the pipper is not showing correct info. There are 2 ways of fixing this. 1. make a target designation where your targets are and you'll get proper aiming info. 2. you undesignate everything, then the piper will use still magically working ARBS to calculate the proper solution. I say magically because it always knows correct distance, even when you don't fly proper attack profile so the angle rates could calculate

Haven't tried that, I could test it when I get home. I do have to point out that they are static objects. If I use active objects, then I get bug described here:

When you go on CAS page, then RCALL, you will see ODU button which says ERASE I believe. With that, you can delete entries in the aircraft system. Also, you can have 15 entries, but you have control on which of those will actually be a targetpoint (T1, T2, ...) for when you go on CAS page, you use "USE" OSB button and then on UFC you enter the number of the targetpoint you want that entry to represent. You have to understand that F10 map and Harrier CAS page is one-way relationship and that is F10 map -> Harrier. The aircraft has no knowledge of which marker did you delete or add on the F10 map, it just "downloads" the coordinates to next available entry on CAS page and it's up to you to decide what to do it. Also, as you did it on the ground the system automatically assigns each entry its own targetpoint, but if you do it in the air only the entry will be made and you will have to make that entry the targetpoint.