Welcome to Project: Gorgon!


Project: Gorgon is a 3D fantasy MMORPG (massively-multiplayer online role-playing game) that features an immersive experience that allows the player to forge their own path through exploration and discovery. We won't be guiding you through a world on rails, and as a result there are many hidden secrets awaiting discovery. Project: Gorgon also features an ambitious skill based leveling system that bucks the current trend of pre-determined classes, thus allowing the player to combine skills in order to create a truly unique playing experience.

The Project: Gorgon development team is led by industry veteran Eric Heimburg. Eric has over a decade of experience working as a Senior and Lead Engineer, Developer, Designer and Producer on successful games such as Asheron’s Call 1 and 2, Star Trek Online and other successful Massively Multiplayer Online Games.



Results 1 to 10 of 18

Threaded View

  1. #8
    So I've done a bit more testing in regards to the "Accelerator" error, and it seems like my guess about the client estimating cool downs on your FPS is incorrect. I first believed this because during my testing, I was testing in an environment where my FPS was averaging 61, and my game was consistently estimating my cool downs were 1/60th faster. Therefore I expected it was estimating based on my FPS being 60 when it was averaging 61. Also Unity having weird problems related to FPS is pretty common, so that also gave me a bit of bias.

    I did some additional testing in 30fps and my client still estimated 1/60th too quickly. Then I did tests where I would purposely change my FPS by changing areas, or forcing lag and my client still estimated 1/60th too quickly. It seems like no matter what I do, my client is always letting me use skills 1 second earlier per minute of cooldown. I'm not really sure if the problem is really just as simple as the client's cooldowns being 1/60th faster, but that seems to be what it is.

    Because of the error message talking about "Accelerator programs" (Which I now realize is probably talking about ping boosters) and network latency, this error probably has to deal with ping to the server, not FPS. The issue is that my ping during testing was around 50-60 which shouldn't result in errors since that's a very stable ping, but over a long period of time it could cause this cooldown issue. I'll throw out another guess and say that the reason for the inaccuracy is because the client's cooldown assumes you have 0 ping. This would make sense if the testing servers for the devs are locally hosted, since they would have 0 ping.

    If anyone else would like to test and give their feedback, please do. Try using a skill that has a cool down of at least 2 minutes, and when it's close to coming off cool down try mashing the key to see if the game will let you use it early and give you the error. According to my situation, your skill should come out 1 second earlier per minute of cooldown compared to what the timer says. So for example if you use dig deep, it should let you use it when the timer says you have two seconds left.
    Last edited by Yaffy; 04-07-2019 at 12:09 PM.



Thread Footer

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •