flyco

OK, I have reviewed my Track. It didn't take long, since as soon as the ac started taxying, it went in a small circle and taxied over the side of the Carrier. It was MP. Oh well! I'll assume I was hit by a clear-weather lighting bolt! Perhaps the god's were angry that I had 'Touched their face'. And, of course, acting on the earlier advice, next time I shut down I will start off by closing down the Left engine!

I do have a track replay, but it is at the end of a 90 minute recording. I will try and see if it is recorded correctly all the way to the end. Is there any way to edit out sections of the replay, so as just to leave the relevant part? Unfortunately TacView doesn’t show it.

I have just flown an hour and a quarter GH flight on the F-18 (no weapons). On shut down on the pan after landing, the aircraft blew-up when I shut down the RH engine. Anyone any ideas?

Since today's update, the STEP no longer shows on my Stores page, when entering PP data for 2 JSOWs, one Station 2 and one on Station 8. Is it me that is screwing up or is anyone else finding the same thing? Edit: this is on a previous mission - could that be the reason? Do I need to resave the mission?

When you say, 'move the throttles out of idle briefly' do you mean, with Warthog Throttles, lift them over the gate to stop and than back to idle? That does sound a questionable procedure.

DCS Crashes on Touchdown I am getting recurrent crashes on touchdown - the system freezes for a couple of seconds and then announces a crash. I have attached a copy of the crash log from the most recent. It only appears to happen on Multiplayer missions, exceeding an hour, and always exactly at touchdown. Fellow players report my aircraft leaping into the air, and freezing at this point. I am also experiencing regular incidents of aircraft going through the runway, although I sense that this is not the same problem - indeed it happens every time I try to start a P-51, and very often with other prop aircraft. In addition, in this latter case the aircraft continues to fly and I can re-emerge from the runway and repeat this procedure repeatedly. I suspect this to be a 'red herring', but felt I should include it for completeness. To the best of my recollection, the crash on touchdown has always happened after a protracted flight in the A-10C. However, that may be because this is the only aircraft I fly for over an hour and a half. From examination of the log, I suspect the crash coincides with the Access Violation message which appears in the log, and which is reproduced below with a few surrounding lines. 2019-08-06 21:01:03.416 INFO DX11BACKEND: Unloaded 33 mb of textures. 2019-08-06 21:01:55.940 INFO EDCORE: try to write dump information 2019-08-06 21:01:55.944 INFO EDCORE: # -------------- 20190806-210156 -------------- 2019-08-06 21:01:55.947 INFO EDCORE: DCS/2.5.5.34108 (x86_64; Windows NT 10.0.17763) 2019-08-06 21:01:55.951 INFO EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Weather.dll 2019-08-06 21:01:55.955 INFO EDCORE: # C0000005 ACCESS_VIOLATION at A70C1164 00:00000000 2019-08-06 21:01:55.961 INFO EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Alan' 2019-08-06 21:01:55.965 INFO EDCORE: OS-Version: 10.0.17763 () 0x300-0x1 I use Helios, with the main electronic displays exported - however, I have done this for some years now without any problems. I understand that I should perhaps try a similar sortie without Helios, but am so reliant on it that I am reluctant to expose myself (and my fellow fliers), to the considerable inconvenience. Does anyone have any suggestions? I will confess that since it always appears to occur on long MP missions, and only at landing, I could continue with it and just make sure that I am the last to land - the main problem then would be that I would never get an uncorrupted TacView record.

Mule, yes it is labelled Second Detent in the controls list. However, that is just a label. You can set it to first pressure, which is what I did.

I have solved some of my problems with the Gun Trigger and toggling LTD on/off. I had both first and second pressures enabled. With just pressure 1 enabled, the LTD toggles on and off with a single press - there is no need to hold the trigger throughout the flight of the Maverick. However, I am still getting Mavericks missing the target with the laser on and the solid square showing in the centre of the Mav Graticule. There also appears to be no input assignment for any of the three Sensor Panels inputs - presumably these will come in time.

I am not sure whether it is just my stick or a bug, but when I want to lase, and press and hold the trigger fully on, the LTD stops lasing after about 1 second. If I just hold the trigger half-way (i.e first press), this doesn't seem to happen. Is anyone lese experiencing something, similar or is it my Warthog Stick that has a fault?

I have just made the attached track file, which shows the submerging P-51. P-51D - Falling through ground.trk

I often get this with both A-10C and F-18C, particularly on the longer multiplayer missions. If I apply power once I am 'below ground level' I can climb out, overshoot and do a further approach - with the same result. I do not, and never have had, the A-4 installed, so that cannot be the sole trigger. I do have a number of add-on aircraft installed through Saved Games. I also have Helios installed and a number of minor mods to allow export of displays - these are installed in the main game folder in a specific My-Mods folder, installed and uninstalled as required using JGGME. Finally, in single player, I find the P-51 always falls through on initial start, or landing, and my other WW2 ac usually do the same (Spit, 190D and 109G). I have submitted tracks of the P-51D, which is the most regular culprit, but have had no response to date.

I am pretty sure that the presence of an A-4, has no significance in this bug. I have had it happen on occasions with F-18 and A-10, and always with P-51, and none of these missions have the A-4 included. I have not been able to identify any common cause, but it is a pita. With the F-18 and A-10 it seems to happen after a longish sortie. Hence I have not been able to get a track for these, but I did submit tracks with the P-51 and T-51, where it always happens. I do have a TrackView of it happening to the F-18, in which I apply the power and reappear out of the runway on the overshoot!

I have been releasing them late, less than 6 miles. However, I am concerned at what I suspect is the 'minimum range' circle. However, I haven't had any overshoots yet.

In one of my missions, I have been dropping both GBU38 JDAM and the JSOW, against Tunguska perched on the side of hills. The only feasible approach path is across the lines of hills. All the weapons seem to trade height for speed early on and as a result make their final approach to the target at a fairly shallow angle. Because of this it is very common for one of the intervening ridges to ‘take out’ the weapons short of the target. This can be overcome to a degree by making a very late release, which to a large extent invalidates the standoff advantage of using the JSOW. Anyone any suggestions or comments?

I run TacView on my Non-Dedicated Server. That is, one that does not use the WEB GUI, but instead operates from the NEW SERVER option at the foot of the main DCS entry page. I, like many others, have found it impossible to get the new DCS Dedicated Server to operate. My question is: is it possible to eliminate or reduce the 10 min delay in data download? I suspect, from browsing the Forum, that it isn’t, but it would be helpful to have a definitive answer.

I would strongly endorse the A-10 as an excellent aircraft to learn on. I have been flying it for over 5 years, and find it robust and forgiving. Nevertheless, it is a capable aircraft that can carry out just about any role - except possibly air defence, although I have taken out the occasional unwary AD fighter with it. If you want to take it further, it is also a complex aircraft with a wide range of weapons available to it It is definitely a ‘gentleman’s aircraft’. As for age, I become 76 next week and am still coping.

Two tracks attached. The first a cold start in a T-51, the second a landing(?) in a T-51. You will see that it flies quite well underground! A new stealth fighter perhaps? I fly with a single UHD monitor and two subsidiary; one a Touchscreen for Helios, and one a small Lilliput for kneepad. For these shots Helios was not in use and all MODS were removed. The Spitfire is fine, but, having seen other comments, I have tried both the Fw-19D and the Bf-09, and both also sink through the concrete. The sea is visible below and eventually they fall into it. Thanks for looking at this. T-51 Cold Start at Krymsk -Sinking.trk P-51 Landing -Sinking.trk

I am looking for advice from someone who knows Helios (1.3 and 1.4) well. I have used Helios (1.3.190.448) for some years, and over that time have built up displays for most of my DCS aircraft, many of them modified versions of other's efforts (thanks a million Capt Zeen). I am considering whether I should switch to the latest version of Helios, but am reluctant to do so from fear of screwing up all my current profiles. (Needless to say, I did not document the changes I have made to my proiles over the years.) May I ask for views on whether the change over from 1.3 to 1.4 Helios can be effected reasonably simply, and whether existing profiles can be used in their original form. I have reached the stage of life where I am forgetting more than I can remember, and am reluctant to risk having to fly without Helios or wade through complex modifications. Thank you, in advance.

I have not flown the P-51 or T-51 for some months, and previously they were fine. However, I now find in the Open Beta version that both aircraft sink into the ground - If I start on the ground they do it as soon as I enter the simulation - If I start in the air they do it immediately upon landing. They work normally in the Stable version. Can anyone suggest a reason for this, and a cure. I have tried a repair with no effect. I have also disabled the P-51 in the 'Installed' page, restarted, and tried again - with the same result. I have also temporarily renamed the 'Saved Games' folder, with again no improvement. So far as I can tell the files are the same in both Stable and Open Beta versions.

Thanks for the replies. In answer to Rob’s question it was in SP, and only in the Open Beta version, Stable was fine. I was not aware that it was possible to transfer most Mods to the Saved Games folder, although I do have some there (mainly liveries etc). I will look into moving my others.

Having returned to the P-51 after many months away, I find that the T-51 and P-51 just sink through the round. On start up I find myself in a subterranean world. If I spawn in the air it behaves perfectly, but I again sink into the underworld as soon as I touch down. I have run a repair to no effect. It only appears to be the P-51 and T-51 that has this fault. Anyone any suggestions?

I have produced a Mission for our Group which uses up to 4 x F-14s for CAP, up to 4 x F-18s for SEAD, and up to 8 x A-10s for CAS, with FAC provided by 6 x FACs, using the standard DCS FAC setup. Each FAC operates on a different frequency, although some targets are shared. When I test it as a singleton F-18 or A-10, all FACs respond as expected and identify and mark all required targets. However, when our group flew it, the FACs stopped responding quite early on, and even seemed to transmit some messages twice, with about 2 seconds between each, so that they overlapped. By the end of the mission, when most of our ac had departed the area, they appeared to come back on line, albeit intermittently. I suspect that the multiple units, responding simultaneously (although on different frequencies to different ac) were overloading the FAC ability of DCS. Has anyone else experienced anything similar or can suggest any other reason, or a solution. As I say, I use the standard DCS FAC procedure, and wonder whether the CTLD system might produce better results.

As someone who spends a fair amount of time ‘instructing’ new members to our group, I would settle for a simple copy of at least some of the more important instruments and controls to be exportable to another player. At the moment I have to formate on the ‘student’ pilot and use R/T to instruct. When covering such topics as entering complex data into the A-10C CDU, for example the ability to see this, as it goes in, would be very helpful. However, I accept that this would not be a simple task to implement and I am not sure how much lag there would be.

When entering a waypoint in the Mission Editor, you need to ensue that the ground elevation is also entered. When entering a way point in flight, by using the CDU, you need to do the same. Usually this is given for you as you enter the position co-ordinates. In what way are these points being entered?

Yes, the easiest way is to use Kneeboard Builder. You will find it in the Forum Mods Section.