All Activity

Yes exactly what I’m saying. Within 15/35 km the Su-27 will give a STT lock signal with IRST lock. You can avoid this with MiG-29, not possible with Su-27 unless you turn radar off completely and idk if it would need to warm up when turning it back on

I think the issue comes from the explosions effects discrepancy I noticed this a while ago and today during test to report it i noticed something. Even if i changed the Airburst Height at which the submunitions released, the effect remained the same. The visual effect of it i mean. If you slow down the replay you can see the submunitions diferent dispersions, but the visual effect will mislead the user. I think it will worth to update the visuals to match the dispersion. That will help the user to see what the settings and how he deployed it really does. null

Same...no QV. Please, what are your setting details in PP and DCS, if you don't mind? TIA. I'm just starting my DCS quest with Super U/W 50ppd.

I just had the problem after a stutter when joining a server. Here is my log file and a video. I have removed the hooks and have tweaked the other settings. lv_0_20251105120442.mp4 dcs.log

Flares: Spam until missile evaded Chaff: Drop some in hope to evade the missile until no more threat.

By my info... Ship Based Country / Name / Guidance / Gen / Air Range (Nm) / ATA rating / Targets @ Missile director / Surface Range (Nm) / Damage / Penetration / Envelope Flight Patch / Speed / Signature / IOC / Remarks PRC / HQ-7 / Cmd/2 gen / 0.5 - 6.5 / 1.0 / 1@2 / 0.5 - 6.5 / 17 + D6/3 / 2 / VLow - Med / 1475 / VSmall / 1990 / - PRC / HQ-7A / Cmd/3 gen / 0.5 - 8.1 / 1.5 / 1@2 / 0.5 - 8.1 / 17 + D6/3 / 2 / VLow - Med / 1750 / VSmall / 1998 / - Land Based Country / Name / Giadance / Gen / ATA Rating / Range (Nm) / Altitude Envelope / Speed / IOC / Remarks PRC / HQ-7/FM-80 [CSA-4] / Cmd/1 / 1.0 / 0.3 - 6.5 / NOE - Med / 1460 / 1988 / - PRC / HQ-7A/FM-90 [CSA-5] / Cmd/3 / 1.5 / 0.4 - 6.5 / NOE - Med / 1460 / 1998 / - PRC / HQ-7B/FM-90 [CSA-7] / Cmd/3 / 2.0 / 0.4 - 8.1 / NOE - Med / 1750 / 2009 / - Surface-to-Air Missile Batteries Country / Syst Name / Acq Rads / Guid Rads / Msls by Lchr / Lchar by Btry / Combat Sys Gen / Tgts@msls Btry / Set time (min) / Rld Time (min) / Remarks PRC / HQ-7 / FM-80 Acq Rdr / Type 345 / 4 / 3 / 3 / 3@2 msl / 15 / 20 / Based on Crotale PRC / HQ-7A, 7B / FM-90 Acq Rdr / Type 345 / 4 / 3 / 3 / 3@2 msl / 10 / 20 / - Land Radars Country / Name / Funtion / Detention Range vs Large / Med / Small / VSmall / Stealthy / Gen / IOC / Mobility / Remarks PRC / FM-80, FM-90 Acq rdr / LAS / 14 / 14 / 10 / 4 / 1 / 3 Gen / ? / M / Performance estimated,designation unknown

@Jayhawk1971 thanks !!! so here is Santa 's strip

Funny, i noticed this last night flying over forest on Syria. Was planning on doing some settings tweaks tonight to see if I can smooth it out. I do not use quadviews (pimax or mbuch) as I find it looks horrible with either one. I'm using just Piplay latest and tweaking in there and DCS settings. I get 60+ fps pretty consistently with piplay set to medium resolution. Does the motion smoothing in Nvidia app and Piplay have anything to do with this?

Don't ask me why, as I replayed the mission yesterday evening, everything goes fine... twice

Не в качестве аргумента, а просто ради интереса. Вот эпизод, в котором RIO F-14D опусывает пуск 2-х AIM-54 по иракскому МиГ-25 в 1999 году (начало с 27:00, причины 40:23): По его словам, процедура пуска обеих ракет была выполнена правильно, но он не увидел обычной горки которые они должны были сделать. В итоге пуск оказался неудачным из-за человеческого фактора: персонал на авианосце, отвечающий за вооружение, по ошибке не взвел переключатель на двигателе ракеты (arming the Phoenix rocket motor) и он не сработал так, как должен был.

Have you pulled sudden high Gs on the Sabre? My memory of it is fuzzy, but either the Mustang or the Sabre (or both) have gun jamming modeled by G forces. Some old bird in DCS does have gun jam modeled as it happened to me and it was because of G forces. I think it is the Sabre but I can be wrong. I can't jump into DCS to test this out right now, but it is a worth a simple test with the mission editor I guess.

Yes I've lowered it now to 125 because even 500 was too much last week. It didn't occur to me to try to exit and come back if it's doing it without making other changes, though. Silly me, assuming it was a constant cause and effect situation. I will see what happens tonight I suppose.

Где все главари (4иж и Ко) и будет ли когда-нибудь обновлен кавказ и пехота?

Hi. So what is a good chaff, flare release program? I'm flying the su27

I think there are some issue with the CBU-99 related to the height at which it release the submunitions. I paired them with the FMU140, and i tried different avaiable options for the Airburst Altitude (height ?). And none of them releases at the set height. For example the default 1500ft releases consistently at around 900ft. I included some tracks with different fuzes, but its easy to test within this mission. BTW. I noticed too a discrepancy. When i set the Fuze 500 in the editor, in game in a HotPlane the weapon page VT1 shows HT 500 Fuze 2200 in editor, in game will be HT 1800 Fuze 2600 in editor, in game will be HT 2200 On another Note: i noticed the effect the submunitions does, the brown dust clouds, are the same even with differen dispersion options. It will be worth that its updated to change with the dispersion, that will give better feedback to the users and avoid confusion with it. CBU_Height_Issue_500_centerHit.trk CBU_Height_Issue_900_centerHit.trk CBU_Height_Issue_1500_centerHit.trk CBU_Height_Issue_3000.trk CBU_Height_Issue_3000_AUTO.trk

This is just an impression, as the screen is from one eye. In reality, in VR, I'm perfectly centered. But if everything is fine in Apache in VR, then there is actually something here for developers to check.

I posted this in January. See https://forum.dcs.world/topic/368442-slave-all-to-spi-fails-most-of-the-time/#elControls_5595989_menu @f-18hornet Replied that this issue was "reported for analysis" and the thread was locked for replies. I have not seen the bug confirmed, and there is still no statement whether and when this will be fixed. In my opinion this is important functionality for designating ground targets. I have successfully used it for a long time, and then an update destroyed it. Not an indication of good software configuration management! The bug fix should be a priority item! ED, please provide an answer!

Sure! Gamma was at 1.9 for the screenshots, vanilla install.

Вот сколько читаю форум, сам Чиж и другие члены команды тут упорно называют DCS игрой. Каждый раз удивлялся, но им виднее

Yeah, I have the same issue on version 1.2.

I've been encountering this issue quite a bit lately where the AWACS ignores targets close to me/intercepting me and instead gives me bearing, range, and altitude to targets hundreds of miles away instead.

Ok, I'm still stuck with my AOA odd behavior. Do you guys experience this as well ? Look at the screenshot : pitch around zero, VS around zero, velocity vector on the horizon, should have AOA around zero but got 8 (analog) and 8.3 (digital) value ! Did I miss something ? I uninstalled the 1.2 and got back to the 1.0.1 version, same problem. How the hell could I've miss that during the hours I spent on the previous one ? (and I just checked othere aircrafts like M2000 or F/A 18, whose AOA is perfectly consistent with the primary flight parameters...)

The 22 October did increase frametime for me in my test (FA-18, Caucasus). At first, I though it was related to the visor introduced but I am seeing this increased frametime with all my airplanes by 0,7 to 1 ms. Flying over high density of map objects, such as trees, always caused frametime spikes but it is now more apparent unless I reduce my settings. Using process lasso will certainly help with the random CPU cycle stealing from other programs running in the background and causing stutters but don't expect it will create headroom unless you have something constantly running in the background. The only three ways to regain headroom is lower setting, upgrade hardware or wait for an optimized/improved changed to software. Hopefully the next patch will give us back some headroom.

To put that into perspective: assuming they would only need to sell 1,000 to make it worthwhile (no idea what the number is, but I'm guessing that's a lowball number) and assuming people wanting one that post here only represent 10% of the people that might buy it if it was available (probably overestimates), that means you'd need at least 100 individual people to ask for it on here. Chances of that happening are pretty slim. It would be nice if it came back, but if it went because it wasn't selling well the chances are very, very low.

Nice! Can I ask which gamma you had set when you made these screenshots?