I got this yesterday on PC, my first Trials game and all, and I've heard the past entries have had spotty PC ports. Well I'm having this weird issue on PC which isn't a major problem but I'm curious if anyone else encountered it. Whenever I go to customize my bike or my rider the game will seem to be in the loading screen indefinitely until I back out and enter again at which point it loads fine. It seems to work this way every time - won't load until I back out and try again.

Apart from this the game runs fine so it's not a huge issue, just curious if I'm the proverbial "only one" experiencing this issue.

sounds like a RAM problem, or maybe a hard drive one.

@corruptedevil: Well I have a brand new SSD and 16gb of Ram and my PC is maybe like 1.5 years old at this point so I'm hoping it's not an issue on MY end.

@humanity: it's not a ram or a hdd issue. I have the same exact same problem. I noticed if I just wait on the first time and don't back out the problem mostly goes away after that.

Good to know I'm not the only one. Not a dealbreaker, just really weird.

A bit late, but I can confirm too. It seems to work after about 30-45 seconds of waiting on the screen, but backing out doesn't work reliably for me.

After having spent a lot more time both in the game and in the Track Editor I can confirm that this only happens for loading in the bikes and outfit menu's. Thankfully the game performs without a hitch where it most matters - the tracks. Respawning, resetting, etc works instantly. The track editor also doesn't have any loading hangups and works quite smoothly - I've actually found it more comfortable to operate with a controller rather than mouse and keyboard which is insane.

So maybe this will get patched in at a later date. It's a small thing but it can be annoying as I'm the type of person that loves customization above all else in games.

I have the same problem as well and I'm running on a Late 2013 Retina MacBook Pro with a PCIe SSD and 16GB of RAM.

Really odd problem, though. I didn't ever have a problem while running the beta.

There are definitely a few bugs that they should *really* iron out on the PC though. The biggest one is to enable frame skipping. 90% of the performance complaints would go away if the game speed wasn't dependent on the frame rate (e.g. If you're running at 40FPS, the game runs at 2/3 speed). I wouldn't notice it much except for the fact that there's a few shaders in the game on some tracks that inexplicably make my frame rate tank, otherwise the game runs rock solid at 60FPS.