The Resonance/2025-08-03/Transcript

From Resonite Wiki
Revision as of 13:28, 20 September 2025 by Hemisputnik (talk | contribs) (Add transcript (the big bad word has been censored))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This is a transcript of The Resonance from 2025 August 3.

This transcript is auto-generated from YouTube. There may be missing information or inaccuracies reflected in it, but it is better to have searchable text in general than an unsearchable audio or video. It is heavily encouraged to verify any information from the source using the provided timestamps.

00:00: and start recording.

00:02: Okay, we should be live.

00:05: I'm going to post the announcements.

00:08: Hello. Do we have people?

00:11: >> Do we have signal?

00:13: >> Is there signal?

00:15: What is this? Twitch.

00:19: >> I just ladies and gentlemen to the

00:24: resident

00:26: official resonate signal land.

00:30: Yes. Yes. It's happening yesterday.

00:35: Need to travel back in time. Okay.

00:37: Posting announcements.

00:40: Live stream. Where's live streams? There

00:41: we go. Posting live streams.

00:45: There we go. And one more.

00:49: Post.

00:51: Okay,

00:52: we should be live. Uh

00:57: odd announcements are out.

01:00: Do we audio? Okay. Hello everyone. Oh my

01:02: god. We got audition.

01:05: Hello. Hello grand. Hello Iceland. I

01:09: don't see Iceland Jon. Hello.

01:14: Welcome.

01:17: Also going to open my documents since I

01:18: already see a schnooped. Um,

01:23: so wonder

01:26: and we got typox.

01:29: Oh my god, we got the silly questions.

01:31: Hello everyone. Um, and welcome to

01:33: another episode of Resonance. I'm

01:35: Fergus. I'm Hyro. Uh, and and this you

01:39: can pretty much ask anything you want

01:41: about the Resonite. Um, make sure like

01:45: for any questions, put a question mark.

01:46: That way they're going to pop on the

01:47: thing. Uh if I curve the camera and show

01:50: you this is, you know, this is what you

01:52: look like from our perspective. And you

01:53: can see you can see the questions. I'll

01:56: put the camera way too low. Uh the

01:58: questions are, you know, popping up here

02:00: so we can kind of like pick them nicely.

02:02: Um

02:04: let me put the camera back where it was.

02:07: Um

02:08: so yeah, we've been using the Twitcher

02:11: for a while. Um but yes, um welcome to

02:15: Resonance. Um, we might be going for

02:18: like an hour or two. Um, depends like

02:20: how we kind of feeling. Um, and we also

02:23: have a number of questions from Discord.

02:25: So, we're going to go through those

02:26: first. Uh, so we're going to, you know,

02:31: wait for like some of the Twitch

02:32: questions to uh the poll first. Um, so

02:38: with that, let's get started. Like I

02:40: think we should be good. I don't know if

02:41: I forget anything important. Um, you ask

02:45: question.

02:46: We're good to go. We'll figure stuff on

02:48: the way. Uh so first question from

02:51: Discord is from Goliauni. Uh they are

02:54: asking,

02:55: do you use llinter for C#? If you do,

02:57: which one? There's some in the solution,

03:00: but I forget which ones. I don't know

03:02: off the top of my head.

03:04: >> I'm not really sure. I usually just it's

03:07: I literally just use whatever the

03:08: language server says should be the

03:10: format when I format the file. we have

03:12: like some stuff set up but uh um for

03:16: some like I know it's prime has been

03:18: like setting stuff some stuff up so I

03:21: would actually know this is this is a

03:22: good thing you know because um while we

03:25: you know we can like um you can ask us

03:27: anything about night for some questions

03:29: we might redirect you to some other ones

03:31: because probably prime is doing this on

03:32: uh Tuesday uh our team is doing on

03:34: Wednesday the moderation team do one

03:36: that's like you know 90 minutes before

03:38: this one so for this one I would

03:40: actually recommend Um, ask Robert Prime.

03:43: He's the one like who set up a bunch of

03:45: like, you know, linking stuff on GitHub

03:46: and so on. He's been working on that.

03:48: So, he can actually give you a better

03:49: answer than uh we could.

03:54: Uh, next question. I'm also going to

03:56: duplicate it because uh

04:00: it's uh she can read it.

04:03: Moving camera accident.

04:06: Um, missing is asking any updates on

04:08: Linux build. have you tested if steam

04:10: recording picks up core windows to

04:11: record video process of starting and

04:13: turned on Linux. Um I should be ready

04:16: soon. Like it's pretty much like nearly

04:18: ready for the thing. We're just kind of

04:19: polishing up a few things. Uh so I think

04:22: it's going to get merged soon.

04:24: >> Yeah, the uh the I'm currently just like

04:28: fiddling with the audio system. It's a

04:30: little bit more involved than I uh hoped

04:33: it would be, but uh it's pretty it it is

04:37: pretty it's pretty freaking close. It

04:39: like almost all works. Yeah.

04:42: >> I was how a lot of things end up being.

04:43: It's like it seems simple and then like

04:45: you get into it all you're like, "Oh,

04:46: this is actually

04:48: >> there's more." But that that's like

04:50: programming in a nutshell.

04:54: >> But yeah, it should be soonish. Um,

04:56: >> ain't that the truth?

04:58: >> For the Steam recording, like I I don't

05:02: really use that myself, so and I don't

05:04: really, so I don't know if you messed

05:06: with that or not yourself.

05:08: >> It It should pick it up correctly. Um,

05:12: I haven't tested it explicitly, but like

05:15: as long as as long as it like attaches

05:19: to the main window, it should work just

05:20: fine. I mean, you can

05:23: if if you can manage to get it working

05:25: in the current state that it's in, uh,

05:27: you could probably test it yourself,

05:29: too. Yeah, I was kind of pre you can

05:32: like test on your own, too, and see like

05:34: how it works.

05:39: Uh, next questions also from Mintshock.

05:46: Let's put this here.

05:48: I'm going to put this here so I can read

05:50: it. Uh, MRI is asking, would it in

05:53: theory be possible to have domains with

05:55: a hub and spoke model or centralized

05:58: connection? This would likely be useful

06:00: for something like concerns and stuff.

06:01: Having one lightweight domain and only a

06:04: few users, the performer and having the

06:06: stream multiple that remains with more

06:08: attendees. Yeah, there's actually

06:10: something we want to do is like having

06:11: sort of like stream only sessions where

06:15: you have like you know limited number of

06:16: people within

06:18: within like you know the world like it

06:20: doesn't get too overloaded like if you

06:21: have like you know concert or lecture or

06:23: something you don't want to have you

06:26: know thousands of people in that session

06:28: because you can't uh that's like oh my

06:32: god thank you thank you nik for the for

06:34: the for the rate um you can't like you

06:37: know have like that many people in the

06:38: actual session but you want that many

06:40: people watching so the core session the

06:42: main session like you know um is

06:45: essentially stream only so like people

06:48: um you know people can join but they

06:50: cannot interact with it like it's sort

06:52: of like you know read only which means

06:54: like the system also doesn't need to

06:55: worry about like you know two-way

06:56: interactions. It's also like just

06:58: receiving data what's happening in the

06:59: session and then you can have your own

07:02: you know friend group session on top of

07:05: that and you can sort of like think of

07:07: it as sort of like augmented reality

07:10: session. So like you know the the the

07:12: whatever like the concert like you know

07:14: or performance lecture whatever it is uh

07:17: that's sort of like the base layer and

07:20: then like your session where you can see

07:21: your friends and interact with them.

07:22: That's sort of like the augmented

07:23: reality and within that augmented

07:25: reality layer you can you know you can

07:27: spawn things you can like you know

07:29: pretty much do like whatever you want in

07:30: normal session. it's not going to be

07:32: visible to the performers and it's not

07:33: going to be visible to anybody in their

07:36: own you know session uh who is also like

07:39: watching the performance but we could

07:41: have like also had like you know limited

07:42: interaction methods for example you know

07:44: like when you upload maybe you know

07:46: that's something that gets transmitted

07:47: to the main session and then like you

07:48: know the more of the watch sessions like

07:51: you know uploading maybe like you know

07:52: there's like a visual or something that

07:54: goes on. So yes there actually that is

07:57: one of the use cases for the domain

07:59: system. um that like you know we have in

08:03: mind uh because I think this that could

08:05: be like really powerful for like you

08:07: know pretty much like you say like

08:08: performances, concerts, lectures,

08:10: anything where you know you have like

08:13: something happening and like you want

08:15: lots of people watching it but you

08:17: cannot have you know a thousand people

08:19: in one spot in one session. So this I

08:20: think is a good way of like handling

08:22: that kind of scenario.

08:29: The

08:31: next question

08:36: uh this is from Nucacon. Uh with the

08:39: recent shutdown of similar service Ne*s

08:42: would the effective loss of all data

08:43: data her as well as the fact that

08:45: shutting down service after people have

08:46: paid to use it is basically what stoping

08:48: games is about. Uh what is the plan for

08:51: if Resonite ever has to shut down? uh

08:54: would you release source code so we can

08:56: run it like a version which doesn't uh

08:58: have that concern by design. Would we

09:00: have time to get all of the server?

09:03: Maybe some way to convert code into web

09:04: assembly or something so they can run in

09:06: over.

09:08: Um, so there's like multiple things in

09:10: this one. Uh, one thing I'm going to

09:12: mention, you can already download all of

09:14: your data uh with the Resonite

09:16: installed. There's a utility and

09:18: everything you have saved in your cloud

09:21: uh you can download, you know, and store

09:23: like locally for backups, you know, for

09:24: future whatever might happen. Um it's

09:27: kind of hard like to answer like some of

09:29: these things because like uh you know

09:31: we're not anywhere close of even

09:34: thinking you know about shutting down

09:36: like that's like would be have to be

09:38: some kind of catastrophic scenario. Um

09:41: however if that were like a possible

09:43: threat like I feel like we would like

09:45: look you know for ways how can we keep

09:46: this running. Um it can already like you

09:49: know run a bit like you know with the

09:51: headlesses where can like host things.

09:52: So like we already have that sort of as

09:54: part of the architecture and I think we

09:57: would probably like you know just put a

09:58: little more work into making sure that

10:01: like it can kind of remain as community

10:03: around you could like you know keep

10:04: hosting it like on your own and maybe

10:06: keep it going but before we would even

10:08: get to that point like we will we will

10:10: definitely look for ways to like you

10:11: know keep the project going without

10:13: having to like actually shut down. So um

10:18: there would be like you know a number of

10:19: stuffs that were happen before that but

10:21: if it came to something like that like

10:24: we I would like I I hate like losing

10:26: stuff you know like and people like

10:28: losing their own stuff. So would

10:31: definitely do something to make sure

10:32: like you can keep like your stuff like

10:34: running. Um it would definitely not be

10:37: converting code to web assembly because

10:39: like um that's

10:43: near impossible in terms of complexity

10:45: and especially like you know to run it

10:46: in another engine like you would still

10:48: run within the same engine. Um

10:51: but like we would like look for ways to

10:53: kind of you know keep things going like

10:55: and keep them community hosted. Um I

10:58: would not want you know like I would not

11:00: want this to disappear but we already

11:03: like you know

11:05: um before hard to kind of keep like you

11:06: know the community going. So I don't see

11:09: us getting to that point right now. So

11:13: hopefully we want to ever like get there

11:15: but yes like we would definitely

11:17: consider like you know some stuff like

11:19: um to be able to keep running things

11:21: locally.

11:26: Next question.

11:30: Oh, that's the same one. I think I threw

11:32: this one twice. Um,

11:40: the next question is

11:44: from uh Papine.

11:46: Popin is asking, "I have tried loading

11:48: into sessions that other users have

11:50: posted using unmarried worlds from

11:52: Ne*s." What?

11:55: So the assets never properly load. I'm

11:59: surprised it loads as much as it does.

12:01: My question is what do you think are

12:02: main cons of bitro in those worlds? I

12:04: know can auto update assets to the

12:06: latest version. So why might these

12:08: assets in have issues updating? I don't

12:12: know what you mean by unmigrated worlds

12:13: because if they're not migrated then how

12:15: are you opening them? Like I I don't

12:18: understand.

12:19: >> Yeah. If the world exists here then it's

12:21: migrated like

12:22: >> Yeah. This like here has this been

12:23: migrates

12:25: >> like that. It doesn't just like take

12:27: half the assets in the world and migrate

12:29: them. If there's if if there was any

12:32: reference to an asset URL in the world,

12:35: it's going to have been sucked over to

12:37: Resonate.

12:39: >> Yeah, sure. Like like when you migrate

12:40: stuff like it should import everything

12:42: like that's contained there. So I don't

12:44: quite I'm sorry. I don't quite

12:46: understand like what you're asking. You

12:48: might need to like uh send a

12:50: clarification.

12:58: Uh let's see. Next question is also from

13:02: Papine. I've been trying to better

13:04: understand semantic difference among

13:06: different sources. Source, changeable

13:08: source and reference source. the best

13:10: mental model I currently have. I think

13:12: about them as our source and all others

13:15: values like from C++ but doesn't really

13:17: work because you can write the sources

13:19: but not changeable sources. How do you

13:21: describe difference among them? Do you

13:23: have any analogies to other programming

13:25: concepts or is frogs engine just very

13:27: different in this way? I think it's like

13:30: its own thing. So like it might be kind

13:32: of hard to like make analogies. Um

13:35: essentially like whether you can write

13:37: or not into source depends you know you

13:39: you can write to sources that represent

13:41: some kind of value or reference because

13:43: like you know that's something you can

13:45: implicitly write to uh you can put like

13:47: source to value and it can be like I

13:49: want this value to be something

13:50: different changeable source that's it's

13:53: like more generalized so it's like

13:55: supports anything that essentially can

13:58: trigger changes um

14:02: so but it doesn't like necessarily allow

14:04: writing. So like that could be something

14:05: like you know like a component uh

14:08: because the component it can change like

14:10: you know stuff and it changes and you

14:11: want the events to like trigger based on

14:13: that but you cannot write to it because

14:14: like um the component itself is not

14:17: implicitly writable and reference source

14:19: like is pretty much the same thing. It's

14:20: just for reference references instead of

14:22: like you know values because we have

14:24: like values this like you know like

14:26: floating point like numbers you know

14:28: integers vectors matrices strings and so

14:30: on. There are sort of like atomic values

14:33: and we have like references that

14:34: reference something else but uh both of

14:36: them like you can vize too because you

14:38: can change either what the value is or

14:39: you can change what the reference

14:41: references to. uh the changeable source

14:43: that's like you know like I mentioned

14:46: it's sort of like a we almost call it

14:48: like super set where like it it it

14:52: triggers when something changes on your

14:53: source but it's not something that does

14:55: all over writing

15:01: this kind of helps a bit. Um,

15:07: next question

15:09: with uh from Triple Helix. Uh, with all

15:11: the drama happening right now

15:12: surrounding the online safety act, how

15:14: does AMS plan to address the issue? Do

15:16: you think like Steam? Uh,

15:21: sorry I missed uh a things like Steam,

15:23: Discord, and many other online services

15:25: in the UK. And there are talks of doing

15:27: the same here in the US. Uh it seems

15:29: these laws aren't just targets

15:30: specifically uh not safe for content but

15:33: any adult content in general things like

15:35: drugs, drinking, violence and users uh

15:38: having the ability to interact with each

15:39: other and since there are plenty of

15:41: things to drink and smoke but and since

15:44: there is a night and the whole thing is

15:46: social interaction collaboration, you're

15:48: not quite safe from fallout of all of

15:50: this. Um all I can say on this one is

15:52: like you know it's this is more like of

15:54: a legal thing and we've been kind of you

15:57: know evaluating this and discussing

15:59: this. Uh but right now we don't have

16:00: like any announcements on the specific

16:02: kind of handling. It also depends you

16:03: know on the specific laws how they're

16:05: implemented how they apply to content

16:06: because like you're mentioning you know

16:08: stuff like drinking and smoking and we

16:10: haven't really seen it being applied

16:11: like for stuff like that. There's not

16:13: really stuff that happens like super

16:15: commonly. We have like you know

16:16: guidelines against like certain content.

16:17: So it's like um

16:21: like it's it's it's a bit of a comp like

16:23: there's not like one

16:25: I feel like one simple answer to this um

16:29: like it's going to depend you know the

16:30: specific law how it's implemented what

16:32: are the requirements and like uh how

16:34: this kind of you know affect different

16:35: things. So um but we kind of like you

16:38: know we always kind of treat these

16:40: things like uh

16:43: we sort of like figure out like

16:44: internally like you know like what's the

16:46: best way to handle it before like we

16:47: make any announcements.

16:54: Uh next question is from missing. Uh oh

16:59: ifs and sire have been told they are

17:01: wonderful people that bring happiness

17:02: and hope to many people around the globe

17:04: today. Also, did you drink enough water

17:06: today?

17:07: >> Oh,

17:10: I had some water. Thank you.

17:14: >> I have enough water right here.

17:17: >> I I made tea and then I had some soda.

17:22: I think the tea is closer to water than

17:24: the soda is.

17:26: But I only had like small cup of soda

17:27: and I had like this much tea.

17:30: >> I think your water ratio checks out.

17:33: Yeah.

17:36: Oh, next one is uh this one's very very

17:40: very long. Um probably not going to read

17:44: like the whole thing. Like it's um it's

17:47: a lot. Um

17:51: I'm just going to kind of skim skim

17:52: through it. Uh and choose asking might

17:57: we sometime in the future see a huge hub

17:59: world like old platform like rival or

18:02: like2

18:05: I have experience having such space in

18:07: social VR the first landing spot for

18:09: public interaction on platform if you

18:12: will especially for platform like this

18:14: so nice to find community basic

18:15: immediately especially a world that is

18:17: designed to show you more places to go

18:20: um

18:22: I'm just going to like

18:25: I I would probably like like keep the

18:27: questions like maybe one paragraph. This

18:29: is like a lot. Um

18:33: like most platforms prefer

18:37: um so seems to be like asking about like

18:40: you know like having like a hub port and

18:42: it's like something we do um

18:47: we do.

18:51: So like we've been kind of talking about

18:52: like you know having like something like

18:53: interior to the home and like being able

18:55: to get to the places. I feel like the

18:57: main thing with those is like hosting

19:00: sessions because like the biggest

19:02: problem with those is like you know

19:04: everybody starts their own session of

19:06: the hub and then it's like you know it's

19:07: not very

19:09: community based. So like what I think it

19:12: needs is just you know hosting some

19:13: public sessions so people can actually

19:15: meet and mingle there. Um, and I don't

19:18: know if it's like necessary to like, you

19:19: know, it needs to be the hump. Um, it

19:23: could be like, you know, like like a

19:24: bunch of other worlds, but like maybe it

19:27: doesn't like be cool like, you know,

19:28: having like official kind of like hubs

19:30: and events and so on, but also like it

19:32: kind of brings the issue like, you know,

19:36: how do

19:39: um

19:41: how do you like, you know, essentially

19:42: moderate that session? because if it's

19:44: something that's running out 24/7, you

19:46: know, people might end up like messing

19:47: it up. So like you might need someone in

19:49: there to kind of like you know make sure

19:52: you don't go like too haywire. So it

19:54: kind of creates like you know some

19:56: problems like that. Um

19:59: the other part is like you know like we

20:01: found like people might be confused by

20:04: those worlds a bit because like they

20:05: know they will enter the hub and they'll

20:07: be like this is like empty and people

20:10: also don't want to like you know

20:11: necessarily

20:12: go like when they want to explore worlds

20:14: like you know they

20:17: like one of the reasons like you know

20:18: like implemented like UI actually browse

20:21: worlds is because that seemed like what

20:22: people generally kind of prefer what

20:24: they find like simpler to use. So, it's

20:27: one of those things where like where

20:29: there's like certain concepts like in VR

20:32: uh that I feel are cool, but they also

20:35: because they're different that they're

20:36: new, they create like a barrier and that

20:39: can kind of hurt the overall like

20:41: adoption. I've kind of run into it like

20:43: with a number of different projects in

20:45: the past like where

20:47: um I would try something new and was

20:49: like you know cool and like cool way to

20:51: use VR but it would just confuse people

20:53: because like they would have to learn it

20:55: and people really don't like learning

20:57: new stuff like they like using stuff

20:59: that's familiar and it's crazy like you

21:01: know this kind of like

21:03: back pressure like you know almost like

21:05: pressure against innovation and trying

21:08: different things so it can be

21:10: challenging and I feel like like

21:12: eventually like we'll probably have like

21:13: you know something like have like event

21:16: sessions and other things and that would

21:18: be kind of cool to bring that concept

21:19: back but like right now I I don't know I

21:21: don't know if like the bandwidth for

21:22: that

21:28: uh I got one more from Discord

21:33: I uh I got out the name but I think it

21:35: was also from true

21:38: um

21:40: sorry for so much What's super question?

21:42: I want to make virtual maker space in

21:44: there hosted on headless for my local

21:46: maker space. I want to make a project

21:49: bulletin board meeting room presentation

21:51: space etc. I want to build grid

21:53: seamlessly integrated in the same space

21:55: but I don't want everyone to crash or

21:57: lag based on what is going on in the

21:58: build grid. Build bubble overlay wall

22:01: system allow me to run build grid a

22:03: separate session and overlay into market

22:06: space session. So if it crashes and gets

22:07: lucky it can just restart on its own.

22:10: get other people can leave B session but

22:12: everyone stays in maker space. Um there

22:14: will be like the domain system. Uh but

22:17: it kind of depends on what causes the

22:18: crash.

22:20: So if it's something you know that's

22:22: within like isolated within the session

22:24: then yeah like it will be just be the

22:26: particle session that goes uh and the

22:28: canary starts but if it's something you

22:29: know say crashes the render um then the

22:33: render like you know we have to restart

22:35: which like you know once splating is

22:37: done like we should have that ability.

22:39: uh implemented you know sometime shortly

22:41: after. Um but if it's like you know

22:45: something that crashes the core engine,

22:47: oh thank you and thank you for the def

22:50: tool uh for the subscription.

22:54: But yeah, uh since it's um

22:58: um

23:00: what I was going to say,

23:03: um

23:05: since it's like um

23:07: if it's like an old engine crash that

23:09: just crashes the core engine, you know

23:11: that the whole thing goes down. So it

23:14: depends

23:15: depends like you know what the crashes

23:19: and usually like you know approach is

23:20: like eliminate as many crashes as

23:21: possible.

23:23: So with this, this is all the questions

23:26: uh all the questions uh

23:30: from this course. We can start going

23:32: through the Twitch ones. And first we

23:34: actually got Grand is back with this

23:37: schnoit. And I do actually have a list

23:40: of those. So I'm going to pick one. Um

23:46: uh still want something lighter.

23:54: So, I'm actually going to this one.

23:57: I have I have I have a list.

24:00: >> Oh, boy.

24:02: >> I I have a list.

24:05: Okay. So, I'm going to um I'm going to

24:08: pick this one. So, one of the one of my

24:10: kind of snippets um one of the things

24:12: like you know um that I run into.

24:17: So, V like you know we like to do like

24:19: very kind of open development. post

24:21: frequent delogs, you know, like you get

24:23: to see like stuff like very very very

24:25: early on. Um,

24:28: you know, and like even tested like you

24:30: know, during the development and a lot

24:32: of companies will not do that, you know,

24:34: they'll keep everything under the wraps

24:35: until like everything's tested and

24:37: ready. And generally like we try to

24:39: like, you know, we want to be more open

24:41: with the development like see like, you

24:43: know, peek under the hood. This is how

24:45: stuff is made. this is how it kind of

24:46: looks before like it normally becomes

24:49: visible to other users. Um and generally

24:52: I feel like there's actually like it's

24:54: mostly beneficial for us to do that. Uh

24:57: however in some cases like we kind of

24:59: run into like where people will kind of

25:01: jump to conclusions. They'll like you

25:03: know start judging things like way too

25:05: early in the development when things are

25:06: you know not finished. Um and you know

25:10: and they start like you know panicking

25:13: about some things and so on. And very

25:15: like you know happened like where um for

25:18: example with the splitting the very

25:19: early versions like they used the JSON

25:22: for like you know the serialization and

25:23: it was pretty much done you know for a

25:25: debugging reason uh and like you know

25:29: and to get like you know bootstrap the

25:30: initial implementation as fast as

25:32: possible and start iterating on it. But

25:34: people are like why using JSON that's

25:35: not good for performance you know and

25:37: they started like people started

25:38: panicking and I heard from like number

25:39: of like people that like you know people

25:42: are like getting concerned and so on and

25:44: and it's just kind of like

25:47: things in development like you know they

25:48: will graph and there'll be like weird

25:50: stuff. The other part is you know we

25:52: also had like you know people like they

25:54: would be like you know watching like be

25:55: like oh like like when when I make a

25:57: video they'll be like oh like why is

25:58: that like you know frame rate so low you

26:00: know and it's like literally I have like

26:03: you know a bunch of debugging stuff

26:04: there's a bunch of bugs happening you

26:06: know there's like lots of stuff but um

26:10: it can be hard because sometimes I know

26:12: people just kind of see something and

26:14: just immedately jump into conclusion

26:17: um

26:19: and it's kind of like that it gets a

26:21: little bit hard to deal with and kind of

26:22: like you know and whenever that happens

26:24: I'm like kind of makes me not want to

26:26: share like stuff like that's too early

26:29: because I'm like you know like I get

26:30: worried like you know how will people

26:32: react to this like because it is you

26:34: know unfinished

26:35: um and I'm worried like you know will

26:38: people like jump to conclusions will

26:39: they like you know panic will they like

26:40: you know start spreading like rumors

26:42: about it because like um because usually

26:46: in during development things are going

26:48: to be in their rough state before they

26:49: get polished. Ed. So that's like one of

26:51: those things and even despite that like

26:54: it was still kind of keep like

26:55: publishing things early and so on. But I

26:57: it makes me kind of understand like you

26:59: know why the bigger companies don't do

27:01: it because like I feel with a lot a lot

27:03: of companies like you know once that

27:04: happens if it happens once the company

27:07: will just like you know they get spooked

27:10: and they just don't do it again because

27:12: like they they want like you know they

27:14: want to eliminate every single for

27:16: subscription because the component want

27:19: to eliminate you know every single

27:22: possibility of like negative like

27:24: perception. So like they see it happen

27:26: once they'll just be like you know we're

27:27: not doing that ever again. Um and that's

27:29: why I feel that's like one of the

27:31: reasons why you don't see a lot of

27:33: companies do it. Um and we also you know

27:35: I want us to be different like I want to

27:37: look like you know way things be like

27:39: yes there's some like negatives with

27:41: that. Um but also like you know we have

27:44: the positives of like you know being

27:45: transparent for the development. I feel

27:46: that kind of helps like you know

27:48: generally build like you know trust in

27:49: the community build like you know more

27:51: transparency for development process and

27:53: get a lot of like very early feedback uh

27:56: from everyone which helps like with

27:57: iteration process. So that's kind of

28:00: like my my main thing is you know just

28:03: be careful about like especially when

28:04: it's development stuff be careful about

28:05: like you know jumping to conclusions

28:07: like you know very early on. Um usually

28:11: things will be kind of in flux things

28:13: might look like weird during the early

28:14: development. Um

28:19: it's um

28:21: and like you know like uh it's like a

28:24: thing like you know if like um

28:28: if if it's if something is still there

28:30: for example like some like major issue

28:32: and it's actually causing problems

28:35: on the release you know that's a

28:37: different thing. But if it's like

28:38: something that happens during the

28:39: development and you want to like you

28:42: know give it like more of like a not

28:44: grain of salt but like

28:48: give more benefit of a doubt essentially

28:50: during that phase. Um

28:53: so that's that's pretty much my

28:57: >> just that the just that the main

28:59: developer knows what he's doing most of

29:01: the time.

29:05: Let let us let let us cook on things.

29:09: >> Let us cook chat.

29:13: >> Do you have any schnuppet yourself?

29:16: >> Oh, dear freaks. I'm I'm so sorry to

29:19: say. I mean, no offense by this, but my

29:21: schnoid's been the audio system.

29:23: >> Oh, no. The part that actually connects

29:27: the audio coming out of Resonate to your

29:29: speakers is older and kind of scruggly.

29:34: So, it's a little bit it's a little bit

29:36: interesting to work with.

29:37: >> Thank you. Oh, I can I don't even know

29:39: how to read the name. You won F98A.

29:43: Thank you for the subscription.

29:45: >> I like your hex code, pal.

29:47: >> That's not a hex code. Is a Is that a

29:49: hex code?

29:50: >> You won You won F98A.

29:53: >> Is that a unic? That's not That's too

29:55: many byes for Unicode.

29:56: >> You is You would be too far. Yeah.

29:59: >> Yeah. Yours is too far. Unless it's like

30:00: unic code, but then it's too many.

30:02: >> Well, you basically

30:03: >> Oh my god. Thank you. No, for this we're

30:05: getting out of subscription. Thank you.

30:08: >> Oh my god. Um

30:12: uh but yeah, the uh the audio system has

30:15: been a little scruggly. It's mostly like

30:17: a combination of like it being an older

30:19: part of the code and also I'm not

30:20: familiar with the SDL audio API fully

30:23: yet. Um, like it should be pretty

30:26: straightforward, but for some reason,

30:29: uh, whenever I like hit a lag spike, the

30:32: audio just all stops forever for some.

30:35: And I don't know why. I'm trying to

30:38: figure out why. And so that's been my

30:39: stop for like the past 3 days.

30:42: >> I mean, audio in general is like bit

30:44: painful. Like you have to like like

30:46: every time I work with it, it's like you

30:47: know you have to carefully like you work

30:49: on it or get things working. You have to

30:50: spend a lot of time carefully balancing

30:52: things and you balance them so it works

30:55: and then you like every time I feel like

30:57: I'm like like not I don't want to touch

30:58: it. If somebody wants like a minor

31:00: change I'm like unless like

31:02: >> I don't want like you to upset the

31:04: balance of it.

31:06: >> So like every time I'm like I have to

31:07: like work on it to do something. I'm

31:08: like oh my god thank you Jake. Thank you

31:10: for the bit. Oh my god we're getting so

31:13: many today.

31:16: But yeah, now the aside from the like

31:20: issue like with the audio networking

31:22: though, um it is like the SDL audio

31:25: system is actually pretty good. It even

31:26: handles like sample conversions for you.

31:30: So like

31:30: >> you can open a device with that ex

31:34: that's supposed to accept like you

31:37: samples and it will just autocon convert

31:39: floatingoint samples into the proper

31:41: format for the device. I mean CS score

31:43: is meant to handle that too. Problem is

31:46: that code makes unit crack. So like we

31:49: had to like we have to make our own

31:51: conversion for it. And maybe maybe it

31:53: would work with like now that like you

31:55: know with 9 but um

32:01: since it was done on Unity like we

32:03: already have like on conversion so it's

32:04: like you know

32:06: >> Yeah, I saw I saw we have we actually do

32:08: have our own resampling code. Yeah,

32:11: >> and we kind of need it too because like

32:12: we need internally for things like when

32:15: we for example playing audio clip that

32:16: needs to get mixed at the actual audio

32:18: system rate. uh we need resampling

32:21: playing anyways

32:23: but it's also like bit conversion like

32:24: you know because like sometimes the

32:25: audio device will you know it will be

32:27: like actually it was kind of really

32:29: weird because CS code will say oh this

32:31: audio device it supports you know two

32:33: channels at 48 kHz with 32bit bits

32:37: floatingoint samples and you open it

32:39: with that format and the audio device

32:41: like oh my god thank you for cheer

32:43: >> thank you

32:45: >> and then like you know then you open the

32:47: audio device you say like yeah I want

32:48: this format format that you said you

32:50: support and they would adise like oh

32:52: actually never mind I support it like

32:53: you know only in this format and like

32:55: that's like with CS score would be like

32:57: you know okay I'm going to insert like

32:58: you know conversion for the for oh my

33:00: god

33:00: >> holy crap

33:01: >> what is happening

33:04: dying

33:06: I I oh I was too slow I was too slow

33:10: thank you beauty so many

33:14: >> holy crap

33:15: >> there was there was so many conf

33:18: there was So many confetti.

33:20: >> Sheesh.

33:20: >> Oh, when I took photo by accident.

33:22: >> Oh my gosh, the whole stream's falling

33:24: apart.

33:26: >> Oh,

33:27: >> but yeah. No, that's the uh that's the

33:29: nice thing about SDL is it doesn't

33:31: really care what the device supports. It

33:33: will just convert whatever samples you

33:35: give it cuz you you designate the input

33:37: format and it'll just do it.

33:39: >> I kind of most audio systems from what I

33:41: found out. Like this like one of their

33:43: functionalities.

33:45: Um, it's just, you know,

33:48: Unity doesn't really like that code.

33:51: >> Ah, yeah.

33:52: >> It just crashes. So, that's why we have

33:54: to write our own.

33:55: >> At least STL seems to be one of the ones

33:57: that actually works.

33:59: >> I Well, I think like I don't think it's

34:01: actually CS like because CS score like

34:03: it also works. It's just units install

34:07: just some code.

34:10: Well, I mean,

34:11: >> that's why I'm like, you know, this is

34:13: this is it's a usually it's functional

34:16: to find in those audio engines like this

34:18: one of their purposes is, you know, they

34:19: kind of abstract you away from that. But

34:21: because we're running, you know, code

34:24: within Unity and like it just it doesn't

34:26: like stuff.

34:27: >> I don't know. I don't know if I mean I

34:30: can also I won't I won't linger on this

34:32: question for too long but uh

34:35: I can also uh I don't know if I can

34:37: entirely blame Unity because CS cores

34:39: internals are like yes a function call

34:42: that takes a pointer that dreferences

34:43: like a pointer to a pointer that is like

34:46: an int pointer to another like structure

34:47: that they've offset by five for no

34:49: reason um that's like invisible and like

34:52: >> it's probably very soon but like it

34:54: should still work like I think it's like

34:56: you say just in general it doesn't like

34:58: calling to some like system like com

35:00: devices and so on like it just doesn't

35:02: work with that. I'm not saying like you

35:05: know it's well written in CS core but

35:07: like

35:08: the way the code is like written is like

35:10: one thing and the way like you know if

35:12: it supports like some core things that's

35:13: like a separate

35:15: >> well you know like the pointer that

35:17: dreferences like a pointer pointer to to

35:19: a void star to an in pointer to like a

35:22: function call that like returns

35:24: >> oh my god

35:24: >> that returns like an opaque structure

35:26: pointer that they've offset by like 17

35:28: for no reason. I mean that's the the

35:31: thing is it's bad but it's bad for

35:33: humans because like for humans it's

35:35: unreadable but like for for like for

35:37: actual runtime like it technically

35:39: works. It's all fully version but it

35:41: works.

35:42: >> It makes me cry.

35:44: >> It's it's bad.

35:47: >> Sure that can be my [ __ ] CS core is my

35:51: >> Yes. And that's also my

35:55: cutest subscribe monster play.

36:04: Oh my god, there's so many.

36:07: There's so many. I'm going to keep

36:10: missing it. What is happening? Why is

36:12: there so many today? I mean, there we

36:14: go. There we go.

36:15: >> Jack, you got to make it so that like if

36:17: people spam the thing in quick

36:19: succession, like the amount of confetti

36:21: is like quadratically proportional to

36:24: >> Oh my god, we'll die. Do you know how

36:25: fast that goes? Thank you, Gala, for the

36:27: subscriptions.

36:35: >> Oh my god, you work for us.

36:37: >> We'll do a factorial of uh how many uh

36:40: things are sent in a row.

36:43: >> I have like a thing that like that just

36:44: moves the camera because there's so many

36:47: there's so many

36:50: there's so much support.

36:52: >> So much. You know what? You know what?

36:57: I'm going to cheat.

36:59: Tongs, all these subscriptions. Thank

37:02: you so much. I didn't expect like this

37:04: money today, but um

37:06: >> thank you.

37:07: >> I was I was I was

37:09: >> they're giving their energy for the

37:11: spirit bomb.

37:12: >> My god.

37:14: The thing is the thing is uh I was

37:18: actually like even almost like cancelled

37:20: it today because I wasn't feeling so

37:22: good and I like like get all these

37:23: subscriptions. Thank you.

37:25: >> Yes. Thank you very much. We uh we do

37:28: not regret can not canceling anymore.

37:31: >> Yes.

37:34: Thank you. That's my That's my DS.

37:37: >> Yes.

37:37: >> I took it more.

37:42: I I I have a list for those two, but I

37:45: also write more.

37:46: >> I I

37:49: >> my Tox I guess I could say is also

37:52: related to the uh the audio system

37:55: because I just like SEO as like an API.

37:59: It's just a nice

38:00: >> Oh my god.

38:01: >> Oh my god.

38:04: >> So many [ __ ]

38:06: >> I have I have a thing. We we need Oh my

38:09: god.

38:11: Mhm. We need we need like a

38:15: we need a thing that allows us to move

38:17: where the confetti happens. So we can

38:19: move the confetti like you know

38:20: somewhere in frame.

38:23: >> Yes. Oh my Oh my god.

38:25: >> Jesus Christ.

38:26: >> Oh my god. It's so many.

38:30: >> It's so many. Thank you.

38:34: >> We need to turn the sticky notes into

38:36: dollars.

38:39: What is What is What is today's stream

38:41: is? Oh, and I messed up the camera. Uh,

38:48: >> wait. I have a I have a What? What if I

38:51: just do this? I'm just going to put one

38:54: I'm going to put another one. Actually,

38:55: let me turn the audio off.

38:58: >> Turn off all the effects on this one.

39:00: >> Yeah. No, no, no, no. I want the

39:02: effects. I want the

39:05: like I want I just want like Okay, I'm

39:07: going to put it here. It's right below

39:08: us. So, like if you if this happens

39:10: again, like we'll get showed in

39:11: confetti.

39:13: >> There we go. See, it works.

39:15: >> Oh my gosh.

39:16: >> Oh my gosh.

39:17: >> Oh, it's going to happen like twice now.

39:19: >> Yeah.

39:21: I mean, it's it's an incentive.

39:25: >> We got like way more than like I would

39:26: expect us to get, but uh more incentive.

39:30: >> Thank you. Anyways,

39:32: >> my ta punks is uh the SDL API. I just

39:37: kind of like it. It's a good like common

39:41: interface. You keep taking pictures.

39:43: >> Yeah, regular but sorry.

39:47: Um, it's just a good common uh

39:50: crossplatform interface that's well

39:52: written and it's fast and also I'm

39:54: pretty sure that it's if I'm not

39:56: mistaken

39:59: uh

40:01: is it what I think it is click

40:05: and it's distributed under the zib

40:07: license which is basically like you can

40:10: like do almost whatever you want with

40:11: it. So it's it's cool.

40:14: >> This was very neat. I like this like

40:16: like obstructing the clipboard too. So

40:18: like we'll actually have like proper

40:19: clipboard support on different platforms

40:21: because it's been like one of the things

40:22: that's been hard to find is like

40:23: multiplatform library.

40:26: >> It's just good.

40:28: >> Yeah. Yeah. Thank you for the tool for

40:30: the for the bits.

40:33: >> So many bits. One cent. Thank you.

40:38: >> We're going to we're going to leave it

40:38: at one bit for now.

40:42: >> Yeah.

40:48: Grand K is asking

40:52: uh if you could be a bird, which bird

40:54: would you be and why?

40:59: >> I'm happy as if it was a space fox sort

41:01: of thing. If I had to be a bird, I would

41:05: probably choose either a raven or a

41:11: I think it's like a starling or

41:13: whatever. Um cuz both of those birds

41:16: have extremely talented um

41:20: noise replication abilities. like the

41:23: >> like the the styling in particular, I'm

41:26: pretty sure um

41:28: is like if you give it no like if you've

41:32: seen the video recently of like I store

41:34: a picture in a bird

41:36: on a bird.

41:37: >> I want to I want to be that bird because

41:40: that that's really cool that it can just

41:42: do that. Like it

41:45: >> it can mimic the reverb of a room. Like

41:47: it's crazy.

41:48: >> Oh my god.

41:50: That's all right. Ravens are smart. Like

41:52: really smart birds. Like really cool.

41:55: There's like I remember there was like a

41:57: video of like raven like you know just

41:59: like taking like a piece of like

42:00: something flat and just Oh my god. Thank

42:02: you.

42:04: They um and they would like you know put

42:07: it on the roof and it was like snowy and

42:09: they would like just slide down and

42:10: bring it back and slide down and like

42:12: it's one of the few like cases of like

42:14: you know in Animal Kingdom other than

42:15: humans of like you know

42:19: playing.

42:20: >> Yeah. Crows have like a they have a

42:22: concept of having fun or ravens. I mean

42:25: crows are like pretty smart like

42:27: >> Yeah.

42:28: >> Those are parrots.

42:30: >> Yeah. Yeah.

42:31: >> Karros

42:33: are like from what I understand like

42:34: they're very smart.

42:36: Very annoying to people because they get

42:38: into everything but also very smart.

42:41: >> Yes. Yeah. I like I like those birds

42:44: because um they have like a concept of

42:47: having fun and like they have a con like

42:49: they will like mourn their dead as well.

42:52: So they have like a concept of loss and

42:55: I've also seen them have casual

42:56: understanding of like water displacement

42:58: which is really cool.

42:59: >> Yeah.

43:02: >> Like they put in a in like a water tank

43:05: to make the water get high enough so

43:07: they could fetch the food out of it.

43:09: >> Oh my god. Oh my god. Oh my god. Where?

43:12: Oh my god.

43:16: >> So much money.

43:17: >> So many.

43:19: >> Well, the the plan work. Thank you, Jack

43:21: the Fox. Thank you, Elephant.

43:25: >> Elephantitus.

43:28: >> Elephantitis. Elephant.

43:31: >> That's a good username. Good job.

43:34: >> Thank you.

43:36: >> Elephantitis. That's a That's a really

43:38: good username, actually.

43:40: >> You know what? You win the best username

43:42: of the day.

43:43: >> Yes, you win you win the best username.

43:49: >> I

43:52: I forgot what I was going to say. Oh,

43:54: there's like a thing is like you could

43:55: also like they have like really good

43:57: memory because there's like those

43:58: stories of people like who like they

44:00: would they would like you know feed like

44:02: like a raven or a crow. They would give

44:04: them like, you know, like a walnuts or

44:06: something and they would befriend them

44:08: and then like, you know, the raven or

44:09: the crow like they would keep bringing

44:11: them like, you know, shiny things like

44:12: gifts.

44:13: >> Oh,

44:14: >> and it's like super cool and sweet.

44:17: >> Those are cool.

44:19: >> I love intelligent animals. They're so

44:21: cool.

44:21: >> Yes.

44:22: >> Like they're really good problem

44:24: solvers, too.

44:26: It it some like I know I know they're

44:28: like still pretty far from it, but

44:30: sometimes like it just seems like

44:32: they're not that far away from just

44:34: being able to understand us fully.

44:37: >> Yeah, I feel like they do have like a

44:39: like they have like a decent like

44:41: understanding of some things. Like to me

44:43: like it feels like you know if like if

44:45: things went differently or like if if

44:46: all of us like you know humans just

44:48: disappear

44:49: >> um like there's like you know some

44:51: species where I'm like they have like

44:54: they they have a decent chance of like

44:55: you know becoming the next like you know

44:58: society species level species like the

45:00: way we are.

45:02: >> Yeah. Like crows and dolphins especially

45:04: dolphins.

45:05: >> Dolphins. Octopi. So too octop like

45:07: >> Yeah. Octopi are really octopi.

45:10: Octopi can be really sweet from what I

45:12: hear as well.

45:15: Very, very loving creatures.

45:16: >> They'll they'll form they'll form the

45:18: society underwater.

45:21: >> Yes. The octopus society.

45:24: >> The only thing I like with the

45:25: underwater is like they can't discover

45:26: stuff like fire.

45:28: >> Yeah.

45:28: >> Which is like one of the things that I

45:29: know like le like human like

45:32: >> development or just kind of curious like

45:35: how that would like work. But

45:39: I know like there's been like examples

45:40: where they've like seen like you know

45:41: they can use tools and stuff like sort

45:42: of pretty smart. Oh my god. Thank you.

45:46: Oh my god. What is it?

45:49: >> Thank you so much.

45:51: Thank you for so many tier one subs.

45:54: Holy [ __ ]

45:54: >> Thank you so much Kyobi. And I didn't

45:57: even catch the first one. It's like what

45:59: is it? An angel boy. Thank you.

46:04: >> So many.

46:05: >> Thank you. There's so many.

46:08: This is a bit

46:10: >> They're just trolling us now.

46:11: >> It is trolling us, but I have to pay for

46:14: it. It's like, you know, like that's

46:17: paying to troll us.

46:18: >> Paying to troll us.

46:21: Actually, I don't know if my frame rate

46:22: goes down if it's just the particles

46:24: when it goes up.

46:26: >> No, I think I think it's the particles

46:28: cuz it's this map is like mostly

46:30: >> synchronous.

46:32: Oh my god. Like uh this is kind of

46:34: tension but like you know like I'm going

46:36: to like on the split ending because the

46:37: particles on split thinning are insane

46:39: like we're like a test like it just like

46:41: be like in one of the worlds with like

46:43: lots of mesh colliders and just around

46:44: 30,000 particles and it just runs

46:46: flawlessly. It's like super smooth and

46:48: like it's insane like some things like

46:50: beu and particle systems they benefit

46:53: like hu hugely.

46:58: Yeah, it's it is absolutely like

47:01: I like it's so crazy to me because you

47:05: know

47:07: people I I sometimes hear people say

47:09: like oh res night's so unoptimized it

47:11: doesn't run well they need to optimize

47:13: the code but like we just got free

47:17: performance like we didn't even optimize

47:19: anything

47:19: >> I mean you know this this is the thing

47:23: I like to say I've been like writing a

47:25: lot of the code not for the runtime time

47:27: we have at the time but for the run time

47:30: we wanted to have Oh my god. Oh my god.

47:36: Glitch is so much money. Thank you.

47:41: How many is that? Jesus. Holy [ __ ]

47:47: Remember cuties. Oh my god. Oh my.

47:56: Thank you be glitch.

47:58: >> Thank you.

48:00: >> There's so much.

48:02: >> It's way too much.

48:06: >> Oh my god.

48:10: >> At least we get to, you know, get to see

48:11: us charge in the particles now.

48:14: >> Yeah.

48:15: >> But yeah, it's crazy. But like yeah like

48:19: a lot of a lot of the code like is

48:20: literally written to like you know

48:21: utilize the modern features of like you

48:25: know the modern net runs and the modern

48:27: approaches like even for example our

48:29: loading system because like people kept

48:31: saying like oh like just make it multi

48:32: multi-threaded and I'm like it has multi

48:35: threaded and one of the one of the

48:36: things that kind of keeps it slowing

48:38: down is like it the runtime because like

48:40: one

48:42: it doesn't do like because like when you

48:43: do multi thread actually puts a lot of

48:45: stress on the runtime and like it starts

48:46: making it essentially choke up. Um, and

48:50: as you know, one of the reasons like

48:51: when you're loading like it's going it

48:52: feels bad. Thank you to

48:56: um but you know now with like the

48:59: spliting everything lot super fast and

49:01: it's because and like there have been no

49:04: changes to that code like it's actually

49:06: the same code. It's just with a

49:08: different runtime and like well actually

49:09: there's a part of like for the

49:10: integration part that actually helps a

49:12: bit too but other than that like you

49:14: know the actual most of the loading code

49:16: is the same and it just like you know it

49:19: kind of lets like the donate 9 really

49:22: lets that code like you know shine and

49:25: like not kind of be constrained by the

49:26: runtime and there's also like you know

49:28: more approaches like that we'll be able

49:29: to use that like we couldn't use because

49:31: they

49:33: were not like available at all for all

49:35: the run times like for Thanks. Oh my

49:37: god. Thank you.

49:40: Um there's so many approaches.

49:44: Um

49:47: like for example spans you know spans

49:49: are like super fast but like on the

49:51: older run times they're like you know

49:52: not as fast as they're like on the new

49:54: run times like they kind of ex like you

49:55: can install them as a package for the

49:57: older run time like for mono and so on

49:59: but like you know they don't have the

50:02: jute compiler like support like directly

50:05: >> which means like you know they're not as

50:06: fast as they could be but with 9 like

50:08: they're even way way way faster because

50:10: it can like do so many optimizations on

50:12: those

50:13: >> yeah spans and stuff in like the new

50:15: runtime are incentivized for like

50:18: vectorization. So that means like the

50:20: CPU can do

50:21: >> like if you're just like you know adding

50:23: a bunch of numbers up in like a span for

50:25: example the CPU can be like oh this is

50:28: like a span I want to vectorize this and

50:30: so it can actually use special

50:33: instructions in your CPU that will add

50:36: like four or even up to eight of those

50:38: or even 16 of those numbers at a time

50:41: >> um at the same exact time. not

50:44: multi-core on one core. It can do yep

50:47: like up to 16 operations at the same

50:50: exact instruction.

50:52: >> SMID it's like single instruction

50:54: multiple data.

50:56: >> Yeah, it's like it lets

50:59: >> in short let's like you know let the

51:01: code kind of shine.

51:02: >> Anyway, I I I hope that answers your

51:04: question about which bird we could be.

51:07: Yeah.

51:14: So, next question is Jay Videns asking,

51:18: uh, have you seen any of the customer

51:20: renders people have been making? Uh,

51:21: I've seen like bits of the godo one. Uh,

51:24: I don't think I've seen any others.

51:26: >> I had like, uh, somebody was like, you

51:29: know, being like, was somebody make like

51:30: a Quake like renderer? Oh my god. Oh my

51:34: god. Oh my god. Even more. Thank you.

51:38: >> Thank you.

51:40: I've seen someone do it where like they

51:42: proxy it into Blender.

51:45: >> Yeah. Oh, I've seen that one too. Yeah.

51:48: It's been kind of crazy what people have

51:49: been doing with the split thinning like

51:51: and like I've been kind of like thinking

51:53: like you know once we're done with the

51:54: spinning I would probably want to like

51:57: Oh my god. Thank you

51:59: callatorium.

52:00: >> Yeahum

52:03: >> thank you.

52:05: We're not going to get through any

52:06: questions at this rate. Um my god um

52:10: people like you know crazy stuff and

52:12: like one thing I'm kind of thinking is

52:14: like like the I don't have like specific

52:16: plan like yet I don't want to make like

52:18: any promises but like um I've been

52:20: thinking about like organizing sort of

52:22: like more organized community effort

52:24: like for the new renderer. I've been

52:26: kind of like writing some things down

52:27: for it. So there might be a thing that

52:29: comes at some point. Uh definitely post

52:32: split thinning, but

52:37: I think I think it would be kind of cool

52:38: like you know like lean more like into

52:40: like community and like make like more

52:43: collective effort to help us like you

52:45: know

52:46: find a new render and like you know

52:49: bringing to like what we need. So

52:51: there's there might be some stuff coming

52:52: with that like once uh once the spot

52:54: goes through. but cool like seeing like

52:56: what people do with it. Uh, next

52:59: questions from Kisser Blades. Have you

53:02: seen Abiotic Factor? I know you've

53:03: bunkered down with Splitting currently,

53:05: but do you plan to play it? Curious any

53:06: thoughts? I've heard about it a bunch.

53:08: Like I've seen like some of the trailer.

53:09: It looks like really cool. Like I know

53:11: it's kind of like multiplayer kind of

53:12: thing and I know some people have been

53:14: playing it. Um,

53:16: I would maybe want to play it at some

53:18: point. I don't know what state it is in.

53:20: One thing I kind of get with some of the

53:21: games is because sometimes I'm like

53:22: really busy with a project. I don't have

53:24: time, you know,

53:26: I don't have time to play something and

53:28: by the time like I'm done, everybody's

53:30: moved on to a different thing. Like I've

53:32: had it happen I've had it happen with

53:34: the

53:35: what was this called? The the co-op

53:37: multiplayer game.

53:40: I'm completely blank.

53:42: >> I'm completely blanking on the name. Um,

53:46: what was it called?

53:49: Uh,

53:50: >> what does it have in it? It's like

53:52: called multiplayer like horror thing

53:54: that's like procedurally generated.

53:59: >> What was it called?

54:00: >> Repo.

54:02: >> No.

54:07: >> No. That was something different.

54:09: Uh I have no clue. That's a lot of co-op

54:12: multiplayer [ __ ]

54:14: >> There was like one like was like a

54:16: really big

54:18: just what was it called?

54:22: Lethal Company.

54:24: >> Lethal Company. Yes, that's the one.

54:26: Yeah. So like um this Lethal Company. So

54:30: like I know like a lot of people were

54:31: playing it and everybody was like

54:32: orgasing groups and I was like busy with

54:34: stuff and then like when I was like okay

54:36: maybe this seems like interesting.

54:37: Everybody's like already moved on to

54:38: like something else and I forget what

54:40: the like I forget what the thing

54:42: replaced it but like

54:43: >> but it's kind of like what happens.

54:46: >> That's kind of what happens a lot. like

54:47: it over like by the time I get into

54:50: something like like everybody's already

54:52: doing something different or when I get

54:53: into it like everybody's already been

54:55: through everything and it's just kind of

54:56: it's it's kind of weird to play at that

54:59: stage because everybody's like, "Oh,

55:00: look this this and like I don't I don't

55:02: get to discover anything and it just

55:03: kind of exists and everybody does

55:06: everything because they've already been

55:07: through it and I'm like I'm I'm just I'm

55:10: just Here

55:17: is asking to prove we've upgraded like

55:19: we've been using it for a while.

55:22: >> Yeah.

55:22: >> How long have we been gone?

55:26: Maybe 2001. Are you doing okay for kind

55:29: of

55:33: case? Uh how does Oh, wait. We have this

55:36: one's Wait, did we answer this one? Oh,

55:38: yeah. This was sorry I'm getting

55:41: brain mixed. Uh how close the Linux

55:45: works?

55:49: >> Aside from my schnuppet uh with the

55:51: audio, it's it's it's pretty good. You

55:54: know, there's definitely like some hoops

55:56: you got to jump through to make it work

55:57: on uh Linux. Um,

56:03: I'm definitely doing uh I'm definitely

56:06: passing the launch arguments to the

56:08: renderer a little bit strangely because

56:10: I didn't want to like rearchitect how

56:12: the uh the whole uh render management

56:17: works like what spawns the the render

56:20: process. So, uh, and then you know, um,

56:28: Fris tells me that I'm a dumb nom. He

56:30: doesn't tell me.

56:33: >> I was more confused because like like

56:34: the there was like a difference that

56:36: just suddenly happened. It wasn't there

56:37: before.

56:39: >> Oh, yeah. Um,

56:40: >> so I was a bit confused by that.

56:43: >> Yeah. I found I found that the uh trying

56:46: to spawn the render after like going out

56:48: of the Linux environ out into the Linux

56:50: environment and then back into Proton

56:52: like mangles half of the environment

56:54: variables because like half of them are

56:57: just strings that aren't supported um in

56:59: the format by like bash or whatever. Um,

57:04: and so I have to like make the

57:05: bootstrapper spawn the renderer because

57:07: it was the original process that spawned

57:09: and so it has all the environment

57:10: correct and uh it's just it's a big it's

57:13: a it's a bit of a merry goound to make

57:16: it work on Linux but it does work

57:21: the things we do.

57:23: >> Yeah. I mean it's going to like be

57:25: beneficial because like just having like

57:27: the native like native Linux for the

57:31: main process and like you know then like

57:33: the actual render like should give like

57:35: a decent performance boost plus makes

57:36: some things simpler where we can just be

57:38: like you know yeah we don't have to

57:39: worry about this like working on the

57:40: proton.

57:42: Yeah, because because proton likenet is

57:44: a very complex like process with the j

57:47: compiler and stuff and there's a lot of

57:48: points of failure where if the thing's

57:51: not implemented exactly right, it's just

57:53: going to make it all explode under

57:54: proton if anything like weird changes.

58:02: Uh, next questions from BD_. Uh, with

58:07: the upcoming data model rework, how much

58:09: do you think impact do you think it will

58:11: have on mods interacting with things

58:12: like I feels or syns? Um, you'll

58:15: probably have to like recompile and

58:17: readjust the most for it. um depending

58:19: on the interaction if you're just going

58:20: to like you know using the core things

58:22: like like most pretty much like

58:23: everything should have like an

58:25: equivalent you could map it to because

58:28: uh part of the data model work is you

58:29: know preserving the behaviors because if

58:32: we don't then all the content breaks so

58:36: but I don't think like you know like you

58:38: we will probably have to like adjust the

58:39: mods because like stuff will kind of

58:41: move around some of the interfaces will

58:43: change you know like the way you access

58:44: certain things will change so um it'll

58:47: probably take like you know some But I I

58:49: think I don't think there would be like

58:51: too much that would like make the mods,

58:53: you know,

58:55: not upgradeable. But it'll probably

58:57: like, you know, break like a few like a

59:00: good chunk of them. Um, and require

59:03: like, you know, some adjustments.

59:05: But I also don't think those adjustments

59:06: are going to be like, you know, super

59:07: huge.

59:09: >> Yeah. I imagine the way that you

59:10: actually set and retrieve data on the

59:12: stuff will be very similar.

59:14: >> Yeah. Uh, next question is from as on

59:17: Twitch. Are you guys in the pre-release?

59:19: Uh, we're not right now. Uh, I mean, one

59:21: one reason is like, you know, we haven't

59:22: merged our Linux support. So, like and

59:25: still working on audio.

59:28: >> So, like, you know, like

59:31: you would have to be deaf and mute.

59:34: >> Yes, I'm I am, Trust me when I say that.

59:37: I am like I am like working constantly

59:40: on trying to make the freaking audio

59:42: work. I am I am I am I am pushing hard.

59:47: >> Your literal virtual existence depends

59:50: on it.

59:51: >> It does. Like that's the thing. That's

59:53: my motivation. If I don't do it, I can't

59:55: play the game.

59:56: >> Yeah.

01:00:00: That's good motivation.

01:00:04: And next question is from Alex Pi. Uh

01:00:07: will we have scan will we have to scan

01:00:09: our faces or provide government ID to be

01:00:11: on resite in the future? Um

01:00:16: don't know hopefully not

01:00:18: >> depends on how this be

01:00:20: >> depends depends on things.

01:00:25: Uh next questions from Grand UK. Uh

01:00:29: could it be possible to stream slot

01:00:31: transforms and components across

01:00:32: session? For example, a concert where

01:00:34: every slot under the stage and main

01:00:36: instance is copied to every other

01:00:37: instance to give impression performer in

01:00:39: every word instead of just a video. Uh I

01:00:41: mean we kind of talked about this one

01:00:42: quite a bit with the previous question

01:00:44: that's pretty much you know the domain

01:00:45: system is going to let you stream some

01:00:47: session and have like another session on

01:00:49: top of it. So they would kind of um they

01:00:52: would kind of take care of that.

01:00:55: Next question is from Spoby or Spope. Uh

01:00:59: world name this world is called uh I'm

01:01:02: also going to bring it out.

01:01:05: Um where's the Why is it not showing up?

01:01:08: Oh, right. I'm on a boring page.

01:01:12: Uh it's called Zary Whoops Sanctuary.

01:01:17: Uh I don't

01:01:20: warp. Uh let me put that there. When

01:01:24: it's backwards, I'm going to just do

01:01:25: this so I can read it for a sec. So, I'm

01:01:28: behind you.

01:01:36: Okay. It's not Halloween yet. Um,

01:01:40: get a couple more months for that,

01:01:41: buddy.

01:01:43: >> Yes.

01:01:48: >> Spooks.

01:01:50: >> Spooks.

01:01:53: Um,

01:01:56: Ace on Twitch is asking question from my

01:01:58: friend. Uh,

01:02:01: what's the estimated ETA for

01:02:02: splittening?

01:02:04: I would say it feels like maybe one to

01:02:06: two weeks. It depends like how many more

01:02:08: issues are found and how quick is to

01:02:10: fix, you know, the remaining ones. So,

01:02:13: um,

01:02:15: depends.

01:02:20: Yeah, I would say that but like you know

01:02:23: things can happen

01:02:25: >> when it's done.

01:02:27: >> When it's done. Um

01:02:31: is asking maybe for stop killing games.

01:02:32: Question asked by Nuki. What do we do

01:02:34: with system shutdown? The main thing

01:02:35: would be the server that connects

01:02:37: players to sessions through the session

01:02:38: browser and the inventory systems. Would

01:02:41: be at least binary available if had to

01:02:43: shut down and things change to let users

01:02:45: decide their cloud provider for sessions

01:02:46: and inventory.

01:02:48: that's like too specific like I don't

01:02:51: know how exactly would handle it like it

01:02:53: might be you know something like you

01:02:55: have like the your inventory stored

01:02:57: locally so you can you know load it like

01:02:59: that way um for sessions like you can

01:03:01: already kind of connect like you know if

01:03:03: you have the direct IP you can connect

01:03:04: through that so it depends like we

01:03:09: haven't like gotten like you know that

01:03:11: far yet but we would definitely like

01:03:13: want to make sure like you can keep

01:03:15: going in some manner but

01:03:18: There's like a technical details for it

01:03:20: like that.

01:03:27: Oh. Um,

01:03:30: Angel was asking, "How is FS doing

01:03:32: lately? You didn't sounded healthy in a

01:03:33: recent gashion spot video. We are a bit

01:03:35: worried of the video, by the way. Make

01:03:37: sure we get a little rest after split

01:03:38: inning."

01:03:40: It's been a lot. Um, I'm pretty much

01:03:45: like been trying to like get a spliting

01:03:46: done as fast as I can and it's kind of

01:03:49: hard because there's a lot of things and

01:03:52: I'm just trying to like go get to the

01:03:54: end of it as fast as I can and it's kind

01:03:57: of been displacing a lot of things like

01:04:01: um but just I don't have time like like

01:04:03: I don't have even time to like clean my

01:04:06: room because like it's just going to

01:04:09: all the work and then like you know I'm

01:04:11: too dead like to like really do much.

01:04:13: So, I'm kind of like hoping to get

01:04:14: through it as fast as I can so I can

01:04:17: >> start paying attention to other things,

01:04:18: too. Yesterday, actually, like I was

01:04:21: like

01:04:22: >> um originally like I was like hungry and

01:04:25: I was like, "Oh, I have one piece of

01:04:28: bread left." So, I ate that. I was like,

01:04:29: "I guess I I need to order groceries

01:04:32: now." So, like um so it's been it's been

01:04:37: struggling a bit. Um, but yeah, I'm hope

01:04:40: to kind of get through it and I kind of

01:04:42: hope like we'll make changes so like we

01:04:44: kind of don't end up like with these

01:04:45: kind of situations again like where

01:04:47: things end up like being turning into

01:04:50: sort of like deadlines and things like

01:04:52: end up like being

01:04:55: way too much of a crunch.

01:04:58: >> Yeah. Like super duper tight and hard

01:05:00: deadlines are just a real killer for

01:05:03: motivation.

01:05:04: >> Yeah. I mean, it's kind of another thing

01:05:06: is like the like I don't even the

01:05:09: motivation is pretty much like gone for

01:05:11: a while. It's just kind of like doing it

01:05:14: like you know out of necessity just

01:05:17: powering through it

01:05:19: >> and it's not pleasant but it needs to be

01:05:22: done. Um

01:05:23: >> it it will be so worth it.

01:05:26: >> Yeah.

01:05:29: Bor

01:05:34: uh godly is asking

01:05:37: uh have you seen or done any performance

01:05:39: comparisons between the fork of beu that

01:05:41: the design currently uses and the modern

01:05:42: version of beu with both on modern

01:05:45: version not necessarily within resoid

01:05:47: seeing little particle su particles and

01:05:50: collisions enabled on the latest pies

01:05:53: where the engine barely breaks a sweat

01:05:55: arises the question of just where the

01:05:57: peak lies once beus updated and can use

01:05:59: the vector types. Exciting stuff. Yeah,

01:06:02: I I haven't really looked into it like

01:06:04: uh myself. Like I haven't really had the

01:06:06: time. Um it's like one of those like you

01:06:08: know kind of like once the main split is

01:06:10: like merge poke around and see like you

01:06:12: know where it's at. Um but I do think

01:06:15: like there's going to be probably like

01:06:16: you know noticeable improvements still

01:06:18: because like even the original beu is

01:06:19: version to be like heavily paralyzed but

01:06:22: while back beu it updated like to net 5

01:06:27: uh at the time and that was like you

01:06:29: know I think net 9 y in order to

01:06:32: actually utilize a lot of the high

01:06:33: performance mechanisms that are only

01:06:34: available in the newer versions. So I

01:06:37: imagine there's going to be like a lot

01:06:38: of improvements even you know since then

01:06:40: and also like uh I've seen like some

01:06:42: post like where he like uh nor like he

01:06:45: rewrote like you know some parts of it

01:06:48: uh to like you know eliminate a lot of

01:06:50: kind of performance bottlenecks and just

01:06:51: make it perform even better. So I I do

01:06:53: feel it's going to be like even better

01:06:56: because the version we have like you

01:06:57: know it's a fork of the older pretet 5

01:06:59: version and once you're able to like use

01:07:01: the latest one I think that's going to

01:07:02: be even bigger boost.

01:07:05: It is very exciting. That was like very

01:07:07: amazing. Like it's very impressive like

01:07:09: piece of like software and one of those

01:07:12: like really good showcases that like you

01:07:13: know you can write really high

01:07:14: performance code in C.

01:07:17: >> Yeah. Like C that shit's not slow

01:07:20: anymore. Like that it's it's so fast.

01:07:23: >> You can write comparably

01:07:25: fast code to like statically compiled

01:07:28: languages like Rust or C++ or C even.

01:07:32: There's even like some tricks you can do

01:07:34: with it that like you know you can't do

01:07:35: like just thanks to the Jet compiler and

01:07:37: stuff. It's very it's very cool.

01:07:40: >> Yeah.

01:07:44: >> It's also like another thing is because

01:07:45: you know once the split is done it's

01:07:48: it's going to be like the new baseline

01:07:50: but there's like you know still bunch of

01:07:51: stuff to do that's going to help improve

01:07:54: performance even further. um you know

01:07:57: like stuff like we're going to switch

01:07:58: like to the math f library because right

01:07:59: now all math operations like you know

01:08:01: they convert to a double do the math

01:08:03: convert back.

01:08:04: >> Yeah. And it's also adding a bunch

01:08:06: because the the floating point version

01:08:08: of the library it doesn't exist in the

01:08:10: version we use. And mono it's actually

01:08:12: funny because mono they actually

01:08:14: switched that like also because the mono

01:08:17: even the new versions of mono they had a

01:08:19: library like that. But also for a while

01:08:21: they would actually just be like they

01:08:22: would be converting to doubles internal

01:08:24: and converting back and at some point

01:08:26: they got convinced they were like you

01:08:27: know let's actually just do it in the

01:08:28: floating point and they found you know

01:08:30: that actually speeds stuff up because

01:08:32: non modern CPUs doing the math in raw

01:08:34: floating points rather than converting

01:08:36: it is faster especially you know for

01:08:39: game engine stuff. So we'll be able to

01:08:40: switch to that. I think that it's going

01:08:42: to give some boost. We'll be able to

01:08:43: switch to like you know the vectors

01:08:45: that's going to give like another like

01:08:46: you know system numeric vectors. I feel

01:08:48: it's going to provide like another boost

01:08:50: like uh there's going to be no tuning

01:08:51: for stuff. Um there's going to be I'm

01:08:54: still going to like optimize some of the

01:08:55: mechanisms like one of the things I

01:08:56: think that's also taking a bit of

01:08:58: performance right now on the split

01:08:59: thinging is I still need to update the

01:09:00: mechanism how the blend ships are

01:09:02: updated on the avatars because right now

01:09:05: uh during some changes I had to kind of

01:09:07: disable the system and kind of rework it

01:09:09: a little bit where when blend ships are

01:09:11: submitted right now on a split it'll

01:09:13: submit all of them all the time. So we

01:09:16: we have avatar that has, you know,

01:09:19: the the hundreds of blend shapes. It's

01:09:21: submitting and updating all of them, you

01:09:24: know, every time. Uh but the system

01:09:27: uh is actually just going to look at the

01:09:28: ones that change and submit those. And

01:09:30: like I already have like bits for that

01:09:31: in place, but I just need like a little

01:09:32: bit adjustment. So I think that also

01:09:34: might give a bit of a boost. Um

01:09:38: and this like you know going to be like

01:09:39: future performance optimizations like

01:09:41: like you know variable rate updates the

01:09:42: data model rework you know adding more

01:09:44: multi- threading for things. Actually,

01:09:46: one of the things I'm kind of

01:09:47: considering is because one of the things

01:09:48: that's high on the list is the IK and I

01:09:52: think like one of the reasons to also

01:09:53: like prior like one of the arguments to

01:09:55: prioritizing that one is because like we

01:09:56: could actually write variety with the

01:09:58: modern approaches um and get some

01:10:01: performance boost from that too and just

01:10:03: kind of write it like you know so

01:10:05: there's like there's still like once

01:10:09: done that's not like you know

01:10:11: that's the end of it. We might take like

01:10:13: a pause, you know, for things, but um

01:10:16: there's like lot room to grow. Um

01:10:21: >> yeah,

01:10:21: >> and I mean a lot. So

01:10:23: >> there's like there's like so much more

01:10:26: optimization that we can do that's like

01:10:28: in of itself its own like I would say in

01:10:32: of itself all the optimizations we can

01:10:34: do combined after we get the initial

01:10:36: splitting done is like almost the same

01:10:39: magnitude as like the splittening

01:10:40: itself. There's just so much we can do.

01:10:43: >> There's a lot. It makes sense like know

01:10:45: one of the reasons like we're doing the

01:10:46: split first is because like it like it

01:10:49: essentially helps everything pretty much

01:10:50: across the board. Like not not

01:10:52: everything gets the same boost like you

01:10:54: know some things like the particle

01:10:55: systems they get a huge boost and those

01:10:58: like the most recently implemented

01:10:59: systems some get like you know less of a

01:11:02: boost but overall everything kind of

01:11:04: gets a boost. So that's like you know

01:11:07: one of the better benefits you know

01:11:08: because like we essentially we do that

01:11:09: one and now everything got a boost you

01:11:12: know we have like a new baseline but

01:11:14: then we can optimize you know the other

01:11:15: systems but also when we rework some of

01:11:18: the systems we can use more modern

01:11:21: approaches that you know we couldn't use

01:11:23: before so we could not be writing them

01:11:25: against like a modern runtime rather

01:11:28: than having to deal like you know with

01:11:29: mono. So it's one of the reasons like we

01:11:32: wanted to do the spliting as the first

01:11:34: thing like as the first like big

01:11:36: optimization

01:11:38: um like the data model rework I kind of

01:11:39: want to use like some mechanisms like

01:11:41: you know that um for that

01:11:44: >> we can we can also like if we really

01:11:47: wanted to we also have the new like

01:11:49: native memory API which gives you

01:11:51: functions to like allocate aligned

01:11:53: blocks of memory so you can get like

01:11:54: super fast vectorized stuff going on.

01:11:57: >> Yes.

01:11:59: Yeah. Yeah, there's like there there

01:12:00: there's there's a lot.

01:12:03: Uh

01:12:05: oh, I don't know someone. I'm sorry. I'm

01:12:08: sorry.

01:12:09: >> Don't don't add a question mark just to

01:12:11: say something to us, guys.

01:12:13: >> Uh

01:12:20: next questions from B if we see pre

01:12:23: should be on the compatibility feature

01:12:24: partial list, but then what's the best

01:12:26: way to bring that to your attention? Um

01:12:28: Em can just mention it on the issue. Uh

01:12:30: right now like I've been kind of

01:12:31: focusing on just uh finishing a little

01:12:34: fewer things like that like to actually

01:12:36: bring it to feature parity which is the

01:12:38: Vive hand tracking.

01:12:40: Uh and I I once I'm kind of done with

01:12:42: that I'm actually going to like go

01:12:43: through all the issues because I haven't

01:12:44: like really I haven't really sifted

01:12:46: through the issues and been like you

01:12:47: know categorized them. So like some of

01:12:49: them like might be just literally

01:12:50: waiting like uh once I'm done with that

01:12:52: like I need to do a pass over the issues

01:12:54: and see like okay like this is something

01:12:56: needs to address this something needs to

01:12:57: be addressed because right now uh the

01:12:59: issues like they they turn like into a

01:13:01: little bit of noise

01:13:03: uh that I have to kind of sort through

01:13:06: where because like there's like a number

01:13:07: of issues where I need to kind of figure

01:13:08: out like is this the same issue or is

01:13:10: this a different issue? Is this like

01:13:11: actually pre-release issue? Like you

01:13:12: know is this something and I haven't had

01:13:14: time to like you know sort it through

01:13:16: yet? Because for some of the earlier

01:13:18: things there were like there was some

01:13:20: stuff where um

01:13:23: there was some there was like some stuff

01:13:25: like where uh essentially the same bug

01:13:28: and it manifested a number of different

01:13:30: ways. So like fix it and then I would be

01:13:32: like okay all of these bugs is actually

01:13:34: the same bug. So like by fixing the bug

01:13:36: like you know there's like five or six

01:13:38: issues like closed and I'm pretty sure

01:13:40: there's like a number of ones currently

01:13:42: which is like you know technically the

01:13:44: same bug and kind of need to like you

01:13:46: know sort it through and figure it out.

01:13:47: But uh right now the focus is like I

01:13:49: just wanted to get like the last

01:13:51: remaining bits of feature priority out

01:13:53: of the way. Uh so we have like you know

01:13:55: everything in place and let's just focus

01:13:56: on bug fixing

01:13:58: you know bug fixing and compatibility.

01:14:08: Um, subscriptions.

01:14:11: Oh, Angel was asking, "Maybe we have

01:14:12: some music in the background is

01:14:14: definitely quiet." Um, I don't think

01:14:17: there's music in here, unfortunately.

01:14:20: >> I don't think I can pull in any music

01:14:22: that won't get us copyright strict

01:14:24: stricken.

01:14:25: >> Yeah, I don't have anything on hand.

01:14:27: Unfortunately

01:14:32: worse with ambiance.

01:14:39: Uh next question is from qualatorium.

01:14:41: Has there been considered to a very

01:14:43: explicitly obtained client telemetry for

01:14:45: fogs were okay with the idea

01:14:46: contributing continuous test data

01:14:47: especially for pre-releases? Is there

01:14:49: potential any useful data that could be

01:14:51: generated from system like that or would

01:14:53: be too much noise? Um and it kind of

01:14:55: depends what data for pre-release that's

01:14:57: usually more like you know bug reports

01:14:58: because we need like we need information

01:15:01: like you know what have you been doing

01:15:02: like you know what's what's caused the

01:15:03: crash we need to gather like you know

01:15:05: logs and so on. So like people usually

01:15:07: just submit that uh and having like your

01:15:10: system you know for telemetry that that

01:15:11: takes time to implement like we need you

01:15:13: know tooling we need like other stuff.

01:15:15: So just using the existing system is

01:15:18: kind of simpler right now. Um

01:15:23: for normal builds I feel like like I

01:15:25: feel like like been one of the things

01:15:27: we've kind of concerned but like one of

01:15:28: the problems is like um the very

01:15:31: explicitly optain like it it sort of

01:15:34: like you know creates a lot of bias you

01:15:36: know towards because like most people

01:15:38: will probably not turn it on and usually

01:15:40: for such systems to get really benefit

01:15:42: from them you want them to be like you

01:15:44: know uh opt out and if we were to do

01:15:48: that we probably you know present the

01:15:49: users be like okay we're introducing the

01:15:50: system by default it's on. Do you want

01:15:53: to turn it off? Like you know this is

01:15:54: this is this is the time. So if the user

01:15:56: is new or even if the user is existing

01:15:58: like they will be presented like you

01:15:59: know with the option to opt out of it.

01:16:01: But we probably have it like on by

01:16:02: default because we want you know more

01:16:04: people to get the data um to get really

01:16:08: benefit from that. But like we haven't

01:16:09: like really made any decision to

01:16:11: actually implement something like that.

01:16:14: Um, and like if we're like, you know, if

01:16:16: we're doing something like that, we will

01:16:18: like um we'll talk about it first as

01:16:21: well. Like, you know, it's not going to

01:16:22: be like it'll not be like one of those

01:16:24: things that's just, you know, it's just

01:16:25: suddenly going to appear out of nowhere.

01:16:28: >> Yeah. We be very transparent with like

01:16:31: what data we're collecting and why as

01:16:33: well. Like we're not just going to be

01:16:34: like, "Oh, turn on the spooky telemetry

01:16:36: option, guys. We we'll tell you what we

01:16:39: need to what what data we collect and

01:16:41: what we're going to use it for.

01:16:45: But yeah, right now like there's no

01:16:46: specific plans. It's just kind of

01:16:48: general thoughts.

01:16:51: Oh my god, we got all the all the all

01:16:52: the subscriptions now. Um

01:16:55: >> Oh my gosh.

01:16:57: >> Yeah, asking uh are Twitch commands

01:16:59: still a thing? I just tried a few of

01:17:01: them, but they seem to do nothing. Uh I

01:17:03: don't think they're included on this

01:17:04: version of Twitch chat pro. Let me

01:17:05: actually see if there's uh I don't know

01:17:08: if this has any commands on it. I think

01:17:11: it's like modules.

01:17:14: >> Yeah. I mean,

01:17:15: >> yeah, there's modules in this one.

01:17:17: >> To be honest, I don't really care for

01:17:18: the Twitch commands anyways. I don't

01:17:20: want my head to be lit on fire every 3

01:17:21: seconds.

01:17:22: >> But they care about it. We need

01:17:24: >> They care about it.

01:17:25: >> They They subscribe so much. We need to

01:17:27: suffer for their amusement.

01:17:29: >> Well, you know what? They There's so

01:17:32: much confetti. Wow.

01:17:34: Listen, that's You want to You want

01:17:36: something funny to happen, you got to

01:17:37: pay for it.

01:17:41: But they are paid for it.

01:17:43: >> Oh my god.

01:17:48: >> For for for this I will um I will um I

01:17:53: will I will There we go.

01:17:58: >> Are you like hooking me in? There we go.

01:18:00: Yeah.

01:18:00: >> No, no, no. I'm trying I'm trying to

01:18:02: push into the water.

01:18:04: >> Why?

01:18:06: >> For the amusement. There we go.

01:18:09: No,

01:18:13: >> how dare you? I'm going to [ __ ] put

01:18:15: you in the water, pal.

01:18:19: >> They paid for it.

01:18:21: >> Put you in the water, bucko.

01:18:25: >> We got We got We got Twitch commands at

01:18:26: home. Actually,

01:18:28: >> all the light.

01:18:29: >> Oh, no.

01:18:31: It actually looks kind of cool.

01:18:35: >> No more light.

01:18:37: >> No more light. This negative light.

01:18:39: >> Yeah, it's negative light.

01:18:40: >> That does look kind of cool. That is Oh,

01:18:42: that's for funky.

01:18:50: >> Actually, be kind of funny is like make

01:18:52: a stream where like, you know, it's like

01:18:54: Twitch commands, but like um you we have

01:18:58: to do them manually like none of them

01:19:00: are implemented. Literally like they

01:19:02: will say something and then we have to

01:19:03: interpret what that command would do and

01:19:04: then just like you know find a way to do

01:19:06: it in real time.

01:19:08: >> Oh yeah. Like it's just like a big queue

01:19:10: of stuff that we have to sip through.

01:19:13: >> Yeah. What if like there be like Twitch

01:19:15: command but it's but it's you know

01:19:17: human.

01:19:18: >> Yes.

01:19:18: >> We just we just do it like you do you do

01:19:20: command something and we just we we have

01:19:22: to figure out like what happens.

01:19:25: >> Yeah. It's it's like a two-word camelc

01:19:28: case like command that we got to

01:19:29: interpret. Yes,

01:19:32: we have to figure out what happens. It

01:19:33: be like one of those like, you know,

01:19:34: creator gem kind of things like like

01:19:36: loose interpretation of things actually

01:19:38: be kind of fun.

01:19:42: >> But it uh

01:19:44: I hope that answers the question.

01:19:47: >> Oh my god. Thank you.

01:19:52: >> Oh yeah, we got crash resite. Actually,

01:19:54: you know the funny thing,

01:19:57: the funny thing for this one, once um

01:20:00: once this split thing is done, I will

01:20:01: implement the way for the render to

01:20:03: crash, we could do like a live

01:20:05: demonstration. I'm probably actually

01:20:06: going to add like a button like, you

01:20:08: know, crash renderer. So, you can like

01:20:10: crash it like intentionally just to test

01:20:12: the mechanism. So, we'll be like you do

01:20:14: this, we'll be like, okay, crashing the

01:20:16: render and then it reboots and we're

01:20:17: back.

01:20:18: >> Pushing test button on the GFCI circuit.

01:20:21: You joke, but this might be a thing.

01:20:25: >> Yeah,

01:20:27: >> I'm going to add a crash button.

01:20:30: >> Goes on a walk and touches grass.

01:20:32: >> Oh my god. So, there's there's just so

01:20:35: many. Let me

01:20:38: go manual just so you can see like, you

01:20:40: know, all the all the

01:20:43: all the crazy subsections. Thank you.

01:20:48: Summers, there's Cheers. There's so

01:20:50: many. You know what? I'm just I'm not

01:20:52: even going to scram. There's There's so

01:20:55: many. Look at that.

01:20:57: >> Oh god,

01:20:58: >> there's so many. Oh boy, there's a lot.

01:21:00: There's a lot. We might need to start

01:21:02: speedr runninging to work through

01:21:03: questions. There's so many.

01:21:06: >> Uh

01:21:07: >> um question speedun. How much time we

01:21:10: have? We have uh we have 40 minutes. So

01:21:13: then drop in.

01:21:17: This

01:21:17: >> this this hasn't been a stream.

01:21:20: Uh

01:21:21: so Nikki can tell us about the world

01:21:23: you're in. I saw some color for garden

01:21:24: stuff. Uh spoiler already asked that

01:21:26: one. Uh

01:21:29: Nikkun's asking uh SDL is one of the

01:21:32: most stable, efficient, effective

01:21:33: libraries after I learn it. I saw Junk

01:21:34: Carmark use it for Quake 4. Did you know

01:21:36: Junk Car is SDL? Does that inspire

01:21:38: confidence is you as well? Yes, it does.

01:21:43: Um

01:21:46: next question. Uh

01:21:49: uh as on Twitch, I'm not sure if Sire

01:21:50: will also work on switching to SDL for

01:21:52: clipboard, but you guys think switching

01:21:54: to will be as complex as switching SDL

01:21:55: for outer io. No, it will not.

01:21:58: >> Yeah, now it's fine.

01:21:59: >> It's it's clipboards relatively simple.

01:22:02: Uh we got cheers. Uh

01:22:05: uh there's another question. How much uh

01:22:08: >> how much? Yeah.

01:22:10: >> Um you might have how much of an income

01:22:13: from Twitch subscriptions? Uh, a lot

01:22:15: more now than before this.

01:22:17: >> Yeah, probably a measurable percentage

01:22:19: more now.

01:22:20: >> Probably a measurable percentage. You

01:22:21: You have to like ask Bob during the

01:22:24: business of his hours at our recup

01:22:25: streams. Uh, he he crunches all the

01:22:27: numbers on that. Uh,

01:22:32: check the Fox. What does Twitch even do

01:22:34: if everyone watching is already sub and

01:22:36: someone gives subs? I think they just

01:22:39: stack.

01:22:40: >> You got to find out.

01:22:42: You probably found out by this time. Um,

01:22:47: what if someone made a sub visual that a

01:22:49: sub sandwich that grows longer in game

01:22:51: every sub? Um, do it.

01:22:58: Uh,

01:23:02: what frogs and dark frogs when are going

01:23:06: to with the bird thing? We already had

01:23:08: like a long one on the bird, so skipping

01:23:10: that. Um,

01:23:13: oh my god. Angel boy VR, I'm I'm scared

01:23:15: to answer this one. How many

01:23:16: subscriptions would we need to give to

01:23:18: make you both verb bird avatars?

01:23:21: Um,

01:23:24: >> uh,

01:23:24: >> 100.

01:23:25: >> I don't I don't know. I don't know how

01:23:27: much they actually say like I was going

01:23:29: to say like a thousand.

01:23:31: This

01:23:31: >> feels too much. Oh,

01:23:33: >> I don't know. Fuks like they there's

01:23:35: already we could maybe almost even count

01:23:37: 100 this stream. So Oh.

01:23:40: 200. But but it's for one person. I It

01:23:44: depends. Like is it is it like Oh, is it

01:23:46: a Wii? So it was How many subscriptions

01:23:49: was this? We're already over 100. Okay.

01:23:53: >> Oh boy.

01:23:58: >> Subscriber for Bird Hub. I guess we're

01:24:01: doing the next one as birds.

01:24:04: >> Oh boy. Thanks, Fuks.

01:24:08: This has happened. I guess we

01:24:12: I should have asked first how many of

01:24:14: this was

01:24:18: we'll be birds the next one.

01:24:21: I don't even have a bird avatar.

01:24:26: Uh next question from Nokun. Uh messing

01:24:29: with lighting effects on Jupiter Station

01:24:31: lately. Do you have any thoughts on

01:24:33: making lighting look better without

01:24:34: overing the GPU? I have a lot of lens

01:24:36: lights that I'm having to figure out

01:24:38: where is the direction lighting for. Um,

01:24:40: and generally with lights like uh limit

01:24:42: their range like you can have lots of

01:24:44: lights if they don't have like too much

01:24:46: range because what if like think about

01:24:48: whenever you have a when whenever you

01:24:50: have light in the scene um let me see

01:24:53: where's I need a brush uh tools

01:25:00: brushes

01:25:02: and I have geometry line brushes uh so

01:25:06: imagine like you know imagine you have a

01:25:07: light and this is the range of the

01:25:10: light. If you have like lots of lights

01:25:11: that have like a lot of range, there's

01:25:13: going to be a lot of overlap between

01:25:15: them. So for all the overlapping areas,

01:25:17: this gets very very expensive versus

01:25:22: if you make their uh you know ranges

01:25:24: smaller so they don't overlap as much.

01:25:26: That's going to be a lot cheaper because

01:25:28: what matters with lights with different

01:25:30: lighting is you know how much screen

01:25:33: area does the range cover and if there's

01:25:36: overlap you know that also like hurts a

01:25:38: lot. Uh the other thing is like if you

01:25:40: have a lot of transparent stuff or

01:25:41: nonPBR stuff, you want to limit amount

01:25:44: of lights, you know, near them because

01:25:46: uh essentially it causes the geometry to

01:25:48: be rerendered. You can also reduce the

01:25:50: geometry amount which is also going to

01:25:52: make it cheaper.

01:25:55: >> Yeah, a lot a lot of like lighting

01:25:56: optimizations will also come with like

01:25:58: light making and stuff in the future.

01:26:00: >> There is a tool like you can bake them

01:26:01: like if we can Oh my god, can we get to

01:26:04: level 90 69? Nice.

01:26:09: Okay, we uh go for stream crash hooks

01:26:12: with subs. I mean, you can try.

01:26:15: I don't think you will, but you can try.

01:26:23: Uh

01:26:25: I guess there's a lot of more.

01:26:30: Uh Nikon's asking, uh what do you think

01:26:33: of the statement? The is only as

01:26:34: optimized as the world you're running.

01:26:36: world builders can do a few simple

01:26:38: tricks to make their words and faster

01:26:39: especially with new spatial variables. I

01:26:41: don't think it's that black and white.

01:26:43: Um optimization is always like a

01:26:45: combination like yes the optimization of

01:26:46: the content matters but uh the other

01:26:50: part is you know

01:26:52: how optimized the engine itself is

01:26:54: because that you know that can add a lot

01:26:56: of overhead for things that you might

01:26:57: need to use. Uh and also

01:27:01: uh what matters

01:27:03: you know

01:27:05: what what matters a lot is as well like

01:27:07: you know what tools does the engine

01:27:09: provide you to optimize your content

01:27:11: with so like I think both of these

01:27:14: matter like you know it's like it's a

01:27:16: lot more nuanced than you know one or

01:27:18: the other. Uh it's also like you know

01:27:20: with a world you can have very light

01:27:22: world that has very low overhead but

01:27:23: then like you know have people join in

01:27:25: their avatars you know they're going to

01:27:26: have like impact and there's like you

01:27:28: know certain amount like you know where

01:27:29: you cannot really optimize it any

01:27:31: further without like you know reducing

01:27:32: functionality like say when you switch

01:27:35: you know from full body avatar to I like

01:27:37: full body avatar with IK to like you

01:27:39: know very simple avatar that can hold

01:27:41: performance but also you lost

01:27:42: functionality you lost you know like

01:27:43: your full avatar so it's um if we like

01:27:46: you know improve that like we lower the

01:27:48: cost of things and that lets you

01:27:51: preserve functionality while having

01:27:52: better performance. So it's it's

01:27:55: performance a lot more kind of

01:27:57: complicated and I I think that's you

01:27:59: know that statement is like too black

01:28:01: and white like either way it's a little

01:28:03: bit too redactive to be like you know

01:28:05: it's it's the user content like thing or

01:28:07: it's the engine thing. Most cases like

01:28:09: it's both. It's combination.

01:28:16: Uh, oh my god, there's so many.

01:28:25: Uh, hey on Twitch. Uh, not sure if I

01:28:28: should ask a question, but I already

01:28:30: asked Ages in the Artimal office hours

01:28:31: and he told me that you came up with

01:28:33: what they are. What inspired you to make

01:28:35: the designs for the 2021 2023 yearly

01:28:39: batches? So the gly batches like they

01:28:41: were kind of like you know I like to

01:28:42: whenever I work on something I like to I

01:28:45: would do this like you know really

01:28:46: reviews and I would like to like you

01:28:48: know give them a theme you know give

01:28:50: give things like a story you know on

01:28:52: what happened that year. So it kind of

01:28:54: started with a spark you know where like

01:28:56: there was initial like when um things

01:28:59: kind of got like you know released like

01:29:01: there was like the initial community

01:29:02: spark that started like you know growing

01:29:04: things because I remember like with my

01:29:07: work like a lot of the times like would

01:29:09: not have like too many like users and

01:29:11: then like you know few users would come

01:29:12: in and they would actually be so excited

01:29:14: they would start like bringing more

01:29:15: users start making things and you know

01:29:17: that was kind of that initial spark and

01:29:20: then like the next year you know that

01:29:21: spark turned into more of a flame

01:29:22: because more people came in, more people

01:29:24: started making things, things started

01:29:25: feeling more alive. Um, and you know,

01:29:28: and then next year after that become

01:29:29: like that that flame became a bonfire

01:29:32: because a lot of more people came in,

01:29:33: they started like, you know, putting

01:29:34: stuff into the platform and they started

01:29:36: like, you know, feeding the flame and

01:29:38: making it bigger, you know, and warmer

01:29:40: for everyone. So um like is is sort of

01:29:45: like you know like giving sort of like a

01:29:47: story to like the growth of like FS

01:29:51: engine.

01:29:57: Uh Gusk is asking uh there might be

01:29:59: issues in V control bindings in the

01:30:01: release. Should I make issue for this?

01:30:02: Uh yes if there's not issue already

01:30:04: please make one.

01:30:08: Uh, yol best Pokemon and why is it

01:30:11: weevil? Um,

01:30:13: I don't know. I'm not I'm not that

01:30:15: familiar with Pokeball. Um,

01:30:17: >> yeah, me neither.

01:30:20: >> I mean, I would say like why why not

01:30:22: though? Like can be any Pokemon.

01:30:27: >> It's all of them.

01:30:29: Uh, SL repo. I not sure which company.

01:30:34: >> Oh. Oh, yeah. There was there was the

01:30:36: Okay. Yeah. Yeah. with the company.

01:30:39: Um, Grand is asking,

01:30:43: uh, currently there's a component that

01:30:45: enables disabling of custom name plus

01:30:47: per user based on settings. Could it be

01:30:49: possible to add similar component for

01:30:51: when user is mutual blocked to do things

01:30:52: like calling systems don't leak

01:30:53: information about mutual blocked users?

01:30:56: >> Yeah, but leak information about who has

01:30:59: who blocked because now you have a means

01:31:01: to query it from other people by

01:31:02: spoofing impulses and I don't think we

01:31:04: want to do that.

01:31:06: >> Yeah. Like I don't fully

01:31:09: understand. It seems like he's saying

01:31:11: like that it kind of leaks the

01:31:12: information.

01:31:15: >> Yeah, I don't quite understand what he's

01:31:17: asking. Like I feel there should be like

01:31:19: more of a GitHub issue because there

01:31:20: feels like a lot of technical stuff

01:31:22: involved.

01:31:23: >> It's because some calling systems like

01:31:25: replicate like the user voice outside of

01:31:27: the users hierarchy so you can still

01:31:28: hear them even though they're blocked or

01:31:30: whatever.

01:31:31: >> I feel that should be a bit of issue.

01:31:33: Like give us the technical details on

01:31:35: that one. It's like not enough to like

01:31:37: really do one.

01:31:38: >> Yeah, we don't want to like add another

01:31:41: mechanism to retrieve information about

01:31:42: who has who blocked though, I don't

01:31:44: think.

01:31:44: >> Uh, GK, what do you think about people

01:31:46: making customers for night for We

01:31:48: already got this question earlier. Um,

01:31:55: Fard is asking, "How do you envision uh

01:31:58: the mentor theme as a sort of creative

01:32:00: core for when there's an eventual dog

01:32:02: with uh influx influxes of new users as

01:32:06: they carrying creative spark that can

01:32:07: inspire others? I feel like like you

01:32:09: know the mentor team is like you know

01:32:11: good for like you know passing on the

01:32:13: kind of spirit of the platform because

01:32:15: what we find is a lot of people who come

01:32:17: to the platform um they appreciate you

01:32:21: know like the helpfulness of the users

01:32:22: and a lot of them like become mentors as

01:32:24: well because they kind of want to you

01:32:26: know pay it forward um and they kind of

01:32:29: inspired you know by that you know by

01:32:30: the kindness and that like welcomingness

01:32:32: of the users. So um I do think like this

01:32:35: is also a good question to ask you know

01:32:37: in a moderation office hours ours

01:32:38: because uh the moderation team is the

01:32:40: one running the mentor program uh so if

01:32:43: you're in Kad and G can give you like

01:32:44: good answer on this one as well

01:32:51: uh

01:32:54: show this one

01:33:01: uh next question is from Qualtorium

01:33:03: You mentioned it's difficult to maintain

01:33:05: original work life balance with project

01:33:06: as important expansive as night. Do you

01:33:08: have any self-care rules you try to

01:33:10: follow to help yourself disconnect at

01:33:11: the end of the week? I mean one of the

01:33:14: rules was like you know like trying to

01:33:15: take like weekends off at least. Um but

01:33:18: like I've kind of not been able to do

01:33:20: that. I've been kind of working through

01:33:21: weekends for past I don't know how long

01:33:26: >> um because of like things like deadline.

01:33:28: So it's going to

01:33:32: it gets difficult at times. Um

01:33:34: especially when like you know things end

01:33:36: up like turning into like a crunch. Um

01:33:40: that's pretty much it you know like like

01:33:41: at least taking weekends taking like you

01:33:42: know some time off like doing like other

01:33:44: stuff. Um it's also a bit difficult in

01:33:47: game sometimes because people like you

01:33:48: know bring up like you know work stuff.

01:33:51: So it's kind of hard to escape it. Um so

01:33:54: like a bunch of the worlds like you know

01:33:56: they have like rules where it's like

01:33:57: this is no work zone you know don't

01:34:00: don't bring things but it's still like

01:34:02: it is very difficult because like you

01:34:04: know one of the things that like you

01:34:06: know we kind of kept like enforcing a

01:34:07: lot is um you know people will sometimes

01:34:11: like be like you know they have an issue

01:34:12: and we'll just tell them please go to

01:34:13: GitHub that needs to be GitHub issue or

01:34:15: they would be like I want I just want to

01:34:17: DM you I just want to hop on a call and

01:34:19: and it's like you know at this boundary

01:34:21: that like we kind of have to keep like

01:34:22: defending over and over and even now I

01:34:25: still get like people like you know who

01:34:26: just DM me logs and I'll have to be like

01:34:28: please pick it up issue uh otherwise

01:34:31: like it just becomes it it it becomes

01:34:33: unmanageable

01:34:35: um

01:34:37: and it's like

01:34:40: I feel like that's like the one like

01:34:42: been kind of like you know we've gotten

01:34:43: like best at like maintaining you know

01:34:46: making sure like things don't actually

01:34:48: go through like you know DMs and stuff

01:34:49: like that uh oops Um

01:34:54: so like you know there's like one

01:34:56: boundary like I I'm pretty strict about

01:35:00: uh where

01:35:04: you know just because like on like it's

01:35:06: like it's nicer like we can kind of deal

01:35:07: with it like when we have time to deal

01:35:09: with it um message to the work mode and

01:35:12: also gives like info and doesn't you

01:35:13: know I would like end up like you know

01:35:16: with having tons of like messages

01:35:18: because I'm still kind of do but like I

01:35:20: would like tons of them because they're

01:35:21: like bug reports. And if I click on it,

01:35:23: I either either have to like deal with

01:35:25: it like immediately or mark it as

01:35:27: unread. So like I forget like you know

01:35:28: so I remember to like look at it later

01:35:30: but then I don't know like you know I

01:35:31: forget this person under me message is

01:35:33: you know thing and this person other

01:35:35: message is a thing I need to respond to

01:35:37: and it just it becomes difficult.

01:35:40: >> Yeah, please do not send us bug reports

01:35:43: and logs and DMs or anything like that.

01:35:45: It is just we don't have the time to

01:35:48: help you personally. Just put it on

01:35:50: please. It's one of those things like

01:35:52: where I know like some people don't want

01:35:53: to like you know use the GitHub um for

01:35:55: like one reason or another but like it

01:35:58: is what we have and like we

01:36:02: like we just don't have the we don't

01:36:04: have the capacity to like you know deal

01:36:05: with it through DMs like it's just it it

01:36:08: it's

01:36:09: >> unmanageable unfortunately. So that's

01:36:11: kind of why we need to like be pretty

01:36:13: strict about that.

01:36:17: Uh

01:36:19: oh. Uh let's see. I don't know what is

01:36:23: the

01:36:27: uh perfusion flux uh crash render to hot

01:36:30: swap to different one. I don't think

01:36:31: that we would like implement something

01:36:33: like that. Like

01:36:34: >> I mean I don't think we would like be

01:36:35: swapping renderers like that but like I

01:36:37: mean technically you could do that but

01:36:39: like once we do switch render I we will

01:36:42: probably not have like two renders that

01:36:44: we maintain. We'll just swap the one. So

01:36:46: while technically you could implement

01:36:48: something like that like we're not going

01:36:50: to spend time on that.

01:36:52: >> Yeah, it is tech it is it is

01:36:55: technologically possible for you to do

01:36:57: it though.

01:36:58: >> But does it make sense to do?

01:37:00: >> Well, I mean I don't know.

01:37:03: >> Is it is it worth their time? That's

01:37:05: that's usually the question.

01:37:06: >> Is it worth their time?

01:37:09: >> I would want to do it for fun. Make a

01:37:11: mod. So I mean one subs are $5. That's

01:37:15: $590

01:37:17: in subs alone. Oh my god. Thank you so

01:37:19: much again.

01:37:19: >> God damn.

01:37:21: >> That's that's a lot.

01:37:23: >> Especially just for a silly stream like

01:37:25: this.

01:37:28: Um

01:37:30: U1F98A I wonder how much for extension

01:37:33: is thesis uh ship of thesis like all of

01:37:35: the core architecture core that survived

01:37:37: for years or did center refactored if

01:37:39: how did the flex development either way.

01:37:42: Yeah, there's like I mean there's a good

01:37:44: chunk like there's like stuff that's

01:37:45: like you know

01:37:47: ancient.

01:37:49: Um like I literally I literally was

01:37:52: looking in the audio system and I see

01:37:53: like the git blame that's like fruxious

01:37:56: 5 years ago.

01:37:57: >> Yeah. And there's even older stuff like

01:37:59: there's there's like pieces that are

01:38:01: like going to be like over 10 years old

01:38:04: because they kind of come from like you

01:38:05: know uh super early projects and some of

01:38:09: them like you know replaced some of them

01:38:11: like you know like I I can tell you like

01:38:14: huge chunks got replaced like you know

01:38:16: like like

01:38:18: I I I I went through like you know the

01:38:20: GitHub tool that kind of checks how much

01:38:22: has been replaced and like there's been

01:38:24: more lines of code deleted from Engine

01:38:27: that like you know than than there

01:38:28: currently is in there.

01:38:31: But this is a lot because it's literally

01:38:33: like it's in the in the range of like um

01:38:37: it's in the range of like hundreds of

01:38:39: thousands.

01:38:41: Um so yeah generally like we design like

01:38:44: things to be like very kind of modular

01:38:46: so it's kind of like easy to like

01:38:47: replace systems. Um, and I've kind of

01:38:50: like I've been doing that like you know

01:38:54: I don't even know how long like like

01:38:55: like

01:38:57: since like you know like sometime I was

01:39:00: like in high school like you know would

01:39:01: be like making like um actually one of

01:39:03: the kind of like you know early kind of

01:39:05: concepts like I was like making an

01:39:07: engine called like sireate

01:39:09: um and kind of like you know developed

01:39:10: eventual like um in ways like the fruits

01:39:14: engine. So there's also like you know

01:39:16: conceptual aspects too. Um so there's

01:39:20: like

01:39:22: like a a lot of this is like you know

01:39:23: like it's it's sort of like a

01:39:24: culmination of like like you know a lot

01:39:26: of my kind of work and a lot of it like

01:39:28: go a lot of it kind of goes like far

01:39:30: like you know super long. Um and some of

01:39:34: it like you know is like has been kind

01:39:35: of changed quite a bit but it's kind of

01:39:36: you know kind of developed and changed

01:39:38: over time. zombies have been completely

01:39:39: made like you know from um have been

01:39:42: replaced by like completely different

01:39:43: systems. Uh some are like you know brand

01:39:46: new, some are kind of like change. So

01:39:49: it's like it's a mix of all of that.

01:39:53: >> Yep.

01:39:53: >> But it's all like you know is made to

01:39:55: kind of like you know work work together

01:39:57: like heavily.

01:39:59: >> You can still go back to some of the old

01:40:02: like worlds where you're prototyping our

01:40:04: first scripting engine and they still

01:40:06: work.

01:40:06: >> Yeah.

01:40:11: just randomly popped my head.

01:40:13: >> Uh, next question. This actually we kind

01:40:16: of speed. We have 20 minutes left still.

01:40:19: Uh, next question is from Kyolps. Uh,

01:40:22: would you guys do something like an

01:40:24: issue page where it turns what the user

01:40:26: type into page also creates issue. I

01:40:28: feel like that might help with some

01:40:29: people not wanting to create GitHub

01:40:31: account. So, what we wanted to do is

01:40:33: like, you know, have it integrated in

01:40:34: game. So like you know we can just go on

01:40:36: a tab and you know for the issue there

01:40:38: and would like you know then we kind of

01:40:40: proxy it to GitHub. Uh so that's

01:40:42: something we want to do at some point.

01:40:43: It's just you know

01:40:45: we can do it like once we have bandwidth

01:40:47: for it and right now we don't have the

01:40:49: bandwidth to it. Uh because whatever

01:40:51: whatever we implement needs to come at a

01:40:53: cost of something else like like when it

01:40:56: becomes priority it means something else

01:40:59: didn't become a priority. And so

01:41:02: sometimes like it's a question is like

01:41:03: you know um

01:41:06: it is a question you know like like

01:41:08: should you know say so like say if the

01:41:10: decision is like should we implement

01:41:12: should we improve the UI or should we

01:41:14: implement like in-game bug reporting you

01:41:16: know which one of those two like what do

01:41:18: you pick would you pick UI okay we do UI

01:41:20: then it's question should we should we

01:41:23: imple should we like rework the IK or

01:41:25: should we implement in game bug

01:41:26: reporting you know and again question

01:41:28: which one do which one do you which one

01:41:30: of those two do you think is more

01:41:32: important and say like it's okay we do

01:41:34: the IK uh and then like say should we do

01:41:37: perflex collections or should we do you

01:41:39: know in-game bug reporting and again you

01:41:42: know say you want bug reporting more uh

01:41:44: or sorry you want collections more we do

01:41:47: that one and that's kind of like you

01:41:48: know how things can happen where

01:41:50: something we want to do but like it

01:41:52: never kind of goes to that level where

01:41:54: it's more important than the

01:41:55: alternatives

01:41:57: um and essentially for something to kind

01:42:00: of get implemented it needs to like you

01:42:01: know rise above that level where the

01:42:03: answer to that question should this be

01:42:05: implemented or should this other thing

01:42:06: be implemented you know it rises above

01:42:09: that um

01:42:12: so that kind of makes like a lot of

01:42:13: these things kind of more complicated

01:42:16: uh and usually like when something like

01:42:17: you know say GitHub is hard to

01:42:19: prioritize because we have something

01:42:20: that already works and we already like

01:42:23: you know we already have like more

01:42:24: issues there that we can like really

01:42:27: handle

01:42:29: so like that kind of like increases some

01:42:30: of the kind of pressure because like you

01:42:32: know um

01:42:36: like you know like we need to also

01:42:38: consider like you know the long-term

01:42:39: impact of it and we have like in game

01:42:41: bug reporting you know we need to

01:42:43: consider what's it going to do with the

01:42:45: quality of the reports is it going to

01:42:47: require more time from us to spend like

01:42:49: you know sifting through the bug reports

01:42:51: um and it impacts you know things and it

01:42:53: impacts our thinking on it so

01:42:57: it is a it is a tricky issue

01:43:00: Um and for us like I would say you know

01:43:02: quality of the issue matters a lot

01:43:05: because we're a small team and the more

01:43:10: time like you know the less time we can

01:43:12: spend like going through the issues and

01:43:14: trying to understand the issues and

01:43:15: trying to you know gather all the

01:43:16: information we need of the issues the

01:43:18: more time we can spend developing. Um so

01:43:22: like you know generally like the push is

01:43:24: you know towards thing which like make

01:43:26: us you know fix more bugs implement more

01:43:29: features and question is will in-game

01:43:32: bug reporting help us you know fix more

01:43:35: bugs and implement more features or is

01:43:38: going to be neutral or is it going to be

01:43:39: detrimental for that and those are you

01:43:41: know kind of considerations that like

01:43:44: go into this

01:43:48: Um,

01:43:51: Arand Meatball's asking, "What

01:43:53: programming languages do you enjoy

01:43:55: tinkering with the most?" I mean, C just

01:43:58: a lot.

01:43:59: >> Yeah.

01:44:01: Um, I used to, it's funny because I used

01:44:03: to like do like C and C++ a lot and then

01:44:05: like and then I found C and like I and I

01:44:08: wrote like a lot of stuff like I wrote

01:44:10: like compilers and emulators and like

01:44:12: you know C++ and like games and um there

01:44:16: was like C# I was like okay and then

01:44:18: like made some projects in it and then

01:44:19: then I went to back to C++ and I'm like

01:44:21: I don't want to deal with C++ it's like

01:44:24: too painful like it's too tedious.

01:44:28: So if I have to like you know like I'll

01:44:30: do things in it but um it's just more

01:44:33: work. I kind of want to play more with

01:44:35: Ras but I don't have like u time.

01:44:39: >> Yeah Rust is Rust is all right. I hear

01:44:42: ZG is pretty good too. That's like meant

01:44:43: to be a replacement for C in particular.

01:44:48: >> Yeah I want I did like interest

01:44:50: tinkering like some of like the

01:44:52: functional programming languages. I did

01:44:53: like play with lisp like a while back. I

01:44:55: kind of been like thinking about

01:44:56: Haskell, but it's also like one of those

01:44:58: languages that's like it's more like for

01:44:59: specific kind of fields. But just change

01:45:01: your thinking a little bit, you know,

01:45:03: that's

01:45:05: about F.

01:45:06: >> Yeah, I've been kind of looking at it

01:45:08: too, but I never like the problem I have

01:45:09: is like, you know, it's kind of just

01:45:11: messing with it, but I don't have

01:45:12: anything serious to write in it. Um,

01:45:15: which kind of like makes makes it

01:45:17: harder. So I mostly just play with the

01:45:19: syntax and I kind of forget about it

01:45:21: because I

01:45:22: >> don't have like to really get a language

01:45:24: I need to like actually write a project

01:45:26: in it

01:45:27: and it takes a while. Um and it's also

01:45:30: like you know I have to have

01:45:31: justification why would I use this

01:45:33: language for this project and um often

01:45:36: times like some other languages don't

01:45:38: really offer substantial you know reason

01:45:41: for that. Um, so it's kind of hard.

01:45:48: Uh, I guess, uh, clear these out. And

01:45:52: then, uh, Kols is asking,

01:45:55: uh, one thing I just thought of since

01:45:57: you guys and me too use C# blood when

01:45:59: you get the web assembly thing

01:46:01: implemented, would you do official SDKs

01:46:03: for that? Like here's an example process

01:46:05: for C C. Yes. Yeah. Like I would

01:46:08: definitely want us to have like, you

01:46:09: know, SDKs. Uh, we provide like, you

01:46:11: know, some samples. this is how you

01:46:13: write things. uh we probably like do

01:46:15: like you know some of the core stuff

01:46:16: like there's actually a good reason that

01:46:17: is like one of the things like where

01:46:18: like it might be good excuse to use a

01:46:20: rest and be like okay here's a rest

01:46:22: example this is how you make like you

01:46:23: know a module in web assembly um

01:46:25: probably you can know do like C++ one uh

01:46:27: two uh and then like maybe have like

01:46:30: community kind of handle like you know

01:46:32: bindings for like other languages

01:46:34: because that's this a cool thing about

01:46:35: web assembly is like you know we don't

01:46:37: constrain just one particle language um

01:46:41: we can just bring whatever language you

01:46:43: you know like like you can compile to

01:46:44: web assembly make bindings and uh and

01:46:47: now people can use more languages

01:46:50: >> let's use visual C++

01:46:55: >> it's uh C++ that compiles to

01:46:58: I know. I've worked with it before,

01:47:02: >> unfortunately.

01:47:04: Not not super much, but I've worked with

01:47:06: it. It's It's weird.

01:47:11: Like, it's one of those things where I'm

01:47:13: like, "How does this even exist?"

01:47:18: Uh, next question from Caster Braids.

01:47:20: Have you played with Elixir? It's my

01:47:21: favorite functional language and I'm

01:47:23: annoying. I'm the annoying er type, but

01:47:25: for it, I love it. Uh, I haven't played

01:47:27: with it one now.

01:47:29: >> Yeah, I haven't really had much time.

01:47:31: >> I don't know what elixir even looks

01:47:33: like.

01:47:34: >> I've heard of it, but like I just never

01:47:36: played with it.

01:47:40: Uh, next question is from uh

01:47:45: Brave uh Bravo Chair.

01:47:49: Don't I'm pronouncing the name right. Um

01:47:53: uh are there block code assistants? I

01:47:55: know I'm getting that I'm wrong. Uh on

01:47:58: the question about earlier from time

01:47:59: management, I like easy tools to make

01:48:01: textures and light sources have as much

01:48:04: as like without doing manual work.

01:48:07: >> I have no idea what you mean by block

01:48:09: code assistant and how that relates to

01:48:12: lighting and textures.

01:48:13: >> Yeah, we might need to rephrase that one

01:48:16: for sure. I don't quite understand. I'm

01:48:17: sorry.

01:48:20: If you're talking about like an LLM to

01:48:24: like help us, hard no on that. I hate I

01:48:29: useless for programming.

01:48:33: Yeah, I don't really know like what you

01:48:35: mean. Unfortunately,

01:48:37: uh

01:48:41: death to asking how's your mood now? I'm

01:48:44: thirsty. I need some water. My throat is

01:48:47: starting to hurt.

01:48:55: Navy 3001 is asking. Um, oh my god

01:49:01: more. Thank you.

01:49:04: Yeah, we definitely have to be burst for

01:49:06: the next one. Yeah, we'll have to we'll

01:49:10: we'll we'll have to

01:49:13: we'll have to um

01:49:15: procure bird avatar.

01:49:22: Uh

01:49:25: I forget was uh all right.

01:49:29: Is that thing going to look for in his

01:49:31: house for for first vacation after

01:49:32: spliting? I'm like I don't get out much.

01:49:36: I mean like I might as well be already

01:49:41: actually. I had like I had to get new

01:49:43: shoes because um like a a week ago like

01:49:47: I well a while back like I had like um

01:49:50: somebody like visiting like from from

01:49:52: the US and I like shoot them like around

01:49:54: Prague and like around and we walked a

01:49:56: lot like we're like 16 kilometers about

01:49:58: 10 miles every day and my shoes I had my

01:50:00: like yellow shoes for like over 10 years

01:50:03: now and like the back of them like it

01:50:05: started just falling apart

01:50:06: disintegrating. So I was like I guess I

01:50:08: need to like start looking at new shoes.

01:50:10: Um, and then I had to go like when I was

01:50:12: back home, I went to pick up a package

01:50:13: and it's just like, you know, 10-minute

01:50:15: walk, maybe 15 minutes stops. And on the

01:50:17: way back, like my heels like hurting a

01:50:19: lot, like like hurting really, really

01:50:21: bad. And I get back home and I look at

01:50:23: it and it's like all bloody like it was

01:50:26: like it started like it just kind of got

01:50:28: like, oh my god, thank you. Um, and it's

01:50:30: like it all started to get like um

01:50:34: it just destroyed it. Um, so, so I was

01:50:38: like, "Okay, I'm ordering new shoes

01:50:40: now." So, I found like shoes like

01:50:42: there's like a they were kind of like I

01:50:44: wanted to like yellow ones again, but I

01:50:45: found like I found like ones that were

01:50:47: like too expensive. So, I ended up like

01:50:49: uh getting ones that are more orange,

01:50:50: but it still kind of look cool. Um, and

01:50:53: there was like a big discount on them,

01:50:54: especially for my size. So, I had to

01:50:56: like get new ones. But I was like for a

01:50:58: bit I was like I can't even go out

01:51:00: because like well I have like other

01:51:01: shoes but they're like very like they're

01:51:03: more like heavy boots. Um like for like

01:51:05: winter and such. Um

01:51:08: but I was like you know like okay I can

01:51:10: like I was like I had like another thing

01:51:13: that I had to like open like pick up and

01:51:14: I was like okay like it's going to be

01:51:16: tricky with the with with those.

01:51:20: But now, now, now I have new shoes and I

01:51:22: need to like, you know,

01:51:24: now I can now I can go like uh walk

01:51:26: around more.

01:51:34: Next question is from uh Amy Defil. Will

01:51:37: we see Aaliy next stream?

01:51:42: >> No, because Avali are not actually

01:51:44: technically birds. They're kind of alien

01:51:46: raptor. So, uh, disqualify

01:51:50: >> that counts. I mean, look, I'm just I

01:51:52: was going to say it doesn't have to be a

01:51:53: volley.

01:51:55: >> It's also I don't want to be in a

01:51:56: volley.

01:51:58: >> Well,

01:52:00: we also figure something out.

01:52:03: Actually, I just got an idea.

01:52:06: >> Uh, oh, okay. Yep.

01:52:07: >> I'll I'll tell you after this three

01:52:09: minutes.

01:52:10: >> I'm going to die now.

01:52:11: >> Oh, no. You don't have to die.

01:52:16: and like have

01:52:18: >> no

01:52:20: >> it would be so weird.

01:52:24: >> What What if they give thousand

01:52:26: subscriptions?

01:52:29: >> I want 5,000 subscriptions.

01:52:31: >> 5,000

01:52:33: this game keep increasing the price.

01:52:36: Would Would you So for 5,000

01:52:39: subscriptions, would you would you turn

01:52:41: into next?

01:52:43: >> Yes, I would wear it for the stream.

01:52:49: Angel prep next for you Syra

01:52:53: like even get like offer here.

01:52:55: >> I don't know. I mean if if we get 5,000

01:52:59: subscriptions uh as well as that I'm

01:53:01: sure.

01:53:04: >> Also why uh Shinszu I forget our birds

01:53:07: categorize as drama.

01:53:10: I don't even know what that word is so I

01:53:11: don't know. Romeosaurus.

01:53:13: >> Domino. I don't know.

01:53:18: No, like we're kind of getting towards

01:53:19: the end of the stream. Um,

01:53:24: as on Twitch, oh yeah, asked any

01:53:27: struggles with implementing V and

01:53:28: tracking so far. Yes, it's weird. Um, so

01:53:33: I've

01:53:34: >> the driver is actually kind of weird

01:53:36: because like it needs like the way like

01:53:38: I implemented originally is like it

01:53:40: needs access to some of the input system

01:53:42: to find like references, but I'm trying

01:53:44: to figure out like why is that needed

01:53:46: and it kind of doesn't fit nicely into

01:53:48: the model. So I was like how like how am

01:53:50: I going to proxy this? I don't want to

01:53:52: like you know make proxying very

01:53:53: specific for this driver. Maybe I'll

01:53:55: have to. So I was like thinking can I

01:53:57: just bring the Vive driver to FKS engine

01:54:00: and just handle it there. there. So, I

01:54:01: started doing that, but I was like,

01:54:02: wait, it seems Oh my god. Thank you.

01:54:07: Ger,

01:54:08: oh my god, thank you.

01:54:10: >> So many.

01:54:11: >> There's so many.

01:54:13: I How many?

01:54:16: I don't know how many it is.

01:54:19: >> Oh my god. Thank you.

01:54:23: >> Thank you so much. I'm

01:54:25: >> one step closer to Sire Valley. Yep.

01:54:30: But yeah, um so I started like porting

01:54:33: it to Franger was like, "Oh wait, this

01:54:34: is dependent like too much on Unity." So

01:54:36: I was like, "Okay, I'm going to proxy

01:54:38: it." So I was like, "Okay, I'm going to

01:54:39: proxy it." But I'm like, "Oh, this is

01:54:40: like weird. Maybe like or maybe actually

01:54:42: don't need this unity bit so I could

01:54:44: have just writed more directly against

01:54:45: the API and just get rid of all the unit

01:54:48: bits." So now I'm like, you know, and

01:54:49: I'm I'm trying to figure out which is

01:54:51: going to be the part of least

01:54:53: resistance. And I'm trying to like

01:54:54: decipher like why is this weird because

01:54:57: like it kind of like needs like tracking

01:54:59: references for things and needs to

01:55:00: transform differently on like which type

01:55:02: like finger segment it is. Oh my god.

01:55:05: Thank you. Um

01:55:07: so yeah it's it's it's um I was thinking

01:55:10: it's going to be simpler but like that

01:55:12: ones and like it's weird and like I'm

01:55:15: trying to still figure out like what's

01:55:17: the best pathway for that.

01:55:19: Um,

01:55:21: so yeah, I wish they I wish like the

01:55:24: it's actually like one of the annoying

01:55:25: bits is like like sometimes like they

01:55:27: will give you SDK for these things but

01:55:30: it's like you know Unity SDK and it's

01:55:31: just written like to use a bunch of

01:55:33: Unity and stuff and it's like I wish

01:55:35: they just had like you know a library

01:55:38: that's just a library that just gives

01:55:40: you the data that's like agnostic to

01:55:42: whatever engine you want to use it in.

01:55:44: some of them like you know we kind of

01:55:45: like end up like just like like pushing

01:55:48: away all the unity bits. So that kind of

01:55:50: works but um with this one I'll have to

01:55:52: like still figure it out if it works or

01:55:54: not. So we'll we'll we'll see.

01:55:57: It's definitely a lot more struggle than

01:55:59: I was hoping it to be and it has to

01:56:03: because like you know that's I think

01:56:04: that's literally the last thing that's

01:56:05: needed for like feature party in terms

01:56:07: of actual features. Thank you very much.

01:56:13: Thank you very much.

01:56:14: >> Thank you. My god, this is so man.

01:56:19: What do we even do with this man?

01:56:22: >> I don't know.

01:56:26: I don't know either. We have to be birds

01:56:28: of some kind for the next one.

01:56:32: >> Yeah, we're going to have to be birds.

01:56:35: Have to be birds.

01:56:42: Are you going to be a cockatil?

01:56:45: A

01:56:45: >> what?

01:56:46: >> A cockatil.

01:56:49: >> Forget forget which one is like the

01:56:51: parrot.

01:56:51: >> It's like the parrot the the white

01:56:53: parrot with like the yellow bloom.

01:56:54: >> Oh yeah.

01:56:56: I don't know. We'll have to figure

01:56:58: something out

01:56:59: >> cuz he can be really loud and annoying.

01:57:02: >> What?

01:57:05: Oh.

01:57:08: >> Oh my god. Bear, can you become multiple

01:57:12: maros that have a hive mind?

01:57:17: We become We become Are there like the

01:57:19: Borg of the Birds.

01:57:22: >> We are bird.

01:57:23: >> We are bird.

01:57:28: Resistance is futile.

01:57:32: Uh we got uh two and a half minutes

01:57:34: left. So I don't think we have like any

01:57:36: there's like short questions we can

01:57:38: still do but uh probably going to like

01:57:40: wrap wrap the stream. I need to get some

01:57:42: more.

01:57:43: >> I would say we're I would say we're

01:57:44: probably done at this point for the most

01:57:46: part.

01:57:48: >> Okay. So thank you. What?

01:57:57: Yes, but it triples his

01:58:04: It cont

01:58:10: bread is good. Actually got fresh bread.

01:58:12: I got like also got like fresh breast

01:58:14: things and they're delicious.

01:58:16: >> European

01:58:17: American bread too.

01:58:19: >> Yeah.

01:58:22: You can tell by the fact that like uh

01:58:25: it'll become moldy after 3 days.

01:58:27: >> It doesn't taste like chemicals.

01:58:30: Yeah.

01:58:32: Anyway, uh

01:58:35: um anyway, thank you very much, you

01:58:37: know, for watching and thank you so much

01:58:38: for so many subs. Like that's like I I I

01:58:43: still kind of flabbergasted like, you

01:58:44: know, with like that many happening like

01:58:46: I

01:58:47: >> Yeah,

01:58:47: >> thank you very much. That helps us like

01:58:49: quite a bit and uh it's very sweet.

01:58:53: >> Um

01:58:54: >> yeah, thank you guys sincerely

01:58:56: >> and thank you for like you know for our

01:58:58: questions. Thank you like you know for

01:58:59: like just being on the platform like

01:59:00: making cool things on here and like

01:59:03: making this place like kind of come

01:59:04: alive. Thank you everyone you know for

01:59:06: helping like you know with the pre-list

01:59:07: testing too because like catching all

01:59:09: the bugs and testing everything that

01:59:11: kind of helps a lot too like get things

01:59:12: like you know get it closer to the

01:59:15: finish line. Um and you know for like

01:59:19: for those like also support on Patreon

01:59:20: and Stripe thank you as well. Um if you

01:59:24: are supporting on Patreon we recommend

01:59:26: switching to Stripe. uh because we get

01:59:28: about like, you know, 10% more from the

01:59:30: same amount of money and that helps us

01:59:31: as well. Uh so if you're still on

01:59:34: Patreon, please consider switching

01:59:36: switching over to the stripe on the same

01:59:38: tier or whatever tier, you know, like

01:59:40: either way, but uh we we get more out of

01:59:42: like, you know, we get more like that

01:59:45: way. Uh and we'll see you next time.

01:59:49: >> Yeah. See you around, guys.

01:59:51: >> Possibly, you know, with maybe I think

01:59:53: at that point like we might be running

01:59:54: on the spot and go harder. So

01:59:57: >> yeah, he's hoping that the splittening

01:59:59: is is nigh.

02:00:01: >> Well, we'll we'll see how this week

02:00:02: goes, the upcoming week.

02:00:05: >> So, thank you very much. Uh and

02:00:08: actually, let's see if there's anyone to

02:00:10: raid because uh there might be

02:00:14: there might be

02:00:16: interesting channels.

02:00:18: you want to like, you know, like if if

02:00:20: you're streaming as an eye, this is like

02:00:22: a perfect time because you're gonna um

02:00:25: you're going to get people. Uh looks

02:00:28: like it might be

02:00:30: just Creator Jam. It's unfortunately

02:00:32: just creator jam. Uh but also like you

02:00:36: know they're they're creator jam is like

02:00:38: excellent because like they've been

02:00:40: running for over five or six years now

02:00:42: like every every weekend like you know

02:00:44: hosting like uh creative building

02:00:46: events. So um definitely like you know

02:00:49: worth to watch and even more like you

02:00:51: know worth a visit. Uh so thank you

02:00:54: again everyone. Thank you like you know

02:00:56: for so many subs. Um

02:00:59: and say hello to my like for us. So I'm

02:01:03: going to do raid

02:01:07: creator gem.

02:01:11: I'm going to get the red.

02:01:15: I think you

02:01:17: and we should be ready. And

02:01:22: now so thanks again and say hello to my

02:01:27: war.

02:01:29: >> Bye.

02:01:30: >> Did I click it or miss?

02:01:35: Oh, there we go.

02:01:37: >> We're good.

02:01:40: And I'm going to

02:01:42: stop the