Author Topic: Vagueness in host-client matching.  (Read 223 times)

Grooveski

  • Hero Member
  • *****
  • Posts: 508
    • View Profile
Vagueness in host-client matching.
« on: July 24, 2018, 01:42:57 AM »
Rather than the host server checking that every bike was a match...
...maybe just have it check the particular bike that the client was trying to join on.

Might cut down on joining times.
...and mis-matches.    :)
« Last Edit: July 24, 2018, 02:11:37 AM by Grooveski »

poumpouny

  • Sr. Member
  • ****
  • Posts: 290
    • View Profile
Re: Vagueness in host-client matching.
« Reply #1 on: July 24, 2018, 07:18:57 AM »
and how does the game is supposed to represent other bike riden by other rider on the server ?

Grooveski

  • Hero Member
  • *****
  • Posts: 508
    • View Profile
Re: Vagueness in host-client matching.
« Reply #2 on: July 24, 2018, 11:26:14 AM »
With one of the default bikes - like it does already with a missing rider model.

I admit the idea has it's own issues - but it'd get around mis-matches due to bikes that none of the clients are using.

Perhaps have it as a server option/override.
...so you could host an Open Class trackday event and not worry about every single bike on every single client matching.
....or you could have it set as it is now - for race events with organised bikesets.

Was just a thought.   :)

poumpouny

  • Sr. Member
  • ****
  • Posts: 290
    • View Profile
Re: Vagueness in host-client matching.
« Reply #3 on: July 24, 2018, 12:53:56 PM »
yeah i like the idea ....