Jabbers_

Correct there is no radio button bound. For me, I've unbound the Jester menu coolie hat, so this leaves it completely open. I also moved my Jester menu button from the throttle to the stick's master mode control button.

You are assuming that its implemented that way. I know a lot of how the missiles are implemented rely on ED and not HB. Once the missile goes pitbull im fairly certain HB has no control of it after that, even if it loses track of the target. (I could be wrong but from what I've talked to the devs about, im fairly confident in this assumption)

There were waypoints in that mission, so the INS NOW was quite a bit longer than it would be without waypoints in a mission. It would probably more close to instant.

I made that and posted that on reddit when someone had asked.

I did say during the stream Cobra asked me not to mess around with the RIO pit because he wanted to show it to everyone in a more formal way... which I respect. A stream of me flicking switches trying to figure out what everything does is not the most intreging way to be introduced to the RIO pit. I myself havent had time (as I stated) to learn it, not so much because of its complexity (though it is rather complex) but because I had been working on the Cockpit Tour and Cold Start videos for HB for the past week or so. Now that those are done, I plan on diving in and seeing what it is all about.

Yes Im obviously not Cobra, but yes it was toned down. The reason it is so loud in this video is I turned off the "Hear like in helmet" option to enhance the audio for the video (and turned everything way up. 400 is around 500 isnt it? ;) It was 3 bindings (excluding setup of ground crew interaction), startup, check, loud and clear.

From my MP experiences RIO works fine.

Here's one

I have a review in the works and did not come up with the same results here, at all... then i looked at your specs and realized why you did.

That’s technically neither of them...but what do I know :smilewink:

Oh boy

In due time Blacked out person is a tester, But he was using his public dcs name and didnt want him to get berated with questions.

Deeper, it tracks fine on the shooters PC, to everyone else it flies straight point A to B (no lofting). Thats what the tacview shows. Left is my pc, right is shooters pc.

Agreed, it was like 50/50 before, i tried about 20 tests with the AIM-54... all 20 broke, so nothing I can do till its fixed. The AIM-54 will loft some (couple thousand feet) even at 15nm, and the problem is it affects my ability to notch because on my screen its closer than it really is. See this image See the difference, missile had passed me, for a while... but in reality was still really close. Can't test like this. The problem is reported, tacviews for reference have been submitted, all we can do is wait and see.

What is it that makes you think they are broken?

Sorry, I didnt get that.

We had our reasons ;)

In Heatblur we trust :)

I was originally asking you what? You said sounds like a maddog 120... but nothing in this video sounds like that. So if you could explain what you meant maybe we can get some clarification.

As shown in my AIM-54 analysis videos, it goes active at about 7.5-10nm away from the target. As far as I understand it, in the real jet, the RIO can choose when it goes active, but in DCS the game engine does it, and as far as i know HB does not have control over this. As far as content creators go, speaking for myself, I try to be as accurate as possible, but hey... sometimes things get fouled up. Good content creators will acknowledge these issues and either correct them or make sure to double check related facts next time. Shit happens, move along ;)

I know what Maddog is, i was more concerned with his comment saying it sounds more like maddoging a 120 and how it at all applied to this video.

Exactly this, HOWEVER, they adjusted that parameter today to make the missile a bit more aggressive, so further testing is now needed ;)

What?