LaCiKa

1st AUTO mode is like switch every second, from HPRF to MPRF to achive best lock, there is no "random". 2nd Again, again and again im not going to repeat my self that P mode is complete joke, you can't achive lock more than 15-20km, even 20km is HUGE risk of lock breaking it's self, i don't know in what world did you get 35km lock on HOT target. Even in Wags video is mentioned some distance of 8nm. Simply radar is bugged it needs to be fixed and give it more power, to me it makes no sense to have 120km+ range on HPRF and 15km on MPRF, simple as that.

Hey, so we have some more issues that we found out, basic story goes like this: in Auto Mode as of my knowledge radar should change PRF on its own in STT depending of targets aspect (Cold or Hot), so what is issue is that when i lock target in Hot aspect in Auto radar mode, when he starts defending and turns Cold i lose lock even giving a fact that we have speed difference greater that +-50kmh and we are closer than 15km of range and he is above horizon so that is issue number one. Second issue is that if target is let's say less than 20km from me and he is Hot i can't lock him in AUTO or Head On mode but i have radar contact of him on HUD, only way i found to avoid this is to use TWF/FHS so its snaps it self and auto locks at small ranges. 3rd is again with Vertical (Close) mode for radar, for targets coming our way i can't get lock but if target is Cold and above horizon and not maneuvering much lock could be achived but at limited range of around +-5km. 4th is about P mode, to me this is very weak mode for Hot and Cold targets, its impossible to lock targets at more than 15km range, i think this should be given more power and buffed as to me it makes no sense to have R-27ER with +30km range and not being able to lock target in P mode which is for closer ranges. But also answer to your question is yea, it's much better now in HeadOn mode and it's not losing lock as before. Hope this helps for further investigation and fixes. AUTOmodeIssue123.trk 1.acmi

I suggest you take a closer look at all 5 tacviews and see when chaffing was stoped and how missile is missing target that is no longer droping chaffs.

So after many years of waiting and hoping we finally get to see 4th gen FF model for RED side (MiG-29A) and i believe that this is first one and last one to be introduced in DCS as of now, maybe this will change but time will tell us. So starting from "Simulation", after we got announcement that MiG-29A is around corner, we also have info that there is going to be implementation of physics for SPO-15LM and how it will detect signals based on physics, right after that we also now have R-27R/ER in Advanced model and so much more, which i like and i support you doing it, BUT biggest issue now comes with F jets as they DON'T have such Advanced models for example AIM-7 and 120s and same issue is with their RWRs as it makes no difference from FC3 F-15C in accuracy and not even close to such advanced way as SPO-15LM and starting from there we can see who is winner. So my question is. Are we going to see same Super Advanced modeling on F jets and their RWRs, Radars, Weapons and so on? And when can we expect such thing?

To me this is bug as missile is missing only few meters from target. AIM-7M and R-27R are almost same in chaff resistance with 27R being just behind it.

Same story no difference, just when missile is about to hit, it goes in other direction. 27R3rdmiss.trk 27R4thmiss.trk 27R5thmiss.trk 27R1stmiss.trk 27R2ndmiss.trk 2ndMiss27R.acmi 1stMiss27R.acmi 5thMiss27R.acmi 4thMiss27R.acmi 3rdMiss27R.acmi

So right now update came out and 27ER is not hitting target no more at range of 15km (No Escape Zone), its missing enemy for few meters. 27ERmiss2.trk 27ERmiss3AUTOmodeLockOn.trk 27ERmissing1.trk AUTOmodeLockOnMiss.zip.acmi HeadOnModeLockOnMiss.zip.acmi P-ModeLockOnMiss.zip.acmi

I tried to switch PRF from Auto/High to P just before lock and still lock is breaking and also i tried old school trick that i do in FC3 is after i get lock in HPRF i switch to MPRF so i don't lose lock while he is notching or going cold, but here on this FF 29 is not possible since IR+RADAR is not working to give it support of not losing lock while radar is switching mode.

MiG-29A had look down shoot down. We know that if target is above horizon makes more sense since it gives radar better picture and no struggle to process terrain, when it comes to ranges less than 25km with this radar N019 it makes no difference except in HPRF mode which is worst for close range combat, but as in modes such AUTO and P it makes no sense to break lock depending on where target is, above or under horizon, giving a fact that target is closing fast, even with his crank to side i did same in his direction of nose so i don't lose closure speed. My personal opinion it makes no sense since i know for sure how radar works in PRF modes. Please take this as reason to take a good look in details more and do tests by yourself, thanks.

Yes that is also a reason to dig deep and see if SPO works with radar in ДОГОН mode (P). Zoraja had his radar in ДОГОН while fighting which he stated.

Here is what i tried with all radar modes: Target Span from M to S to L to default, no difference, only on S you get maybe faster detection. COMP Switch even if it says in manual not implemented Foe or Friend IR+RADAR (also not implemented) and TWF/FHS or RHS Still no luck.

Yugoslavia purchased 14 MiG-29B (9.12B) and 2 (9.12UB) in 1987. , all of them have been even worst than 9.12A and had limitation for radar power and so on. The 9.13 and all current variants that Serbian AF has now were not present in 1999. only 9.12B variants. Anyway this is just story, not much to be seen but gives some reasons to give a deep dig for SPO-15 having warning and operating while having radar ON, hope this helps, thanks for replys.

I just replicated this 5 times in row, i think something is broken for sure. BrokenLock1AUTOCMBT.trk BrokenLock1HEADON.trk

First i want to point out that this is from Serbian pilots reports during interview after they have been shot at or shot down by USAF F-15C's mainly using 120B in Operation Allied Force in 1999. During first day of operation 24.03.1999 Pilot Nebojsa Nikolic had proper RWR warning that he is being locked and missile warning. Survived 3 fireballs from missiles. Pilot Predrag Milutinovic had two times lock warnings and missile warning. Later was locked from firendly KUB which he also had lock warning but no missile launch indication and that way got shot down in final landing aproach. 26.03. Pilots Slobodan Peric and Zoran Radosavljevic in their formation flight towards 2 pairs of F-15C's, only Zoran had SPO warning that they are being locked from their 2 o'clock, it is unknow if his radar was functional or not, but Slobodan's radar was malfunctioned and SPO also he is the one who survived to tell us that he only has seen 4 white missile trails and gave command to Zoran to defend also. 07.04. Pilot Boro Zoraja after take off had SPO go crazy in his headset, giving him missile warnings from 2 o'clock, he took off with radar enabled, managed to dodge first missiles, re committed to enemy, had one of targets locked at 30km after his SPO went crazy on him giving him missile warnings again but from 12 o'clock while hold target locked. This was in fact longest flight of Serbian AF during this operation and it lasted 40 minutes, his oponents were 3 F-15C. 08.04. Pilot Dragan Milenkovic almost same story as of Boro's but had two times missile warnings and lock on from his nose while having radar in search mode. So my personal option is that SPO-15 IRL is not this much bad as is now on MiG29A. Here is video from their story's.

1st. So issues is that lock is lost very easy, target needs to do just crank left or right 45+ deg and lock is lost. And it doesn't matter if target is above horizon or under it. This aplies to all modes, worst is P mode, then AUTO CMBT and Head on is only mode that gives a chance to hit target before lock loss. This aplies to range up to 25km max. 2nd Issue comes from close range, if you hold lock and let target to come closer than 10km, 90% it will lose lock, only moment when it wont is when target is in your HUD. 3rd Vertical radar mode 99% won't lock target, only moment i found it that it works is when target is cold, not maneuvering and above horizon. 4th Issue with Persuit mode or Auto, scan rate is way too long it makes no sense. Again speaking for range up to 25km max. Tacview-20250920-013550-DCS.zip.acmi

I'm no expert in AH64 since i got it like few days ago, still trying to figure stuff out but what group of us have seen is that George as CPG is locking targets at very top of Lock box or most of the time its on border line of each 4 sides of that lock box, so is this a bug? and will George become some better at targeting in future updates? Here is video of example,

No sense reply..

So i can't find button or just it's not implemented in game for ATGM, so when u lock target with AI via menu and you line the sights u get a tone for LA, but when there is no units to select and u want for example to fire missile at building or house it doesn't give u that tone for LA, so would be nice to let me know why is that?

It worked, that was problem for take off, thank you

So it goes like this, deleted all my files, made new profile, deleted game, module and nothing works i just CAN'T TAKE OFF from ground in SP Editor!!!I Bdw i can take off from cold start BUT ONLY on Servers!!!!, next i tryd taking HOT heli in Editor and placed it on 500m ALT & SPD 250kmh and all it does is just goes down, its like throwing rock out of plane, won't move stick or anything all it does is just gets collective at maximum and i am still falling down!!! While placing Ka-50 HOT and COLD it works fine... Next is with my friend he flown with others and for him everything works fine but when he comes to be Operator in my heli he just can't launch missile, hears like he has cockpit open and has no sound of engines of mine heli then after like 5 minutes he gets my APU sound starting and rotors spinning, while we are airborne, he sees me fly but without engines ON! And i don't know what could be problem anymore... And after 2 days of trying to get understanding of what is going on in Multicrew way above we found solution, if we get at the same time in heli before taking any action it gets all those bugs, and after we start heli he HAS to go back to spectators and join again so it can work all fine.

Tryed it and still same, uses 1% less xD soooo DCS thing......

For this game if they knew how to optimize it it would take up to 8GB RAM and 3GB VRAM....

Is there any hope that this is gonna get fixed, 17GB of RAM usage for such a game that has no more than a plane texures to load and flat map, such as Syria, i can't play the game with out stuttering every 10 seconds or so, on any map, i already spent 1200 eur only on 3 components for my PC few weeks ago just to be able to play DCS with better FPS, graphics and hope to get rid off stuttering and then i come to this, same as before, i am here just to ask for help and answer if there is any solution coming soon... My PC specs are this: ZOTAC AMP RTX 2060 6GB Intel i7-8700 MB: Gigabyte H370M RAM 24GB Kingston HyperX Fury B&R SSD Kingston 256GB (where game is located) & Page File turned on HDD 1TB Cooler Master 700W PSU Just to note that i have settings set to medium, pre load radius half, MSAA 4x and other things off...

Always first time i join server where i can see F2 view on friendly i can see that JF-17 has PL-5's at iner pylons instead SD-10's and also today was playing F-18 against JF-17 and as for my game i see that he has PL-5's at iner pylons, he fired at me i have not seen any smoke from my 10 o'clock from SD-10 as should be while i was holding him in TWS and in next moment i got blown up and it says that he killed me with SD-10 but i didn't had any RWR warning, just painting from his radar, also this all was happening in 10nm, PLEASE FIX THIS, it's MAJOR bug for us who fight against Jeff's, but bug goes off and u see everything as normal after first death!

This problem is since JF-17 came out, every day i get at least 3 crashes when i get shot down, moment of crash is in choosing new plane after death. I would like you guys to look at this soon and repair it if possible, here is log. :) dcs.log-20191220-122740.zip dcs.20191210-042116.rar dcs.20191215-180844.rar