MarcT-NL

Hmmmm welllllll, I totaly don't have to be rewarded for beta-testing. My reward is that I can fly in DCS for free (well... you know) and pretty often get amazed by what I see and achieve in a mission and so. But what realy bugs me (no phun intended) is that if I am to test something, I don't expect to find the bloody obvious. I don't expect to find things that have allways worked perfectly before. Like a canopy that doesn't work anymore, or a few levers in the cockpit. I expect to find a bug that only occurs is very special situations. And I expect them to be resolved at some point.

Regression testing ? I don't think there is regression testing. Hence the appalling number of new bugs every single update. Things that have always worked fine suddenly break. You can't tell me that somebody sat in a P-51 before the release and didn't notice weird behaviour of canopy and air-controls. Either they did notice but couldn't be bothered, or they never tested it in the first place. Well, it's the open Beta I suppose.... we are the testers. We have become the fixers too.

Yeah. Apparently it was "fixed internally" whatever that means. I wish they would fix it externally.

Thanks pmiceli. It is a shame it had to come to this, where the buying customers start fixing bugs...

June 17th 2021. Mega-update yesterday. Hind, Cyprus and much much more... Just those pesky P-51 controlls seem realy too much. Editing LUA-files again.

Ah. OK, I tested it. Seems to work. See the YT-movie. My recordings are dreadfull stuttering, but I hope you can still see. First I do a little dogfight, which I win of course :). Then at 06:00 I set prop to 2500 and MP to 30. Then with a HOTAS-button, I put the ram-air lever back. So it's not an axis, it's a button right. After that the MP is reduced a bit. I think that is what you meant, right ? By the way... anybody any tips on how to improve recordings ?

No, I don't think so. I bound the controlls to switches on the HOTAS, but it's still not binary. If I press the switch I see the lever moving forward/backward. When I release that switch the lever stays in that position. Works fine by me. Works as it always has, before 2.7.

OMG. That's such an insult to the buyers ! ED, or whoever is responsible for the P-51 just can't be bothered.

Yeah. After each update I edit the LUA-file again. Seems simple enough, but apparently it's not so easy to imply in an update...somehow...

OK, thanks for investigating. Some decisions of the FA-18 engineers are just beyond me I guess.

Well, we have different opinions about easy and intuitive. But our opinions is not what matters, and this forum is not the place for this discussion perhaps (although...what would be the place for this discussion?). ED aims to make things as they are in RL, and that's how it should be. If that means the mav won't deviate from the target-point, then I have an issue with whoever invented the mav, but not with DCS. The fact that they actually carried the MAV-E more often is irrelevant for this. So to ED: If the mav is supposed to stick to the target-point, then everything is fine...ish If not, have a look at the track I provided a few posts back, or let me know if you need anything else.

Here is a track. I put 4 BTR-80's in the field, near waypoint 1. I designated WP1, and the Litening-pod slew to it. Then I targeted the first BTR and set a point-track. Then I SOIed the maverinck, which slewed to the target immediately. As soon when it became in range I fired the first mav. Immediately the second mav became active and also slewed to this target. No use in shooting it again but I could see the next BTR in the mav's seekerhead. I tried to slew to it, but it wouldn't move. I undesignated the target, and after that I could shoot down the 3 other BTR's. I hope this helps. FA-18 AGM-65F cannot deviate from TGT.trk

...assuming you have a pod. What if mission-control just gave you a waypoint and you'd have to kill everything near it ? You could do it with the seekerhead, but it's quit a hassle when you have to designate to find out the location, then undesignate so you can target something, trying to remember where the targetpoint was... Imagine you were a real FA-18 pilot, and your life would depend on smooth operating weapon-delivering... If you don't shoot quick, you will likely be shot yourself. And then somebody says "This is correct as is...". I would quit this job I can tell you. I'm going to make a trackfile now.

Again: not sure if this is correct-as-is, but is is different from DCS 2.5.1 I believe. When you have a target-point, and you uncage the AGM-65F, it automatically slews to this point and locks a target if it can find one, right ? In 2.5.1. you could then SOI the AGM-65F and with TDC choose another target and lock that. In 2.7.1. you can't change from that target-point anymore. You can undesignate target, and the maverick will be operable again.

That is correct. It doesnot step automatically.

I'm not sure if this is related, but I noticed that when you carry GPS-guided bombs, and they are populated with coordinates, then that has become your target-point. Don't know if that is "correct as is". But try to deselect the JDAMS and then try again.

Last week I learned that the HSI, not displaying the map anymore in scale 80 and 160 is actually correct "as is". Which is a pitty but so be it. Yesterday I found that the SA-page also can display the map. In scale 80 and 160 however I expect it also should not show the map. In stread it shows the map from scale 5. It actually doesn't erase the map after you have been in sclae 5.

No map in 80 and 160 ? That's just plain terrible ! That is so stupid ! If that is as it is supposed to be, so be it but I'm shocked ! Why ? I would encourage ED to deviate from realism in this case. Pfff, realism, who needs it ? Realism is for pussys

I only tried this in Caucasus-map for now, but since the update of may 20th 2021 the map in the HSI is gone in scale 80 and 160. Works fine in 40, 20, 10 and 5. I already deleted FXO and MetaShaders but that didn't work.

After today's update (may 20th 2021) this still applies, sadly.

After today's update (may 20th 2021) this still applies, sadly. Air-flow and carb-heat levers have become binairy. Please respond if this is intentionally. Also, at mission start, both levers are in the back-position. They should be in the forward-position in my opinion.

Thanks. Couldn't find that in the manual.

I'm not sure if this is a bug. I cannot find in the manual how it is supposed to work, but: In the HSI, when you select "Mode" and then select "DCTR", your position is placed at the bottom of the display. However, there is no way to put yourself back in the center. I would expect to press DCTR again, but that doesn't work.

So there is something wrong too. It seems you can't bind al the intercom volume-actions, except to a keyboardbinding maybe ? When you look in the axis-bindings you'll probably find the orange ones too.

Probably has been asked already, but what's the difference between the 25 and the 30-NA ?