All Activity

Buenas! Estoy queriendo organizar una partida red flag inspirada en la campaña de Reflected. Este jueves 5 la quiero lanzar para probar que todo salga bien, explicar las reglas del juego y demás y el sábado 7 lanzarla en modo algo mas serio . El nivel por ahora no es nada del otro mundo pero en algún momento hay que aprender si os animáis estáis invitados. "Colt-1" x4 F18 -CAP- "Colt-2" x2 F16 -CAP- "Ford-1" x2 F18 SEAD -SA6- "Dodge-1" x4 F4 STRIKE -EWR- "Chevy-1" x2 F5 STRIKE -RWY ATTACK- "Chaos-1" x3 Apache/Kiowa SEAD -SA8/SA9- Briefing: Aquí https://discord.gg/RcNGPrF6

Ships don't have jammers for any other aircraft and there's no option in the mission editor for ECM using, which leads me to suspect #2 is the case. There also examples of the Viggen being jammed by vessels which IRL do not feature jammers (like the Grisha V). The Viggen is however also susceptible to jamming from aircraft, which works in the same way it does for anything else.

I'd pay for a Mig21 upgrade right now, but I can see both sides of the coin here: Having already four aircraft without developer support (RB), and with Mag being so uncommunicative (and not very proactive resolving some issues), questioning the purchase of one of its modules (including the F4U) is like a leap of faith... although that's what DCS is all about. My advice: enjoy the MiG-21 as it is. We have great maps right now. It can do almost everything it was designed to do.

Both options would make sense.

I might be wrong, but if you have an AMRAAM selected, then I think this is correct behaviour. It overrides the XMIT switch.

Hey all, I noticed a glitch in the DCS 2.9 multithreading. I'm running an i9 11900K with 64GB and a 3090 FTW GPU. I ran two tests, both in an A10 in Syria using the Takeoff instant action. Test 1 - With all 16 (logical) cores enabled, my stuttering in VR was outrageous. Every 0.5 to 1 sec, a big stutter. Test 2 - Process Lasso'd DCS to use cores 11 - 15. Far, far fewer stutters (but they're still present every once in awhile, especially when all the cores get fully loaded, then back to heavy stuttering) My dcs.log is attached. My CPU doesn't have P/E cores on the die. Just hyperthreading. FPS are always very high (pegged out at 72 fps, solid). The only thing I can conclude, at this point, is that there is a glitch with the way multithreading coordinates resources between threads. More cores should not result in more stuttering. Other things I've tried (to no avail): debar on/off hyperthreading on/off un-parking cores dcs.log

You're so welcome! I'm really glad to hear that you're enjoying it! Thank you for posting, I appreciate it so much!

trapper

I was meaning the Quick Mission Generator doesn't support mods. Instant action missions? Don't know.

It was mission 01 of the Rampagers. To be clear, the mission debrief recorded a successful destruction of both targets. I received a 100% score. The ATFLIR showed the destruction visually. But there was no screen message of either target being destroyed during the mission. There was also no record of either target even being hit or in the bda of the DCS post mission page. This has been a problem for me in other missions in DCS for at least the last couple of years. This is why I don't think this is a problem in The Rampagers Campaign - I believe it is a DCS problem. I have repaired my install several times to try to correct this, with no success.

On the main dashboard but has froozen in flight also on standalone version. It make no diferrence betwwen versions the core 1 running at 100% usage.

Don't think we'll get it back unless enough people complain and offer constructive ideas for going forward... mine is: Keep QAG if you like, but bring back the CFM generator for those that found it useful per my previous post above...

Any update or repair of DCS is going to remove the avionics stuff since those are modified files. That will need to be reinstalled every time a repair or update is done. See the first post for more information on this.

Yes. Definitely the Meteor. Good for Korea too.

Пробовал на днях в друга полетать вр шлеме,верно сказано,нужно это попробовать,теперь думаю как летать опять на мониторе ...

and the Meteor. It was already flying in squadrons in 44', though initially held back from flying over enemy territory. By late 45', there might have been a decent amount of them, and with no Germany to deal there's a good chance of them seeing action in the east. It's an interesting point that the Meteor was faster than the Shooting Star (IIRC), and it's possible that the US might have bought quite a few Meteors, just as they later bought Canberras.

From my point of view I wouels doubt that a RX9060XT will be sufficient for VR. Because of my own experience I say that a RX9070XT is a minimum!

Having used this for a few hours I find that simple dogfight missions are quick and easy to generate. More complicated missions, with more assets, leads to longer generation times. Some maps take longer than others. Cold War Germany is terrible. Normandy 2 works fine. It's still a work in progress and for me (with WW2 missions) it's much better than the previous one.

For BFT04 we check the altitude you are at approximately 4nm from the end of the runway. Typical glideslope should be about 3 degrees. If you are lower than 310m ~1000ft then you are below the glideslope. If you are higher than 405m ~1328ft then you are above the glideslope. In between these ranges at 4nm from the end of the runway would put you within the glideslope. I found that a common rule of thumb is 300 ft of altitude for every nautical mile from the runway. So at 4nm 1200 ft would be ideal. Close enough for this type of mission. In BFT09 you get to use the ILS so we actually check the position of the needles to determine accurate glideslope.

Hello everyone. For the past 5 months I haven't heard any new announcements about the upcoming free Su-25. If anyone has any information about it please post anything you have here. I think we would all appreciate it greatly.

the mod works again after I jumped into F-15C cockpit and back.

You happen to have the clear canopy mod installed to get rid of the pesky reflections?

Thanks for reporting that. We will retest. It's likely the triggers need more tweaking again as you suggested.

Thanks for reporting the issue. They should definitely be spawning to the east of India not west. It could be a change to the AI behavior (I know ED has been making lots of changes to the AI as the other campaign developers have been complaining about it). I'll do some testing and see if I can replicate the issue. Our triggers are pretty simple and the AI should seek out the player and not abandon the engagement. I'll report back after we have a chance to review what is going on. Update - You didn't indicate if this was in the FC version of the campaign or not. We checked both versions of BFM 02 which is the engagement with the F-4Es and we found that they are setup to spawn east of India. We tested the practice missions and they worked as expected. If it happens again please save the .trk file and send it to us and we can take a look.

Thanks a lot for the fix, Ugra!