All Activity

I'm definitely using the correct buttons to open the radio menu... but still same issue. Even when on the correct channel with the correct frequency set for that channel in the ME, that station doesn't appear when opening up the radio menu. Still can't figure it out. I'll play around with it a bit more. Maybe it was just on the CWG map that the issue arises. Haven't tested any other maps yet.

I believe you also need to ensure you're in the correct flaps config before to button. I'm away from the sim, so someone may need to confirm that statement Sent from my SM-S928U using Tapatalk

Did you post in the wrong part of the forum? The A-10C HUD brightness is a rocker and there's nothing analog about it. Plus the pilot body show/hide keybind makes little sense before they add the pilot body.

Ok, let's see where the issue stems from (extract from the manual): Let's start with LITERALLY the first sentence of this chapter! Read it? Good! Now have a look at your tachometer - 1200RPM right off the bat! Go through the actual procedure, read the manual, and you won't have problems. (I know for a fact, that the engine seizing to work later in the flight is most often the culprit of having improperly warmed up the engine. You ain't the first, and neither the last to experience this.) Another quick note; you don't need to murder the primer pump to start a Daimler. Three strokes are more than enough during what you might call average weather conditions. In winter, you might want to do 4-5 injections are plentiful. How will you know if you primed it enough? Simple, when you pull the starter handle, watch the fuel pressure gauge - 0.8 bar during engine start-up is perfect. Anything below, let go off the starter handle, and stroke it some more. (The manual does state that you might need as many as 15 strokes, but that would have to be a very hard beaten Daimler, stored for years with neglect. You won't need that many.) Yet another note: you move the throttle forward during start-up, which is not needed at all in the BF-109K4. Actually, in order to specifically not go above 600RPM, you should leave it at minimum setting. That will also solve your uncontrolled rolls during start-up.

Hey CH, any update on the J-35 and when we might get a release? Thanks!

Don't assume that just because you can't, nobody else can. I have flown the BF-109K4 with manual prop. pitch in combat without any issue. Actually, it is more work to keep it properly alinged manually so as to not over-rev or over-torque the engine, but you can push more out of the plane versus automatic governor. The automatic governor is not perfect, far off. It is there, to automate a part of the flying, such that he pilot can dedicate more of his attention to the actual combat. Frankly, it had to do with Germany losing pilots faster than it was able to replace them. This is an example of a measure meant to alleviate that problem, by shortening the curriculum for aspiring Luftwaffe pilots. Send the video over, and I'll let you know what you're doing wrong/what's happening.

Если репортить баги, то в англицкую ветку самостоятельно, хоть с гугл переводчиком, типа "твоя-моя-непонимай". Там быстрее. Тут скорее посильная помощь, я давно не видел, наверное с марта этого года, чтоб кто-то комментировал из ED.

What is the key binding to angle the camera up or down.. Been messing with camera view for a while and can't seem to achieve the proper view. I can move forward, back, up or down, left or right but can't seem to find tilt up or down. Do I really have to play with the snapview lua file?? Thanks

I have enabled the in-game option and I've been using fixed QuadViews for some time. I have eye tracking working with my BSB2e, but I'm not getting dynamic tracking in-game. I've heard mixed things about support for DFE with BSB2e, but QuadViews lists it as compatible on their GitHub. Just wondering if anyone has gotten it to work.

Thanks for the reply sleighzy. As I was further investigating my issue after I posted here earlier, I learned that Windows 10 doesn't support mixed reality. So I'm just going to box the Quest 3S up and send it back. Its clearly time to build a new PC designed around supporting the Meta Quest 3 512GB in DCS. It would have been nice to learn about this before I ordered the Quest 3S but as usual, I like doing the hard and more expensive way.

Thanks for the report. Fixed it internally, will be available in one of the upcoming updates.

In this first image I can't see the target at all. He's at 1300kph TAS and we're at a 2755kph closure rate. For the second case, target is flying at a 30-ish degree crank and I'm able to see him just fine at a 2200kph closure rate and the target also at 1300kph TAS. Now for the third trackfile, the target is at 552 TAS and the closure at a 1652km/h closure rate, and I was able to find and lock the target just fine

There are no stupid questions. The DCE settings are not really user friendly ^^. What's more, when you try to add or correct things, it often breaks something else

Can you please add binds for: - Analogue axis for the HUD brightness - On/off for Show Pilot Body

I have also had a successful flight in the Gripen, with no issues.

Yes it is, TDC range

So if it wasn't fitted to "this version" then at what range is the delta H value referenced to ? is as has been suggested (and in game evidence supports this) it is referenced to the Acquisition cursor range ? Is this a yet to be implemented feature ? or what we are stuck with ? The "correct as is" label and the quote above from Matt in the post above to this thread implies its not going to be incorporated. .... a definitive statement here would help. Elevation changing as you try to position the acquisition cursor over the target makes it almost unmanageable in free search type operation. Probably OK in the guidance mode with DL doing the work for you. I guess TWS is the go as then I presume elevation will be controlled by the TWS mode itself ?

DCS Kola map forum: null

As far as I’m aware the manual describes the limits of speeds for each radar mode as “detection of air targets flying at speeds,” it is not “detection of air targets flying at speeds plus your own speed (absolute closure.) So for MPRF front aspect it’s 270-1100 kmh. This means that no matter the speed of the MiG-29 it should detect a target up to 1101 kmh. If you look at lower of speed ranges for each mode, the low end is the notch speeds, which means it’s the target speed in reference to the earth, not your closure speed. Referencing L-18 and German manual. As well as Russian 9.12/13 manual.

As title says, the Mig-29 Radar is not able to see targets in Medium PRF (PURSUIT) if the closure is too high even after a certain point. If the closure is lower, I'm able to start seeing the target in MPRF. However, if we're both head-on and at high speed, the target is literally invisible to the radar even pre-merge. I have attached 3 track files. One with high closure rate and the target being in a head-on aspect, no contact whatsoever before the merge. Second one is with the target in a crank with medium-ish closure and I'm able to see him just fine. Third is with the target head-on but maintaining a very low speed, also able to get contact at about 38km. Thanks in advance. HIGH_CLOSURE_HEAD_ON.trk MEDIUM_CLOSURE_CRANKING.trk MEDIUM_CLOSURE_HEAD_ON.trk

@Laxxor are you still seeing this issue with bouncing cargo?

Well of course now it seems to be working. Maybe just pure luck I was getting completely clear skies so often. Thanks for replying and putting up with my stupid questions.

I've got the latest...553 I think? I've been messing more with it, so I'll generate a new mission.

Best sp campaigns available for dcs imo.