Winston 60

Yes, I realize that it didn't work perfectly before but the 'autopilot light' used to come on before in the bottom of the warning light panel and 'altitude hold' at lease tried to work. Now there's no 'autopilot light' at all when pressing keys/buttons for 'altitude hold'. It's like a completely dead keystroke/button press now. Not even a hint of it attempting to engage, while 'attitude hold' still works fine and the 'autopilot light' comes on for that. :joystick:

Is your comms menu open? The mouse cursor will not go away in multiplayer with the comms menu open.

The only thing I can put my finger on is the CBU-97's exploding when dropped from the A-10A. Not when they explode and disperse, but when they explode on their targets. This is another old bug revisited. Most other jerks and pauses seem completely random as far as I can tell, happening when rolling in on a target and lining up the bombsight for a weapon release or just flying straight and level then beginning a turn. We realize that a player spawning in or an enemy flight spawning in creates a pause, can't help that, it's always been that way, but all these new jerks, stutters and pauses are 1.5.6 specific only. They did not occur in 1.5.5.

While our lag is not massive, we are also experiencing increased lag, jerks and pauses with a much smaller number of clients. This is very disheartening to us because we did not experience these things in ver 1.5.5. Problems began with the first release of 1.5.6. A rather large number of "fixes" and "improvements" were incorporated then but at the same time a lot of other things were broken and new bugs were introduced too. I think at the moment the stable release version is sadly lost in numerous bugs, problems and some amount of indifference. Nearly all of the attention seems to now be with Alpha, WWII and the merge to 2.5 instead of insuring the stable release is up to the high standards we've become accustomed to. There's just too many versions now for ED to manage. Unfortunately it the stable release that's going to be left behind in the race to new and better things. We're not happy with it, but we do have faith, and will deal with it while still remaining unhappy until a new release version is playable without all the frustration. EDIT: Multiplayer jerks, pauses and lagging when flying A-10A, F-15C, Su-33, Su-27, Su-25T, F86 Sabre.

Nope, still does not work. No autopilot light, no altitude hold. :cry:

Please put mission editor questions in the "Mission Builders' Corner topic above. This topic is for missions and campaigns. Could we please get a Moderator to move this so the user can get his question answered?

Your Radeon R5 M430 laptop video card scores 624 on passmark tests. This low cost video solution was not designed to play complex games. In comparison, a Geforce GTX 880M laptop video card scores 3,569 on the same test. Perhaps this could this be the reason?

As of the stable release version 1.5.6.3930 of Apr. 7, 2017, the F-15C's "Altitude Hold" autopilot no longer engages with the default keys, reprogrammed keys, or if programmed to a button. Autopilot light does not come on. The "Attitude Hold" functions properly, autopilot light comes on and the "Autopilot Off" seems to work after having engaged "Attitude Hold". Could someone verify this please?

I can confirm in testing with two clients that this bug has been resolved in stable release version 1.5.6.3930 of Apr. 7, 2017. Thanks ED! :thumbup:

We tried to confirm this for you tonight Drexx, but using the stable release version 1.5.6.3930 we were unable to crash my server on destroying several bridges. Using Su-33's we destroyed a railway suspension bridge with bombs, a regular road bridge with bombs and two road suspension bridges with bombs. None of the events crashed the server or generated any errors. Could be a module or weapons issue. What type of plane killed your bridge and with what weapon?

For all FC3 aircraft, this bug remains and was not fixed in stable release ver 1.5.6.3930 of Apr. 7, 2017

No problem. Seems logical and it may just be that way but I still think the stable release version should live up to it's moniker. I guess I'll just have to get used to the fact that the less important but recently introduced bugs are going to remain until version 2.5 version takes care of all our problems, right? :smilewink: I'm checking the other stable release version bugs that I have reported over the last 2 months and report on those as well. As I post them, maybe you could check to see if some of the other unresolved and persistent bugs are going to be worked on?

BIGNEWY, if your guess is right, that's too bad; too long to wait. This bug was not present in 1.5.5. Why did they introduce faulty clouds into 1.5.6 and now have us suffer through with these? Why can't the clouds from 1.5.5 be rolled back into the stable release version? :cry:

Please note that mission editor questions belong in the Mission Builders' Corner topic just above this one. This is to keep the clutter down in this topic which is reserved for missions and campaigns. :thumbup:

After 8 weeks of waiting and hoping that the stable release ver 1.5.6.3930 patch of Apr 7, 2017 would repair this clouds bug, I can report that this bug still remains. :(

No, the "time more" condition is not necessary. You can have the first group already active in the mission by setting it's start time same as the mission start time. When using multiple groups that are the same you only have to create the first group, then select it and press Ctrl C to copy, then click on the map where you want to paste the clone and press Ctrl V. You can create a dozen clones in just a few seconds. Saves a lot of time.

kylekatarn720... ruskybeaver is correct. Using mission builder functions you cannot spawn in again a group that has already been spawned in and killed, but this simple and easy mission editor procedure can spawn identical groups in the same location providing you create them with a different group name. Have a look at your mission now. I have simply created a total of 7 tank groups and triggers to spawn the next one in when the previous group is dead. I simply copied one of your groups and and pasted it back in to your mission changing only the name. Everything is copied, even waypoints if it is a moving vehicle group. I hope it makes sense to you. If any questions, please ask away and Happy Mission building! :yay: winston-mod.miz

Recently I hyped DCS to some friends... but they beat me down a few weeks later for pointing them to such a buggy game. :chair: Ouch! I don't want to go through that again! All my explanations of why ED can't take the time at this point to ensure the main product is in better repair fell on deaf and unbelieving ears. I'll begin recruiting and promoting DCS World again once the game is in a better state of repair, perhaps after the WWII stuff is done, oh... and the 2.5 merge is made and ED can devote resources to seriously squashing some bugs and improving the game's stability in general. I'm hoping then I'll get those friends back! I do so love this sim but have to be wary of promoting it, in it's current condition, to experienced flight simmers.

Should be simple to do with simple mission editor triggers. Post your mission as you've created it so far and I'll take a shot at modifying it for you. You can then look at the mission in the editor again to see how I did it.

A medium thickness silicone grease can be found at your local hardware or home supply store. It's called "plumbers grease" and it's inexpensive in a small quantity tube. If you need to get inside the TWCS to apply the grease to the total contact area, this video will show you how. Disassembly begins at 20:24

I stopped working on mission four because of the planes spawning on the carrier bug https://forums.eagle.ru/showpost.php?p=3056771&postcount=31 and the clouds issue. I see in the open beta they say the spawning in issue has been fixed so if someone can confirm this, I'll start working on mission four again and try to have it ready for the next stable release version.

Release version only for me. Before the bugs can get ironed out between open beta and release, they first have to be reported by the open beta users. Often bugs aren't being found or reported by the open beta users which allows the stable version to be released a week later in a buggy condition. I'm beginning to wonder why there's even an open beta release at all any more. But I'm always hoping that some bugs will get squashed between open beta release and the stable release like in the past. :(

Go figure! It works, that's the main thing. :thumbup:

In-game map drag = Left mouse button Mission Editor map drag = Right mouse button

Swirling, rotating, disappearing clouds bug in 1.5.6 is not old. Stable release 1.5.5 did not have this bug. This is a new bug introduced in 1.5.6. It is a reoccurring bug and we had it in a previous release version version and it was fixed before in rather short order by ED. But I was thinking if Ed doesn't want the problem of fixing the old engine then they shouldn't break things with new patches of the old engine. Clouds were fine in 1.5.5 then 1.5.6 is introduced and now the clouds are broken. I really hope ED doesn't ignore the stable release version just because they've got too many versions to support? In fact I'm counting on them to repair this clouds problem in a reasonable amount of time. I'll remain confident in ED's ability to get this fixed. After all, the Stable Release Version really needs to live up to it's name and implied standard. It's the only version I'm playing and that's the reason I'm so passionate about new bugs being introduced where there was no such bug in the previous version. ...and let me take the time now to thank ED for fixing the multiplayer carrier aircraft spawn problem. I'm looking forward to this when the stable release 1.5.6 comes out. :thumbup: