Author Topic: Replay buffer size helps prevent core.exe?  (Read 999 times)

doubledragoncc

  • Hero Member
  • *****
  • Posts: 4273
  • If it dont fit HIT it!!!!!!!!!
    • View Profile
    • GPBOC Live Streams
Re: Replay buffer size helps prevent core.exe?
« Reply #15 on: February 25, 2017, 11:24:34 AM »
Thats interesting h

Maybe P should look into a way to keep the profile from being effected during such actions

DD
GPBOC Live Streams: https://www.youtube.com/c/IASystemsComputerControls

Teamspeak: Server IP: 82.43.148.211  user password "yougetin"

i5 7600 5.0GHz z270 ASUS Maximus Code Mobo 16GB 3866MHz DDR4 RAM ASUS Strix GTX1050Ti OC 4GB DDR5 Kraken X62 AIO Cooler

MonJue

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
Re: Replay buffer size helps prevent core.exe?
« Reply #16 on: February 25, 2017, 01:50:26 PM »
Thats interesting h

Maybe P should look into a way to keep the profile from being effected during such actions

DD

+1

tchemi

  • Sr. Member
  • ****
  • Posts: 432
    • View Profile
Re: Replay buffer size helps prevent core.exe?
« Reply #17 on: February 27, 2017, 11:42:00 AM »
IIRC, bikes and tracks are only referenced by their names in profile files. It could be a solution to identify each bike/track/helmet... (any artifact that can be added removed or altered by user actions) with a generated unique ID depending on the artifact version. It exists some good algorithms that can generate a unique key depending on the content of files. If anything is moddified in a bike file, the generated key would be different.

On the pros : You will prevent any alteration due to updating the bike. You are sur to use configuration that suits only the current version of the object
On the cons : You will loose your setups and maybe reccords, and the fils may become difficult to read for a human eye.

Other simple solution, add version number in the name of the bike.
Piboso has nothing to do, it's all on the modder to take care of that. But, maybe you don't want to ride a YZF-R1_v1.2 :/