-
Posts
2654 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Hobel
-
Do you know what the actual target was?
-
looks good, now give the missle 25-30° loft and show what happens then
-
These values can also be accessed outside the editor. Try it yourself with 35-40,000 and mach1 shots - the results are similarly good. This
-
It depends, there is also a bug report in dcs. As far as I know the longest in dcs is +12 seconds irl videos show 8 seconds as far as I have seen Oh, I misread, I was assuming PDLT for friendly.
-
also here your Tacview shows that you make all your Aim120 shots under 10,000 feet, one should not be surprised to have so little range... and here ~50nm 4 Missles 4 Kills Tacview-20240603-163444-DCS.zip.acmi
-
No not because of flare, at exactly 18:12 you hit the notch and hold it for a short time, the missle loses the lock at below ~25kts Vc. When the missle is exactly 2798feet away from you, you leave the notch and accelerate above 25kts again. we could now argue that the missle should now see you again, but it doesn't do that and I can't answer why.
-
can you please upload a track of your scenario, otherwise we can't help you, you have also skilfully ingorised explanations from other users so far
-
TGP on our Viper? How well does it actually integrate wih Mavericks?
Hobel replied to RyanR's topic in DCS: F-16C Viper
4 https://forum.dcs.world/topic/277761-inner-wing-pylon-payloads/?do=findComment&comment=4836887 -
investigating Maverick BGST & JDAM PPT Still broken post patch.
Hobel replied to Shibiswag's topic in Bugs and Problems
You're right, somehow altitude has no influence, the bomb hits the target. -
investigating Maverick BGST & JDAM PPT Still broken post patch.
Hobel replied to Shibiswag's topic in Bugs and Problems
Hm ok will have a look. I'll come back to this later. Can you send me a track of it so I can see your procedure? -
investigating Maverick BGST & JDAM PPT Still broken post patch.
Hobel replied to Shibiswag's topic in Bugs and Problems
What you describe is what I mean, the "too long" comes from the jet(in dcs) , the bomb lands around the actual coordinate in a cep that pretty much matches your experience "~13m" Also altitude actually plays an important role in dcs. For example, everything around the center. GBU38 -
investigating Maverick BGST & JDAM PPT Still broken post patch.
Hobel replied to Shibiswag's topic in Bugs and Problems
Can you be more specific? -
investigating Maverick BGST & JDAM PPT Still broken post patch.
Hobel replied to Shibiswag's topic in Bugs and Problems
As far as I understand it, this part is still WIP. This means that the GPS bomb will land exactly on its PP coordinates in the future. No matter if the f16 drifts 10-30m inaccurately. However, I wonder how TGP designations will work in the future if the f16 always has 10-30m drift, if you then make an exact designation on the target you give the bomb the drift of the f16 with + the bombs ~5m cep. Does this depend on the sub mode? -
is basically still WIP. PP bombs do not currently work accurately, before each bomb drop you have to redesignate the target for a good result Here is the whole discussion : https://forum.dcs.world/topic/347411-f-16-pre-setting-jdam-accuracy-steerpoint-in-free-server-after-april-patch/page/3/#comment-5447434
-
my first wild guess is that the 2700RPM is to blame, try holding 2600RPM and see what happens then
-
Negative, direct hits destroy light vehicles immediately, bmp2 etc need 1-2, that's fine. But what often happens are no direct hits and since the aoe is not even or hardly able to damage a jeep, the problem lies there
-
45 seconds life time, with that you can cover about 10km, sometimes more, sometimes less actually, you can laser targets up to 15km with the Apache
-
Similar issue with the Blu97, to achieve an effect the bomblet must hit directly. The HE effect is sometimes close to 0 with light targets. Blu97 example
-
I am more than aware of all the points you list. So I come back to the point, what logic should the ADI altitude direction interact with if the system it is connected to only works in 2D? the indicator as described should show the vertical direction to the waypoints/mark point, but since our ka50 only has 2D what should be fixed here? Either it was a superfluous display or there was an option to enter the alt in a certain way. In real KA-50 images/videos, for example, the flag is not visible.
-
Your other points are valid and I cannot refute them due to lack of evidence. But what do you mean by that? I have also marked point 10, but as I said, it doesn't seem to be implemented ingame. Otherwise, explain how point 10 works or how the red flag( point2) goes away.