Galinette

We already fixed a radar stuck in TWS bug, coming next update. In that case, using mode reject should go back to RWS, though.

No, I confirm this is likely a bug related to the module HRM radar accessing units that are being deleted by the engine. Such a bug has been already fixed, this comes in next openbeta update.

I confirm that currently SORT mode will use the EL setting. I missed the actual behavior. Fixed (too late for next update, will be more likely in november)

(developer here) No, they will only show on active radars. Not because they emit, but because they either scan across your position, or are tracking towards your position. In game both give the same effect because it's not possible to discriminate the cases. I believe that IRL a scanning antenna will create the whiskers, while a tracking antenna will only create a powerful return that smears horizontally. And yes this is not interference, but purely caused by the antenna retro reflection.

Yes, that's because AoA sensors are more as ideal , feather like. They move with every minimal breeze or turbulence while on the ground. IRL sensors have some mass and a little bit of friction, so they will be stuck on the ground if winds are light. They can show a similar behavior under very strong turbulent wind. In many cases the aircraft will ignore value below a threshold CAS. So yes, it's not 100% correct, but not 100% a glitch either. Should be improved, but not a big priority at the moment.

The gyro compass would like to have a chat with you. Edit : I was certain that the gyro compasses you find everywhere were purely inertial, I forgot these are slaved to magnetic sensor. My bad You are fully right that most (and even 100%) of western aviation works on magnetic headings, and that DCS ATC is wrong.

Thanks for reporting, this is now fixed! It may not make it for next release, but the next one.

Damn, smaller FOV than the G2? Loosing the stellar microphone, acceptable audio, and the already not so good FOV of the G2 might be a no go then... I'll wait a bit more too see what's coming next. I guess that with a half price offer Varjo has something under the hood.

Doing a mod is quite straightforward, you just need to rescale the textures (keep in mind you need to keep power of 2 size and save the texture with mipmaps). However, it will most likely break integrity check. I agree that having a default base DCS install with low detail models, and the option to download high detail versions for each aircraft or in a pack, would be a plus. This should be requested in general DCS forums.

(RAZBAM answer) ASL is wrong in presence of INS drift, but not enough to be stuck on the side of the HUD as you experienced. This is fixed for next release. It works fine if you are using EGI (mission date set after 1997). But it is unlikely the cause of what you describe, which looks like user error. By purchasing an Early Access module, you had this information: Writing here that you are disappointed is fine, stating this is "fraud" is not.

Really? Like 90 FPS ? Do you have special mods / fixes for this or is it plain vanilla DCS with OpenXR?

Here they are : 12900K, RTX3090, 64Gb DDR5 Though, my question is not "Do you think this spec is enough", I know people use an aero on similar setups. But rather "Do people usually notice a decrease in FPS between a G2 and an Aero" on the same system, I'd be interested knowing if anyone here moved from a G2 to an Aero and what was the result.

Hi everyone! How would you value an Aero upgrade from a Reverb G2 for exclusive DCS use? Does it require more ressource or may I keep a similar FPS? The 990€ sales are really tempting. Thanks a lot!

Magnetic is a huge mess because the correction varies in time and space. Its only reason to exist is the use of magnetic compass. Inertial navigation and satellite positioning natively use true north which is a stable reference. It's very complex to abandon magnetic, as everyone needs to make the switch at once. Though, it is seriously considered in some places where magnetic is a real pain in the butt. https://www.icao.int/safety/OPS/OPS-Section/Documents/ICAOSL087Doc1_presentation.pdf

Here is the update! Will be included in october patch: F-15E: - Fixed a bug where TWS freezes the radar in presence of AoJ returns - Fixed TWS struggling to convert a HoJ track into full track in some cases Second line should solve most issues people had, misinterpreting them for wrong burn through ranges. This was in fact track correlation / kalman filtering problems, you can see the actual "burn through" ranges in RWS quite well as every return is displayed without track processing.

Okay, this track helped finding a nasty bug causing TWS to get stuck. Thanks a lot! Hopefully this will solve all above problems

Hi, thanks a lot for the track! I'm trying to analyze it. I'm not sure it's really stuck in this case, what I see is a multiple "end of bar" event caused by some unidentified yet scan pattern bug that causes the TWS frame to prematurely end and brake the lock as no contact is found. It doesn't look stuck as in other reports. I will look at what goes wrong here anyway. If anyone manage to makes a similar short track showing the actual "stuck" state, and let it running in that state a bit (10s is enough), this could be extremely helpful.

Yes it does

Drift rates ARE that much. Commercial aircraft do have several NM of drift after a transcontinental flight. They don't need more precision though, landing is not performed using INS. Without GPS, they use radionavigation beacons (VOR, ILS...) and ATC radar. INS is just a fully autonomous backup way of roughly knowing where on earth they are. What SloppyDog explained above is a simplified version, but he is mostly right. Drift will NOT get to a limit and stop. A more complex picture : drift is not linear but a stochastic process. It will randomly drift in continuously variable directions over time. The advertised rates are not a constant, but a confidence interval (aka n.sigma). So it says that after one hour, there is a good chance (95% if this is 2sigma) that your drift is lower than 0.8NM. It can be zero if you are very lucky, or more if you are very unlucky. Even more complex picture : the drift rate variance is not even constant over time, it follows a 84min oscillation. It's about zero after ground alignment, then increases to twice the advertised value after 42min, and back to nearly zero after 84min and this cycle starts again. On average over 84min it's the advertised value. A perfect velocity update resets this cycle. The 84min is related to earth gravity and radius. Now yes excessive drift rates have been reported, there is likely a bug. It will be addressed at some point

The Eclair-M with proper SPIRALE integration. Before this additional decoys were loaded in a cheap DIY dispenser with an additional box in cockpit not integrated with the CM suite. The old box isn't anymore in the DCS model but it's still possible to restrict loadout to remove the Eclair-M in the mission editor.

Check this, it's a M-2000P RDM video featuring DEC. Notice the color scheme which is a bit different from the RDI. It was a core feature of RDM and RDI radars from the start

The color DEC mode was absolutely not a late upgrade, it was even present in the RDM radar. There are videos of peruvian M-2000P RDM DEC mode. NCTR was indeed added late 90s or early 2000s and the green radio too. I'm not sure the old radio model is still available. But we could disable NCTR based on year

There are two binds allowing to select AA guns. 'CNM AA Gun' does switch to the gun mode 'AA Gun SELECT, else PCA SELECT' does select the gun mode but needs to be kept pressed, it reverts as soon as you release The second one is meant to be used with a stable switch that locks into position. If you bind it on a push button, it will behave as OP described in the third post. The real jet use a stable three position switch, with 'C' (Cannon), 'N' (Neutral), 'M' (magic) positions.

No, this is a bug. Or not really a bug but a limitation. The visor uses a flat geometry but with a huge horizontal FOV like this it most likely have to be redesigned with a curved geometry to cover more than 180°

Hi, Thanks for reporting. Could you share: - Your CPU specs - The number of radar threads in special options - The "Civilian Traffic" in graphical settings - Does decreasing/removing civilian traffic in settings improve the issue? It was working well in Vegas when the interaction with civ traffic was developped (I tested major cities on every map) but DCS MT changed a bit the radar threading game as less CPU ressources are available to the radar. I may need to rework it a bit. Thanks