Graphics

Hey all,

Not sure if I'm overlooking something, but some testing for the most part confirms my theory.

An active production already makes great use of Datalinq Key macro equations to set a %race% to pull from Datalinq.

But I recently learned some new tricks from the forum like comparison operators for XML. So, I've been toying around with adding these to my Datalinqs, like instead of just looking for..

Race<%race%>\RaceNumber

I can look for

Race<RaceNumber=%race%\RaceNumber

But for some reason, this is breaking the macro equations:

I thought maybe in this project's specific case the search was failing or something but with a test scene I can confirm that even with the XML search, a pure %takeid% macro still works. 

And will break once I add an equation:

The quick solution is to just hardcode the Datalinq key for the scenes, and that's potentially what I'll do, but I do like the ease of an operator being able to simply drop the template in more times to give more race capacity if needed (as rare as that is).

In any case, it does come across as a bug to me, so I at least wanted to get something about it here so it might be fixed. But if I am missing something, please let me know!

Thanks!

Could you just do %relid% instead of an equation.  So if your group is 1200 and your take ID is 1201, if you enter %relid% it would be the equivalent of doing TakeID-GroupID number to give you an output of 1 in this case.  This limits you to 99, but most things usually happen less than 100 times.

That's certainly a option, but I don't currently use scene groups for each kind of scene, just each track. All 1xxx are Track_A, 2xxx Track_B, etc.

So a %relid% for TakeID 1201 wouldn't give me the right key in Group 1000.

It would work, but would mean reworking the entire sequencer and lead to exponentially more Groups, and somewhat less organization since Groups can't be nested in another Group.