Forum - DDraceNetwork

[BBvideo=560,315]https://www.youtube.com/watch?v=HbbvMb7 ... e=youtu.be[/BBvideo]
I think the point is pretty clear here, i just wanna know if this is fixable. I actually had to change the second part because it just wouldnt work anymore. (map: Freezejump)

#offtopic -> i like your signature, this hoe ain't loyal.


Yes i got the same problem multiple times on some maps too.

The problem occurs when you copy it to a new map because of the new location of the part. While I was mapping Hostile 2, I had the same problem with the last part and I noticed that there was a fonctionnal area which is 30 tiles off the top, right, bottom and left (if I remember well). When getting too close to the borders the parts physics work differently.

Pipou wrote: Mon Oct 16, 2017 9:57 am When getting too close to the borders the parts physics work differently.

I dont think it's only the borders, because In every clip i used, the part was pretty much in the middle of a big map. It must be some kind of pattern.

We use floating point numbers to calculate the positions, velocity, etc. So the calculations are not exact and in a different location in the map you have a different amount of rounding error. Some more details: http://www.itu.dk/~sestoft/bachelor/IEEE754_article.pdf

I don't think we will be able to fix this without breaking the physics of existing maps.

Oh ok interesting

@deen. Does this mean that for example, the shown parts can only have 2 outcomes based on where they are? Or is there even another possebility in yet another spot. How far does it go up?

Ah ye sure these floats. I also had problems hardcoding my ServerSide dummys. Because the x velocity gets diveded on slowing down.
---> If you stop moving (Pressing a or d) then your vel never gets 0.000000.

Im 'corneum wrote: Mon Oct 16, 2017 1:45 pm @deen. Does this mean that for example, the shown parts can only have 2 outcomes based on where they are? Or is there even another possebility in yet another spot. How far does it go up?

Yes, the physics in different parts of the map are slightly different. The absolute x and y locations count. If the map is huge, the physics will break entirely and any movement is impossible or your tee just starts flying around randomly. But probably the RAM is too small to make a map big enough.

If I were starting a game like this from scratch, I would use a fixed maximum size for the map and use fixed point numbers with deterministic behaviour everywhere.