All Activity

You set the QNH given by the briefing on ground so your altimeter reads the elevation above mean sea level. Above the transition altitude you set QNE/Standard to get flight level. There is no real altitude, only altitude in relation to your selected reference altitude. That's either flight level, level above ground (height), altitude above MSL, density altitude or other. Temperature affects your altimeter so it reads something different than height, that's normal. You don't compensate for that normally. That's one of the main reason for the devaition you see.

It happens at random. I notice it when doing air starts to practice BFM. A small percentage of the time and you will have the roll input stuck. No predictability to it that I can find and a restart of the mission makes it go away.

@BIGNEWY@NineLine Just to add some context to this, many of us that have bought the NS430, are not able to use it for this exact reason. This is not just an issue for this one server but any that have dynamic ground games where creating farps that you don't want the other side to instantly know where they are as otherwise strategy becomes pointless. If I had a £1 for every time I heard why doesnt the 430 work etc as its affecting literally every module, well i'd probably have more spare cash than the MOD. Given that the NS430 has had some recent adjustments please can we get this to the dev team and at the same time whilst emphasis is on this new product address the other post on the databases raised in another thread, as i see in the folder there are still only displaying 3 maps (so i chased in the actual 430 forum section about this the other week re missing map data in south atlantic, but its actually every new map, also about radio functionality if that has not been resolved as yet (not been able to test in MP as per above). Not hijacking this thread, as i asked MartinCo about this earlier issue he posted and it all ties in with the overall issues of the 430 implementation. Please can we have some priority put into the 430 in general on the justification its for a new module launch, and a new product launch re the 430 kit for the Mig29. I mention about priority as i note in the forum post i chased last week i was bumping it after 18 months with no response. Many thanks.

It’s used for all air to ground as primary ranging. For CCRP, the WCS just remembers target position if under the nose. The only other way to range is inaccurate radar altimeter like Hind. And that doesn’t work well for strong dives. If your doing air to ground and the “A” denoting laser is on isn’t on, your doing something wrong or burned it out.

Hey Oban, did you ever get the Lynx sorted?

Hello, CH47 pilots can now This mean that when you press 1 or 2 , the CDU switches accordingly which is "perfect" with the strange way of binding "Active CDU" keys only Choosing PLT or CPLT will work (and override by seat position ) It requires to update your DCS Bios with DCS-BIOS Nightly 2025-09-21

https://rutube.ru/plst/133782?r=wd

Speaking about original, soviet times Yak-52, - all the gauges that have a letter "K" at the end of their naming are capable to be back-lighted (red light) - they just have to be connected to electric power. However, I did not see this to be done IRL. Original Yaks-52 did not have any external lights (except an external green lamp on the left side of the plane to indicate that the GPU or other external electric power source is connected and which is not modeled in DCS if I remember properly). As the plane was not flying in the flight schools and airclubs night time those gauges were not connected (I did not find any info that planes were pre-prepared for this from the factory) and there were no switches or regulators to bring their backlighting ON). At the same time planes were equipped with PU-26 and Baklan or other radios and it was easy to install any lamps to their control units. Nowadays people equip their planes as they wish, so, you can see everything. There also are Romanian built planes, Yak-52W and they can have lights. By the way, in DCS we have a "First flight" livery for Yak and some of those planes IRL have at least NAV lights (there are a lot of videos on youtube) and some "glass" gauges inside (from Frontline avionics )

Ok cheers. I am wondering about CCRP. Because in the F16/18 it is used for level bombing. But I get the impression the community is using it in the MIG-29 for dive bombing, that can't be correct can it? Anyone knows if it should be used in dive or in level flight?

It’s from two years ago, back then things were changing patch to patch and sometimes we and sometimes not. Just use flares to target at night now

Yeah, you get A at the right time. I also tested the radar altimeter ranging with laser off.

Hi, .\DCS World\CoreMods\aircraft\MiG-29-Fulcrum\DTC

As I said. The only change i did was change the cloud settings. When I had overcast. The SAMs only fired when I flew below the cloud cover and then only at me and my wingman. When I removed the clouds cover. The SAMs started to spew out missiles at aircraft, HARMS and JSOWS. Same with the aircraft, as soon as I removed the clouds the HARMS flew away and I also saw JSOW impacts.

@WolfyDHowler You are using FSR for upscaling but be aware that the implementation in DCS is FSR2 only. It doesn't take advantage of the superior FSR4 your 9070XT is capable of. Early FSR implementations produce blurriness in cockpit & smearing of moving objects. With your hardware, I'd try no upscaling, MSAA 2x, VD Ultra @ 72 fps (Godlike would probably be pushing it a bit too much), medium-ish graphics option in DCS and QuadViews fixed foveated rendering. You don't need the OpenXR toolkit, it's deprecated anyway. That is what I was running with a 6950XT so your GPU should have no issue with that. On my 7900XTX, I use the same setup except that it can sustain 72 fps in VD Godlike. Might be worth a try. Even in Ultra on the 6950XT, I had reasonably sharp cockpit gauges and displays. For instance, the small QNH digits in the analog altimeter gauges are just readable. An alternative to no upscaling & MSAA 2x is to use optiscaler to force FSR4 on DCS, which would probably make sense given that your CPU natively supports that.

Thanks for the information & it seems to correspond with what Cap described in the video above. I shall do some more testning. @AeriaGloria have you used the laser range finder as it should? Cap is talking a lot about the laser range finder in the video, I havent been able to test it out properly yet.

Li metto qui disponibili. I use basic level fusion, the file is not very clean https://drive.google.com/file/d/1ByHeJTIJM75N_uFgxlD8v0U311Y7wpHt/view?usp=sharing

Oh, cool! Thanks! Sent from my SM-A536B using Tapatalk

All manuals, 9.12, 9.12A, 9.12B, show the right border in the TP mode. It doesn’t matter which of the three becuase their HUD only determines on software updates they can all have. Video evidence shows this as well.

Se vuoi ti mando i disegni e puoi stamparli come preferisci. 37cm and 45cm at the base of the stick where the wrist rests

Awesome explanation! Appreciate you!

i have tried to play a morse code sound using two methods: 1) a unit tuned to a freq and transmitting message with 1W - audible in the mosquito R1141 at 98ft. ASL at 60 nm over the channal 2) a small zone using the "Radio Transmission" also set to 1W (smallest possible) and again audible at 60nm at 98 ft. ASL I believe this is some what unrealistic to receive a signal sent out with 1W from a ground station from a range of over 60nm, hidden well below the curvature of the earth. How is it possible to limit the transmission power of a signal if a power of 1W is not low enough??

Perfect, thanks

I mean either it’s 9.12 or 9.13 which could be loaded with same software. Nothing else has the same HUD.