I have some code for a simple digital number readout that I used to test the scores for Project Spin. I had to make it trials during testing, so I put in a custom score readout that floated above the rider. That way I could get some baseline scores for medal times. The code is not very well optimized though, so it's pretty laggy if you update it every tick. Should I add this one?
Also, bobozilla, I'm pretty sure you don't need those interval triggers. I added a filter to prevent the LB when it gets to the first checkpoint to the simple version. All you need to use is the impulse from the LB button.
for checkpoints
i would
on press RB->set value event(set,value=min(number of checkpoints,stored checkpoint value+1)).target=stored checkpoint value
on press LB->set value event(set,value=max(0,stored checkpoint value-1)).target=stored checkpoint value
With the unnecessary SVE's and VDS's, they were. But now that I've seen your updated simple version with the GF, I was able to simplify the advanced version quite a bitOriginally Posted by Luthanick![]()
You should try to optimize it as much as possible before making a tut.Originally Posted by Luthanick
let me explain this.Originally Posted by dasraiser
RB on press target=
SVE(set,value=2IO(Min,OP1=number of checkpoints,OP2=2IO(ADD,VDS(CheckPointIndex),1)),t arget=VDS(CheckPointIndex))
LB on press target=
SVE(set,value=2IO(Max,OP1=0,OP2=2IO(Subtract,VDS(C heckPointIndex),1)),target=VDS(CheckPointIndex))
no need for generic filters, its just
1xVDS
2xSVE
4x2IO (Two Input Operator)
and the 2xbutton events
yeah i understand the need for the template system your knocking up, great work by the way
the () are set up like maths brackets and have to be expanded.
so
place a VDS, this is the checkpoint index
place a 2IO, set to Add, operand1=VDS, operand2=1 :- call this "VDS+1"
place a 2IO, set to Min, operand1=total number of checkpoints, operand2="VDS+1" call this "Clamp Upper"
place a SVE, set to "Set", point value to "Clamp Upper" and set target to the VDS call this "Out Upper"
place your RB and pass the impulse to the "Out Upper"
place a 2IO, set to Subtract, operand1=VDS, operand2=1 :- call this "VDS-1"
place a 2IO, set to Max, operand1=zero, operand2="VDS-1" call this "Clamp Lower"
place a SVE, set to "Set", point value to "Clamp Lower" and set target to the VDS call this "Out Lower"
place your LB and pass the impulse to the "Out Lower"
this is equivalent to
for RB:
Check Point Index=use the minimum value of either "Maximum Number of Checkpoints" or "Check Point Index+1"
and for LB:
Check Point Index=use the maximum value of either "zero" or "Check Point Index-1"
I know this is supposed to be simple, but I just can't grasp it. I'm trying to make super simple, very easy-to-understand setups, and this just makes no sense. I have no doubt it works, but it's too nonsensical for a layman like myself and most Evo users to understand.Originally Posted by dasraiser
2IO = Two Input Operator
SVE = Set Value Event
VDS = Variable Data Source
sorry i thought you used these abbreviations!!?!?
RB = Right Bumper Object
LB = Left Bumper Object
the "label name" was so you can identify the thing that needed to be connected.
ie "Clamp Upper" is just the Two Input Operator that's set to Min and has Operand1 set to the total number of checkpoints and Operand2=the checkpoint index with 1 added.
I know the abbreviations. Hooking it up makes no sense. I appreciate you trying to clarify, but some things I just can't understand, no matter how well they're explained, and it pisses me off so ******* much!Originally Posted by dasraiserIt would be great if you could make it on google docs.