jojo

@Zabuzard Up

The manual is little bit short here. 1- is it working already ? 2- if yes, how do we do that with Jester from front the pilot seat or jumping into the back seat ? Thanks

OK thanks. I understood that the guidance started when pressing bomb release, but I wanted to be sure that Jester was computing offset with the WRCS board “tell Jester”. Thanks for your patience

Same problem for me. MT Client. Virpil WarBRD base + Thrustmaster Hornet stick. The slower it gets, the more difficult it is to trim, at landing AoA I’m fighting the jet. I can’t let the stick go even half a second. I’m always one click too much or one click not enough with the Trim HAT. I can trim the Tomcat in landing configuration fine.

But there is also a roll guidance, isn’t it ? Jester has to enter N/E and E/W offset. My question are: - does he assume offset from current waypoint and next waypoint ? - when does he input offset into WRCS ?

Thanks. Just to be sure I'm doing things correctly: - offset needs N/S & E/W ranges in feets. - I assume Jester uses the current WP as IP and the next one as target when we tell him the parameters through the WRCS page ? - Jester tends to switch the waypoint early. Does it have impact on offset guidance ? Do we need to tell Jester to hold on IP waypoint. Maybe we could tag the waypoints in mission's editor with #IP and #TGT as names to preset the parameters ? Thanks. Just to be sure I'm doing things correctly: - offset needs N/S & E/W ranges in feets. - I assume Jester uses the current WP as IP and the next one as target when we tell him the parameters through the WRCS page ? - Jester tends to switch the waypoint early. Does it have impact on offset guidance ? Do we need to tell Jester to hold on IP waypoint ? Maybe we could tag the waypoints in mission's editor with #IP and #TGT as names to preset the parameters ?

Am I the only to struggle with the trim ? I always get a click too much or not enough. Especially in landing configuration, I can't manage to trim "hands free" for landing AoA...

Oh, is loft attack working with Jester currently ?

I looked in the manual, but I didn't find anything about navigation update with Jester. It's difficult to perform a low altitude attack mission without being able to fix the INS drift frome times to times...

It's hapening at time 07:45

The AI MiG-21Bis can perform 9G to 10G sustained turn but you don't see any problem with that ?

Hi, I will do it when able. Thanks

Ah OK, thanks. I tried the (usually) default RShift + P

I'm not single digit FPS, but it's worse than F-14 which is already a FPS eater ! Probably a no go for MP in VR...

Same problem with Reverb G2. The problem is even worse with the bombing table !!! Yet the Kneeboard is ok.

Hi, I don't understand, did you get the pilot body in F1 view ? If yes, how ? Thanks.

Hi, I filmed that at Le Bourget Air & Space museum. Enjoy

Actually, there isn't a lot of space for avionics in this tiny airframe. For guided missiles, you have dedicated interface black boxes inside of the jet. So between R530 and Super 530F you need to swap the black boxes so the Mirage F1 systems can talk with the missiles.

Look at the beginning of the take off run https://youtu.be/9eEGHGwRUv0?feature=shared

IRL it's closed by the relative wind (speed), not manually. GBU-24 + Super 530D at the same time ?

Thank you for your work Would it be possible to provide a simple demo mission please ? I tried to make a simple mission with your script, with an AWACS. I get the options through F10 menu, I get message like scanning and so on…but it isn’t reporting me any contact despite the basic AWACS giving me contact through radio. EWR.gciMaximumRange = 100000 -- meters Is it 100km from the detecting unit or from the fighter ? Thanks

Up

UH-72 Lakota is a variant of EC145, there is no EC142. UH-72 was selected in 2006, there was no feneston variant of EC145 back then. Fenestron came with EC145 T2 which first flew in 2010.

So it's working for you on OB 2.9. Thanks, that's just what I wanted to know. It wasn't a bug report.