HI Mark,

With 186 the initial.C and inital.H codes have stopped working.

I thought maybe that because we now have @DC and @AC you had changed it so I put:

[ir_translate]
;@DC initial=ffffff.L,ffffff.L,20DF0B
;@AC initial=000000.L,ffffff
80b44918=000000.L

And then I get an IR Translate Error popup at start.

Which is the correct method, @DC/@AC or initial.H/initial.C ?

Ta.

Initial.C and Initial.H are the correct way.

But this whole "Initial" thing is very timing-sensitive, in that we are never really sure when the player is up and running, and if we sent the initial sequences too early, they get ignored.

Best suggestion I have is to place a bunch of null.L codes at the front of the initial sequences, to delay them a bit:

initial.C=null.L,null.L,null,L,button1,button2, ...

Hmm.. Tried:

[ir_translate]
initial.C=null.L,null.L,null.L,null.L,null.L,null.L,20DF0B
initial.H=null.L,null.L,null.L,null.L,null.L,null.L,null.L,null.L,null.L,null.L,null.L,null.L,000000.L,ffffff
80b44918=000000.L

and still no joy....

Okay, I'll fix it.

Okay, Hijack v189 is out. This version features

all new implementation of "initial=" for startup button macros

requires "[output] notify=1" in config.ini for "initial=" to be triggered

all ir_translate flags now work with initial=, permitting multiple instances in config.ini with different flag combinations, as in:

	initial.CTA=xxxxxxx,xxxxxx

	initial.HT=xxxxxxx,yyyyyyy

	initial.CP=zzzzzz,zzzzzzz

ir_translate button flags are now case-insensitive

Have fun.

-ml

I like rubbing your lamp!

You're the quickest genie on the planet!

Cheers. Will try it now..

Works a treat.

Cheers mister!