skywalker22

Do you have the track, or tacview?

Exactly, this is the major factor which is far off how RCS "works" IRL comopared to DCS. So it really does not matter much (It only matters head-on, so nose hot) if there is some ambiguity between RL and DCS.

Wouldn't be easier to use HUD (HMCS) as SOI and create a new Markpoint over target, which is offset of waypoint, and for fine tuning use of TGP? At least this is how I do it. I doubt there is any easier way.

Personally I have my own audio even now on G2 Reverb. So this is not an issue here for me. But it would surely require 4090 for 5120x2560. But as said, hardware is not everything, if its not supported by the software. I would say its not very smart idea to preorder it, would be best to wait. ps: there will be audio, in form of audio strap (additional $100) - for those who are interested into it. and Full StreamVR support, that means something good for us as well

Missile missed by 3 feet that proximity fuse would go off

Button T for seperating contacts is not working well. It seems it only seperates some clean formations (if one after another, or from left to right), but does not seperate some mixed group of planes, or in environement with lots of planes on some small area.

What is your purpose of using off-set? You can always you Markpoints (using hud, tgp,..)

Chuck's manual, on page 688-690. It's all there.

No, I didn't pass out. This must be something wrong with the telemetry data, 20Gs (also on my as well). How is that possible? On the HUD max I ever saw, was 9,8 or something. 2x more? This has to be somehow connected with the latency. At one time there is 0G, next second is 20G (or some way higher number then 9). Example: And I was pulling Gs all the way, despite tacview draws a straight line, and 0Gs. What I really pulled was a circle shape and max 9.2G at max - according to the HUD. So here is the proof that DCS struggles in multiplayer, specially on crowded servers like GS is.

Well, since you were saying about this celebrity Moltar guy and his smooth trajectories, can you then explain AMRAAM's behavior from the video bellow. I went watching him, and I discovered this weird thing, just 2 minutes after we "met" in the sky - and btw, he should be dead by my missile, but miraculously my missile has gone stupid, despite perfect parameters (he wasn't doing anything to it that it should went stupid - but ok, lets leave that). Never ever seen that something before.

How can you tell the difference of the smooth/not smooth trajectories from tacview? By just observing it? I wouldn't take that as granted, as to be 100% accurate at all times. I am from EU, and I have ping cca usually 100-200ms. I surely cannot have same as those from the states/canada. And I agree on your last statement about calculations, but still, missile should still try to go into intercept trajectory (sooner or later (we talk in ms or seconds) and not just follow up it's target (which happens in many occasions - from me and to me). But again, latency can be a bi*tch, specially at this very high speeds, I won't deny it.

Yesterday on GS server - What do you guys think of my amraams. Red F-16 (Skywalker22) Tacview-20230209-145926-GS-server.txt.acmi PS: I would dare to say, that this is also the price we have to pay on overcrowded servers. Tried amraams on 3 different servers with 10-20 people, and all was fine, as expected. -- As @Ghosty141 said, it really seem that the missile tries to fly parallel with it's target, and not trying to intercept it - in most cases. You can see the proof of that on my example here as well.

I doubt this trick works IRL, but thx to @Furiz this works fine:

No need, here is the trick

Damn, just shot 6 of them from close range (hot 5-10nm), and none hit the target... waiting for server`s tacview, but something is definitely not ok here. This is getting worse and worse, lost all the hype of flying DCS.

I think you will get IC error using that mod in multiplayer on server which requite pure script. Better do the repair, and stay away of mods. Anyway, I tested yesterday using reflection on or off, there is no fps loss, so I turned it on, before I always had it on off (thx to you and this thread ).

Thx for that @Moonshine but what's also puzzling me, that @BIGNEWY didn't have those chevrons (as far as I understood him - based on his words). And another thing, this ECM Using option is not even used or turned on by default in editor - so how come it works in game?

I deleted F-16 module, and installed it all over. And its same thing. Why would jamming appear only in STT, but not in any other target type (system and bugged)? This makes no sense. If I would really get jammed, I would see that much earlier then 40nm on FCR with those chevrons on top of the screen like @Moonshineexplained (questioned). And surely not only in STT mode. There has to be something wrong here, because I doubt that's only me having this issue (if we all have same modules of course!). It's not that it's some kind of a big deal, but it can be frustrated.

@BIGNEWYso you are saying that when you lock into STT any of these aircrafts (bricks) F-14, F-15, F/A-18, M-2000, Mig-29S, you do not get any jamming chevrons over the bricks (contacts) on the radar scope between 40nm and 30nm, and not even any freezing of them (so they are standing still not moving)? They all work as usual, coming closer and closer and with no jamming chevrons? I will try to do as you said, delete the F-16 in the module manager, and istall it all over again. I have no mods installed what so ever, and never had any F-16 (double seater or any other) module installed eitgher - not interested into any, I am too much in love into yours

So there is nothing wrong? It's only strange that no one (BN and NL) could reproduce this issue. What about you?

One thing I noticed, when in STT, I got those 2 yellow symbols over the target like I am being jammed. Only in STT, when going a step back, those jamming disappears. Do you also get that?

I don't have any mods in there. So when you lock the target in STT (twice TMS UP), it moves towards you? For me it doesn't at least not to approx. 22-30nm (depends of the aircraft). If its not in STT, its all fine, but in STT, it nots (its as explained). Its a simple one, me in F16 and AI in what ever plane facing hot to each other (no matter of altitude). Always the same on all maps. I repeat, No mods, and slow repair done! I almost never use STT, but I used it today, and found this out.

Hi there @BIGNEWY I did as you instruced, but the issue is still there. f16_FCR_STT.trk dcs.log

When locking a radar contact into STT, no matter of the mode (RWS or TWS), from 40nm to cca 20nm, the target is not moving on FCR. It stays on approximately 35nm range. This applies for following aircraft: F-14, F-15, F/A-18, M-2000, Mig-29S and regardless of the map. Example is in attached track. f16_FCR_STT.trk

Not really, was just saying. I have G2 Reverb.