Terzi

Do you have the correct emitter code entered? For Hawk it could be 203, 204, 206 for the current default RWR library in DCS.

You don't need the laser to fire mavericks in F-16. You need an image lock from WPN screen.

There are three control positions for speed brake: Speed brake OPEN works like spring loaded switch. It opens up as long as you keep it depressed and returns to mid position when you release. In the middle the switch keeps its current position. When you switch to close it closes completely and does not return to middle position. By the way there is no light for speed brake. It says CLOSED in the indicator when its completely closed and shows dots if its open. Its located on lower left side of the cockpit near the countermeasures panel. Check F2 view to experiment after assigning your keys.

Yes this is as it should be. Older block 30 aircraft was vibrating during FLCS test. Even that vibration was disturbing the INS alignment.

Thanks!

Hello, I have purchased the Apache with summer sale. I would like to ask for advice about good tutorials and advice on how to learn it. I have studied a bit but got a bit overwhelmed with all the buttons for CPG. I am looking for a fresh start step by step. Thanks.

Just to comment for choice "Otherwise": I don't fly FC3 aircraft.

Hello, Any tutorials how to use HOT3 in L model? Any videos? I searched YT but always find old tutorials.

Okay the title is fine. How about the hidden deadzone in maverick WPN page that I mentioned in the 1st post? Is it going to be fixed or needs evidence? Has ED even looked at it?

I think my original point was not clear. I was not complaining about FCR cursor speed. The problem I described above is: Maverick WPN page has some hidden deadzone and you can have hard time doing minor adjustments. (Was the topic title somehow changed?)

This needs a contrary evidence? How? Should I jump in a real F-16 (I wish I could) and make a video? This is about usability. Please test this: Try moving the Maverick WPN cursor by tiny amounts. You will understand the problem for sure.

Hello, I am a VR user I remember seeing other F-16 player's aircraft watching during taxi, takeoff and landings. The nozzle movements used to be visible. Now it is constant position in all non-ab states. Has something changed? If yes can you bring it back? If I watch my own aircraft everything looks flawless. Also I would like to note that control surface movements of other players are lagging and wheels of other AC are seen rolling during TO and Landings. I mean when he puts his gear down wheels are turning already.

Just a reminder. Any comments on this from officials?

Oh I did not see that. Thanks for clarification!

Hello, Since I cannot see it on the Viper Roadmap, I want to ask here. Are we going to get any updates on this system? I will not say here what is missing and where to look for due to our community rules. Current version what we have features an EGI (Embeddded GPS/INS).

Yes when you take a minor damage your fuel will very rapidly drop to 0 lbs at a constant speed. This legendary module deserves better

I might have missed, is the F-15E going to have a jammer? In release, in EA, post-EA?

Hello Bignewy, There are still lots of missing issues with normal, stored and in-flight INS alignment procedures and how the INS system benefits from GPS. Since I cannot see any additional work regarding to INS listed here, I am asking. I will not go through every bit of the procedure in here. Currently what we have now is quite simplified. For example, when you move your aircraft from one location to another, then try re-aligning, the jet will not read its location from GPS. This is an EGI (Embeddded GPS/INS) block 50. You can refer to sections 1-273 and 1-322 of the document called -34. I can open a separate topic if you need.

Hello, I setup my TDC cursor axis to have no deadzones in hardware and DCS settings. On the FCR I get zero deadzone (as intended) where I can move the cursor with excellent slow rates precision. But in Maverick WPN page there is a hidden deadzone that you can never get rid of. You need to move it up to some point (let's say 5%), and only after that point, maverick screen will move with 6% input rate. You can never move it with e.g 2% control. If the cursor graphs would be visible just like Right Ctrl + Enter I could show it. Please try yourself and if you cannot generate, I will try to make a video. Thanks!

It is the same buttons where you slew your radar cursor. nullPlease see the picture.

Some joystick brands' software assumes a key is pressed when an axis is moved beyond certain threshold. Alternatively you can choose a button press from settings.

I have the same issue. With the FCR page and TGP the slewing seems quite normal. When I try to slew the AGM-65 WPN page, up to some point slewing does not work (deadzone) then when it starts moving the crosshair moves very rapidly. Very hard to adjust it on a specific spot. Let's say putting it on a tank from 10-15nm. Just an addition, one may offer to do the adjustment from the axis settings, but in that case FCR movement will be affected badly. I am happy with FCR movement rate but same axis used for Maverick WPN page moves very fast.

Thanks Wyvern. I hope after the tests they add it officially.

Hi all, few questions: Is the PL-12 officially added to JF-17 now? If yes, why do we need to do it manually? Is this a mod? Is it allowed in MP servers?

Even if the visibility is clear, and you have good visibility and image can be clearly distinguished on MFD, your airframe needs to be at certain range. For example you cannot lock a vessel from 20+nm even if its a huge target on the MFD where real life image processing algorithm would lock it right away. DCS does not use image processing like real maverick does and rely on magic if the range is okay. For example you can lock a target even if it is behind the cloud and maverick actually points to it. I reported this before and it was tagged something like provide track or public evidence I can't remember which one. I did not provide because everyone can try this without needing evidence. Try placing it on a big vessel and try locking from 20+nm.