About using the "--F30" and "--F" framerate throttles correctly

[Lünk]

In the original post by the SEGA staff with the "public test branch" patch (5th of Nov) they instructed us to select the "publictest branch" option under the BETAS tab in the properties window and wait for it to patch (approx. 6mb), before applying the "--F30" or "--F" launch options. Then in another post (on 23rd of Nov) they mentioned the two frame rate throttles under patch additions without any mention of the publictest branch BETA thing anymore.
Does this mean that the two framerate commands can be used as launch options for just the REGULAR version of the game as well? Or do we always have to switch it to the publictest branch BETA version in the properties menu first? Will my game go all haywire if I choose the wrong option?

I'm asking this because about 2-3 weeks ago, when I first followed the instructions for utilizing the --F30, it didn't do the 6mb patching process like they said. It DID throttle the framerate to a lower one as it was supposed to, but I was still worried I'd done something wrong and risked damaging the game somehow. After all, these commands are designed to tamper with the application's internal mechanics in ways not explicitly planned by the developers, so I'm trying to be extra cautious with whatever I'm doing.


Long story, short: Do I always have to set the game to the "publictest branch" BETA in the properties menu and THEN use the framerate throttle launch options? Or are they meant to be used on the regular version of the game? Or does it not matter at all which one I use?

Thanks guys!

[Minka]

They're meant for the beta version, which is where all the patch updates have been so far. It doesn't really look like there's going to be a regular public version without this beta branch nonsense at this point, going by all this feet dragging, so best to just flip the beta branch on and pretend it's the version everyone gets.

And no, the framerate throttles won't damage the game. Worst that can happen is the scripted/automated events in the levels going wrong because of the hard-coded object physics and general engine timings.

[Zappy]

Originally posted by Minka:

[The beta] is where all the patch updates have been so far.

Originally posted by Patch: 06/01/2016:

• Steam Controller template added.
  
• New players will start with 9 lives instead of 4.
  
• Existing save games will be updated automatically when current lives are exhausted.

I got a game over recently and got 9 lives, and I'm NOT in the beta branch.

Originally posted by Lenny:

-Stuff-

They made a beta branch update before, adding the framerate throttle things, then they made a public update later, which also had the framerate throttle things, so it does work for the regular version of the game, don't worry.

From what I can gather, the regular version has been updated later than the beta version, so I would personally stick to the regular version of the game.

But beware, if the game isn't running at 60 frames per in-game second, several things may not work as intended, such as a long row of enemies in one level where you'll pop all of them if homing-attacking the first at 60 frames per second, but less than 3 at 30 frames per second.

I'd advise no framerate throttle thinging if you can get 60 frames per second, but if you can't, I'd advise just using "--F" so as to get the maximum framerate your system can deliver to hopefully avoid bugs like the one I mentioned right above.