-Martin-

1. On the L-39 special tab it is possible to dismount the gun-camera from L-39ZA (keeping the gun-sight, naturally). This works perfectly in SP, but in MP this setting is apparently overridden by the server, or it is by default mounted if the server does not have the L-39 module installed. Would it be possible to make the client setting priority so I can enjoy a dismounted gun-camera also in MP? 2. If an appropriate option is selected, the gun-camera exports firing solutions as pictures into tracks. In the folder L-39C/Cokpit/GunCamera there are several files that define how the gun-camera behaves. Would anyone have any idea how to mod them so that the gun-camera saves the pictures it takes into a file? I would love to review my firing solutions without looking at tracks. Best Wishes

Dear Alpenwolf, I am not sure if it will work, but if on the PC that is running this server someone could on the L-39 special tab in the Gun Camera drop out menu select Dismounted, that could do the trick.

I was wondering if we could have L-39ZA on this server without the gun camera, as it serves no purpose and merely obstructs the view. I have the option selected on my L-39 special tab, but it affects only SP not MP. I assume that to the get a dismounted gun camera the server needs to select this option. Would you consider it?

The biggest issue for me personally is that there are no AI bombers to intercept in my Mig-15. If there is a server where we could do such missions even if there are no other players then it could be easier to attract more people to fly.

Dear Alpenwolf, I love this server, what a great job on creating the missions. I was wondering if you could consider adding high altitude AI bombers, in particular on the blue side. I would love to take my Mig-21 to intercept them. I believe that adding an additional task beside bombing will attract more players even if the server is empty which in turn will attract those looking for dogfighting. I imagine that the bombers would spawn at a base, fly to drop bombs on Suchumi, Maykop, etc. (depending on the mission) and fly back. Martin

Dear All, I suspect that there is a problem with my motherboard so I am thinking of replacing it and upgrading my PC. I was wondering if you could state your opinion whether the following upgrade will be good for the DCS, in particular considering VR. My current build: MSI Z97 Gaming 5 Motherboard, i5-4690 3.5GHz CPU, 8GB DDR3 1600MHz RAM (I had 16GB but the problem I mentioned), MSI GTX1060 6GB GPU, SSD, Win 8.1. What I plan to get: MSI H270 Gaming M3 Motherboard, i5-7600k 3.8 GHz CPU, 16GB DDR4 2400MHz RAM. I will keep the rest of my previous build, in particular the GPU and Win 8.1, to save some money, unless you confirm that Win 10 is much better for VR as rumored. I am interested to know if, in your opinion, I get significantly better performance. Otherwise I might want to fix my current system.

As I am apparently one of only few people who use Steam I feel obliged to come forward and express that I have only good experience using the Steam version. The speed of download is also excellent and if you are subscribed to the beta branch there is only a few days of delay on each update. On the other hand, I understand why those who are interested in a module that is not available on Steam would prefer to migrate to the standalone version.

Dear All, I found out what was wrong, you will surely facepalm after reading this: I was flying the helicopter all the time with the throttle set to idle :doh:. Once I moved it to auto the voice warning appeared. Unbelievable that it could fly at all. Thank you for all your responses.

Thank you for your response. The LWR works (it lights up), and I think I switched the Ekran on too. I have this issue even if I begin in an already flying chopper straight from a mission editor.

Dear All, I just started with the Ka-50 and I am puzzled why I do not get any voice warning (Betty) once LWR goes off. I have seen videos where people were getting this warning, either in English or Russian, but I do not get it. I am missing something? I am supposed to turn this feature on by a switch? Thank you for any response and sorry for what might seem to you as a trivial question.

Dear All, Thank you so much for your detailed answers. I will wait for the next sale to get the Ka-50 module.

Dear All Owners of Ka-50, I am considering whether to buy Ka-50 but I have the following concerns and I hope that you would be so kind as to help me to clarify them: 1. I really cannot spot a single target using Schval in Su-25T. On the other hand, in Gazelle spotting targets is very easy, probably also due to ability to adjust contrast and brightness. I understand that in Ka-50 this features, unlike in Su-25T, are available. Nevertheless, does it help or is Schval as bad as in Su-25T? 2. I enjoy flying Gazelle on the 104th Phoenix Dedicated Server as the RWR warns me against any long range threat and I can blame only myself if an ATGM or an IR SAM shot me down when I do not scout well. Naturally, I am concerned that flying Ka-50 in this environment will be either frustrating or boring. Is this justified? Do you find yourself either shot down without warning as you approach the target area or, given you survived, the game turns to a boring distance sniping from a single spot? 3. Are there any IR SAMs that use also laser ranging or is the LWR useful only against ATGMs? Thank you and best wishes.

Hello, I had exactly the same landing problem. I have not figured the correct procedure yet, but it helps if you level the plane over the runway from a usual >300km/h speed, do not reduce trust or change AOA, let the plane gently sit down and, this is crucial, just as the main gear touch the runway or even a split second before deploy your chute to avoid bouncing back up. Hope this helps.

On the center panel (the panel where you for example turn on your gunsight) there is a button that deblocks your gun in all situations. Unfortunately, you cannot map it to your HOTAS so employing it during dogfight is difficult.

Dear Bersagliere, I think that I can give you a competent assessment of this plane. I fly it a lot in MP and it is my second the most favourite plane. In MP L-39 is primarily an F-5 hunter in the ACG server. It has a better turn rate, no smoke exhaust visible from kilometres as other planes and excellent low speed handling so flying it low in circles will give you some kills against F-5s trying to do circles with you. In my experience way more kills than Mig-21. In my eyes Mig-21 is as a dog-fighter clearly inferior to F-5. On the other hand, I would avoid fighting A-10 in L-39. A-10 has possibly the same turn rate but it is faster and one missile is not enough to take it down. I have never managed to take A-10 down, twice I got a damage but they survived. On the other hand, I was shot down by A-10 at least 3 times. About helicopter hunting, I do not think L-39 is a plane for that. They are hard to visually spot and track by an IR missile seeker, so something with EOS or radar such as Su-27 would be much more effective. Furthermore, L-39ZA's gun is not the best for air combat. Normally, you cannot use it even in medium AOA turns. It is possible to override this, but as the button doing this cannot be mapped to your HOTAS, setting your gun ready in a stressful fight is difficult. There is however a trick you can use to mitigate this: You set your gun ready before entering a combat but do not charge it. Once you need your gun you simply charge it and it is ready to go. Thanks to this I have killed even one F-5 with guns. L-39 is furthermore a joy to fly even in SP. Navigation flights are great: There is one training mission where your outside vision is obscured by a hood so you must fly only by instruments. Or you can set up a night flight or bad whether conditions and try to land using the RSBN system. The ARC system is better and actually practically usable in L-39 in comparison to Mig-21. L-39 has also great failure and structural damage model. You can lose your wings by pulling too hard, you can get engine fire and put it down, you can do emergency landing on a road with actual need for emergency hydraulics system to operate emergency breaks if you use all the main hydraulics pressure on airbrakes. It is not like Mig-21 where you usually always explode. So, looking at your planes, I would say go for it. You already have Hawk, which is supposed to be a similar plane, but has the plane actually delivered the same fidelity as L-39? (Just asking, I do not have it.) Also, L-39 has the same engine simulation as A-10C. On the other hand, to be fair, if I consider bundle (Mig-21 + L-39) vs (F-5) I would say (F-5) was better as you would get something in between Mig-21 and L-39 in a single plane. But you already have Mig-21. So a more natural choice would be L-39 in my opinion. You use Mig-21 as an interceptor as it was designed and L-39 to kill F-5s and enjoy an excellent plane modelling. As I do. Martin

Thank you for confirming this bug and supporting my comment. I find the explanation below by Pocket Sized plausible, perhaps there is something about the L-39 that makes the issue more prominent in this plane. If this is really the mechanism then I would like to note that, based on my experience, such a `dead' trait must also carry to in-cockpit sounds and at least to some of the plane's electric systems. Furthermore, I did some testing where I lost both wings completely but the bug was not triggered, at least not immediately. Obviously, I could not fly for long :). Once again thank you all for your input.

Hi Grunf, I have the same problem as you have described above. Have you managed to get it working?

Dear All, I am experiencing the following bug from the time I picked L-39C in the early access nearly a year ago. I thought that this bug, given how old it is, was widely known. But from my recent correspondence on this forum I realised that this might not be the case. I was wondering if anyone could reproduce it. Bug: After the pilot dies in a way that the aircraft is not completely destroyed the following will happen: 1. In-cockpit view is available; aileron, elevator and rudder can still be controlled, the canopy can be jettisoned and the pilot can eject. 2. All electric systems are turned off, most of the instruments do not work (stop-watch works), all in-cockpit sounds disappear. DCS version: All 1.5.X versions, currently 1.5.5, tested only on Steam. Reproducible: Yes, easily, for both L-39C and L-39ZA, and during both single and multi player. How I can reproduce it on my system: Method 1: The easiest way is to set engine fire in the editor, wait for 2 minutes (do not take any actions to put it off), and there you go. Method 2: Damage the plane during take off by violently pulling up so as to damage the tail. Resulting engine fire will promptly lead to the bug manifestation. Method 3: Take the plane to combat. Either dive onto some APCs or let F-5s on the ACG multiplier server to fire at you. Sooner or later the bug will appear. Many thanks for your feedback.

Dear George, I have noticed that your bug list does not include the bug that I am experiencing very often; once the pilot dies I can still control the plane. I've already talked about this in another thread, nevertheless I have not received any feedback on it. I was wondering if there was anyone else who was experiencing it. Maybe you recognise it as a `disappearing sound' bug, as the in-cockpit sound really disappears when this happens. But it is not the fact that sound disappears which is the problem. As at that point the pilot is already dead, we should not have the in-cockpit view and be in control of the plane at all.

Hi IronJockel, Thank you so much for adjusting the ping limiter. This is my favourite server too, really the only place where I can fly L-39 in a meaningful way. But my ping is usually around 260-280 since, unfortunately, I live far away from Germany.

Dear Typhoon, I have tried to replicate the problem as you have described it but without success. I have even tried to deplete my battery by turning all the electric devices on, turning the emergency generator off, and repeatedly switching APU on and off, but I have never seen the APU light to flash. Furthermore, subsequently I was able to start the engine. I presume that you have tried the opposite actions to remedy your voltage issue too without effect. On the other hand, I once managed to get into a situation when I could not restart the engine at all, albeit it did not appear to be an APU related problem. Sorry for not being very helpful. I tested both hot and cold start L-39ZA and hot start L-39C in DCS 1.5.5 on Steam. Martin

Thank you for your response. Of course, I did not expect that one would be able to dismount the gunsight in reality on L-39ZA, and we are not able to do that in DCS. But if the same is true for the guncamera, I was wondering why the option to have it removed had been implemented in DCS. I personally find this option great as explained above, and I hope it will stay. In any case, observing that L-39C is too unaffected by my setting in MP, I came to personal conclusion that whether or not the guncamera is present on L-39ZA depends on the server settings. I will consider positing my query directly to server administrators, should it be indeed possible and appropriate. All the Best

Thank you for your answer. I was actually talking above only about L-39ZA and yes, from my experience, the gun camera cannot be dismounted in MP on this plane. I considered it a bug since I was able to dismount it in SP. Your response prompted me to test L-39C in MP. Oddly, regardless of my setting on two servers I tested, not only the gun camera was absent but the whole gunsight. So now it seems to me that either this setting is determined solely by server administrators or L-39C in MP is always without the gunsight and L-39ZA has both the gunsight and the gun camera, regardless on what I set in DCS. In either case, I hope that eventually I will be able to fly L-39ZA in MP without the gun camera as I can do in SP.

Dear Redglyph, I tried the following to replicate the issue as you have described it, but unfortunately with no success. (DCS 1.5.5 on Steam, SP) 1. Engine fire set in the editor -> All sounds off but the log said that the pilot had died. 2. Engine fire set in the editor -> All sounds off but the log said that the pilot had died. 3. Engine fire set in the editor -> Shutting the fuel valve and applying the fire extinguisher -> Emergency landing, sounds on, the pilot was alive. 4. Scratching the tail during take off -> Fire -> All sounds off but the log said that the pilot had died. 5. Scratching the tail during take off -> Fire -> Shutting the fuel valve and applying the fire extinguisher -> All sounds off but the log said that the pilot had died. 6. Being fired upon by APC-s -> Some system failed, sounds on, the pilot was alive. 7. Being fired upon by APC-s -> Fire -> All sounds off but the log said that the pilot had died. It is interesting that after my pilot died I still could eject and sounds returned. I could even walk around my burning plane on the ground. It would be even more interesting to know if you could replicate the issue that I have. Best Wishes

Dear Yuya and Redglyph, About Issue 1, my experience is that all sounds disappear only when the pilot dies. So the problem on my side is not the disappearing sound, but the fact that I am still in control of the plane after my pilot died. My personal guess is that you might be experiencing the same thing. To verify this, check your event log in SP and messages in MP. Bug Report: All 1.5.X released on Steam, both L-39C/ZA since the early access of L-39C, reproducible every time. Best Wishes