Jump to content

Welcome to Gaming On Steroids Forums
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account
Photo

Prediction problems


  • Please log in to reply
1 reply to this topic

#1
Tefridon

Tefridon

    Newbie

  • Members
  • 2 posts

Hi,

 

I have been tinkering with the settings for quite while now and the biggest problem seems to be the prediction being way off when the ball hits goalpost.

 

Prediction does not calculate the spin of the ball with the speed or is there something else?

 

Secondly, when I tested in tutorial - aerial - pro almost always when the ball was not lined up with goal. It did not make any goals with normal aerial which should be most accurate mode. With default settings it was the worst. Had to set the value more higher to get the "small touch" to the ball.

 

I will be testing more when I just have more time. It seems like there is no "perfect settings" to match all the situations.

 

Awesome work Heisa. Keep it up!


  • 1

#2
Heisa

Heisa

    RocketLeague Dev

  • RocketLeague Dev
  • 1,435 posts

Hi,

 

I have been tinkering with the settings for quite while now and the biggest problem seems to be the prediction being way off when the ball hits goalpost.

That is because, of the collision detection tracing as a box instead of a sphere, which causes the most problems with it. It is still way better than the engine prediction (type 2).

 

 

Secondly, when I tested in tutorial - aerial - pro almost always when the ball was not lined up with goal. It did not make any goals with normal aerial which should be most accurate mode. With default settings it was the worst. Had to set the value more higher to get the "small touch" to the ball.

Currently, the aim at goal feature is limited, there is indeed no perfect value that works in all cases. The old default settings were:

125
170

But sometimes it would wiff because of that, and that is also the reason why the default is set to 85 currently

 

 

Awesome work Heisa. Keep it up!

Thanks


  • 0




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users