Tiramisu

When I switch my seat from the commander seat to the co-pilot seat, then I often have the problem that the Petrovich AI messes up the flight. Even when I am requesting control quickly, it can mess up the flight stability for a short time or even lead to disastrous results, because the AI does not smoothly take over the controls. The second problem is that my axis are not updated when I switch to the front seat, which can e.g. lead to an idle collective position for a brief time (despite of my options settings to always update my current axis position) until I change my collective to update it. So I suggest to simply grant the player control for the flight controls immediately after switching to the front seat, and properly update the axis positions to ensure a smooth transition during flight in single player. The player can still decide to grant AI control afterwards. Thanks.

I was only flying in single player, but I hope the investigation of the bug you are referring to will fix my problem as well. If you need more details about my setup, then please let me know.

I do not know much about the Apache, but the Mi-24 turned out to be much more fun than I expected. I fear that the Apache is too much computerized for this kind of fun feeling. Maybe I am missing something, but isn't it going to be rather like an American version of the Ka-50? I am just trying to figure out for which kind of virtual pilots the Apache is a good choice.

The reason might be the account verification. I have a similar issue, because I have many modules and the more modules you have the more time it can take for your internet connection to verify that you are the rightful owner. It can be quite annoying, but it does not seem a very high priority to fix this issue. For DCS you need enough patience.

On certain occasions the modifier buttons on my controller are ignored by DCS, i.e. when i press a modifier + button, then only the unmodified button is registered. I do not know what is triggering this bug, but I have noticed this since I increased the amount of my modifier buttons from two to four. When this bug occurs, the modifier buttons are not registered in the the control options as well. However, when I open the window where you define modifiers and then press ok, then the modifiers are registered again. So it is definitely a DCS bug and no problem with my controller.

I have found a way to bind the gun deblock button. You can either download my attachment and overwrite your game files with it or edit the files yourself. If you want to edit it, go to your install directory and open the file ...\DCSWorld\Mods\aircraft\L-39C\Input\L-39ZA\joystick\default.lua with an editor. There you can find a lot of entries between two curly brackets which looks like this: join(res.keyCommands,{ ... }) Between the brackets add this line: {category = {_('Center Pedestal'), _('Armament Control Panel'), _('Only Front Cockpit')}, name = _('Deblock Guns'), cockpit_device_id = devices.WEAPON_SYSTEM, down = 3077, up = 3077, value_down = 1, value_up = 0 }, If you want to add this for keyboard bindings as well, you need to do the same for the file ...\DCSWorld\Mods\aircraft\L-39C\Input\L-39ZA\keyboard\default.lua Obviously, this only makes sense for the L-39ZA, because the L-39C has no cannons. Also note that setting the arms-switch for the cannons back to off and then on again, will automatically re-enable the gunblock limitation. Credits: I have learned this how-to from https://www.reddit.com/r/hoggit/comments/7wli5i/how_to_add_extra_bindings_for_clickable_cockpit/ Input Modifications v1.0.zip

I would rather like to see a completely new map with narrow map boundaries stretching from Northern Israel to Yemen with the Western boundary reaching to El Alamein or beyond.

I also agree, and it is not just the mountains. Flat areas also need more shadows, because even small bumps create those contrasts that are missing in the ground textures. Therefore, those ground textures look quite artificial. Are the devs working on this? Or is there any mod? Mustangs texture mods seem to be abandoned.

It looks like your engines only take damage, if your cannon bursts are too long with the gun deblock mode. Very short burst are ok, so there should be no limit there. But I think there is no override button for launching AA-missiles at lower speeds. There are also machine guns, but they are very weak. Even unguided rockets are better in dogfights than MGs.

In general I am also interested, but the SFM of the AI may be a problem. I have tried the first mission of that Yak-52 campaign and noticed very soon that the AI can accelerate much better than me and make Loopings at speeds that were too low for my own Yak-52 causing me to stall. So please bear that in mind.

Here it is. http://cdn.akamai.steamstatic.com/steam/apps/316965/manuals/DCS_L-39C_Flight_Manual_EN.pdf?t=1455639851 From page 168 onwards.

Or maybe not. They seemed to RTB at first, but it now I think the AI is just having problems to stay in close formation during aerobatics. A simple turn will make them fall out of the formation by several miles.

Whenever an aerobatic maneuver for an AI group starts, the wingmen will leave the flight lead and return to base. Only the flight lead AI will continue its flight and do the aerobatic maneuvers.

I am using the default cockpit and the native language in the options. Stil I get imperial units and not metric ones. This is really bad, because many instructions are with respect to metric units. I think it would be even worth a bug report, because this does not make much sense. Unfortunately the L-39 does not get much attention from the devs any more.

Aerobatics can be a good starting point for learning how to fly an aircraft well. So it is quite sad that the L-39 does not have any AoA-gauge. I mean the manual of the Mig-21 has some very interesting descriptions about how to use the AoA-gauge for aerobatics, but in the L-39 we do not have anything similar. I find it a bit hard to fly perfectly without any AoA. At least it has a G-meter, but it is located quite low in the cockpit. Note that there is a manual from ED for the L-39C that can be found in the internet, which contains more information about aerobatics than the standard manual in the installation files.

Thanks, a repair does not seem to help, although I can try it again to be sure. I have not done a full reinstall yet, but I guess that would be my last option, once I get a better SSD. For now I will simply avoid the F-14 and just hope that the performance gets better in the following updates.

About one year ago the loading times for the F-14 were acceptable and after the first few reloads it all went quite fast. Now I came back to this module and the loading times have significantly increased to about 5 minutes or more despite DCS being installed on a SSD. Since I am often reloading missions, the F-14 has become almost unplayable for me. Other modules (even the Mi-24 Hind) are loading much quicker than the F-14. Also my RAM usage is increasing to almost 28 out of 32 GB during loading. It seems to me like a bug. The task manager says that my SSD is at full working load, while my CPU and my graphics cards are not working very hard, so the reading times are the bottleneck here. My specs: AMD Ryzen 5 GTX 1050 Ti 32 GB RAM SSD-type: WDS100T2B0A-00SM Edit: "Wait for pooled task 2" is often the phase when it takes a lot of time to load. For other modules this is not the case.

The link in the first post is not working for me.

When you have enabled the "Hide Control Stick" option under Gameplay, then the pilot's arm in the L-39ZA will be stretched to infinity and have a weird rotating animation. Even when you hide the pilot's body this annoying glitch will still remain for the the arm of the pilot in the backseat and you will be able to see it in the front seat. By deselecting the "Hide Control Stick" this bug dissappears, but I do not like it since this is a global option. Unfortunately, there is no keybinding for the L-39 for hiding the joystick. Btw. the same bug does not happen in the L-39C.

I have to cancel my MP session today as well. Very frustrating.

I am getting these errors after buying the Fw-190A and Bf-109, which I tried for free a few months ago: I am not able to play with my modules any more. What should I do now?

DCS does not return errors any more for some strange reasons (or only on special occasions). So your code might be faulty even when you have no errors in DCS. First of all make sure that you define a unit table correctly. E.g. pUnit = Group.getByName( "Aircraft Group #001" ):getUnit( 1 )or pUnit = Unit.getByName( "Test Unit #001" )In addition you should write pUnit:getFuel()instead of Unit.getFuel("test")

Thank you, c0ff! I appreciate your efforts.

It takes about 2.5 minutes for the account verification and the loading time. I think the time when the small window with the DCS logo appears is only used for the account verification itself, because the loading screen appears much later and takes less time due to my SSD. See for yourself: In the past DCS launched much quicker for me, but I believe the more modules I own the longer it takes for the account verification. By now I own almost all aircraft. So maybe this issue could be solved by checking only the account itself instead of each module separately. Sorry if this was a bit ot.

Unfortunately, this does not work, because DCS does not recognize any audio device that has been turned on after launching DCS. In my case my headphones "Bose QC35 II" is not even listed the audio options. So I cannot select it manually: Only when I turn them on before launching DCS, my headphones get recognized: I know you guys have more important issues to solve, but since this problem has been newly introduced to DCS-beta just a few months ago, I hope you can fix this easily. Preferably, I would like to turn on my headphones after the DCS launch, because it takes a very long time until DCS has verified my account each time when loading the sim.