All Activity

He's saying that the lamp and sensor work for some range that's considered neutral. It is not a precise point that'll give you hands-free flight and it's also not the trimmer's job. Use AP instead. This comes up for every module and it's just misunderstanding of the trimmer function. Hence the trim sensitivity workarounds because people apparently want their aircraft to fly on rails

Interesting project! Are the two Arduinos automatically recognized as two different Windows game controllers? Until now, I have been using Leo Bodnar boards. However, these are quite a bit more expensive than the Arduino Leonardo boards...

Agreed. If they really want this to be a Cold War map, they shouldn't have set the default date to 1999 to begin with. Apparently, according to their sources, several aerodromes in Normandy also had ICAO designators back in 1944

Do you use VAICOM/VoiceAttack?

VR Pimax Crystal OG + Quad-View Foveated + Eye Tracking I also have slight banding and flickering in VR. I don't use Pimax's internal Dynamic Foveated Rendering & QuadViews. I use the conventional version: mbucchia -> Pimax-OpenXR mbucchia -> Quad-Views-Foveated TallyMouse -> QuadViews Companion That's why I don't think it's because of the Pimax update. ED: Can you please check this, we had a similar problem a few DCS updates ago. Thanks and greetings Tronix

Their GIS data probably just says "power line here" without specifying the type. Maybe IRL the poles are much smaller than these?

no its not:

@Calvin.Pimax Hi, I am on the latest Pimax Play, 1.42.1, and latest Crystal Super firmware. If you read my post above this I am rather happy with these updates. But - the last few days I can not use the volume buttons on the headset to access menus any more. Pressing the Volume up for 4 seconds (or even more) does not work to get to menus. That was a nice feature to have because that let me just keep my hand controllers safely in the box The volume buttons do work for adjusting the volume with short presses. Is this a known bug?

It would be more efficient to base expectations for a DCS MiG on a docs for a real MiG. MiG-29 and F/A-18 or F-16 are different aircraft with different performances, you can't say "It's a bugged model because it climbs faster than F-16", better say "It's a bugged model because it climbs faster than a real MiG-29 here's the graph's superposition of real and model". Now that would be "professional level".

This would indicate you are having a different issue entirely. If you unassign the Pitch and Roll Axis from all controllers and you are still getting failures in the BIT your problem isn't being caused by inadvertent inputs from a FFB joystick. Unfortunately the BIT is rather picky to begin with and can fail for a number of reasons. It fails if you haven't switched off ground power when you try to run it for instance.

We await the master to get into the cockpit. Looking forward to some videos from you comrade, Ironhand.

Первое впечатление от модуля МиГ-29 (9.12) https://rutube.ru/video/fd0f68725005e9c00410420e804f74ad/

So you are saying that it IS in neutral position after AFCS test even though the trim neutral lamps aren't lit?

Перевести ЗК в РУЧНОЕ и летать как на Л-39, нет проблем. И да, у РСБН не радиалы а азимуты. РСБН ориентируется по истинному направлению меридиана.

I suppose technically IRST model just scans for any particles, but IRL smoke trails from missiles(unless it's a space launch) and smoke screens don't block or give any contrast to IR sensors IRL. Clouds do because they are made of water.

Yeah maybe. Just so small I've not really noticed it, or it's overlapped with other HUD items....

The lamp wont light up at a precise point, the sensor lights up when it thinks it is neutral, almost like in a dead zone. we have checked and its not a bug. thank you

Not sure what this is referring to—must have missed it—but thank you for the enthusiasm. I’m still a few days away from having the update downloaded (slow internet) so that I can finally download the MiG. Looking forward to jumping into the cockpit.

Radar cuts off even itself, not just SPO. It cuts off itself. And then this signal is just copied to SPO too. Othervise radar would have shown only a white wall at all times instead of contacts and clutter. So yes when radar is emitting, SPO is "closed". Indeed. You just have to understand this "disabling" lasts for 3 microseconds every next 3 microsecons. This is HPRF duty cicle, MPRF is much much easier.

Yea, this is a big deal on night environments and had been broken for months now...

We are investigating MSI work has complicated things a little but we are working on it, please dont forget the complexity of what we are dealing with. thank you

We are looking at improving jamming logic in the future, but I do not have any news to share currently. thank you

this is already reported, I have moved the post to the main section as it is a clarification question not a bug report parse thank you

Hi, I have already reported this to the team and it will be fixed in a future patch. thank you

I'm quite certain you both have if you've locked with the radar. If locking with the irst or any of the IRST close combat mode you won't see it since your not locking with the radar.