Trials Evolution - Guide to the Editor | Forums

[sipe]

question to the devs.

Is it possible to put text on the screen, say like, the MPH of the bike somewhere on the screen?

if yes, how would you go about putting text on a screen?

Thanks

If track is defined as skillgame, you can add multiple counters, timers and custom values to the screen. There is lots of text presets to choose from and also wide range of text formatting for your values.

[Happyflow]

No possibility to pop up a window with customised options to choose from which each would be sending out an impulse?

[rlmergeuser]

question to the devs.

Is it possible to put text on the screen, say like, the MPH of the bike somewhere on the screen?

if yes, how would you go about putting text on a screen?

Thanks

If track is defined as skillgame, you can add multiple counters, timers and custom values to the screen. There is lots of text presets to choose from and also wide range of text formatting for your values.

are you not allowing custom text on screen because of possible abuse from the users?

[rlmergeuser]

I agree with Happy Flow on data sources being pretty straightforward to understand. But I also noticed that its very similar to programming, so maybe that's why I found it so easy to grasp. I just know its going to be crazy awesome getting into stuff like that.

Question.
What if I had a barrel with visibility set to true.
And then I created a filter that checks to see if its visibility is set to true. And if it is then it sets it to false.
And then I have another filter that checks to see if its visibility is set to false. And if it is it sets it to true.
What would happen to the barrel? Would it repeatedly blink in and out of visibility?

simpler more programming-esque version

If Barrel.Visibility = True Then
Barrel.Visibility = False
Else
Barrel.Visibility = True
End If

How would that look if it were executed?

[NonRedOrchid]

If Barrel.Visibility = True Then
Barrel.Visibility = False
Else
Barrel.Visibility = True
End If

How would that look if it were executed?

Hate to be 'that' guy but,

if(barrel.isVisable() == true)
{
barrel.setVisability(false);
}

else barrel.setVisability(true);

Wow, that made me feel like I haven't wasted the past two years of my life haha

[rlmergeuser]

I agree with Happy Flow on data sources being pretty straightforward to understand. But I also noticed that its very similar to programming, so maybe that's why I found it so easy to grasp. I just know its going to be crazy awesome getting into stuff like that.

Question.
What if I had a barrel with visibility set to true.
And then I created a filter that checks to see if its visibility is set to true. And if it is then it sets it to false.
And then I have another filter that checks to see if its visibility is set to false. And if it is it sets it to true.
What would happen to the barrel? Would it repeatedly blink in and out of visibility?

simpler more programming-esque version

If Barrel.Visibility = True Then
Barrel.Visibility = False
Else
Barrel.Visibility = True
End If

How would that look if it were executed?

Well, as you describe it, on half the ticks, it would turn visible, and the other half ticks it would turn invisible. I'm not sure exactly what we'd see though, as perception of 60 fps is sketchy. You might see it as a blurred object etc.

I'd assume the starting state would take precedent, and the filters would examine the barrel at the same time, so only one state is true per tick.

[rlmergeuser]

I am so confused about data sources and some filters. I definitely want to learn them but man is it gonna be hard.

[Happyflow]

Depends on what interval you are setting the datasources and/or filters. If both start at the same time for example and they send an impulse every 1 sec the barrel would stay the way it is. (You would not see the action..) If the interval differs it would blink.

Btw. I also have decent programming knowledge could really be the reason for this being so easy to get.

[rlmergeuser]

If Barrel.Visibility = True Then
Barrel.Visibility = False
Else
Barrel.Visibility = True
End If

How would that look if it were executed?

Hate to be 'that' guy but,

if(barrel.isVisable() == true)
{
barrel.setVisability(false);
}

else barrel.setVisability(true);

Wow, that made me feel like I haven't wasted the past two years of my life haha

Haha, never feel bad for being able to grasp something as logically demanding as programming.

But I never established what language I wrote my code in, whic really wasn't in any language, but the closest to what I used would be BASIC. Even then its still flawed because I didn't declare the variables or define their data type and scope. Lol.

I agree with Happy Flow on data sources being pretty straightforward to understand. But I also noticed that its very similar to programming, so maybe that's why I found it so easy to grasp. I just know its going to be crazy awesome getting into stuff like that.

Question.
What if I had a barrel with visibility set to true.
And then I created a filter that checks to see if its visibility is set to true. And if it is then it sets it to false.
And then I have another filter that checks to see if its visibility is set to false. And if it is it sets it to true.
What would happen to the barrel? Would it repeatedly blink in and out of visibility?

simpler more programming-esque version

If Barrel.Visibility = True Then
Barrel.Visibility = False
Else
Barrel.Visibility = True
End If

How would that look if it were executed?

Well, as you describe it, on half the ticks, it would turn visible, and the other half ticks it would turn invisible. I'm not sure exactly what we'd see though, as perception of 60 fps is sketchy. You might see it as a blurred object etc.

I'd assume the starting state would take precedent, and the filters would examine the barrel at the same time, so only one state is true per tick.

Hmm... I understand that. That used to happen to me when I would mess around with certain things on computers. its clearly switching between true and false rapidly, but only one of the two boolean states is being displayed.

Isn't there a data source/filter that allows you to delay the speed at which an impulse causes an event though? If so I would like to ammend my question to:


What if I had a barrel with visibility set to true.
And then I created a filter that checks to see if its visibility is set to true. And if it is then it sets it to false after a 1 second delay.
And then I have another filter that checks to see if its visibility is set to false. And if it is it sets it to true after a 1 second delay.
What would happen to the barrel? Would it repeatedly change in and out of visibility?

I just want to know if paradoxical (not sure if that term is right for this) events can occur.

Depends on what interval you are setting the datasources and/or filters. If both start at the same time for example and they send an impulse every 1 sec the barrel would stay the way it is. (You would not see the action..) If the interval differs it would blink.

Btw. I also have decent programming knowledge could really be the reason for this being so easy to get.

Ahh yes, I forgot about that problem! Since in programming the computer reads from top to bottom that problem almost never affects me (directly), but there's no top-to-bottom in Evo.
So to fix the interval thing, don't you adjust the offset value or whatever its called? I cant remember.

[rlmergeuser]

I'd still say basically the same answer, however this time your ticks are 1 second apart. As both filters would interrogate the barrel at the same time. One doesn't have priority over the other.

First Tick

Is barrel visible? - - -Is barrel invisible
Yes - - - - - - - - - - -No
Turn barrel Invisible- Do Nothing

Next tick

Is barrel visible? - - -Is barrel invisible
No - - - - - - - - - - -Yes
Do Nothing - - - - - -Turn barrel Visible

Repeat ad infinitum

I could be wrong, of course. (and the filters could do something a little different, is barrel visible? No. Make barrel visible, instead of the other filter doing it.