Is there a point in this day and age to actually link bike skins to different dynos?Why isnt the skins just standalone, unlinked to any dyno. This way people can switch freely between dynos mid-season if they want instead of making a teampack huuuuuge just because maybe someone wanted more than one dyno.

I can maybe see a point in linking the skins to a bike size. So you link your skin to either 250, 350/450 or twostrokes.

Maybe I´m missing the whole point of this but it would make some things smoother.

Taking myself as an example. I run the fc450 dyno normally. This is of course because when you need that little extra power for say a big jump or a long uphill its really nice when you dont have the cornerspeed of Mullins or Fresquez. However when a track doesnt have those things and maybe is more on the slippery and techincal side maybe I´d rather have the yz450 or crf450. I can still run the fc450 of course as its not that big of a deal but I might feel slightly more comfortable with those less powerful dynos. Not enough to warrant an extra 20-30-40mb (or however big another bike is) in our already large teampack so I just go with the fc450. Both for my sake because I wanna ride our really nice bikes but also for people who took the time to download our packs to actually get to see us. It´s really annoying when you download a 700mb teampack and then at the next race you cant see half of that teams riders bikes or gear because they happened to wanna change it.

This is a very small thing I know but I feel linking the skins to one specific dyno doesnt accomplish anything. Maybe this is a coding problem that I dont understand but hey, please explain because I´d be happy to know

jlv wrote:Actually, if I could come up with a fancy AI image recognition function that could tell which brand the skin is I'd probably force the skins match the dyno. A Honda skin on a KTM is an abomination!