jojo

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.

Yep, the time is Zulu (I've worked all my life in military or civilian aviation, local time makes me cringe). Yes, I designated the TOT WPT in the séquence, it's boxed. I would just like to know if somebody managed to make it work in OB 2.9 ? Apparently nobody is using it...

- select SEQUFC on HSI - Enter TOT - Select target point - Enter ground speed (or not, I tried with and without). The chevron below speed indication is stuck to the right, no matter what speed I'm flying. I tried to enter TOT matching ETA on HSI, the chevron is still stuck to the right.

Everything is in the title. I read the manual, I tried, but it doesn't seem to work.

As far as I'm concerned, it's in the screenshot above.

The bug is till there. No script or trigger. I just put the Mirage in air start. I tested twice, first time with my switch in retract position, second time with the switch in extend position. Both times the gear is extending and I have to cycle to the other position to retract it. It's working with any other module ! Mirage F1 Air Start LDG lever down.trk Mirage F1 Air Start LDG lever up.trk

It happened to me during Raven one campaign. First time I managed to dodge it when coming out of S-3. Second time I was just about to plug in when it collided with me coming out of left basket. I also got destroyed when the AI did a sudden and brutal horizontal and flat translation into me. Allied AI is a dangerous hazard when close, more than the enemy... On top of that the AI doesn't even get a scratch and continue to fly miles nothing happened...

It just happened to me during Raven One Hornet campaign. The "wingman" is scripted and not really into the same flight. Here I was trying to join up after departure... So I suppose the bug isn't about refueling, but AI doesn't acknowledge player's presence. In MSN02 I had to avoid the wingman coming out of the tanker.

Sorry, no track yet. But to summarize: - HOTAS synchronized option is active. - HOTAS command are cycling as expected (up is up, down is down) - despite the switch being in the up position, with air start the landing gear is going down when starting in flight. - by deleting the HOTAS assignment, the problem is solved. - the problem doesn't happen on other modules (so it isn't on the hardware side).

Thanks for the confirmation. I didn't have this issue prior to last update

For the landing gear I'm using a two position switch (T4 on Virpil Mongoost CM3). I ticked the option to synchronize switches position between game and controllers. When I'm using the switch, it's operating with the expected motion (forward = retracted/ back = extended). Before starting the flight I'm checking my throttle, the switch is in retracted position. However when I'm using Instant Action missions and I'm starting in the air, the landing gear is extended. So if I don't start the flight with throttle at idle, by the time I'm cycling the switch retracted/ extended/ retracted the landing gear is jammed. The landing gear shouldn't be extended when starting in flight !

Just saying, to prevent you from disappointment. Last time I just had a couple of buttons to bring back. This time it's almost everything to re-do from scratch...

I don't give a s... about Sinaï map ! Tonight I had a slot to play with some buddies, tomorrow I won't ! We couldn't make the update, so no issue, ins't it ? Just play on the current OB... But no, we can't even connect to our account ! Some didn't connect for the last 3 days and can't even launch solo. This is a bad system, period !

After spending more time on it, I can't say if the problem is asymmetrical load or just the unwanted roll in basic AP mode ? When it does happen, it's like the control loop is "diverging", when the AP finally disconnect, if the plane is rolled on one side, the trim is unrolled to keep this position. So maybe if you fixed that already, it will be OK with asymmetrical load ?

OK, thanks.

[Edit] Actually, even with symmetrical load the AP tries to kill me. 6 000ft, trimmed and level, 300kt. AP + ALT: it can be fine or it can randomly bank left/ right more than 60° then disengage. I can't provide a short track because I can't identify the triggering cause, it happens randomly.

Mirage F1 CE, single-player, multi-threaded version, latest Open Beta. Take with one fuel tank, 2*Magic, 2*Super 530F. Shot 2*Magic & 1*Super 530F. Left Super 530F remaining. Aircraft trimmed when engaging the AP, I cut the throttle to slow down. Flaps retracted, the AP (PA + ALT) can't handle the asymmetry below 350kt (start banking left). Below 300kt It's becoming wild, it's over-banking to the right then to left and AP fails. In landing configuration it seems to happen at slower speed, but it fails before reaching final approach speed. I don't think it's an acceptable behavior for an all weather interceptor with such advanced auto-pilot.

Radar air to ground ranging was not available for a lot of Mirage F1 variants. It’s probably a thing for Mirage F1M, but for instance this is why you have a laser range finder on Mirag F1 CT: this were upgraded Mirage F1 C-200, but they kept the original Cyrano IV radar which lacked air to ground ranging. It was cheaper to add a laser rangefinder than to upgrade the radar.

It's true, but we can make some educated guess. If I understood correctly, there is an automatic gain reduction system which is operating when the gain control is set to maximum. The elevation is set to D+06, so likely in look up. My other source is that I have the chance from time to rime to play DCS with a former Mirage F1 CT pilot. He always said that the noise level is too high.