DCS start up lag time on remote

I don't know which version you had loaded before? I can only guess on the reasons.

I believe there is a delay on lash-ups, as the program has to work with PS2 and PS3 boards that have different defaults. Might also be the remote talking to the TIU over new code for the lash-ups as well? Things change and the app has to be considered in the program.

I just upgraded to 6.1 (getting a WIU at some point) and have noticed no lag on startup, but I only have 1 TIU. 

I see a noticeable lag after I shut down using the "ALL" command.

Once all my MU's (two 6 engine and one 5 engine) are in WD a start up command takes 3 seconds.  I am 6.1  using 2 channels in passive.

Thanks for the replies guys!

Jeff..... probably just me but i think everything with the remote is slower with 6.1.............Clem

Clem,

On the contrary, I find DCS 6.1 to be as responsive as, if not more responsive tban, any earlier DCS release.

Barry, any ideas on the delay I'm experiencing? Specifically delayed on the lash up start up. Thanks

Jeff,

There’s a bit of stuff that the TIU does to startup a lashup. The more juts, the longer it takes.

Whatsa jut?

so is there any way to alleviate this issue? The delay is significant in length compared to previous versions of DCS. thanks

Jeff

I don’t see “big delays”.

Clem  I believe your correct there is more delay with 6.1 but you have to remember every time  they do a upgrade of the software from  say 6.1 to something larger the bigger the program becomes the slower the system will be but  not much of a delay, its inevitable with modification of any software. when windows 7 went to windows 10 I could see a difference! not much you can do about it just live with it, its a train  just enjoy it!

Jeff remember you can always go back to previous versions if it works for you as long as there are not bugs in the software that you use!

I thought I had noticed this delay after the attempt to clear the lash-up defaults for direction. Originally, the DCS software ( 5.x?) would confuse the settings between PS2 and PS3 and mixed lash-ups of them would fight each other until the direction button was toggled. So I thought 6.0, or whatever was the next upgrade started a longer delay in lash-up start ups.

6.1 sure hasn't solved many of my MU problems. I have three; PS3 and PS3. and two of a PS3 with a PS2. The pair of PS3s screw up about 50% of the time on startup. Sometimes one starts in conventional, other times one just won't move even though the lights respond. Once in a great while the direction button fixes it, but not often. I have to shut off the TIU and try startup again. It seems to me that the first MU startup takes 3 to 4 seconds, but the other two much less after the first one is going.

John H posted:

6.1 sure hasn't solved many of my MU problems. I have three; PS3 and PS3. and two of a PS3 with a PS2. The pair of PS3s screw up about 50% of the time on startup. Sometimes one starts in conventional, other times one just won't move even though the lights respond. Once in a great while the direction button fixes it, but not often. I have to shut off the TIU and try startup again. It seems to me that the first MU startup takes 3 to 4 seconds, but the other two much less after the first one is going.

John..are you app or HHR?

Remote

I found something interesting, although probably not groundbreaking! It maybe confusing as I'm going from memory without notes.

I ran a set of engines in a new consist with the phone app (call set #1), along with another set I'll call set #2 with the remote. There were some anomalies going on that I didn't understand but both consists ran. We took a break and after(with a cycle of power) we started another session. Set #1 just happened to be a pair of engines already created in the remote, but with the opposite engine in the lead. I ran that set #1 with the remote in the first session and running in reverse, the rear engine would sound the horn. I started running the second session and had created the consist in the app in the opposite positions and the lead sounded the horn.

 So we ran the consists again on a third session and to my surprise, the front engine would sound the horn using the remote, which still showed the opposite positions. If that didn't surprise anyone we had to cycle the power to swap out consist engines in set #2 and when I restored the power once again ( fourth time), both engines in set #1 sounded their horns!

 So how come with each session did the consist swap what engine would sound the horn? Was it from different devices and old lash-up builds confusing the system?

In my MUs, both horns sound.

In my mu's, one engine may have eng sounds,another the bell and another the horn. I have used only 2  firmware applications 4.2 and 6.1 using remotes and both have been remarkably stable and individual engine settings stay put. Engines are a mix of ps3 and ps2 3v. All engines are in the active list and my read button has been disabled because if you inadvertently hit the button it will scatter your engine settings.

Hmmm, I use the read every day. I should investigate if that's what is causing some of the issues. 

I have a feeling that I may have to clean my main remote up to get rid of old poor housekeeping. It maybe time to reset it and start fresh.

Joe,

READ is a one-trick pony. It just sorts powerered vs. unpowered engines. Period.

JEFF, did you try doing a reset of your TIU's and remotes after doing the upgrades? You will have to upload your remote's content to your computer so you don't loose it. It may help with your issue.

My lashup experience is: 

The PS2 Lashups take a considerable amount of time to respond when switching to them in the remote and startup.  Once they are started up, they are fine.  If I go to another engine then come back to the lashup, there is the time lag again.

PS3 lashups are quick and responsive all the time.

John H posted:

I see a noticeable lag after I shut down using the "ALL" command.

Interesting observations with this post. When i shut down i just power off the TIU and track transformers with one master remote.

Often times the DCS remote has already timed out and shutoff . Restarts very consistent..1 one thousand 2 one thousand on 3 one thousand mu's start.

I usually just turn off the transformer at shutdown , also. If the remote is on all engines when I shut it off, it takes longer for the remote to boot up the next time. I wasn't very clear on that.

John H posted:

I usually just turn off the transformer at shutdown , also. If the remote is on all engines when I shut it off, it takes longer for the remote to boot up the next time. I wasn't very clear on that.

Any chance you could build  a 2 or 3 engine mu on a test track isolated from your lay out?

I just started all three MUs, two on one track and one on another. They actually started correctly, by the way, which only happens half the time. I hit the read button and here is what happened. All the MUs went to the inactive list, all the individual engines came up active. All the smoke came on, all the ACC and DEC went to default 4 and 2, sounds all increased and crew talk started as soon as the MUs were brought active. This was the second time I tried it. The first time everything happened right after I hit the read button, without bringing them up.

As far as the test track is concerned, I usually just take engines off the layout or park them on a dead siding, and use the layout track for adding engines. I only have 6 diesels and 1 steam, so usually not a problem.

Thanks for testing..read button is evil when it comes to mu's. All of mine are disabled for this reason.

When i need to reactivate a unit , i >eng>select eng address #>press select. This process is rarely needed as all my engines stay in the active roster. Reload your mu's making sure they are in the active list ,throw some settings in (eng vol etc) start up and stop several times and see if settings maintain.Do not use the read button. Keep in mind a ps3 and ps2 mix might get confused on direction...just cycle your direction button once and all should be good.

in a lashup one thing that is anoying is the engine/prime mover volume settings. when engine/prime mover  sounds are  adjusted in the lashups menu screen only the lead engines sound is affected the other engines have to be adjusted in there respective menus. this seems to be both on the app and remote. why is that? when going into the lashup's settings menu should not the engine/prime mover settings be for all engines in the lashup?  

Lionelzwl2012 posted:

in a lashup one thing that is anoying is the engine/prime mover volume settings. when engine/prime mover  sounds are  adjusted in the lashups menu screen only the lead engines sound is affected the other engines have to be adjusted in there respective menus. this seems to be both on the app and remote. why is that? when going into the lashup's settings menu should not the engine/prime mover settings be for all engines in the lashup?  

I don't use this approach as i found it annoying and unstable as well. What i do is set values for each member engine. One engine may have the bell only,another eng sounds only and another the horn only and the rest all values set to zero. You could set all values in one eng only and silence the rest with zero settings. My mu's remember there settings each and every startup session..also i use the remote vol + or vol- as a master volume. The 2 buttons i never use are eng snd and read. BTW if engines are sitting hitting the doppler button will mute the entire mu...handy if the phone rings etc.