DDraceNetwork

RedRay32

it's the map's fault, not yours or your server's, and as far as I can tell there's nothing unusual about it hihi

ur wrong

09:16

its ddnet velocity calculation problems

Muzcuk

i cant join ger1 and ger3 servers its saying server is not responding yet but i can join normal ger and ger2 (im verifyed and this still not work) @Davide

Any fix?

ᗰaksym

its ddnet velocity calculation problems

yes, because your map is poorly made, this problem occurs at very high speed values

ᗰaksym

its ddnet velocity calculation problems

Feature, not a bug :) Basically, half-intended behaviour. A result of a feature that never expected the player to move that fast

It's like strong/weak - it's a bug that we now consider a feature

NO ITS NOT

11:42

ITS A NUMBER ROUNDING ERROR THAT GIVES INSANE NUMBERS

11:43

Y YALL MAKING NONSENSE TRYING TO LOOK LIKE YA KNOW SMTH

11:44

it even can be easily replicated with right setup

isn't it used for some skips

11:48

and even some maps

ᗰaksym

NO ITS NOT

It is

ᗰaksym

Y YALL MAKING NONSENSE TRYING TO LOOK LIKE YA KNOW SMTH

Go read the code yourself before telling me that I don't know what I'm talking about Everyone who knows a good bit about the game knows what velramp does

Cammodude

and even some maps

makes me want to play around with hilarious velramp tunes

ᗰaksym

ITS A NUMBER ROUNDING ERROR THAT GIVES INSANE NUMBERS

Wait till you find out some map setups won't work if you move it's x axis ~500 blocks because of rounding errors greenthing

@ᗰaksym do you have the map file

meloƞ

Wait till you find out some map setups won't work if you move it's x axis ~500 blocks because of rounding errors greenthing

It can be 1 tile

12:39

Source: my map

risu

Feature, not a bug :) Basically, half-intended behaviour. A result of a feature that never expected the player to move that fast

i wouldn't call it half intended

louis

i wouldn't call it half intended

The lower half of the velramp is intended, the upper half you're never meant to reach :)

And if you want to simply disable velramp wackiness in your map it's as simple as tune velramp_curvature 1

that looks like speeders with the limit because those break a lot

♂S1mple♂

Source: my map

meloƞ

Wait till you find out some map setups won't work if you move it's x axis ~500 blocks because of rounding errors greenthing

so it is a bug, huh?)

ᗰaksym

so it is a bug, huh?)

Completely unrelated issue

14:02

That is, rounding errors exist in the game, but what you experienced isn't due to one

The speeders give you far too much speed, the velramp is designed in a way that the faster your lateral speed is internally, the slower your real lateral speed will be. So speeder sets your internal speed waay too high, after the velramp that becomes 0. As your internal speed starts decreasing the effect of the velremp eases off, and you start moving faster, until you get to the peak speed then your speed starts behaving as one would expect with your internal speed matching your speed after the velramp

14:15

Is it a bug? Maybe of the map, the way the velramp was designed is a bit of a shame, it is an attempt to cap the lateral speed but not a great one. It’d have been better if proper drag (which creates a terminal velocity) was used instead of this weird stopping behaviour. Or an “accelramp” that applies to the acceleration rather than velocity (which mimics drag tbf). Is the velramp a bug? Not really, it’s an old design decision that assumed no one would ever go fast enough to hit the end of the ramp where they stop (edited)

Honestly now that I think about it disabling velramp when you're making a map seems like a pretty good idea

14:18

allows you to map very fast parts without worrying about weirdness

It might have unintended consequences, it'll basically uncap velocity

Learath2

It might have unintended consequences, it'll basically uncap velocity

Well yeah, you'll have to make the map with that in mind

isnt the clip in the video also because of bad speeder code? not only bad velramp code, but a speeder bug

louis

isnt the clip in the video also because of bad speeder code? not only bad velramp code, but a speeder bug

I think the speeder code is fine, it just adds speed, the tee just behaves weirdly at those speeds

14:27

I guess you could consider it a "bug" that the speeders are allowed to add that much speed

that looks like the bug where a speeder with max speed property will shoot you upwards if you're on the side of a block though, when it seems absurd for it to do that

14:29

or maybe not, it's hard to tell without entities

risu

Well yeah, you'll have to make the map with that in mind

well current collision check code is unprepared for way too high velocity

zhn

well current collision check code is unprepared for way too high velocity

Can you even go through solid tiles?

Guys does someone know why my points are higher on the ddnet webstite then in game?

Refusing

Guys does someone know why my points are higher on the ddnet webstite then in game?

sometimes databases are out of sync.. simply wait 1-2 days

Jupstar ✪

sometimes databases are out of sync.. simply wait 1-2 days

ok ok, i just finished map and the points were added in game at my lower points. i think they gonna add at the points i have on the website?

yes

louis

that looks like the bug where a speeder with max speed property will shoot you upwards if you're on the side of a block though, when it seems absurd for it to do that

i agree that there's also a literal bug with speeders when a tee is aside a wall and either pushes a or d, it results in a division by 0 of the speed vector which gives INT_MIN on x86, resulting in the tee going up and left

risu

if it's killing performance that's very sus

yeah but there's 1 more guy here and when it's 1 hook that doesn't move the lag is barely noticeable (still there), when it's 4 hooks that move constantly it causes big lags (edited)