darkman222

Everybody hopes for. With obviously different priorities. Yep. I was just responding because I was quoted. Your issue is logged and registered by ED. Now its in their hands to deal with it. Peace man.

The F16 is far away from a point you'd even think of polish, is what I am saying. I did not say you should not report. I was saying to put the level of urgency it in perspective. Do so. And dont forget to tell heatblur devs that the F14 pilot cant be shot at although it has been requested for ages now because it is highly relevant for competitive dogfight events.

But the OP question points to this exact moment You need to guide it until it goes self guided. With STT, only spikes from the locking aircraft no missile warning. With RWS softlock only RWR nails, no misile launch warning. When the AIM120 goes pitbull: Missile warning. With the AIM7 immidiate missile warning when being guided through the mothership. That should be or was the case when I did some tests with the F18 with Aim120 but also with Aim7, more than one year ago.

Yep. If I was unclear, that was what I was trying to say. But this leaves another off topic question. Why can the RWR detect a launched semi active missile Aim7 Sparrow which is also guided through motership illumination and some kind of data link to the target, but why cant the RWR detect the guidance of the AIM120?

Wow. Reinstalling the OS. Thats dedication... just kidding. I did the same in another case. But I know this is not the solution youre looking for, but cant you use steamVR for the time being? It never stopped working for me that way.

@BIGNEWYThank you. I am not saying that it should be changed. I am just saying that the way when the LOS circle was shown before serveral updates makes more sense in practical way. If it is only shown when pressing TMS up, it gives a less useful information instead of when the LOS circle is shown already while its travelling to the TD box (visible in left MFD). But if thats the way it works in the real jet, sure, no complaints. Also what @Lord Vader says (in his updated post) is not the case. Please watch the second video I posted again. The LOS symbology is NOT shown after these steps. Which is another indication that something might be wrong here.

@Hobel It kinda does. What needs to be done beforehand is a TMS up, it will show the LOS circle anyway then. If you go DGFT on and off it will break the lock / ground stabilisation and the TD box is free again, with the LOS circle chasing it. @Lord Vader Can you please have another look at this issue? Although I am not a fighter pilot my senses are that this cant be correct and is also very impractical and very inconsistent.

VRam is always near 100%. I also suspect this a reason for stuttering. Regular RAM is only maxed out on MP Missions on the Syria map.

Userfriendlyness yes, but please ED, do nothing that affects multiplayer performance in a negative way!

Thanks. For the guys with the big pockets aiming at 90 fps (Hz): Varjo Aero ( I also have a Pimax 8KX), RTX 4090, Intel 13900KS Summary: 90 fps possible, GPU can sometimes be the bottleneck, but set to 3000x3000 pixels is "low" enough that the GPU is not getting in the way. CPU bottleneck is still very often the case. With the 13900KS on 4ya Caucasus Server I might say like 30 % of the time youre getting in CPU frame times over 11 ms which causes stutter. Worst example 4ya Syria server going up to 16 ms. Permanent stutters. Single player missions highly depend on how they are setup. A sinlge F16 on Caucasus with no other aircraft in SP goes to a frame time of 4,5 ms which is a butter smooth 90fps experience. But no mission is setup like that of course.

You can do that because SRS is a separate running program. I would not recommend it though. If you do, you can create a lot of confusion, as the transmission for someone who has both running SRS and VoIP will hear the same transmission double and with a delay. We had that in a flight with our squardron and the issue was very hard to spot until we found that some people were listening to both systems at the same time making the transmissions almost unreadable. Better chose one or the other. Or at least use different buttons so at least you know where youre transmitting.

But given the fact that the ground around the airfield is not flat you could not use your RADALT for flying a circuit approach reliably. So you need to calculate the airfield elevation from your QNH altitude. If you dont have the aerodrome chart, approach or someone else needs to give it to you then. Is that right @Lace ?

This is what I am talking about. The difference to my procedure only was as follows: -(after TMS up long) DMS down short to refine target. The result is the same, that the LOS symbology is NOT shown on HUD or JHMCS. Thus the pilot has no reference in the HUD or JHMCS where the LOS seeker of the Maverick is looking. Also not knowing if the seeker is still slewing to the TD box in the JHMCS if he is looking outside of the cockpit and not glancing with the eyes on the MFD. Because if you look at the MFD with your head the TD box will be moved away from target and so will the LOS seeker of the Maverick, which of course not intended if you want to assingn a target via JHMCS. Please see new video and track with the procedure you suggest @Lord Vader https://www.dropbox.com/s/0p6y0o06svd9hyx/mavD vis LOS not showing.trk?dl=0

Cant test your track cuz I'm at work, but isnt the low pitched missile sound telling that its an active missile that is still tracking. Wasnt it changed like: new active missile -> high pitched sound... if still active and tracking after 15 sec -> low pitched sound.

In reality if you STT lock a hostile he will receive a STT lock from your aircraft. If you fire your Amraam it will be guided through the Link16 from your jet, thus no missile warning yet. So if you just RWS "soft locked" him he wont hear any warning. Just nails from an F16 (whis is not audible currently in the F16). If you STT lock him, he will get a F16 spike warning from his RWR. When the missile is not guided any more by your jet he will get a missile warning. Out out curiosity I tried it once between my 2 PCs with two DCS installations. It seemed to work that way. At least one year ago. When the F16 will get the PRF tone library the audible RWR sounds will change a lot. Be aware of what your learn now you'll need to unlearn at some point.

Makes sense. Kind of. As I did not enter any coordinates , and we dont have the Catridge yet, I think DCS assumes there is a imaginary cartridge with the coordinates already inserted.

Varjo Aero in native mode aka no steam VR had worse performance than with Steam VR for me. So as I am using the Aero with steam VR it never stopped working for me.

To conclude my testing I have uploaded a short video. Result: In MIZ pre GPS era INS drift is modelled. I will drift about 1100 ft per hour. If you start up cold, ground aling, without entering coordinates, it will give perfect GPS alignment, which will start to drift over time too. About the ground align without entering coordinates I am not sure, but the rest looks pretty realistic I would say.

As shown in the video by Grim Reapers (31.12.2021), the Maverick seeker heads movement is visible in the JHMCS and HUD. This is not the case any more in DCS 2.8.6.41363 Open Beta. Reproduction: -AG mode -Select Maverick (VIS mode) -go to WPN page -look out of the cockpit with JHMCS -TMS up long -Seeker visibly moves on the MFD, but not shown on the JHMCS or on the HUD -TMS up short seeker, stops at current position and shows in JHMCS -TMS down, seeker continues visible in JHMCS too now. Looks like a bug to me, because it makes more sense how it used to work in the Grim Reapers video. Issue was already in a few OB versions earlier before I decided to post it. Does not matter what Maverick variant ( D or H) Track: https://www.dropbox.com/s/x66hefdcj0rpyz6/mavD v2.trk?dl=0 Video:

Quite some while ago, I made this video. Also as an instruction to myself, when I have to setup a new operating system and cant remember everything correctly. The problem is the cryptical ending of the input files. But they are consistent in one operating system installation. Once you get used to this procedure it does not take longer than 10 mintues to setup a new operating system / PC with the same physical hardware controllers:

Thanks you brought this up. I was trying to use TMS right for multiple targets as I thought it used to work but it did not any more. Thought I was missing something. Following the thread now.

VR for me too. Specs with Varjo Aero. Not the worst system null

Your frame test ran fine on my system. Cant confirm that one.

Itll sit on top. And you need DCS running below for the crosshair if you want to grab coordinates.

I dont know what you guys want to prove here. Watch the videos about folds of honor where there was G limits introduced and monitored. It was done for the fly by wire aircraft too. Because you can catch the G limiter off guard. More in the F18 than the F16. As the F18 relies more on instantaneous turning. It is not unrealistic or gamified. In the F16 you can even trick the G limiter by simply doing a loaded barrel roll. Which is realistic, because the F16 FLCS is only good at monitoring on axis the same time. But in all cases the G limiter ( both F16 and F18) catches back on and does its job as intended. And that kind of over G ing in the F16 is treated as every other aircraft over G ing with an extra in depth inspection and being grounded in first place. Of course there might be still a lot of FLCS behavior wrong in the F16 but in that special case i believe not.