The overall display is 320. Left is 0 right is 320. A trip across the screen from left to right uses any of the concepts and formulas that you guys mentioned. To travel from right to left, just subtract the whole formula from 320 (or something further off-stage like 350 or 400). @benkidds if you give us the text string you’re trying to pass, we can throw a sandbox face together in inspector mode so you can get started.
the data Mellin asks for is precisely what’s needed. Looping the time cycle means the cycles have to fit cleanly in a 60 second period.
2 seconds - 30 times a minute
3 seconds - 20 times a minute
4 seconds - 15 times a minute
5 seconds - 12 times a minute
6 seconds - 10 times a minute
10 seconds - 6 times a minute
12 seconds - 5 times a minute
15 seconds - 4 times a minute
20 seconds - 3 times a minute
30 seconds - 2 times a minute
Without some additional math work, the formulas above work fine if your text pass fits into one of these cycle periods. So a text pass that crosses in 13 seconds is no good. Either make the text shorter or change the pass speed (faster or slower)
Without knowing the text string length its difficult to say. I wanted the right most part of my text to start on the far right wall. Hence the calculation of my text string length (125px) minus 320 (far right wall). Knowing that #DWE# starts at 0 the text would only move within the 195-0 x axis. See the new face I just created. Watch the date text.
This is what I was hoping to achieve and it seems to work well so far with the support from all above, thanks
Any recommended improvements welcome, I have the X axis using:
thanks yes longer ones just about stay on the screen as it starts again so may increase the value to compensate for that.
Just working on steps to miles conversion now but want to restrict number of decimal values so miles looks like 1.15 rather than something like 1.15434326598 and so on !!
Change “#DWE#” (both of them) for something like “(#DWE#-0.5)”, while not changing any other parts of the script.
This will make that script think that it’s earlier than in reality.
Only problem with that would be if you have variable text lenth (i.e. the weather text, where “Sunny” is obviously shorter then “Mostly Cloudy”). You would have to account for the graetest lenth to not overwrite the prior text. If you allways use the same length you would be fine.