Zeus67

Please provide a track file.

The keyboard issue is solved here: https://forums.eagle.ru/showthread.php?t=245594

Hello folks, The update has arrived and among the things included is the NVG. Unfortunately a mistake was introduced in the keyboard keybind file and DCS does not load this file and thus the keybinds are lost. Since this is a lua file, we can give you a repaired keybind file that you can use until the fixed on is released on next update. The file must be copied to: Mods/aircraft/M-2000C/input/M-2000C/keyboard. Overwrite the existing one. BTW, there is a small bug that was introduced at last time. When starting on the air, the GUN ARM switch is in the ARMED (Up) position now, but the guns are not armed. You must cycle the switch down and back up for the guns to be available. default.lua

Eventually

Last update about the changes. See the first post.

I meant 10 and of course 11 is true since the radar does not change status at all.

Our friends at the AdA made some corrections to my post.

Hello folks, here are the news regarding the M-2000C updates: Pending review by our friends at the AdA, here are the changes to the PCA/HUD: 1. PCA and HUD are now independent of each other. So HUD mode does not depend on selected weapon nor master arm position. 2. Master Arm now just enables weapons release/fire. Setting to SAFE or ARM does nothing else. 3. HUD enters into AA mode when: Selecting CAN or MAGIC by using the HOTAS button, or by selecting Super 530D on the PCA. 4. MAG button on the PCA does NOT select Magic. It performs other functions. 5. Selecting an AG weapon will NOT set the HUD to AG ATTACK mode. Only the PCA will enter into AG mode. 6. To set the HUD, actually the entire aircraft systems, into AG ATTACK mode the pilot must click the PIP HOTAS switch forward (it is the same switch that sets the Special Modes when in AA mode). NOTE: The PCA must be in AG mode for the aircraft enter AG ATTACK mode, otherwise AA Special modes will be invoked. 7. With the HUD/Aircraft in AG ATTACK mode, clicking the PIP HOTAS switch forward again, will return the HUD/aircraft to NAV mode, but PCA will remain in AG mode. (To be confirmed) 8. With the HUD/Aircraft in AG ATTACK mode, clicking the PIP HOTAS switch back, will save the AG weapon selection and release parameters, return the HUD/aircraft to NAV mode, and the PCA will also enter NAV mode. (To be confirmed) 9. CAN and MAGIC can only be selected via HOTAS. 10. When selecting CAN or MAGIC, the radar will become active, even it the power switch is physically in the SIL position. 11. Upon deselecting CAN or MAGIC, by selecting PCA SELECT, the radar will return to SIL if the switch is in the SIL position. 12. Trying to select a weapon on the PCA when the system is in CAN or MAGIC modes is not possible (to be confirmed). Our goal is to have these changes ready for the next release. They are undergoing testing right now. Corrections to the above post: 3. Selecting POL in the PCA will also set the HUD in AA mode. 7. Unconfirmed. Clicking the PIP Forward after the system is in AG ATTACK does nothing. 8. Confirmed. The AG remains selected even if the PCA is in NAV mode. 10. Unconfirmed. Selecting CAN or MAGIC does not change radar status. Selecting SPecial Modes Forward or AFT sets the radar on EMIT if the switch is in SIL. 12. Confirmed. Final PCA/HUD updates after review by our friends at the AdA: 1. PCA and HUD are now independent of each other. So HUD mode does not depend on selected weapon nor master arm position. 2. Master Arm now just enables weapons release/fire. Setting to SAFE or ARM does nothing else. When the switch is in the ARM position the weapon code will stop blinking in the HUD. 3. HUD automatically enters into AA mode when: Selecting CAN or MAGIC by using the HOTAS button, or by selecting POL or Super 530D on the PCA. 4. MAG button on the PCA does NOT select Magic. It performs other functions: enabling the missile and starting MAV search. 5. Selecting an AG weapon will NOT set the HUD and aircraft systems to AG ATTACK mode. Only the PCA will enter into AG mode. 6. To set the HUD, actually the entire aircraft systems, into AG ATTACK mode the pilot must click the PIP HOTAS switch forward (it is the same switch that sets the Special Modes when in AA mode). NOTE: An AG weapon must be selected for the aircraft to enter AG ATTACK mode, otherwise AA Special modes will be invoked. 7. With the HUD/Aircraft in AG ATTACK mode, clicking the PIP HOTAS switch back, will save the AG weapon selection and release parameters, return the HUD/aircraft to NAV mode. The PCA will also enter NAV mode. The AG weapon remains selected. 8. CAN and MAGIC can only be selected via HOTAS. 9. Trying to select a weapon on the PCA when the system is in CAN or MAGIC modes is not possible. 10. Selecting AA Special modes will activate the radar, even if the switch is in the SIL position. Note: Selecting an AA weapon (CAN, MAGIC or S530D) will not change the radar status.

Yes, that number is the altitude above the ground for which the cue must be aware of. The PUC does not appear at the selected altitude. It appears 9 seconds before you reach that altitude. It appears below the VVM and starts climbing towards it as you approach the selected altitude. When it reaches the VVM you are at the selected altitude. The PUC is used so you can plan your pull up and not go below the selected altitude. In other words, you must start climbing when you see the PUC move.

Yes, the fix is included in today's hotfix.

The PULL UP warning is not controlled by PUC, which is the PULL UP CUE when dive bombing, but with the GPWS option. Click the ODU button that shows GPWS until the semicolon is not visible. Be warned that the GPWS will be disabled for 20 minutes only, it will automatically enable itself after the timer has expired.

The bug is being fixed.

It tries to load a markpoint, but there are none when the mission starts.

Folks, there is a bug in the INS when starting cold and dark. After aligning, the INS can get stuck in an invalid steerpoint and cannot be moved from it. The bug is fixed on development and will be available on next release, but until then it is advised that you start with the aircraft HOT ON THE RAMP or ON THE RUNWAY.

When the radar is in low altitude mode, the search antenna stops working. Only the tracking antenna work and that does not display anything on the scope. The radar basically turns itself into a gunnery radar. BY the way, setting the radar back to STANDBY for about 3 minutes will cool it down so it can operate again.

Bug fixes in the first post

Yes, clicking the switch from FAR to NEAR and vice versa toggles between those two frequencies.

Folks. several bug threads have been merged, not deleted, because they refer to the same problem/bug. Case in point the several keybind, missing animation bug threads.

Hi, Please send the DCS.log file. You can find it at Saved GAmes/<DCS version>/Logs

The ARK-5 does not have presets. The frequencies values in the ME are used to pre-tune the ARK-5 to those values. If you move the tuning handle, those frequencies are lost. I set that option as a help for quickly using the ARK-5, specially when a mission starts in the air and you have to land on an airport. So instead of looking for the airport's beacons frequencies, the ARK-5 is already tuned to them. But, if you tune to another frequency, those ME frequencies are lost.

I am still looking for a way to optimize it. I have ideas for other radar equipped aircrafts to use this function as well.

Just the K-13A (R-3S)

The problem is finding reliable sounds that are close to how the original engines sounded. It is a very old aircraft and there are almost no films of it, except for some propaganda that have loud background music.

It should be available on next Stable update.

Folks, the engine behaves as per the power curves it has.