Hobel

Azimuth has no effect on DBS1/2 only on Norm/EXP(which is currently not working properly either, but there are already reports of this)DBS1/2 stands alone and has its own Area, as you can also see in the IRL video, the radar only scans selected areas and tries to do this in high resolution quite similar to the F15 (don't know what the mode is called there exactly) if you go to the "zoom modes" the azimuth has no effect there either

Which version are you playing? In the current Open Beta I can destroy almost 4-5 tanks with a CBU-105.

can you please upload a new track again, there have been several updates in the last weeks and months. I made a video here which I think is what you are describing here. What you see in the video works very much as intended. I Lock on the target and change the radar elevation, the radar now scans the new radar area and jumps again and again to the track, which is part of the cycle as long as the lock is held, hence this jumping. Maybe you could talk about why the short jump is displayed, but in essence it works as it should so the track seems to be a bit broken, maybe because it's a bit older? but at the beginning of the first track it seems to work as shown in my video. and It is clear that it does not jump in the STT, the radar is only focused on this point

Track replay pls?

hmm, so that doesn't work for me

@Ramses823 @Twantick Okay, I've taken a closer look at the whole thing again. The range scale (i.e. not the distance to the target) has predefined areas. This is shown in DCS as follows in EXP/DBS1 mode it is always One-fourth of the selected range. from 10 range scale you see a square of 2.5nm 20>5 40>10 80>20(not for DBS) DBS2 is from 1nm to max ~7nm, depending on selected scale. The confusing thing here is that in Wags' video the display is not reset when he selects range scale, however it seems to be correct as it is now that every time you change the scale the image is also reset. you can still get the result as in the video. select the desired location, put Coursor on it and then press the desired scale and then can you use EXP/DBS1-2 to "zoom" into the area. Here is an example:

Have not seen the track. But that is correct so far. DBS1-2 is already the "best" possible mode. Depending on the set distance EDIT: range scale, the respective EXP/DBS has its fixed areas and dcs represents them quite accurately. I will come back to this later. However, there was another problem that had an influence in this aspect, I'll have to look for the report. It was all a long time ago One aspect. You can also see the "jump backs" of dcs here, which has already been reported https://youtu.be/9YQtUl_tmbE?si=ML-avciAe8CVodS8

Yes, you can enter tgt in the INU, which will then be displayed in the Abris. I can't remember exactly why it works this way but not the other way around. @okopanjaCould explain this aspect better And as a reminder, fast alignment is not intended for combat use, especially if you want to work with target points and the INU

Intresting post about Sa-15

According to the ED statement, the ABRIS cannot send such data to the PVI-800, so the plan was rejected. I would also think that at least the KA-50III should be able to do this because the KA-50III is an ED product with the "what if?" philosophy.

yes, this is the point of the second video you can enter the displayed coordinates into the PVI-800. In the past, the ABriss was supposed to update the PVI-800 automatically every 300 seconds, but unfortunately ED abandoned this plan ¯\_(ツ)_/¯

as I said, show me the track then i can rule out user errors this is not necessary you can either create them yourself or you can use the information from the Abriss to fix the INU. Here is an example of how it works with the Shark Planner (<Link), these things can also be entered manually, but of course it is faster this way, unfortunately DCS still lacks such tool. In the video I cause a 1km drift. and then I create a fix point ingame and use it directly, as you can see it's no problem and here is an example, you can enter the coordinates in the PVI-800 and then it is up-to-date again

if you see it again send me a track i'll take a look at it

Yes, one button that resets all mfd pages every time. I also find it more practical to set mark points with the Viper with the f16 it is tms up and in the f18 an osb button and then you also have to redesignate the targets every time

Hm, I would say the same about the f18. I think the f16 has a much better workflow. Especially the fact that you can switch very quickly between a/a and a/g. That's not so easy with the f18 And the automatic MFD page memory function in the f16 is also nice.

Yes, but if it worked as reported in the other topic , TWS would be much more likely to softlock on targets that are a danger. as the prioritization is currently not optimal.

hm does this apply to the entire aircraft or just the pilot? if the pilot takes a fatal shot, are these 27 seconds perhaps the "dying process" of the pilot? that once initiated no further damage can be done?

just need to know more about the situation, some Sus have ir jammer that + flares could sometimes be enough. But the whole thing is quite vague as it is

Blu97 "bomblets" can penetrate up to 200mm of armor. Tanks or even apcs are very weakly armored on the roof. In dcs a Blu97 does 11% damage against a T80 hit directly on the roof. Recent conflicts have shown that homemade bombs smaller than a Blu97 can still completely destroy a T-tank Has already been discussed here https://forum.dcs.world/topic/247220-correct-as-iscbu-87-bomblets-are-not-armor-piercing/page/2/#comment-5268313

If 100 seconds is the realistic value, then unfortunately this is the case until new evidence is found. For example, the Russian 27ER has only 60 seconds, although it could theoretically fly much further, but 60 seconds is correct When the battery is empty, the rocket logically no longer sees the target.

It is possible that this is hardcoded, many things are not visible, so it is not possible to customize it. but I'm not that familiar with it. and btw 70-75nm are possible only you have to fly fast and high Tacview-20231030-223148-DCS.zip(1).acmi

It used to be 80 seconds and was then adjusted to 100. maybe the Aim120C 5 has even more but who knows Now all Missles have a life limit. Perhaps irl other factors also play a role so that it is not always fixed at 100 seconds so that it fluctuates between ~-+10 seconds.

Watch on youtube how the Hellfire hits a jeep directly, the jeep is broken but almost all the people on it can still run away? yes I agree, I don't think the radar is intended for soldiers and if there is a vehicle next to it, that's the higher priority

Aim120C battery lifetime is 100 seconds. I have only looked at the Tacview here and there it is over 100 seconds 12nm before the impact, the Aim120 runs out of power EDIT: too slow

Would it be possible to switch MFD windows on and off with a hotkey? Razbam Module offers this to some extent, if it were also possible with Apache, the problem would be solved in this way, you would only have to switch off the MFD Window with a key command