AJaromir

Sorry to wake up this topic. Just IMO there is one important thing to fix in the SU-33 manual. Those take-off weights are quite difficult to find in the DCS:SU-27 manual because those are written only in the "SU-33 HISTORY" chapter. It is not possible to find them in any charts in manual or in any guide. BTW the SU-33 manual does not contain any "flight school" chapter which would be important for players those did buy the SU-33 and have no experience how to take-off/land with it from carrier and generally from/to normal airfield e.t.c...

Good day. In the manual is not written if this valve is opened in pulled or pushed position. After some tests I've found the pushed position is opened and pulled position is closed. Also with that I've found the standard commands work opposite way. That means the command "Fuel valve CLOSE - RWin+F" Opens the fuel fire shutoff valve and command "Fuel valve Open - RAlt+F" closes the fuel fire shutoff valve.

Hi. I know, this one probably has low priority. Just wanted to know how's going....

Just a note from manual: So maybe the reducing RPM is essential. IMO you can not judge the FM when noone of us did fly this machine IRL. And because all other aircrafts do..... Mind this is Jakolev Jak-52 and not the Zlín Z-50. So, only the real Jak-52 pilot konws. Not the chairforce pilots.

The engine RPM depends on the load. (See the AplhaOneSix comment.) Mind the engine has independent drive turbine. Than means it is not connected with compressor. The compressor is driven by its own turbine. So, the engine core turbine that drives compressor is changing its speed to keep the rotor turbine in steady RPM. Check this video:

Just to make things clear. This is what I mean via mission editor payload menu: And this is what I mean via ground crew comms rearm menu:

Here are the tracks: VIA EDITOR.trk VIA RADIO.trk

This bug is in DCS for many years. I've figured out it depends whenever I choose payload in the mission editor or via ground crew radio comms menu. When I choose the payload via ground crew comms menu, the KMGU-MER mod is not working properly. More about that in the video. Manual about this says: СЕРИЯ КМГУ-МБД (SSC-MJM SERIES) – a special release mode for the KMGU submunitions dispenser and multiple ejection rack (MER). KMGU submunitions are dispensed at 2-second intervals, MER munitions are released 0.3 seconds apart, according to the total quantity specified by the salvo size switch.

Tascam DR-05, version 2. I own it. Really good toy, cheap and very accurate.

So, did you download game ready drivers or creator ready drivers?

Bump. The issue is most probably still there. - I have to ask for repair aircraft to fix this problem. This seems correct. But - with the "unlimited ammo" gameplay option simultaneously with the "immortal" gameplay option, the range is still shorting and the dispersion is still increasing. Also - It seems still does not matter on burst lenght or cooldown time.

What I noticed and made me happy, is the much lower "miss" tolerance. You have to be really accurate to get the fuel. At the other aircrafts, the hose just "teleports" to position, but not here :)

Please, can you or someone post link to download this file from Stable version? Thank you.

O.k. In the newest Beta the bug is still there.

Great news! Thank You for Your efforts! Right now the new update is out. So first I will check if the issue was fixed before trying this.

First of all I have bad experiences with upgrade from W7 to W10, making clean instalation is much better. Also before instalation of W10 make sure the manufacturer of your mainboard provides drivers for Windows 10. If not, it is better to stay with Windows 7. Download all drivers to any removable drive. Download the W10 instalator via official microsoft tool to any 8GB USB FLASH https://www.microsoft.com/software-download/windows10 Most Intel chipset boards uses their own special HCI drivers. Those are IRST drivers. It is good to unpack the driver pack somewhere into W10 instalation on USB FLASH. Make sure you have the latest version of BIOS firmware. If available, in BIOS (UEFI), set the UEFI mode with Secure Boot mode on and Fastboot mode on. Then start with instalation of Windows 10, the best is to install to clean drive with GPT instead of MBR. To do that, you have to clear all data from drive. In windows instalator, press shift+F10, Write: diskpart press enter Write: list disk enter check the drive number you want install W10 in Write select disk # - substitute "#" by drive number number enter write clean enter Now all data from HDD are wiped. write exit enter again write exit enter Continue with instalation. If you did the step with unpacking IRST drivers: When selecting the W10 instalation drive, select "load driver" and find the HCI driver located in the IRST driver package for your 64-bit system. Continue by common steps of instalation. Quite important thing: While the OS is installing, unplug your ethernet cable. W10 is automatically downloading all drivers once connected to internet. My experience is to not let OS download and install its own drivers, drivers provided by manufacturer are much better. After instalation of all drivers, conect your PC to internet. DCS usually wants to instal .net framework 3.5 You can install it manually via "control panel\All Control Pane lItems\Programs and features\turn windows features on or off"

This does not work because latest beta also had messed some input controls settings.

Please, IMO one thread is enough: https://forums.eagle.ru/showthread.php?t=233656

IMO this does not matter on Mig-19p. Do not make 20 threads about the same issue. https://forums.eagle.ru/showthread.php?t=233656

In my case, I still did not find any solution. Right now I don't have enough time for testing.

Because you are doing it wrong. Evereything you put in game core folder, will be owerwritten with every update. Open Notepad++ Write: options.graphics.maxfps = 60 use file encoding UTF-8 without BOM Save the file in "'%userprofile%\saved games\dcs(or dcs.openbeta)\config\autoexec.cfg

Thank you all for answer. In my case it happens most often after mapping the analogue brake axis.

Tried to make rollback to Stable - no issue there, only the assigns are messed.

I don't own the Mig-19. This solution did not help, just like in your case. Still the same issue. This is not even workaround because this is exactly what it does. No matter if I click the axis assign button or select the axis commands category. If you have 3 controllers with total 11 axis (like I do: Stick - 3 axis; Throttle 5 axis; rudder pedals - 3 axis, eventually TrackIR - 6 axis - so total 17 axis), you won't like it. The issue is very random. Sometimes it looks like everything is o.k. Sometimes it stop woirking after setting firs axis, sometims after 4th axis.

Have some news. Not every addon do that. E.G. SU-25T - no problem. L-39 - problem F-5E - problem Will update the list