pierrewind

I assume this is related to the recent changes to DCS weapon encoding, but in multiplayer some external fuel tanks and the super 530D aren't available. This has been tested on multiple servers and reported by multiple users. It seems ok in singleplayer.

It's been two years since this bug was filled. It has not been acknoweldged, nor has it been fixed. Is the yak 52 considered dead at this point?

+1 Runways lights isn't turned on at times we would need them. That is also the case for some ILS in some situations... I also find the truck threshold lights to be very anoying. It would be nice to get rid of these trucks and maybe replace it with proper approach lights. ALSF2 type would be so nice at major airports. Though a bit overkill for smaller ones!

Thank you for the answer. Attitude indicators have been designed with system that keep it level. It usually is accomplished through small exhaust ports within the gyroscope. Then with precession it will bring the gyroscope level. This does introduce small errors with turning and accelerations. Other more advanced gyroscopes may use other systems. It also allows the gyroscope to maintain a constant reference in regard to the earth "plate" . At the moment, it seems the attitude indicators are not able to regain this reference. Not being able to regain/maintain the level reference if a delibarate choice is a wrong choice. (note: on the ground, it is able to regain reference) The earth rotation has influence but this instrument is designed to account for it In flight, you should never have to cage/uncage unless you run into some specific situations such as hitting the attitude indicator limits.

Here is the track applicable to the P51 Gyro Bug 2.trk

On some modules, once the artificial horizon developps an error it is unable to correct it. This has been observed on: -The F5E -P51 -FW190 -(problem likely on other airplanes as well) Picture taken on T/O, 30 minutes later the problem was still there (or maybe increased). There wasn't any significant maneuvering. Doing 90degree turns showed the gyroscope reference as being wrong (opposite bank at 180 degres, pitch up/down at the 90 degrees). Reference wasn't regained in flight. Once on the ground it seemed to be able to correct this error within 10 minutes with an expected 2 degrees per minute correction (spooled up). The fact that the gyroscope is unable to regain the reference in flight is a big problem. It for example will make uncaging the attitude indicator in flight quite impractical or render the attitude indicator information unusable after it developps errors. Ps: Similar to:

Same here

When close, the solar pannels just fade away within what appears to be some sort of sphere/circle

RX580 getting similar artifacts. Though, it seems less frequent/more random for me than what I see on the videos.

Same here; Happens on regular flights. Asside form impacting the interface, it also bugs the FLOLS and the LSO screens.

Thanks for the reply! Further tries did show the same result as you. My testing was a bit flawed as I used different missions. So it appears to be a choice of DCS to turn of the "inactive" ILS. To me it doesn't really sound like a good option now that bad wx is fun. But that ain't anything to do with razbam

EDIT: This is Due to DCS disabling "inactive" runway Hi Razbam, I could not get the ILS to work on these airports with the M2000: -Sochi -Senaki -Kobuleti -Tbilis RWY31 -Vazian RWY31 -Mineralyne RWY12 -Kutaisi may also have an ILS on 109.75 (not listed in f10 map, but shown on mission editor) Some limited testing with the A10 appear to be mostly working (Asside from vaziani Tbilis and mineralyne not working; some not tested). I seem to recall having this issue before 2.7 as well! Again, thanks for the great work. PS: failed to report it in bugs section

Great! Thank for this work!

Hi Razbam, First of all thank you for this amazing update, it is a great step forward making our lovely module that much better! I have however spoted a few errors in the autopilot code: --ILS Glide doesn't disengage with trim up/down --ILS Loc doesn't disengage with trim left/right --ILS Glide/Loc captured before deviation bar is centered --ILS Loc armed and captured lights sometimes illuminated simultaneously --ILS is using INS data to guide the aircraft to the runway (likely should use only deviation indications [Bar right, I go right; left, I go left...]) --ILS armed disables the active ALT mode (likely should transition from alt capture + ils armed to alt off + ils GLIDE capture) --Bank increase on pressing Alt Sel below 50degrees speed. PS: I also seem to experience occasional "random" hard crashes on ILS capture phase MIRAGE 2000 AUTOPILOT ISSUES2.trk

Found this extract from the mirage F1CZ flight manual (using a similar autopilot) available here: https://www.avialogs.com/aircraft-d/dassault/item/2764-1f-f1k50cz-1-1-mirage-f1-flight-manual-aircraft-operating-instructions

It was also my understanding that this is the normal expected behavior in regards to the trim inputs. However when arming the approach mode, the autopilot disengages the alt hold mode and doesn't maintain the altitude correctly. This is to be corrected by a trim up input. Which in turn will disable the glide. This is expected, but undesired in this situation. The issue is not in regards to the trim up input. But it is about being forced to use the trim up input to correct for the autopilot unable to maintain the altitude. Then low speed gain. Yes 200kts or 18 AOA from the widely available manual. This used to be a significant issue for me at speeds even close to 220kts. I haven't seen anything on the changelogs but the behaviour may now be a bit less agressive. My experience would tend to dictate this limitation was introduced to prevent a speed decay to "stall". But, as can be seen in this video, it likely has been cleared to lower speeds since then, particularily in approach mode. Mirage 2000 Djibouti

Hi razbam. I have noticed for a long time the autopilot being overly agressive at low speed. (gains too high). This is very clear in heavy configurations. Due to this high gain, the autopilot enters an oscillation. Depending on speed this oscilation can be divergent leading to a loss of speed/control. Unfortunately this renders the autopilot unusable in these configurations. There is also a logic issue when capturing an ILS. When the localiser is captured, the glide slope also captures even if not on glide. This is wrong. From alt mode -> arm ILS -> Loc captured + alt; gs armed -> glide captured -> loc + gs; alt gone. In the current configuration the autopilot would loose altitude on approach. Correcting it requires a trim up input wich in turns disables the gs mode (undesired). Seeing these corrected would be a great step towards the flying through autopilot philosophy of the M2000. PS: I am aware there might be some overlap with previously reported bugs and some grey areas in the various operating modes. MIRAGE 2000 AUTOPILOT ISSUES.trk

Here is the track. To me it feels like the engine is running out of gas and the "nourice" cannot refill... But since the fuel level of these does not change I guess it is not modelled. Mirage 2000 Restart Bug.trk

Well, when we say doppler radar, it is in fact pulse-doppler. This combination allows to obtain more information in a single pass. (A pulse radar wouldn't be as complete, though the pulse-doppler also has limitations). There is 0 reason for this inacuracy. The radar can obtain the relative target speed via the doppler shift. or via the distance shift between the two passes. The two methods are very accruate! The pure doppler radar is used on road radars... to my knowledge it is precise to less than 5% and will not show speed as if you're running backwards... https://en.wikipedia.org/wiki/Pulse-Doppler_radar

Not as I understand a radar. Radar goes first swipe, and it give a relative distance to target. Then , when it crosses the target again on a swipe (not necessarily the first after) it will get a new distance. Then we do (D1-D2)/Dt and we get the relative speed! To have the best refresh rate, then you get to play with bars and azimut or STT/PIC.

Affirm

It is still present. mirage 2000 Throttle bug.trk

This bug is still active. mirage 200 PID speed bug.trk

Works fine for me. Make sure you don't have multiple axis assigned to the brakes!

Hi razbam! When a target is locked in PID, the delta V can be wrong (most importantly showing negative closure speed when actually closing on target). In PIC the issue seems to go away. Thanks Pierre mirage 200 PID speed bug.trk