All Activity

I used a tablet clamp, it fits well and I can move it around. I don't use a simpit though, just everything on top of my desk. I have a similar clamp for my Streamdeck.

Any plans to arm the forward firing guns on the A-20G, so that AI could implement strafing? Great and well used A/C in the ETO, as well as a stand-in for the B-25 in the PTO now emerging. Please advise. @BIGNEWY Bowie

Здравствуйте, а может кто подсказать, в чем разница между взлетным и посадочным положением закрылков на новой 29ке? По обоим командам и кнопкам в кабине закрылки встают в посадочное положение вместе с предкрылками, это баг, или в этом есть какой то, недоступный мне смысл?

Do you have a link to this Retribution mission Thanks

I flew Caucasus last night to see if I could see any of the changes, TBH I couldn't see any difference, it would be nice if ED showed some comparison shots to show what changed. I also flew SA last night using the instant action F4 free flight mission and noticed a lot of blurry low res textures on the lower half of the snow capped mountains, it ws as if the textures wouldn't load in.

I'll take a look soon. Thanks.

please ED fix the bug write only the road with very slim thickness , don't write the text info of the waypoint on the map , it clutter too much the map

See here: https://forum.dcs.world/topic/378937-read-first-changelog-for-mig-29a-fulcrum-2025-09-17/?do=getNewComment

So far it is working perfectly at least for me.

(JFYI this is a user sharing their own made up guess and not anything official)

I configured everything according to the tutorial, and the RSBN causes the HUD symbology to disappear in the final. The PRMG can't capture on the HSI and ADI. The ADS needles don't move, and the HSI flags remain activated. It might not be a problem, but it's worth checking. If I made a mistake, please let me know so I can fix it. Thanks! MiG-29A Fulcrum RSBN-PRMG.miz MiG-29A Fulcrum RSBN-PRMG.trk

Yeah, it is a known bug. Something is wrong with how its synced. For performance reasons they aren't synced individually but we pack them in some "clever way" and exploit some DCS shenanigans for it. Seems that something stopped working with that some time ago :D By the way, for syncing issues its important to differentiate between: * Player looking at AI * Pilot looking at own aircraft * WSO looking at own aircraft * Player looking at other players aircraft These situations are all handled differently internally :)

Well, presumably not a campaign hotfix that may or may not come out later, but I'd expect it in the next month's big patch.

@-Rudel-, what is the possibility of the Corsair being "slammed" on the deck during spawn-in to cause the tail to shear off? Hmm...what if the damaged landing gear (potentially tail wheel) causes the Corsair to spawn farther back? Maybe the carrier can't "see" the tail wheel and positions the main mounts closer to the deck edge. This would in turn cause the tail to hang over the water and shear off during spawn-in. As noted in this track file on an ashore parking spot, the plane is violently dropped after the repair cycle is completed. Imagine the plane being dropped during a spawn that is ~60ft above ground. Does my hypothesis have merit? 2025-09-18 Corsair Repair x2.trk

@Dragon1-1 I believe the A-6 will get lots of love and attention once the Eurofighter is up and flying. Mike Force Team

Holding the joystick whilst the AFCS does its start up bit didn't fix the issue. However HIP Game's solution of switching to the default Moza Frogfoot profile in the Moza cockpit app did solve this problem. I noticed that the stick moved through a much greater range of movement with this profile set, and I was able to switch to my preferred Mig 29 profile after the startup, which although being a bit of a drag as I have to unplug and climb out of my VR simpit to do so, is at least a work around. First world problems eh?

More or less correct. Along with lower duty cycle it uses 2 PRFs for eclipsing reduction. The FMR is also in 3 stages for range resolving and de-ghosting. Lower duty cycle would invariably mean it's a lower PRF is my assumption, probably closer to 100khz, vice Velocity Searches waveform being closer to 180-200. Somebody would have to do the math on that one i dont know what pulse widths were used. The best i've been able to gather for what exactly the waveform for PDI is on the 65/73 is it's the high duty cycle HPRF used for Velocity Search that is broken up by periods of the range bin'd HPRF for "burst ranging" (mentioned on other documentation about the 65/73). This is the reason i have become skeptical of claims that the late sparrows launched by more modern fighters dont give launch warnings. Should be a case by case basis determining if the waveforms change between STT and illumination. Which in this case it does and should trigger launch warning imo.

I'm fine with that, as long as it arrives eventually (and before I'm too old to sit at a PC to pretend to fly for hours at a time)!

I had a try at rolling back the Intel ME that accompanied the latest bios but it wouldn't allow it. So, I guess I'm stuck with the latest bios. I'll try reinstalling WIn11 and pray that fixes it otherwise I can leave HT off for now. Someone mentioned the latest major Windows 11 update contributed to their long loading time (which could also apply to me as I did all these things around the same time) so yeah hoping a fresh install fixes it. Thanks for your report on how rolling back the Bios fixed your system.

Yeah. Simple fact in terms of processing power and digital systems, by the time the 80s rolls around is where the west just blasts ahead. So while the MiG-29 9.12 would do great against F-4E, and could hold it's own vs the F-16A's and even to a degree the F-15A, by the time they arrive in any numbers to the Frontline units in 1986 they are basically 5 to 10 years behind compared to the latest F-15C's and handful of F-16C's block 25 stationed there

A successful landing in my book; alive and on the deck!

What is your setting for your MFDs? null

I know this thread is a few years old now but I'm just getting into VR (quest 3) and really wanting to use the HMD in the F-18 to spot ground targets. I align it but the HMD remains well above my view when Im looking straight forwards down the planes nose. Its not an alignment issue, its not a 'centre VR' issue, the HMD remains high no matte where you move the cockpit camera view. It means to use the HMD to spot ground targets I have to bury my chin in my chest to get the HMD low enough to pickle targets. Surely thee must be some way of adjusting its position (as opposed to aligning it)?

No. Save up and wait for the release of future hardware.