falconzx

I posted this video some time ago in a different bug report topic but here you can see exactly what happens. This is the default freeflight mission, i gain altitude and at the same time i follow the contacts at my 2 oclock with the antenna elevation, moving it down slowly, then at 0:46 i have a negative ~20° degree antenna, then i immediatly bug it. As you can see the antenna when searching was in the correct position and i understand it because it not wobble in a different position when i command the bug. Then at 0:52 i command unlock, meanwhile the target moved closer and my antenna was following him until its ~30° negative. Then at 0:58 and following i'm moving my physical axis to the max gimbals, as you can see i've lost ~30° positive. so now my antenna capability is not anymore +60/-60 but +30/-60. And the center is not anymore 0° degree, but -30°. i can't demonstrate this last feeling because you have to feel the physical axis center detent to know where is the center. But trust me when you are used to feel that detent, you expect to see your antenna at 0°. For an experienced pilot see it in a different position is quite destabilizing

Here you bug the target one single time in the whole video (2:00) so here we have only one chance to reproduce the bug, and probably you inadvertently reduced the amount of it because at (1:58) before pressing the TMSup you were moving the antenna like crazy . and you obtained the lock just because the radar due to its remanence remembered the target position you obtained at 1:44. In fact when you press your TMSup (1:58) the antenna deflect down automatically, leaving the more centered wrong position you were at the moment of press, this leads to a not very big decentering, but probably it happened anyway. Sadly you not tested the gimbals after that moment. If you want to try again just don't move so much the antenna around, it's not necessary to reproduce, you can pick the same mission, just put the antenna in the correct position(deflected down in this case) and leave it there when bugging (as the correct way to operate the radar to find that contact), TMSup twice like you did at 2:00 and then tms down twice to return to the base search state. Then try the gimbals up and down. PS. Put the azimuth to A1 or A3, i think nobody would use A6 in tws. Just to stay in the usual "testing" field. Thanks very much!

this is not correct! The absolute axis wrong recentering happens EVERY single time you do the steps to reproduce. If @BIGNEWY can't reproduce is because maybe he doesn't have a device with an absolute axis to map the ant elev knob.

The stuck issue maybe is fixed, but not the re-zeroing/centering on a wrong absolute physical axis value. (I described the re-centering antenna "way to reproduce" in this thread) It continues to happen. When you reproduce with the described steps(or just loosing the target in a real combat situation), the physical axis center doesn't match the FCR gimbal center, and the physical axis max gimbal doesn't match the FCR elevation max gimbals.

Anybody knows about this choice? In a BVR situation machspeed or TAS is just much more useful and senseful

That's because a lot of RL pilots use the hud repeater on MFDs

Squadron: 36°Stormo Virtuale Timezone: 18:00z - 21:00z Maps: Syria, PG, Caucasus

Actually i flew yesterday with my mates in the night using formation lights (Strobe only, preset C) in slightly open formations and it was nice. It's true that if you increase the distance lights tends to suddenly disappear. But we have the same with afterburners. P.S: Please do not turn the F-16 in a christmas tree like the Hornet was some time ago.

Thanks man for your feedback, it would be nice to have some positive feedback from ED on it. Maybe the topic title is a little misleading. The issue i reproduced in my tracks and video i posted is more about a wrong recentering of the axis range over the elevation gimbal. It means that if it recenters -20°, sweeping my axis it will result in a -60/+40 when it should be -60/+60.

There are good examples of amraams losing targets with no reason. Thanks for those. That behaviour before this patch was very rare. I hope ED is going to fix what caused that in a hotfix soon. Some of those examples contains near misses that i think should continue to happen, with the new physics it can be possible that in certain situations(drifting in direction change, noise from a CM) a missile can not reach the correct distance to detonate even if it guided itself to the target.

Oh the topic is "there is no BVR fight with amraam in DCS" so adding your statement it become, since 2 years there is no BVR in DCS with amraams. Just watch a random tacview from any day before this patch and you will see thousands of BVR examples. Trust me

The simple reason of that is: in real life you have just ONE life. Amraams like any other human artifact is imperfect but still dangerous for someone who have just ONE life. Here we have infinite lives, so don't blame ED if they make missiles more realistic. Just understand that here people don't have to go back to base to live another day, you can try and try to die more and more, and learn, until you find a way to survive even in a complex storm of imperfect missiles. Here you will have the opportunity to learn this. And this is something that nobody in real life will never do. So if you act in a "non realistic way" is not necessarily a simulator problem in this case, but a people's choice. So guys, just stop to speak about real life in an amraam topic pretending to know how an amraam would behave and how much hard should be evading it. Fortunately the real world never saw an half of what we see in a single hour of combat in this simulator. Someone speaks about "gameplay" like this environment should be "balanced", or even palatable to a fair "competition". Oh my.. this is not a moba game, this is a simulator, and the reality doesn't pretend to be balanced. And we are speaking about a BETA version, remember it.

It happened to me too when my wingman with pdlt active on him just passed in front of me while i got TWS active. The track file on him was created (and maybe i bugged him switching targets with TMS right on FCR) and PDLT octagon freezed in that position. When this happens if i make HSD SOI and i try to TMS right to cycle, the cycling action stops on the bugged one and do not step more foward.

At the moment i think this issue is the priority, it makes the missile quite useless. For the notching angle window, from what i tested personally it seems a little bit reduced, but i'm not here to say if it is easy or not, and I'm not interested to discuss if it should or not. At least until we speak through subjective statements. In DCS i think the intent is to reproduce a missile with all his flaws and limitations, how big they are and how they impact is not my business, i trust ED choices and its sources. For sure i would not love this simulator, and i wouldn't even call it simulator, if the missiles were a launch=kill weapon.

They still aren't automatically synced. Press 3 times TMS right (OA1->OA2->back to TGT) is a workaround for now.

Ok yesterday night i've made some tests with my squadron mates in MP. What emerged is a problem with the inversion of closure speed. Seems that the missile loses the target easily when the hot target just turn cold. No CM involved, just an extending turn. On the other side in some pure "notching" test the missile was pretty good, you need to be very precise on angles to get a lock loss, and it is quite fast to reacquire you like before. So what we suggest to the team to find the issue is to test the hot to cold target maneuvering cases.

Thanks for the dogfight workaround. ED please, we posted a lot of tracks, a lot of evidence of people reporting this issue in multiple threads. I can't believe it's still marked as "can not reproduce". The recipe is: use the axis for elevation, fight against a target with an huge difference of altitude from you.

In this track you can see two issues: -First, when i roll 180° degree, and i want for example scan the same area the contact is, what you can see from the carets is that radar is struggling to move out of the area i want to scan to retreive data of my bugged contact, this should happen when i search in a different portion of the airspace, and not when i'm searching in the same area. On the other side, when i scan a different area, the radar position is very close to the target... The same happens to the elevation but it's less evident in this example. -At the end of the track i make some rolls keeping my heading quite steady on 360°. Look at the Intercept course, it moves following my rolls, it's something that shouldn't happen. Actually seems that in RWS bugging the Carets visualization and the calculation subdued to that datas (apparently the SAM patterns too), are considering the antenna position before it gets gyro stabilized to match the MFD visualization. f-16_RWS_carets_scannedarea_and_InterceptCross.trk

Before posting in Bugs section i wanna ask how this instrument logic is supposed to work. I noticed that in RWS, more exactly in SAM mode or DTT, when we have at least one track bugged, the Azimuth and Elevation Carets are following a strange logic when they stop to the contact position to update the tracking informations. If you try it leveled it's all ok and seems normal, the strange logic is noticeable when you start banking, and it's quite evident when you are up side down, i mean 180° of bank. The intercept cue cross, seems following the same logic, i imagine you have to center it to the radar screen to have a computer calculated lead intercept course, well, it seems to be correct only when your wings are leveled, if you go, in the extreme case, upside down, 180° of bank, it's completely reversed. Someone have noticed that, yet? Best regards.

confirmed by experiences of mine and of my squadron, fuel leaks seems has been implemented recently but no vfx associated to it.

Ok, as i see this topic was marked as "cannot reproduce" i feel we need to dig more into this. Actually what i found is that TWS recenter the axis value after every unlock/unbug. This means that this bug can be reproduced without doing something odd or out of normal procedures. What i did in this video was simply entering in free flight, bumping up to reproduce a look-down situation, and bug a target then unbug. What i did after was just move my axis from 0 to 100% some times to show my elevation is not centered anymore and i can't move my antenna up more than a certain angle. Here i attach a track, in which i do the same thing. If it can help i use X-56 Rotary axis for elevation the marked with "G" one, labeled JOY_RZ in "controls". I have edited it with 25 of curvature, but i tested without it, and it happens in the same way, so that's not the cause. EDIT: you can also notice in the video that without moving the antenna, in the exact moment i unlock, the elevation instantly pops down. f-16_elevation_recentered.trk

Yep, it's a good thing, You can have different settings for different screens and modes, it's an awesome feature, use it

Steps to reproduce: -Set TWS. -Find a target, wich is a lot lower than you (that's very important!!). I just bumped 10/15 angels more than a 15/10miles bogey. -Lower the antenna and bug it in TWS. -Move the elevation axis DOWN and leave it there ( just the physical axis, it will not be affecting the symbology because the radar is scanning the bugged's elevation) -TMS down to unlock the target. -Now try to use the elevation, and tah dah, It's not centered anymore.

In the last patch, i experienced radar elevation freezes in TWS. Probably it doesn't happen to who is using buttons, i'm using analog axis so it could be only related to that. Anyway...it happens every time so it's very easy to reproduce. I just did it now in free flight mission. Steps to reproduce: -Set TWS. -Find a target, wich is a lot lower than you (that's very important!!). I just bumped 10/15 angels more than a 15/10miles bogey. -Lower the antenna and bug it in TWS. -Move the elevation axis DOWN and leave it there ( just the physical axis, it will not be affecting the symbology because the radar is scanning the bugged's elevation) -TMS down to unlock the target. -Now try to use the elevation, and tah dah, It's not centered anymore. Hope it will be fixed soon. It's a thing emerged recently, i'm pretty sure it was ok in the previous patches.

Squadron Name: 36° Stormo Virtuale Aircraft Selection: J-11, MiG-29, M-2000C, F-16C, F-15C, F-14B, F-18C Timezone : UTC+2 (+1 winter time) Pilot Roster: =36=Falcon =36=Drigo =36=Ghost =36=Merlin =36=Rabo =36=Darihawk(R) =36=Dankym =36=Redshark(R) =36=Eircog =36=Warhawk(R) =36=Mav =36=Tournament =36=Majo =36=Firo =36=Johnny =36=Devil =36=Falez(R)