DackSter94

No, 3.6 km at 40nmi is nothing. . Imagine finding something at 20 miles, most a2a combat happens under that in DCS (if not under 10). For reference: Alt coverage of some aircraft in DCS at 40nmi at 4 bars: M2K: 10.4km F-15C: 12.8km JF-17: 3.7km :megalol:

Noticed that it is very hard to pick anything up within 30 miles. Turns out that altitude coverage is very small. In the screenshot below you can see that at 40 miles radar covers only 12000 feet. If we do some math here, that is about 2.8 degrees only (in 4 bars!)!

So I was playing and realized that I couldn't find bogeys when pointing radar cone exactly at their range/altitude when there is altitude difference. It's specially noticeable when operating in one bar scan. So I made a test mission where i fly at 20000 feet, and bogey is flying hot at me at 3000 feet: So something is off. Horizontal scan ccm is the same thing, if there is significant dive/climb angle, when I elevate/lower movable dashed line and put it on the bogey, it doesn't lock, but if i put it above/below the bogey enough: it locks. Also it seems that I can only detect bogeys at some distances like say 25 miles, but when he gets closer, he disappears i can't pick him up again on regular basis. Although that might be related to previous bug. Also some other behaviors I noticed: Before when you moved antenna up and down number of bars would always be locked near antenna symbol, but now it moves separately as demonstrated here: Bug or feature? If bug, maybe related to elevation problem. Another behavior: In one bar scan, when you move elevation, antenna movement displayed by antenna position symbol is not smooth: Bug or feature?

If targets are flying away it could be due to similar speed of your and their aircraft. However radar seems to be very much broken, specially something about radar elevation.

Nice work putting it together. After my first test i realised that my memory wasn't running on 17 CL. Bios took odd number and makes it even above(18). But that was for tests on gtx 1060. For my 2070s test I used ryzen dram calculator to calculate timings. So timings for RAM I used and use now with 2070s are 16-19-20. Although I doubt this change affects much.

Thing is i run tracks 3 times in a row for an average number , I think second and third tracks always get better performance in low 0.1% because probably less load stutters. I didn't get 2080Ti as i was planning and instead went for 2070S, which is probably bit closer to 1080. I only run test once (not 3 times like others, which will probably give better results) and i got these numbers: 53.6, 96.3, 169.8 (0.1%L, 1%L, Av) I also tweaked memory settings with ryzen DRAM calculator which allowed better latency.

So you are saying my cpu will die in couple of month? :) coz my voltages reach almost 1.5 while doing anything rly, even randomly on idle.

Yes it's on QVL list of the motherboard. I can run memory at 3600, but then infinity fabric clock gets automatically set to 1600, if i try manualy set it to 1800: PC doesn't last long and freezes/doesn't boot.

Mirrors are off. I might do new one with something free and no reshade, after i receive new gpu hopefully soon.

2x16

I'm hopefully gonna get 2080 ti by end of this week or next week, so i can test that too. Anyways i found out that my memory wasn't running most efficient settings. My infinity fabric seems to suck big time in silicone lottery, i can't even run 1800 on it, so running memory at 1800(3600) doesn't seem to be most efficient thing. Need bios updates to see if it fixes anything.

I squeezed 5-10 more fps from 0.1% lows if I leave VCore voltage at Auto Which is insane voltage that goes up to 1.5v, hence I lowered it, sorry for not mentioning it, I didn't think it would have any effect. Lol is 1.5v even safe :D? The cpu/fan behaviour is annoying on default voltage/windows power plan settings. CPU load spikes either randomly or when you launch apps, and fan annoyingly spools up and down.

I don't have VR and i don't use MSAA at 1440p. But I usually play at 1080p and there i use MSAAx2. Maybe performance difference will be bigger at 1080p.

3700x Benchmark vs old i5 3570k Old setup: CPU: i5 3570k OC (boosts up to 4.2GHz) RAM: 24GB DDR3-1866 (CL 10-11-10) GPU (same): Gigabyte GTX 1060 6GB New setup: CPU: Ryzen 3700x Stock (boosts to 4.3GHz+) RAM: 32GB DDR4-3600 (CL 17-19-19) GPU (same): Gigabyte GTX 1060 6GB Game settings: Resolution: 2560x1440 Everything on minimum or off if possible, except the following: Textures – High, Terrain Textures – High, Visib. range - high, Res. Of cockpit Displays: 1024EF, Preload raidus: 60500, Anisotropic filtering: 16x,[x] Full Screen, [x] Scale GUI Reshade: Default Lumasharpen and HDR effects on. As you can see I’m probably (and hopefully) GPU bottlenecked, and difference between 6 y.o. setup is not big. The way I measured it is I recorded a track(Caucasus map), where your location gets shot by MLRS after some time (which causes fps drop). Camera motions and plane motions in the track are the same (or close to being so I hope). All I did after is played track 3 times and averaged the values (I start playing the track by pressing pause and about half second later I press the button to record benchmark data with MSI afterburner for 3m:16s). I will attach the track I used (you need su-25A or flaming cliffs 3 to play it). In first day of installation 3700x performance was actually worse in 1% lows by 10 fps, but today Ryzen gods had mercy and made it slightly better. benchmark.trk

Nice. Also any benchmark for 3900x would be appreciated if anyone has it :D

Radar stabilisation binding is reversed. "Stab in, else out" does "Stab out, else in" and vice versa.

After Aim-7MH release, it would loft every time. Now it's weird: I fired it once today it lofted, I fired it like 10 times more from same conditions it never lofted again. So what gives? I know on F-18 you can chose between loft/norm mode, is there such option in f-15? Also why MH and M have different smoke trails? I think M version uses old flight model or something. PS: on HUD, where it should tell missile , it's quantity and type it says for example M2F, which means 2xAim-7F, even though I have MH selected in loadout screen, and stores display confirms it. (It's same for Aim-7E)

Event: 1v1 Squadron Name: RvE Teamspeak/Discord: RvE Discord Contact person: =RvE=DackSter94 Aircraft Selection: Mig-29 Pilots: UK - =RvE=DackSter94

IAS in export.lua gives inacurate output in relation to ingame stats bar (I saw values of up to 10km/h off just in one test). Also, last time i checked couple of month ago, fuel consumption export wasn't working. Is export.lua obsolete and no longer being fixed/supported?

Вот только в реале у ракет есть память, и они будут лететь туда куда цель летела в последний раз, и они тебя сразу найдут когда ты выйдешь из этого "магического" положения в 90 градусов (а намерено ты там остаться не сможешь, ибо СПО неточные в ирл как в дкс). А если на тебя ещё и радар пускающего самолета смотрит из под другого угла, то ракета и так будет знать где ты.. А в дкс как только ракета теряет захват она начинает лететь с 1G, если пере захватит то даст 15G и сольёт всю скорость...

Грубо говоря, в ДКС по дальности по маневренной цели(по крайне мере на высоте 1000-2000м) 77 хуже 120B на 12%, а 120B хуже 120С на 17%(думаю с высотой будет похожие результаты. А вообще слив скорости/дальность полета ракеты имхо только одна из проблем. Другая проблема в том что ракеты в дкс не способны сопровождать цели сверху вниз. В мультиплеере все не летают, а ползают по земле. Т.е наша ракета летит с верху вниз, и как только цель при отвороте проходит близко или через 90 градусов относительно линии визирования ракеты на цель это уже в 40-50% случаев слив захвата, а с диполями вероятность слива захвата уже все 80%. У 120С немного лучше с этим, но тоже плохо.

But when we gonna be able to climb to flight ceiling without flaming at at 13km??

=RvE=DackSter94 - Ka-50

You can disable it in mission editor, in one of the aircraft submenus.

Caucasus, means forget about seeing contacts...