Hoggorm

Basically the same result but different cores max out...

Hello, I am, in VR, CPU bound and see that two of my 16 CPU cores peak to 100% during gameplay. The rest however are at about 50% or lower. Could this be the cause of the CPU bound message? I see someone say I can turn off those two CPU in DCS spreading the load to the other CPUs insted. Would that be a solution to my issue?

Thank you for your reply Hobel, So, the missile goes active based on distance to target? I was under the impression that it was based on time (to impact or after launch). That explains at least why there is so little time to react. Now in this specific scenario included in the Tacview, I shoot two AIM120 myself at Tax, but as he turns cold, and no missile warning has sounded I was fairly certain he had not shot at me, or at least that his missile no longer was provided tracking. That is why I targeted the next aircraft, a F18. I've included a new Tacview recording since this was not included in the first. Here, I am shot down so obviously no radar guidance from me anymore. Still, my AIM120 seem to track the F18. This time a miss though. The F18 does indeed fly fairly straight ahead after I am shot down. To me though the AIM120 seem to adjust its course even before the 5NM where the F18 reacts and start its defensive maneuvers. AIM120 tracking after radar loss.zip.acmi

Hello, I'm having a hard time avoiding AIM-120s fired from a F-15. They fly high and fast but I see that the missile warning appear only seconds before impact. In the Tacview recoding attached you can see user Tax in his F15 fire at me, Hoggorm, at 04:58:12. He then turns away so he must loose radar track with me(?). The missile still homes in on me. I fire an AIM120 myself just before the missile warning goes active. I now try to place the missile on my 9 o'clock, but it is too late. About 13 seconds after the missile warning sounds I am hit. First I find it strange that the missile is able to track me even though the launch aircraft has turned cold. 2nd I find it strange that the missile warning goes active so shortly before the missile hits me. What did I do wrong here? How can I counter this and survive the next time? hit by AIM120.zip.acmi

I see. So when waiting until the missile go active and then turn gives a better chance of hitting I would assume? While turning immediately can make for a lucky shot.

Hello, When I fire a AIM-120C the HUD will show a Axx counting down until the missile go active on the target. So what I try to do is at least keep the radar looking at the target until the A changes to a T. Now sometimes I need to turn away early, lets say at A19. To me that should say that the missile have not gone active and will be a miss. Still I see that many times I do hit anyway. So what happens? Whit still 19 seconds left until the missile is active I no longer guide the missile but it hits nevertheless. I was hoping you could explain to me what happens and how early I can turn away and still hit the target.

Ah, so this has been reported a long time ago. No immediate fix to be expected then I assume...

As far as I understand the POS EOM mode will also do this. This was the mode I was in during this attack. I see. Then my understanding was wrong and I had a little more faith in the weapon than what I should have had. Nice to know and this answers my question Thank you for reporting the Roland needing two HARMs to be destroyd. Absolutely. 203 was entered for the Hawk Tracking Radar in this specific mission.

Thank you for the reply Hobel, Yes, please find a relevant track file attached. We were two F16 who did two strikes on a SAM site at Fujairah airport. The steerpoint for us both is exactly the same and is set just south of the airport near the SAM site. On the first run the flight lead hit a Roland twice and destroyed it. I hit a Roland once but did not destroy it. Another HARM destroy a Hawk TR. One of my AGM88s really wears off. I've never seen that before though. On the 2nd run (20 minutes later) I assume all radars are off (we did not know that at the time), but you can see that even though, again, we fire at the same steerpoint all HARMS rain down over the airport at random. I would expect them all to hit basically the same spot? There is a Tacview recording of this as well here (My callsign is Hoggorm): https://drive.google.com/file/d/1ZasUpwRX5Ak399ACjjWV46texEyOkNk4/view?usp=sharing The first run is about to hit Fujairah at 0728. The next run is about 20 minutes later at 0749. HARM strike Fujairah.trk

Hello, I try to attack a Hawk SAM site in POS EOM mode. I've added the exact coordinates for the Tracking Radar part as a steerpoint and launches when within range. I assume the SAM site turns off its radar from time to time. Anyway, I see that often the missile does not hit anywhere near the steerpoint at all (often it does hit, but then I assume the radar is on?) It can overfly the steerpoint with several thousands of feet. Is this normal? I would expect the missile to hit the radar even if the radar was off if it was located at the steerpoint? Or am I assuming too much?

Would it be possible to add a feature where I can be in the TACTICAL CMDR or JTAC/Operator position, add coordinates there and save to a file that can be sent to friends that execute the attack?

Thank you Despayre

Nice! Thank you!

Hello, I was wondering if there are some relatively easy missions, or even a full campaign, that work well to be played with a friend as RIO? Even better if they are designed specific to be played with a RIO! I`m interested in both payware and freeware.

Is this add-on considered cheating in multiplayer servers that monitor integrity, such as Operation Blue Flag?

Hello, I've not used DCS for nearly two weeks and there has been two or three updates since. Two weeks ago I was able to get the green GPU bound message in the FPS counter nearly all the time, now I do not see it anymore. It is basically just alternating between red and yellow CPU bound. What can be wrong?

Thank you, LeCuvier, for your suggestion! I'll consider it.

Thank you Hempstead. It sounds a bit risky, but I guess I have little choice...

Thank you Hempstead, I might have not been clear enough, but all but the up direction works. Up is the only direction that is not responding. Do you know if there are any instructions available on how to open the throttle up so that I can take a look? If the Coolie switch is available as a replacement part that is super I'll contact Thrustmaster then I guess.

Hello, My Thrustmast Warthog Throttle Coolie switch up stopped working today. Both down, right and left work as normal. The throttle is just over 2 years and the warranty is expired... Can a new coolie switch be bought from Thrustmaster? Is it easy to open up the throttle and have a look inside? Maybe I can see what is wrong with it, but I do not dare unscrew anything yet... Is there a procedure on how to do this somewhere?

Thank you Chain_1, I'm not all that found of mods. They tend to break at the most unfortunate of times....

I appreciate your suggestion Jascha. Thank you. One of the throttles, although not in use for the F-16, is perhaps not the best solution for me. Maybe the zoom slider will do? I'll test it.

Hello, I've mapped ANT ELEV Know - CCW and CW to my Thrustmaster Warthog Coolie switch but feel they are too sensitive. Just a small touch on them slams the radar antenna way up or way down. It is difficult to fine tune the elevation. Can this sensitivity be adjusted?

Ok, this can make sense. However I am no computer expert at all so I still wonder why this theor. (theoretical) FPS message only appear in the MultiThread test version and not in the regular open beta version? If FPS is 35 and theor. (theoretical) FPS is the same (35), will that give the same performance, or experience, as FPS 35, theor. (theoretical) FPS 60? Or will the latter be better? To me the MT version appear to be more smooth, even though I get the same FPS reported in this specific mission (35 FPS) on both.

Thank you for the replies. I still do not have full understanding of what (theor. FPS 59.8) means in the green GPU BOUND message when the actualt FPS appears to be lower.