escaner

In RWS/LTWS with a reduced azimuth scan area, how can you select now where to point the antenna? It defaults to center, but I would like to move it left or right. Clicking with the TDC just tries to go STT there. Thanks

The HMD automatically rejects most of its symbology when looking through the HUD, but when we have an A/A target locked, it displays its TD box anyway in the HUD area. Therefore many times we see two TD boxes in the HUD: one drawn by the HUD itself and the other one by the HMD. This situation is very confusing for me, because most of the time they do not even match position due to field of view limits in both displays. Is there a way to prevent the HMD from displaying the TD box in the HUD area? Is this behavior even correct? It seems so weird and confusing... PS: sorry if this has been discussed earlier, but I cannot find any post about it. Thanks for your help

Indeed, both the F/A-18 and F-16 have been at 50% discount during the pandemic confinement sale and free trial period in March-April-May 2020. I think that they were again at 50% later at the very close summer sale, but not sure there. There were also coupons advertised by several Youtube channels that increased the discount further by 5% IIRC. https://www.digitalcombatsimulator.com/en/news/2020-03-18/ They never have reached those discounts again though.

Thank you NineLine, I appreciate the feedback.

Now that there seems to be some F-5 love again, maybe you could look into this 4 year old bug report that never got any answered or fixed. I am attaching a track that basically does the same as in the first message description and the video. Thank you. f5-df-rdr-bug.trk

I have uploaded the trackfile here, but even at 2x speed it deviates from the actual events pretty soon for me. The maximum closure with the "ghost" happens about 29 minutes into the mission. My radar could see the contact (upper HAFU) even at over 80NM and when not scanning its position, and as dorianR666 says, Tacview does not show anything at its position. https://drive.google.com/file/d/1AKGGp4UzfucH71_yP3yfxlUuYeoctSg5/view?usp=sharing Edit: I have tried the track also without acceleration and it also does not work for me: at some point my aircraft starts turning to the left and going upwards instead of following its actual flight. But this kind of things has always happened to me while other people say they work for them, so who knows.

BIGNEWY, I don't know how to replicate the problem. there should be a couple of tracks from multiplayer sessions in my disc, but they must be 3h long, probably not useful. Would a chunk of video streaming help?

I keep finding these bandit air to air contacts. I can lock them but visually there is nothing there (see screenshot at 0.1NM range, it should be perfectly visible). I will not lose lock on them even when they are behind my aircraft, out of gimbal limits. AMRAAMs do not track them and Sidewinders do not give me tone either. I cannot find any post about them in the forums. What are they? Is this a bug? If so, has it been reported? Thanks

These CMS hat changes aren't supposed to be something related to the newer suite in the Tank Killer module? Also, the original Warthog module manual was not updated, which is inconsistent to updating the CMS functionality as happened in it.

In the book "Hornets over Kuwait", Jay Stout (USMC pilot in 1991 ODS) says that for CAP (defending their air base in Bahrain IIRC) they were taking 2 fuel tanks (one under each wing), 3 or 4 Sparrows, 4 Sidewinders and full gun ammo. That is weird, because in order to carry 4 Sparrows they would need to carry one of the tanks in the center pylon or drop 2 Sidewinders, but I guess you get the picture.

High lift devices. That is the generic name for flaps & slats in aviation.

I had this issue with buddy lasing on November 3rd on OB release, but I remember the vehicles moving to another place when destroyed from longer ago, which I guess could be related. @uri I don't knot whether it has been reported or not.

You definitely can buddy lasing Hornet to Hornet, I did it a couple of weeks ago, but there is an issue where the guy who was dropping the bomb (he was also hosting, not sure if that matters) did not see the vehicle in the same place I did. So I saw the bombs explode right on target, but they were not destroyed because _his_ bomb was not hitting the target in _his_ sim. When the target was eventually destroyed I could see it jump to the place it actually was in his host.

Yep. Actually to add even more confusion, in the F-14 you launch rockets with the trigger and in the F-18 with the pickle button.

Thank you guys for the replies I guess it is the similar with HMD guiding the 9X without radar ACM modes enabled? I thought I would need to press uncage when the target was under the seeker, but had inconsistent behavior. It could also be what you say: just uncage once, I am gonna try that.

What exactly is supposed to do this UPLOOK mode in the AIM-9X with the HMD? It is enabled with castle down from HACQ and disable with castle up. Also, when moving the AIM-9X around out of HACQ, I can hear a sound that reminds me of the RWR, but looks like it actually is the 9X. What does it mean? Thanks

Same here. If A forum is not on Tapatalk I stop using it altogether on the phone.

You should really refrain to make agressive comments like this when you obviously don't know what an encoder is or how it works. Hint: they don't work with axes.

I tried binding rotary encoders to the HDG and CRS 2 way switches in the F-18, but looks like their standard DX pulse in each "click" is not long enough. Sometimes I see the switch in the 3D cockpit slightly moving, but the actual HDG or CRS value never increases or decreases. Then tried different DX pulse lengths with TM TARGET, where I can easily configure them. The standard 32ms pulse does not work and the maximum the GUI allows (50ms pulse) is still hit and miss. Sometimes it registers, sometimes it does not. Binding the encoders to other similar controls (COM channel, radio volume, RWR volume, etc) works just fine. Anyone has tried this?

I don't have a crash log because my instance does not crash. AFAIK, he sent the automatic crash report.

Anyone having this problem? I have modified Cage the Bear mission #2 for multiplayer, selecting the plane as Client instead of Player and launch it with my computer as MP server. Then I join as RIO and my friend selects Pilot. When I give an order to our F-14 wingman, my friend's DCS crashes. When he gives an order to our wingman, there are no crashes. We are running the open beta version. I saw a fix for something similar to this in a recent patch release, but it still happens to us.

Video showing the problem: Mission attached Loadout: 8 x GBU-12 + TGP + 1 x AIM-120C + 2 x AIM-9X + 1 Fuel tank Steps to reproduce: 1. A/P - BALT 2. Select weapon 82LG 3. Select Master A/G Mode 4. Bomb MODE: MAN 5. Pickle 3 times to drop 3 bombs 6. Deselect 82LG 7. Deselect Master A/G Mode 8. JETT STATION SELECT: LI, RI, LO & RO 9. SELECT JETT - STORES 10. Press JETT -> DCS hangs F-18 jett crash.miz

I would definitely use it to get rid of the ladder, which is misleading. Actually was trying it from time to time to see if it was finally implemented.

Thanks for your thourough reply QuiGon OK. In this case, TWS Auto is supposed to automatically change the azimuth width and bars if necessary (e.g. several missiles on the way with aircraft separating one from the other) or should I still do it? I don't think it is that because actually there can be several flashing contacts at the same time in TWS. I wonder if it means that they have arrived to some range (maximum, optimal, etc.) or that the computer has a valid track to launch or something like that.

Yesterday I tried flying RIO in the F-14 with a friend and had a few issues plus many doubts. I hope someone can help me. I was server for the session: 1. In TWS Manual, every time I fired a Phoenix it changed to TWS Auto. Is this normal? 2. In the previous scenario, if I changed back to TWS Manual and changed the azimuth from narrow to wide, the tracks disappeared (only did it once, didn't want to happen again). Anyone experiencing this too? This was happening to me some time ago changing range, or between TWS and RWS, but I though it was fixed. 3. The manual says: "The launch zone vectors are activated manually by the RIO or when time to maximum launch range is less than 60 seconds and replaces the normal track velocity vectors." How does the RIO manually activate the launch zone vectors? 4. What exactly means when the contacts flash in TWS? 5. When as RIO I select the TCS view, the pilot radar screen (TID) goes blank. Is this normal? 6. I could not hook my contacts (hafu on top), but I could hook datalinked contacts (bottom hafu). I would say that some time ago I could hook my own radar contacts and then STT with the radar mode button. This cannot be done anymore? 7. Is there a way to move the display to see more airspace behind my own aircraft in the TID, eg my position in the middle of the display? I can move it forward, but not backward with hook + HCU offset. 8. After some time, datalinked and radar contacts seem to appear at different positions, no longer correlated. This is INS drift? Can it be easily fixed? 9. Both times that I talked to our AI F-14 wingman, my pilot's DCS crashed. I think we were not even in the correct frequency, not sure if that matters. Anyone has experienced this? When this happened, my aircraft stopped in the air and I was dumped from it even when I entered the aircraft first. I hoped to pause and wait for him to reconnect, but obviously it was not possible. Thanks a lot!