Lashups

I am only running 4.x release of DCS; however, when you create a lashup (MU) the individual engines go into the inactive area.  You can bring the individual engines into the active area and modify individual settings of the MU'ed engines.  Then go back to the MU and elect to save the configuration.  If you are lucky they will be saved and present on the MU startup.  If you can get them in sync, then when you turn the MU smoke on or off all the engines should respond appropriately.

When I get an engine that the smoke is stuck on in a consist, it has been that the engine also was not responding overall to commands in that condition. There have been various reasons and times this has happened. The consist may have started out OK and then this issue popped up. Usually it started as soon as the consist (lash-up) was created.

 A cure that sometimes works if it's the culprit, is from a near dead battery in a PS2 engine.

 I would recommend you charge fully any PS2 batteries. You check signal strength in any area of your layout that engines act up. You work to remove any power dips in those areas.

I would swear in my mind, that it has also happened from certain DCS versions that had bugs. All I can state is that I'm happy with the latest version overall and it seems to work well for me.

 If it continually happens you might try confining consists to either all PS2 or all PS3 engines and see if that helps. I had that issue with a release of DCS. I'm thinking it was a 5.x but I forget which version exactly.