Today I went through my skill game and disabled all the 'reset at checkpoint restart" options in an attempt to disable the B button using nannerdw's tutorial.
However, the main OPE used to move my game character is being reset to "off" when I press B. It is off at the start of the game because I have a cut scene at the beginning, the OPE turns on afterwards.
Anyway, when I press B the OPE disables again, any idea what's going on?
Make sure you uncheck the reset in CP restart option for whatever is feeding it impulses too. I don't know your most likely complex setup you have going so i'll just say as a last resort you can have the B button activate the OPE after the cutscene too.
From nanners tutorial as reference: On true of the generic filter> impulse clamp filter.
Impulse clamp properties:
Enabled= True
Max # of impulses to=1
Max # of impulses from=0
Reset In CP restart= false
Select event/filter to a state event, state event ON targeting your ope.
Now after your cutscene have a state event turn off the clamp filter and from that point onward every time you press the B button your ope will be reactivated.
If you already have B button doing something else then just use a impulse splitter from the generic filter.
I've had to do this numerous times for silly little things...tbh it was not worth it. That file size limit warning is flashing on my screen and I am far from done yet.
Anyway, if you have RCPR box unchecked for the OPE and it's interval trigger then you shouldn't need to do the above, but as I said, I don't know your code so
Scratch that, it wasn't the OPE it was the interval trigger. Not that it makes a difference I don't think. In addition to that problem, all the buttons are not enabling either, they are disabled during the opening cut scene and if you press B they go back to being disabled
I'm not sure this whole B button thing is worth it. It's a nice idea in principle but I don't like the "stutter" the screen does when you press B.
It is worth it really...in all but filesize. Going through all your code after you already built everything must be tedious as **** though. Needs to be done right from the start ideally. If I were you I wouldn't bother.Originally Posted by JaminBen007Scratch that, it wasn't the OPE it was the interval trigger. Not that it makes a difference I don't think. In addition to that problem, all the buttons are not enabling either, they are disabled during the opening cut scene and if you press B they go back to being disabled
I'm not sure this whole B button thing is worth it. It's a nice idea in principle but I don't like the "stutter" the screen does when you press B.
Senior Member
sounds like your state events have reset checked or a VDS, there are a lot of tools that use this options and all objects advance physics have it listed too. its a task to do but its worth going through every bit of code to double check there all off.Originally Posted by JaminBen007Scratch that, it wasn't the OPE it was the interval trigger. Not that it makes a difference I don't think. In addition to that problem, all the buttons are not enabling either, they are disabled during the opening cut scene and if you press B they go back to being disabled
I'm not sure this whole B button thing is worth it. It's a nice idea in principle but I don't like the "stutter" the screen does when you press B.
edit: and its well worth doing
OK OK, I'll give it another look through lol. I did spend two hours yesterday going through it all, and I've double checked the triggers and objects in question and unchecked all the checkpoint restart boxes, but it's entirely possible I have missed one I admit.
The only reason this wasn't done when I started out, is I started this track and abandoned it before the disabling B button thing was done. It's only due to the mini-game comp and the new dlc objects coming out that I decided to revive it.
