RPY Variable

1) Point one can't invalid, because is not a statement.. so no logic there. But the new statement you make is also invalid, because if I use the word with your criteria, a player that is not aware that on curtain conditions he may have certain advantage, he may not be "exploiting" that advantage. So therefore, some pilots may be exploiting some feature, some may be exploiting other, some may be exploiting all and some none. So if I want to refer to what advantage so-and-so is using or not using, this word, as part of the English vocabulary, fits. 2) And then, can you be a little more specific?. Since "you can home on jam pretty effective" is a rather ambiguous argument to put the kitten. I mean, you missed the argumentative part. I may be perfectly wrong, but prove it with an argument. Again, you mean with a mad dog missile?, or you can do some sort of jamming track with the F-16 or JF-17 radar to at least give azimuth and elevation to the missile??

1) exploit: "make full use of and derive benefit from (a resource)." What is the problem with that word? 2) In the F-16 you can't home on jam, and I believe you also can't on the JF, but I may be wrong on the latter. Maybe with a maddog missile, but good luck doing that at 30nm and dithout altitude information... so no, you can't.

Not jamming at all. Jammer OFF

Two double tap shots (4 hits total). One front aspect, other rear aspect and did nothing to a player driven Hind. The Vikhr warhead only weight as much as an entire Igla. In my opinion this is a bug. https://streamable.com/fyic2k

Same with F-16 yesterday... I couldn't see him while I was not jamming, but couldn't see him because of his jamming. Regardless of that, he was able to lock me up and shoot at me. So I wasn't able to burn through his jamming, but he was able to shoot at me while jamming at the same time, and not via STT. And the guy was clearly exploiting that all night.

Oh men. that was it. I needed to be logged in. I even went to the shopping card to se if there was an upgrade option. Thanks.

I didn't bought the A-10C upgrade because I didn't fly it that often and I didn't like to much the monocle thing, frankly not interested. But now, there is usually slots for A-10C II only on servers I play. So now if I want to fly the A-10 I need to buy it again at 80 usd... So I never touch the A-10C again. And I get the server slot logic.. with the 300 slots per server, having to add even more slots for the same aircraft is illogical. The last time, the BS1 and BS2 used the same slots, so there was not problem. But now for the BS3, it is going to happen the same as with A10C and A10CII. I'm not against paying for an upgrade, or whatever, but the methodology, with the "limited upgrade time" if not, 80 dollars to be able to use an aircraft you already own... not fond of that. So I learned my lesson, If I want to keep flying the K-50 I will have pay for the upgrade instantly because then your aircraft wont be on the servers. Ok... but I find it quite compulsory and it leaves me with a bitter taste. EDIT: I take back what I said. It still is 20usd for the upgrade. Last time I checked, I even went to the shopping card to see if there was an upgrade option. But when you login, the price changes. So it's not 80 usd for the upgrade, it is 20usd.

Yes I'm aware. I'm not talking about that. I'm saying that for example, the radar screen or instruments look good, but some switches look like if they were 5mm tall (mirage 2000C ins). Like there is no relation between the scale of two thing in the same cockpit. One thing is big and other is small at the same time.

For me it was a good first impression. Didn't find any obvious odd flight and ground handling dynamics that other modules had (and still have). Systems works more or less as expected. The cockpit looks good in VR, I don't want to name names, but some modules look good on 2D and in VR you realize thing are way out of scale, like some thing are big and other are minuscule at the same time, you realize that they where model pure eyeballing measurements. This one looks good, at lest nothin way to obvious. The only thing I can think of that looked weird, was the rudder pedals angle seem way to vertical.

Super Etendard... MM38 Exocet missile, carrier operation, INS and air refueling capability.

Would be nice to have a little more travel on this two switches. In VR the movement it is almost negligible (like 3mm) and you need to push the button multiple times to be able to guess the position. And it as a very important switch, it has to be toggled multiple times. On reality one would push or pull, and feel the feedback on the switch, but on DCS we only have our eyes. It is as simple as putting a little more travel on the 3DMax (or whatever) animation. I don't think this is a game-breaker modification. I'm really enjoying this aircraft. It may be my favorite.

The behavior is correct. You are not "updating the waypoint" -> you are using the waypoint to to update the INS. You are telling the aircraft, "you know that bridge that you think is over there... well it is actually over here".

Sort of.. The FIX position update part works fine. But it seems to mess up the markpoints you make after that.

Yes.. a FIX update to update the INS position. Problem 2 I will check in the afternoon but it should not matter because it happens right after alignment is complete. I make a Stored Heading (STOR HDG) align and before I move the aircraft, a waypoint with the aircraft location at start has the diamond at 300m from the actual aircraft location. DDCS server to be specific. But just to be sure. What should be the correct behavior in the following situation: Cold start -> align the aircraft -> make a waypoint 001 on the exact map position where the aircraft has started (without moving the aircraft) -> Where should the waypoint 001 diamond be?

I'm not refining the markpoint position. I'm updating the INS position with waypoint 1, and only then I am making a markpoint. The problem is that the markpoint is deviated from the position that it was made. Try it yourself. 1) Make a waypoint 001 on the end of a runway in the mission editor. 2) Then open the mission and, simulate doing a INS position update by moving the waypoint 001 diamond to the control tower. 3) Make a markpoint on some recognizable location, for example a bridge. And you'll see that when you CZ the markpoint it wont be on the position you made it.

It is as if the markpoint drift of where it point in relation at where it should be, is the same drift of the INS update between the old and the new diamond location.

Problem 1 a) I update the INS position using some known map static object. b) Make a markpoint via TGP over some target. Problem: The markpoint seems to be way off and no where near where it was made. It is my understanding that the markpoint is made relative to the aircraft location. So if the markpoint is made AFTER the INS update, regardless of whether the my position it true to my real position in relation to the earth, the markpoint should be pointing to the same target. Conclusion: I find it imposible to make a markpoint after a ins update. It seems that the markpoint system gets screwed after a INS update. Problem 2 In multiplayer I do a "stor HDG" align, and the position of the waypoints I made are always off in relation to the map. If I make a waypoint number 1 on the end of the runway the position is always off by like 200 meters. That is why I make an INS update to have the aicraft true to the map, but then I can't do any markpoints. I made a short track demonstrating the problem 1. F16_ins_mkp_possible_bug.trk

I had the same problem, even after multiple updates. I did a "repair and cleanup" and it fixed the issue for me. Maybe it also fixes it for you. https://www.digitalcombatsimulator.com/en/support/faq/repair/ My problem:

That seems to be the datalink targets missing. My fault. But still... it was not showing the search targets as well. I shot down two bandits by blind TMS up on a known location. Targets like 15 nm away. Even the AWACS was invisible to the FSR. And it was on a look-up attitude at 15 miles. Only visible by bugging him via TMS up on known location via HSD FSR cursor mirror.

FCR does not display datalink aircraft, it also doesn't display search targets (white dots). But if you press TMS UP (aiming the cursor via de FCR cursor mirror on HMS over a datalink target) and lock a target, it will bug a target and then show the appropriate symbiology and it will also STT. But if you are not lock at something, the radar just wont show anything. Edit: the datalink must have been the IFF OUT button. But wouldn't explain the missing white dots.

Also when you make a FTT the FCR background goes blank.

https://streamable.com/jkyj33 Two AIM-120 this time. I made one press.

I have 3 different problems that have no logic, are they bugs?. Problem 1: When I'm in expanded mode 2, or whatever on Ground Mapping, if I want to zoom, when I press the obs button, the radar resets itself. This wasn't the case before this makes work with the ground radar very cumbersome. Is this a bug? https://streamable.com/6u084b Problem 2: Trying to make mark points on Freeze DBS. If I select TMS up twice in other to store the mark points , the FZ image just disappears, it appears again a millisecond and the disappears again, so I'm unable to make a second mark point on the same FZ screen. So a) multiple mark points are not possible. B) The screen is black on after the first mark point. Is this a bug? Same goes If I TMS Right or TGT/OA1/OA2. As soon as I do it once, FCR screen goes blank, So OA1 and OA2 are useless. https://streamable.com/r6uprl Problem 3: If I'm on a DBS screen and find something, and want to make a mark point, when I select "7" (MARK) on the ICP, the FCR goes to AGR screen, so I have to go again to GM->DBS1->DBS2. So every time I want to make a mar point I need to configure the FCR all over again and find the tgt's again with the ICP previously configured. Is this a bug? https://streamable.com/2yih7g

It is possible. I have a ppt button that was use as PPT on a Cessna on my X-55 weapons release. The original was broken.

Well. I tried with settings back to default and wasn't able to reproduce the problem at all. I tried with FSR on/OFF, FFR, postprocessing, world scale, sharpness full/min, and maybe a couple more and it didn't reappear . I need to try more times and in many different scenarios in order to feel comfortable saying that it is fixed, but it is a good start. Thanks a lot for your time and effort.