It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
STAR WARS™: Episode I RacerDo You also have strange hit detection in the game?(3 posts)(3 posts)
(3 posts)
Pages:
1
This is my favourite topic
Posted May 24, 2018
Well, I have replayed the game at least 6 times so far. And from what I have noticed, I get a feeling that the game has some serious problem with it's hit detection. Like sometimes You can hit the wall at full speed and nothing happens, while other times a mere scratch is enough to kill You for a few seconds.

And sometimes You crash even though You shouldn't. Probably the best example is Zugga's Challenge on Mon Gazza - namely this section:

https://youtu.be/r2fMEZCL2Ts?t=4m26s

What to me is this - I hit the brakes, safety go below the giant mobile crane and go ahead, and all of the sudden I crash one of the engine. Even though there's nothing there, just the air.

The only way for the get past is when that giant craze is in it's farhest position:

https://youtu.be/r2fMEZCL2Ts?t=2m21s

But that only happens when I am really lucky.

How about You?
Posted May 24, 2018
avatar
Wykletypl: Well, I have replayed the game at least 6 times so far. And from what I have noticed, I get a feeling that the game has some serious problem with it's hit detection. Like sometimes You can hit the wall at full speed and nothing happens, while other times a mere scratch is enough to kill You for a few seconds.
What framerate are you running the game at? Only some have reported issues when running it over 30 frames per second.
Posted May 25, 2018
The volunteers working on OpenSWE1R have recently documented how the collision model for the tracks work.

Linked here are different collision types (each in a different color).
This is a screenshot overlaying the collisions on Ando Prime over the track graphics.
We are currently busy researching how exactly collisions work and how they affect the pod.

These screenshots are examples. However, with a bit of work it would be possible to look into the collision files of the spots you've mentioned to see what might go wrong.

Korell also said something very useful: The framerate (especially if it's not very stable) can cause very glitchy behaviour.
So if the problem is not reproducible, then this is likely the culprit. If it's reproducible then it's likely a problem with the collision files.

I'd suggest you check out the SWE1R Discord server and maybe someone (me?) can help look into this issue in the future.
Due to the complexity of this kind of bug, I'd assume that it's very unlikely it will ever be fixed by GOG.com.
Post edited May 25, 2018 by JayFoxRox
Pages:
1
This is my favourite topic
Community
STAR WARS™: Episode I RacerDo You also have strange hit detection in the game?(3 posts)(3 posts)
(3 posts)