DDraceNetwork - developer

update to 16.2.2 failed: and ddnet gives this : "Can't continue to execute code, because object libcurl.dll not found. Reinstalling the program could resolve it"

01:04

took the dll from https://ddnet.tw/downloads/DDNet-16.2.2-win64.zip and works without issue so update for some reason couldn't download that dll

can there be a ddnet.tw/releases/novice page for example

04:21

to see all the novice releases sorted by time of release

louis

can there be a ddnet.tw/releases/novice page for example

https://ddnet.tw/ranks/novice/

that only goes down a handful of recent releases i believe

oh that makes sense

can someone clarify 0.7 and 0.6 please

04:40

what version are we on now

04:41

i mean the first instinct would be to say 0.7>0.6 but i heard that its the other way around and that 0.7 is referred to teeworlds 0.7 (edited)

0.7 is the Teeworlds client 0.6 is the DDNet client

04:48

at least i think

06:51

hi there crisis my old friend

06:51

https://www.bloomberg.com/news/articles/2022-07-11/euro-plunges-to-fresh-two-decade-low-as-dollar-runs-rampant

@Ryozuki "0.7 is the Teeworlds client 0.6 is the DDNet client" is that correct?

ddnet uses the 0.6 protocol yeah

protocol?

the way client and server comunicate

06:56

when tw updated to 0.7 they decided to break it so its not compatible

sixup too

and ddnet stayed

06:56

at 0.6

oh ok

ah client

is that like a general protocol or is it only in the scope of teeworlds/ddnet ?

tw

@bluesky tw, they released 0.7 with the main idea to fix some vulnerabilities about the netcode

06:57

that's how they broke 0.6 compat

okay so if i got that right, the client versionnumber isnt the same as the 0.6 or 0.7 protocols (edited)

06:58

two different things but still used together?

wdym "still used together"

i mean like they both are version numbers but for 2 different things

06:59

16.2.1 uses 0.6

06:59

?

DDNet in general uses 0.6, only server side supports both versions to allow 0.7 players to join DDNet servers

06:59

Only teeworlds switched on 0.7, not DDNet

ReiTW

@bluesky tw, they released 0.7 with the main idea to fix some vulnerabilities about the netcode

okay okay

https://twitter.com/ianlauerastro/status/1546625603641790465

Ian Lauer (@ianlauerastro)

HUBBLE vs JWST: Here's the difference. Welcome to a new era of astronomy.

Likes

120839

Retweets

23578

ReiTW

DDNet in general uses 0.6, only server side supports both versions to allow 0.7 players to join DDNet servers

because if someone uses tw, they will probably use 0.7.5

07:01

okay now i got that whole seventosix thing too

07:01

thanks ^__^

bluesky

because if someone uses tw, they will probably use 0.7.5

yes but they can still play on DDNet thanks to sixup, until DDNet decides to stop that compat

ReiTW

yes but they can still play on DDNet thanks to sixup, until DDNet decides to stop that compat

Awesome that this support is implemented, yet its still a pain to play ddrace with the tw client*xddd (edited)

that's why, use ddnet

@heinrich5991 https://docs.rs/libbpf-rs/latest/libbpf_rs/struct.Map.html#method.update this is an example of function I have to use

Map in libbpf_rs - Rust

Represents a created map.

07:16

the value of a map can be for example in C:

struct stats_p {
    unsigned long pass;
    unsigned long drop;
};

and I kinda need to know how to pass that in those functions

07:17

ne is OS dependant right? if yours is big endian or little

it's CPU dependent

07:23

so then you can just cast your type to &[u8]

07:23

your C struct is also CPU dependent

heinrich5991

so then you can just cast your type to &[u8]

lol is thta even psosible?

only using unsafe, but that's the way to go here

like

let stats = Stats::default();
let stats_slice = stats as &[u8];

?