What i really really want for the EOS System:

2) You'll need to get more info about what you want. Eos has 2 dark move options.

4) I thought this was maybe possible because you can wrap text in DS by using || in the label but this doesn't work.

5) About + Address will give you the DMX output on every param.

6) I doubt you'll get a new manual until version 3.0

6) When will the Version 3 will Roll out?

No 1 you have exactly in the same way as on Transtechnik. Make a macro saying "sub xx at yyy" ,
The cue zu execute macro (macro number).

About the darkmove.... bit lost in Translation. Pm me in German if you want.
Generally you have the same as on The consoles (as far as I remember my Tat Prisma ntx). It's setup Automark.
The mark function in EOS far more versatile than darkmove in TT, once you get used to it.

No 1 you have exactly in the same way as on Transtechnik. Make a macro saying "sub xx at yyy" ,
The cue zu execute macro (macro number).

About the darkmove.... bit lost in Translation. Pm me in German if you want.
Generally you have the same as on The consoles (as far as I remember my Tat Prisma ntx). It's setup Automark.
The mark function in EOS far more versatile than darkmove in TT, once you get used to it.

Sorry but Nope.
Not the same way like TT.
In a TT SQL i say, create a new Step in SQL and in this step i can direct set the Values (Level, Time In or Out) for the Submaster.
This new Step gets a Hang or Follow Time (for TT means TVZ or TS Time)

I have a Effect at Subamster 1.
I need this Effect first with 100%, later with 75%.
With a TT System i can direct say, Level at 100% or 75% Time in/Out in X-Y Seconds.
On TT Systems i don't need to work with a macro. I can but i don't must.

And thats not possible with EOS. With a EOS System i must creat for every Level or Time In-Out a new Macro.
If i work with diferent Rate and Size Level for the same Effect on EOS i must create Macro for Macro for Macro....
And then i can't see the Name of a Macro in my Q-List....

I used the Automark Function.
But the MH moves if i get a at 0% Lightcount and a new P/T Position in the Q i say Light at 0%.
On TT System the move wait till the light is complett off.
in my Tracklist on TT i also create the Cues with values (for P/T, Beam Parameters,...) in it. But if the Dimmer for a Lamp is under the "Take-In-Level" the Values for the other Parameter have no effect for the Cue.
The Console ignore theses Level and don't move or change any Parameter for a MH at 0%.
With last Software Release on TT comes a new Menu, called 425. This Menu Clean Up this Values the "Empty Steps" for transport a TT Show on a EOS Desk

I understand the dark move function you want, this is how preset style consoles (reading some of your comments indicate the NT was a preset console), unfortunately Eos is a move fade/tracking console.

I can't see Eos adding this dark move feature anytime soon because it goes against the theory behind the console.

Anne product manger for Eos (move fade console) and Sarah product manager for Cobalt (preset console) wrote a white paper on the theory behind these two concepts. If you search the ETC website you can find this paper.

In a preset console 0% channel are ignored but this isn't the case with tracking/move fade consoles.

1) Hopefully at some point we'll have the same commands option we have in MS so we can reduce macro's in cue sheet, at the moment macro are the way if you need these values to come from a sub/fade and can't just be recorded into cue.

4) I understand what you want here and I think this is already on the list. As I said you can put in a line break in other targets and I thought this maybe possible in Notes as well but sadly not.

5) I gave you the wrong toggle here. About+Live (double hit Live to lock) and this will always display the output values. By design you don't see the levels from Park in the live display, this won't change.

6) At the moment we're getting one or maybe 2 major software releases a year so version 3.0 is a couple of years away.

Here is the search to find the white paper.

5) About display also shows the true output in the DMX column. this also reflects parked values. this is shown either in the CIA (ZIB is the german translation for that) or in a tab.