Harker

It's exactly that. Only the sun and the moon can fully illuminate exteriors and cockpits and cast shadows. The SC lights, airport runway floodlights, aircraft lights and some ground vehicle lights can illuminate the terrain and exteriors, but not cockpits. Everything else, such as airport apron lights, city lights etc are not lights at all, just textures and thus don't illuminate anything.

NATOPS NFM-000 gives the limitations for coordinate entry when creating a waypoint. There are no mentioned limits for elevation entry. I'll pm you the exact page.

1. This is correct behavior. When you have an L&S designated but you're not in STT, the undesignate button will step through MSI trackfiles in order of descending rank (or swap between the L&S and DT2, if you have a DT2 designated). To completely remove the L&S (and DT2), you need to select RSET. 2. This is also correct-ish behavior. When in STT from RWS or TWS and the undesignate button (or RTS) is pressed, the radar will simply exit STT and return to its previous mode. It'll keep the L&S designated. The issue with 2 is that the L&S shouldn't need to be detected by the radar again, to become designated after exiting STT, it should simply remain designated upon exiting STT. This is because, in DCS, MSI processing stops as the radar enters STT from RWS or TWS, whereas this shouldn't be the case. MSI trackfiles are not the same as radar contacts, although in DCS, the essentially are the one and the same. In reality, they're two different systems and the radar is merely one of the contributors of the MSI system.

Yes, the interrogator module still emits a radio pulse. IRL, it's possible that an RWR will filter it out completely or show it as an unknown emitter (assuming it's in the bands the RWR detects, I don't know the exact frequencies that IFF systems work in). But even if the RWR doesn't pick it up, the IFF antenna will and if your jet doesn't have the correct keys and can't reply to a Mode 4 interrogation (coalition specific), you'll be notified that you were interrogated and failed to reply. In the F-18, for example it's an "M4 OK" or "IFF4" advisory (Mode 4) for successful and unsuccessful replying and you can also have the voice message "Mode 4 Reply" played. So you'll know that someone interrogated you. All of the above are not modeled in DCS as of now though, so if you interrogate someone with your radar off, they'll get no warning whatsoever.

For dumb CBUs, the HT setting is for the jet to calculate the correct bombing solution. The burst height itself is set on the ground, on the bomb itself. And we're still limited to 1500 ft in DCS right now.

IRL, if you get interrogated and fail to reply, your jet will let you know, either with an advisory, audio warning or both. In DCS, this is not implemented in any module, AFAIK. Also, since the OP mentioned changing the radar range, this setting only changes the display range. Your radar will still radiate the exact same way, no matter the range of your display (notable exception is the F-18, where it'll default to MPRF while you're at the 5 NM scale). But you should should be able to run IFF interrogations with a silent radar, since the two are different systems.

Thanks for the kind words and sorry for the late reply! I recently stopped getting notifications from this thread, for some reason. First question: Choose Static MFD reflections, as my mod is replacing the textures related to this option. This leaves you with the option between using my "LCD" displays and the traditional green DDIs, without fake reflections baked in. Second question: Thanks for pointing this out, I'd missed it. I updated the mod and made the lines appear white. Not off-white, as the MDI font. The crosshairs are part of the Maverick video and the missile outputs the video only in grayscale. On the other hand, the display options are controlled by the aircraft software and thus have this off-white color.

Sorry for the late reply! You don't need to use OVGME. I specifically made it like that in order to avoid triggering IC. If you still want to, make a copy of the FA-18C-CPT-TEXTURES.zip, located in DCS World\Mods\aircraft\FA-18C\Cockpit\Textures\, place my f18c_cpt-displayglass_refl.dds and f18c_cpt-displayglass_refl_RoughMet.tga files in there and delete f18c_cpt-displayglass_refl_RoughMet.dds. Then, you can install it with OVGME as usual. While you're at it, you can install the other files for the Mods directory with OVGME as well.

The only things that actually emit light properly in DCS are the sun and the moon. Next, you have aircraft exterior and gear lights airfield light trucks and some vehicle headlights, that illuminate the outside world and objects but not the cockpit interiors and they also don't cast shadows - very simple implementation. Every other light, namely street lamp lights, airport apron lights, apartment lights etc are not lights at all, just bright textures. Their effect on the ground is also just a texture, baked on the map. They don't illuminate anything and they emit no light at all. The latter is the reason why cities etc don't give off any ambient light in DCS. Thus, there is nothing to illuminate the clouds above or the surrounding terrain.

And contains all other user options as well. Backup that entire folder, see if the problem fixes itself and if you're up to it, then you can copy back your old files one by one (copy one thing, go in-game, see if it works - if yes, continue, if not, you've found the offending file).

In DCS, ECM (noise jamming) can degrade the performance of radar-guided missiles, by denying range information to the launching radar and thus preventing the computation of an effective interception trajectory. Instead, the missiles will head directly towards the jamming source, which is a very ineffective way of guiding. Also, noise jamming in DCS is 100% effective up to a point (usually 21 NM) and completely ineffective after it, simulating burn-through. It should of course be a more gradual shift and the burn-through distance should depend on the radar in question. As for IR guided missiles, some aircraft such as the Su-25T (and the Ka-50?) have DIRCM systems that can mess with the guidance of IR guided missiles, by flashing infrared radiation in an attempt to confuse the seeker. This is different from ECM, however, which has a completely philosophy and operates in the radio frequency range.

Good catch. There's a video out there, that's showing the GMT sweep in a IRL cockpit, that we can use for reference. I don't remember how to find it, but I'll look.

There are two issues here. The first one is the increased RCS of missiles, so they should up on radars all the time. While an A2A missile could technically show up on a fighter's radar as a raw return, it's generally unlikely and getting a full track from it (which is what happens in DCS) is even more unlikely, because the radar will likely won't correlate the returns. This is all based on conversations with IRL fighter pilots who operate these radars regularly. By extension, it's likely that the same inaccuracy exists in FOX3 radars, in DCS. The other issue, as GGTharos points out, is that FOX3 radars currently lack gates of any kind. A FOX3, once active, will look for the target that matches the range, velocity and velocity rates of the one that the firing platform is tracking. It stands to reason that it'll be able to differentiate between different targets in front of it. Only if it can't find the intended target, will it throw the gates open, in an effort to locate it. Also, IRL, the fighter-missile datalink does not get severed when the missile goes active, like it does in DCS. The missile keeps receiving information on the target and correlates it with info from its own radar, for optimal tracking.

I don't see how this is even an issue. I physically need to stand up in order to see above my canopy in VR. I cannot do that during ACM, for example. And I can't look through the fuselage, under the aircraft, because I'd need to sit down on the floor. At best, I can stick out my head out the side, when seated, which might offer a very minimal advantage, if any. It's certainly not something I've ever thought about during gameplay, it always fell into the "ah, that's neat" category.

Try unboxing ALG (Automatic Level & Gain) and adjusting the Level and Gain values yourself. As soon as you unbox ALG, you'll get the LG option next to OSB1, click it and you'll be able to adjust level and gain values using OSBs 2/3 and 4/5 (they'll replace ZOOM and FOCS). You can also play with the DDI contrast knob and see if it helps, in addition to adjusting Level and Gain.

Cage/uncage works now.

+1. I like the idea and I've expressed it in other threads as well. As someone who has no interest in the early Cold War era and minimal interest in WW2, I'd prefer to just save bandwidth and storage and not download anything more than the default livery for every such module.

Should also say GO STT instead of GOSTT. Small typo

I've experienced this on occasion and it's really annoying. If I forget to set the "Silence" command or it bugs out for some reason, I just change the channel. Although I don't play a lot of SP nowadays. If you can, create a small track that shows the problem and submit a bug report .

Pretty clear here. Although not the same Lot as ours, I can't imagine that this would be different.

Tested as well. Tracks correctly with STT from ACM, but not with STT from RWS/TWS.

You should go STT before launch though, with MSI, especially if your frame times are long. The radar should also transition to TWS AUTO on the L&S from RWS/LTWS, but we don't have that yet.

Don't try to enter STT with the TDC. It works, but it's a bad habit and it can create problems with closely spaced contacts. Use TDC Depress to designate your L&S (and DT2). You can then command STT on the L&S with Sensor Control Switch (SCS) towards the radar, when your TDC in open space (not over a contact). So you don't have to deal with double clicking the TDC, potentially designating the wrong contact in the process etc. You can also command STT by hovering the TDC over a radar contact, without having to designate it as the L&S first, even if another contact is the L&S. There is also functionality that's correctly not present in DCS, but will hopefully come in the future. Specifically, MSI processing stops when you enter STT from RWS and TWS now, in DCS. But it shouldn't, meaning that you'd still be able to view offboard and radar memory (memory also isn't working correctly right now, plus there's radar memory and MSI memory) HAFUs while in STT. You should also be able to designate any of these HAFUs as the L&S/DT2 and attempt to STT it with the SCS, as described above, even if your own radar is not currently seeing it (it'll command your radar to look at that azimuth and elevation and attempt to locate and lock that contact). Hopefully these features will make their way into DCS and increase our quality of life significantly.

I also thought about that. You might get a brick here and there, but more likely than not, a trackfile will not be generated and maintained. That's from conversations I've had with IRL fighter pilots who operate mech radars regularly. There is also the problem with the Hornet in DCS generating a trackfile from a single hit, whereas it should normally need at least two.

Did you try the "Use system resolution" option in the VR settings?