[PLUGIN Development] Extended API Interface, Procedures to set values

Discussion in 'Wish Lists' started by MerlinC, Nov 22, 2014.

  1. MerlinC

    MerlinC Registered

    Joined:
    Nov 3, 2012
    Messages:
    282
    Likes Received:
    3
    When Simracing leagues are using rFactor (and as of today most leagues are migrating to rF2) for a race series their intention is to implement the rules as close as possible. Unfortunately rF2 does not support certain features like limited number of tires (and getting used tires), DTM DRS rules,...

    This would not be that much of an issue if the API would provide some procedures to set values because the community of plugIn developers should be able to extend the function of rFactor if the API interface would be extended. Here are two examples:

    F1 Rule - limited number of tires and getting used tires:
    - Driver should have a limited number of tires for all sessions (see FIA homepage for more details on the regulations)
    - Thus I could envision a plugin which is manageing the number of tires, attaches to every tire set an identifier, stores the wear rate in a database and whenever the driver selects the same tireset the wear rate is being set by the plugin. Everything straight forward but how to set the wear rate to a certain value (TelemWheelV01.mWear).
    With an API Function allows setting the starting tire wear rate when you select your tires in the garage this could be achieved easily. And there would be no need to implement it to rF2 like other F1 simracing software is doing that

    DTM DRS Rules
    Drivers just allowed to use the DRS once per lap. Afterwards it should be disabled. Again there is a flag you can read in the TelemInfoV01.mRearFlapLegalStatus but you are not able to set the value.

    I assume that set functions are not supported to avoid cheating?! The risk of cheating is an issue for sure - but could be avoided if the set functions are only being available if the plugin is either is being called by a dedicated server (assuming that the server admin is typically not cheating :rolleyes:) or in an offline game (if someone is cheating against the AI it's his decision).

    If the community supports this idea I would appreciate if you could just reply to the thread. If there are further uses-cases where a set function would make sense feel free to post it here.


    EDIT 01/16/15:
    - I had like to add a request that methodes get added to the API providing information when a driver joins and lefts the race. As of today the only way to know on a server side plugin that a driver joins/lefts is that you keep a list of all drivers and look whether you find the driver/car combination in the list. Especially identifying that a driver left tricky and the server clearly registers this events. Function could look like

    void DriverJoined (const VehicleScoring



    - Additional methode

    Kind regards
    Merlin
     
    Last edited by a moderator: Jan 16, 2015
  2. MerlinC

    MerlinC Registered

    Joined:
    Nov 3, 2012
    Messages:
    282
    Likes Received:
    3
  3. Frog

    Frog Registered

    Joined:
    Dec 23, 2011
    Messages:
    4
    Likes Received:
    0
    we also want to use rFactor2 instead of rFactor1.
    because we need "league suitability" by driving with a very high realistically.

    +1
     
  4. Jeferson Richart

    Jeferson Richart Registered

    Joined:
    Oct 23, 2013
    Messages:
    174
    Likes Received:
    34
    DTM DRS Rules... :rolleyes:
     
  5. Nazirull Safry Paijo

    Nazirull Safry Paijo Registered

    Joined:
    May 28, 2011
    Messages:
    1,417
    Likes Received:
    35
    Yes!

    Ive beeen thinkin of limited tires per racing weekend and reusing old tires since 2006!

    Plss...pls...plss....make it happen Tim...plsssss ;)
     
  6. GCCRacer

    GCCRacer Banned

    Joined:
    Dec 12, 2012
    Messages:
    1,317
    Likes Received:
    2
    Sounds like a great idea.
     

Share This Page