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.