Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Global Sets #56

Open
freezy opened this issue Sep 11, 2019 · 0 comments
Open

Implement Global Sets #56

freezy opened this issue Sep 11, 2019 · 0 comments
Labels
boring Some VP internals that need to be ported (or not)

Comments

@freezy
Copy link
Member

freezy commented Sep 11, 2019

In Visual Pinball, under Preferences / Configure (Optional) Global Physics Sets, you can define up to nine "Sets", which are flipper and playfield settings that will override those defined in the table. Sets can also be imported and exported.

In the code, these show up as override* properties of the data object. For example, the FlipperData has those props:

public overrideMass?: number;
public overrideStrength?: number;
public overrideElasticity?: number;
public overrideElasticityFalloff?: number;
public overrideFriction?: number;
public overrideReturnStrength?: number;
public overrideCoilRampUp?: number;
public overrideTorqueDamping?: number;
public overrideTorqueDampingAngle?: number;
public overrideScatterAngle?: number;
public overridePhysics?: number;

Those would be set from the global sets. Currently they are undefined.

This is probably low priority.

@freezy freezy added the boring Some VP internals that need to be ported (or not) label Sep 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
boring Some VP internals that need to be ported (or not)
Projects
None yet
Development

No branches or pull requests

1 participant