1. #11
    it happened again on version 1,06:
    on dynamic-3 Shaky grounds I did 0:42:18 with 0 faults and I hadn't any highscore but it says I didn't beat it..........it was 1:40AM , april 15; my profile name is still schtroumf.
    this one is annoyung cause the end is quite hard...[/img]
    Share this post

  2. #12
    sebastianaalton's Avatar Trials Developer
    Join Date
    Mar 2014
    Posts
    2,455
    Originally Posted by schtroumf
    it happened again on version 1,06:
    on dynamic-3 Shaky grounds I did 0:42:18 with 0 faults and I hadn't any highscore but it says I didn't beat it..........it was 1:40AM , april 15; my profile name is still schtroumf.
    this one is annoyung cause the end is quite hard...[/img]
    Ok, then there are 2 bugs. We fixed the bug when connection gets dropped during run, and the high score got lost. This bug you are having must be a different one then. We will investigate.
    Share this post

  3. #13
    Thanks for posting additional information about the failing highscores.

    I was able to find the cause for this, it was an issue with the server configuration, and it's solved now.
    Share this post

  4. #14
    that's cool
    thanx to you
    Share this post

  5. #15
    I'm sorry, but it happened again.....
    it was 2:30AM, april 17 I took a screenshot this time and it's on rapidshare:
    http://rapidshare.com/files/108093419/untitled.bmp.html
    Share this post

  6. #16
    OOops.... I didn't say anything, 5 minutes later the highscore was updated.
    it seems to work
    good job guys
    Share this post

  7. #17

    grrr

    I had the same problem again: today, may 7th, at 2:15AM my time on "I want squirrels" didn't count. I did 00:48:86. you can see the copy of the screen here:
    http://rapidshare.com/files/113100790/trials2.JPG.html
    Share this post

  8. #18
    sebastianaalton's Avatar Trials Developer
    Join Date
    Mar 2014
    Posts
    2,455
    I have informed our server programmer (Jukka) about this issue. He can check the server logs and investigate what went wrong.
    Share this post