This is a transcript of The Resonance from 2025 November 29.
00:00: We're recording.
00:01: >> Okay, we're live.
00:04: Uh,
00:05: >> hi.
00:06: >> Hello.
00:08: Let me also
00:10: sorry for the few minutes delay dealing
00:12: with a few technical issues.
00:16: Uh, my VR hardware, but should be fine
00:18: now. Hello.
00:21: I'm going to post the announcements as
00:22: well.
00:25: Let us know if there's any put in the
00:27: chat list. Let us know if you can hear
00:28: us. Fine. Where's Discord?
00:34: Uh, everything's being bad. Come on.
00:39: Discord. There we go. Posting this.
00:47: Posting this.
00:51: Hello. Do we have anyone in the chat
00:54: already? Anyone watching?
00:58: Post another one.
01:02: Ah, it popped. It's popping. There's
01:05: people. Hello.
01:07: Hello again. Hello. It's Viral. Hello,
01:09: Qutorum. Hello, menu. All right. H6
01:12: check. The focus are going blah. Hello.
01:14: Can you hear us? Fine. Is the audio
01:16: fine? What's uh because I restarted? I
01:18: need to redo this. There we go. It's
01:20: kind of cold here. Hello and welcome.
01:24: Uh, welcome to another episode of
01:27: Resonance.
01:29: Uh, also let me make sure so I can see
01:31: the preview.
01:33: There we go.
01:36: Uh, hello noble. I just woke up. Hello
01:40: beauty
01:42: TomTom.
01:43: >> Yeah, this sounds like make some siren
01:46: noises.
01:47: >> Yeah. Oh,
01:51: >> all right. I forgot the um a bus just
01:54: stopped in front of us. Um, it's fine.
01:57: It's going to There we go. It's fine.
02:01: It'll It'll go away in a second.
02:05: >> I I guess I can make some siren noises.
02:09: >> Yeah.
02:09: >> Here. Is that Is that siren noises?
02:12: >> Hello.
02:14: They can't actually see. I I'm showing
02:16: them the the bus right now. Go away,
02:19: bus. Sh.
02:22: We're We're not getting on.
02:24: Go away, bus.
02:27: There we go. Good bus out of here.
02:30: Shoot. The
02:32: >> the bus isn't very active this time of
02:34: year in this part of the world.
02:35: >> Yeah, it's like everybody's, you know,
02:37: going going for Christmas. This is like
02:40: Christmasy wintry kind of environment,
02:42: which is why I picked it. Um, yeah.
02:47: So, uh, I'm going to
02:50: It's actually funny. You can see it like
02:52: behind us like flying away.
02:56: Sing up a wild animal.
02:58: >> Okay. So, audio is fine. Welcome to
03:00: another episode of Resonate. Uh this
03:02: like a weekly podcast usually um where
03:06: you can ask anything about Resonate. Um
03:08: where you can answer questions whether
03:10: it's technical, whether it's about the
03:11: team, the philosophy of the platform,
03:13: history, past, you know, future whatever
03:16: you want to ask, feel free to ask. some
03:18: questions we will redirect you to some
03:21: different sources like um for example
03:24: the moderation office hours or uh you
03:27: know the art team office hours and so on
03:29: there probably one probably once too. So
03:32: we'll try to give the best answer for
03:34: some things like we might redirect you
03:35: to teams handling certain [music] things
03:37: who might give you a much better answer
03:39: than we can but you're always free to
03:41: ask and some of the questions if they're
03:43: going to repeat it will probably [music]
03:44: just
03:45: give you a summary and direct you to
03:47: like our existing videos because clips
03:49: from this uh streams um some of the most
03:53: interesting questions uh or most useful
03:55: questions um we clip and they're
03:58: available on our YouTube channel. So,
03:59: it's kind of, you know, easy to kind of
04:01: go back and just direct people to answer
04:02: them. Oh my god, I just saw the bus
04:04: blast stuff. Um,
04:07: yes. Uh, we also have new section where
04:09: we'll be uh showcasing some of the
04:12: community stuff and we also have like an
04:14: announcement today regarding some of the
04:16: parties and things we've been we will
04:18: like we've kind of already been focusing
04:20: on in the background. Oh my god. Ah. Oh
04:22: my god. Thank you, Jay.
04:25: Wow. They're
04:27: heard where stuff is. Oh, they're going.
04:29: [music] Interesting. They don't respect
04:30: the gravity.
04:33: The gravity is so weird. But yeah. Um,
04:36: so we have like some announcements, too,
04:38: which is like one of the new things
04:39: we'll be go doing is like where we'll
04:42: introduce some of the things that we
04:45: want to do to some of these streams. So,
04:47: it's kind of like, you know, you can you
04:49: get to ask us questions about it right
04:50: away and we get to kind of know explain
04:52: it and then we have like, you know,
04:53: better materials to pair it. So, um,
04:55: stay tuned for that. Uh, we're going to
04:58: go through [music] questions from this.
04:59: Oh my god. Thank you. Thank you,
05:01: Curioex. Um,
05:04: thank you. Um, what was I saying? Yeah,
05:07: [snorts] we're going to go through
05:09: questions [music] from Discord first.
05:11: Uh, we're going to go through some of
05:13: the, um, Twitch ones as well. If you
05:16: want to ask question like live, uh, make
05:18: sure to put a question
05:20: um,
05:22: to put like put a question mark at the
05:24: end of the question. So, um, oh my god,
05:28: thank you, Z.
05:30: Um,
05:34: what was I saying? Um, make sure to put
05:36: a question mark that way kind of pops on
05:38: our chat and like, you know, we don't
05:39: miss it. Um, probably at some time like,
05:42: uh, we might do like a full hour or
05:43: something depending how time goes. Um we
05:46: will go you know through some of the
05:48: community stuff and we'll uh also you
05:52: know get to the some of the
05:53: announcements we want to make about some
05:55: of the stuff we want to be focusing on
05:57: or that we have been kind of focusing on
05:59: in the background. Um so you'll see. So
06:03: with that let's get started. Also I'm um
06:06: I think I forgot to mention I'm here a
06:08: bit s um let's move the camera here.
06:12: There we go. and
06:15: let's start going through the Discord
06:17: questions. So, [music]
06:19: the first one, these might be out of
06:20: order by the way. Um, it should be fine.
06:24: So, the first question is from a
06:28: computer user fake.
06:30: Uh, they're asking the [music] phase one
06:32: requirements on the newer GitHub
06:34: discussion mentioned quest support. Is
06:36: the Quest 2 include indis or is it
06:37: referring to headset [music] with Quest
06:38: three levels of performance? understand
06:40: if it's too early development to have a
06:42: good answer to this question. So I don't
06:45: believe there's anything on between
06:47: Quest two and Quest three that would
06:48: just make it not [music] work. Um so
06:52: it's going to be more like you know the
06:53: way the difference between these two
06:56: would be is like you know more like a
06:57: difference [music] between you know say
07:01: high-end PC and you know maybe mid PC.
07:04: If you have highend PC [music] you can
07:06: do a lot more stuff. You can do a lot
07:07: more complex worlds. you're going to
07:08: get, you know, better frame rate like,
07:10: you know, with like lot less of users.
07:12: Uh if you have lower PC, then you might
07:14: need to like, you know, lower quality
07:15: some more and maybe you don't get as
07:17: much uh as many frames in the same
07:19: scenarios, but you can still run things.
07:21: So, um I believe it's going to be, you
07:25: know, just a case of of that except you
07:27: on mobile. Um I don't think like it
07:30: would just fundamentally not work on
07:32: Quest two when it works on Quest 3. Um,
07:35: we probably don't want to like any
07:38: requirements that would make it like,
07:40: you know, a Quest 3 exclusive.
07:45: Uh, next question is
07:48: >> same person.
07:49: >> Oh, it does.
07:53: Uh, so it's from the same person. Um,
07:56: one thing we're also going to ask
07:58: actually like if you're um asking
08:00: questions in Discord, please keep one
08:03: make uh make a separate message for each
08:06: questions. Don't lump multiple questions
08:08: into you know single message because we
08:11: actually found this is uh this causes
08:13: some issues when making the video clips
08:16: because usually the way like when I try
08:18: to quickly cut the clips I will just
08:20: scrap the timeline. Oh my god. Thank you
08:23: be on the score.
08:26: just floating away.
08:28: >> They're flying away. Oh my god, thank
08:30: them.
08:31: >> There's helium.
08:33: They're just flying into the sky. Do I
08:35: need to move this or something?
08:40: >> I put like Okay. I think it's I think
08:42: it's I think it's funnier to have them
08:43: flying in the sky.
08:44: >> What if I do this? I'm just going to do
08:45: this in case. We'll We'll see what
08:47: happens. Um [music] yeah, just aim it
08:49: just aim it right at our heads. That's
08:51: Oh, that's good. That's That's great.
08:53: >> Yes.
08:54: Uh so
08:58: what I was saying yes uh please make a
09:01: separate message because during editing
09:02: I usually just scrub a timeline so it
09:04: can be like you know I can because I can
09:07: on the timeline I can very quickly see
09:08: like oh this is on screen so this is
09:10: this question I I just find like point
09:12: like where I bring it in I find point
09:14: where I bring it off and you know that's
09:16: my start and end of the clip. It's super
09:17: quick. Takes like you know like I don't
09:20: know 20 20 seconds tops to like clip out
09:23: a question. If it's multiple questions
09:26: lumped into one message and we bring it
09:27: as one message and I want to clip one of
09:29: the questions then actually need to like
09:32: listen to the whole thing and just scrub
09:34: along and find where that part answer to
09:37: particle question like you know starts
09:39: and ends and that takes a lot more time.
09:42: So please for the future like keep it um
09:46: make sure it's uh one individual message
09:49: for each questions just so they kind of
09:51: you know separate it. Uh so a user that
09:57: ask the previous questions also asking
10:00: um middle less important questions. What
10:02: are the specs for PC use for VR and what
10:04: VR setup you using? I'm actually running
10:06: on my laptop because my laptop's faster
10:08: than my desktop. Um, I don't have like
10:11: the best hardware myself. Uh, the laptop
10:14: is pretty beefy. It's not as fast as
10:16: some of the computers that people have,
10:18: especially with the like um the 3D cache
10:21: chips. Uh, it's like um it's a laptop
10:24: RTX 4080.
10:27: Uh, and it's like a Intel i9 like CPU.
10:31: It has like eight power cores and 16
10:33: like efficiency cores. Uh I don't
10:36: remember the
10:38: I don't remember the model number from
10:41: the top of my head. It also has 64 gigs
10:42: of RAM and bunch of hard drives. And I
10:45: kind of use this one a lot because like
10:47: I travel like a bit. Uh so I have like
10:49: you know VP PC and I can run VR like
10:52: even like when I'm when I'm at home and
10:54: because it actually like I benchmarked
10:56: it and it's actually faster than my
10:57: desktop. I just use it for VR. I'm
10:59: streaming from it. um they kind of at
11:01: some point want to like you know build
11:04: like a better PC. So like it's kind of
11:06: because this one it doesn't handle some
11:08: of the heavier stuff um as well
11:10: especially if I want to do streaming.
11:12: Um, so I I'm thinking about one of the
11:15: X3D like CPUs, but you know, cost manage
11:19: so and is not a huge priority right now.
11:21: So eventually, but uh it's pretty decent
11:25: for VR.
11:27: And so I do want to share yours.
11:30: Uh yeah, I'm uh running a
11:35: uh for my CPU I'm running a 7800 X3D.
11:39: So, that's one of the 3D uh Vcash chips
11:42: that uh for expansion there. And it does
11:45: it helps quite a bit with um like just
11:48: just crunching when I'm playing like
11:51: video games. It's really it it was
11:53: really good for Resonate pre-splitting
11:54: and it's great for Resonate
11:56: postsplittening because of that cache.
11:58: Um I think it's got something crazy like
12:01: 96 megabytes of like L3 or something.
12:04: Um, and then my
12:08: GPU is a 7900 XT with 20 gigs of VRAM.
12:13: Um, and
12:16: >> yeah, 20 gigs of VRAM is very nice to
12:18: have. Um,
12:18: >> yeah, I wish I had more.
12:22: >> Nvidia likes to skip out on the VRAM,
12:24: man. I don't know. I don't know.
12:26: >> I um I I don't really feel like I've
12:29: been missing much from
12:32: Nvidia. a lot of the AMD tech has caught
12:34: up quite handily. Um,
12:37: so that's that's kind of my specs. I I I
12:40: mainly run an AMD card because I use uh
12:43: Linux and uh they work a little bit
12:45: better on there and it's been pretty
12:47: good. I've actually been going strong on
12:48: Linux for about a year.
12:50: >> Nice. I've been kind of like thinking
12:52: about like I I I kind of would want to
12:55: switch to MD cards like in part like you
12:56: know because of the VRM thing. The main
12:59: thing that's been stopping me is because
13:00: I do a lot of like photoggramometry and
13:02: stuff and often times that just works on
13:04: Nvidia which sucks but and that kind of
13:07: keeps me on it which I wish like they
13:09: would like you know support open
13:10: standards like open CL or just making
13:13: CUDA specific but it's what it is and
13:16: it's kind of you know them
13:18: >> keeping the vendor lock in.
13:20: >> Yeah. Usually what I see some what I've
13:23: had [music] some of my or what some of
13:25: my friends tend to do is they'll like
13:27: take their old Nvidia card and they'll
13:29: like shove it in uh
13:32: uh oh sorry my game lagged. They'll like
13:34: shove it in a server or something. Um
13:38: >> and they'll use the server for all that
13:39: those tasks and use the AMD card for the
13:41: rest.
13:42: >> Yeah. But then you need you know two
13:44: GPUs because like a lot of it's like
13:46: computer heavy. So like if you want lot
13:47: [music] of compute for like you know the
13:49: processing
13:52: cannot go in the video. It sucks.
13:58: Um
14:01: next question is from flu.
14:06: Uh it's a long one. Uh this one I think
14:09: actually know what this is like. Uh
14:10: they're asking what are your thoughts on
14:12: the idea of various departments in
14:13: mentor organization with tiers of
14:15: accreditation testing. So mentors could
14:17: specialize in flex components, avatars,
14:18: blender, various levels of depth and
14:20: have different batch to display for it
14:22: to speed up deployment of mentors
14:24: specifically needing to be solved.
14:26: So this is actually one of those
14:28: questions that might be best to ask at
14:29: moderation office hours because
14:31: moderation team is responsible for the
14:32: mentor team. Um, personally I like this
14:36: feels like it might be like too
14:38: complicated [music] because like you
14:39: know there's a lot of training. How do
14:40: you like verify like different things
14:43: like you know it's adding like a lot of
14:45: requirements and structure and that
14:47: might like become a friction point and
14:49: like and the different badges you know
14:52: on display like that's going to be hard
14:53: for people to recognize because you know
14:55: we already have a bunch of badges and
14:57: like we tell people like look for
14:59: somebody with a mentor badge. Um, now we
15:02: have to tell them like you know look
15:04: like if if you look if you want this
15:05: look for somebody with this badge or
15:06: look for some if you want this look for
15:08: somebody with this badge and dispatch
15:09: and dispatch and there's like you know
15:10: 10 different badges like that will
15:12: become overwhelming especially to new
15:13: users. So I don't [music] think that
15:15: part would be a good idea but feels
15:19: more
15:21: so like when I'm not sure like what's
15:25: the best like what's the underlying
15:26: problem you're trying to solve is like
15:28: you know just finding mentors who can
15:30: help with specific [music] tasks. Um it
15:32: might just be better to have like you
15:34: know some system where mentors can say
15:35: like I can help with these things and
15:37: then it just you know and if you have
15:40: like you know for example if the user
15:41: goes to the user help they can be like I
15:43: need help you know with avatar and
15:45: mentors who can help with avatars you
15:47: know will naturally react and then if uh
15:50: we have mentors you if somebody going
15:52: like you know they need help with
15:53: perflex then mentors who do with perflex
15:55: who are confident with it can help you
15:56: know with it kind of thing. So it's just
15:59: finding the mentors with the right
16:01: skills. I feel like maybe making it like
16:04: not too rigid but like making something
16:06: where it's easier to like you know um
16:10: find the right person like maybe maybe
16:12: like [music] they could like list it
16:13: somewhere but depends like you know how
16:15: people like find mentors to help with
16:17: things but seems like the easiest thing
16:20: is just you know in the in the user help
16:21: just ask be like I need help like you
16:23: know with protolex uh and then mentors
16:25: who [music] you know who can help with
16:27: that can be like yeah I can help
16:31: some Um, so we'll see. But ask the the
16:34: moderation of first hour. Maybe they'll
16:35: have like, you know, some like ideas
16:36: with like stuff they wanted to do.
16:43: Uh, next question is from Ozie.
16:50: Ozie is asking, is it intended design
16:52: decision for Fenders to have dynamic
16:53: [music] modules as in grabbing one of
16:55: the fields on the list and sorting in
16:57: module? Why don't variables are spatial?
16:59: It seems kind of funny to do but could
17:00: really need for more advanced particle
17:02: systems. Yeah, you can do that. Um the
17:04: hide [music] of like proto like sorry um
17:07: photon dust is that it is you know
17:11: modular like and that makes it a lot
17:12: more flexible than the old system. And
17:15: one of the things like you know for
17:16: example dynamic loaded modules that can
17:18: be used you know to create all kinds of
17:19: effects as for example reactive user. In
17:21: fact the audio system the way it works
17:24: it does it does the same thing with
17:26: filters. So for example, the reverb
17:27: zones instead of them just being fixed,
17:29: they actually work as spatial variables
17:32: where you have a special variable that
17:33: defines a volume where there's like you
17:35: know a specific component and then on
17:37: the listener there's a special variable
17:40: collector which will collect all the
17:42: variables at particular point in space
17:44: that uh are like you know audio filters
17:46: and it'll just dynamically you know
17:47: drive them in the list and like as you
17:49: keep moving around the world the list
17:50: keeps getting modified [music] depending
17:52: on where you are and that way you know
17:55: we don't need like a dedicated system to
17:57: handle this is a ham generic system and
17:59: you can you know use this for other
18:01: things as well. Um one thing you need to
18:03: be um careful with is you know making
18:06: sure that like whatever effects you're
18:08: doing um it achieves the effect you want
18:11: because you can like by driving things
18:12: you can diverge things for different
18:14: users which in some cases you want to do
18:17: like you know depending for example
18:18: where the user is in the world you want
18:21: the effects you know for example for
18:22: audio like with the reverb zones like
18:25: you want it to be diverged if a user is
18:27: in particular zone you want them to have
18:29: reverb if another user somewhere else
18:31: you don't want them to have the reverb
18:33: uh and driving is a mechanism to do
18:36: that. So if you want to do the same with
18:37: particle system for example the
18:38: particles change somehow um
18:42: you can do that too. Uh the other
18:45: consideration is like generally you
18:46: shouldn't be like changing the modules
18:49: too much because like uh that's a little
18:52: bit more expensive. usually should like
18:53: build your setup and then just like
18:54: enable and disable the modules. But um
18:57: it is like a fair thing you can do.
19:03: Uh
19:11: next question is from our boy. Uh what
19:15: do you think the default button bindings
19:17: forite will be on Steam frame
19:19: controllers? Will jump finally get its
19:21: own button instead of thumb stick click?
19:23: Um, will D-pad just be used at four base
19:26: buttons? Will the new L1 L2 sh be used
19:29: at all? Meant to ask it later week, but
19:30: look at the wrong thread. Um, I'm not
19:33: sure yet. like uh it's one of those
19:34: things where I kind of like you know
19:36: want to get my hands on the controllers,
19:38: see what it feels like and you know make
19:41: decisions based on that because it's
19:44: like it's one thing you know like you
19:45: can can speculate like what would work
19:47: with those controllers and then like
19:50: often times what I find happens is you
19:51: know you get them in hands you feel like
19:53: no this is actually feels this [music]
19:54: way you know um so I feel it's going to
19:57: be decided like you know once we
19:58: actually have our hands on the hardware
20:00: um and figure out like what makes most
20:03: sense and for you know the mappings
20:11: uh which are again valve please def kit
20:20: next questions from nurun just want to
20:22: say I was bit skeptical that would be
20:23: worth it but I'm feeling like I'm not
20:25: successing times for some things without
20:28: any new bugs I was also worried I might
20:30: have issues on Linux but apparently we
20:31: have it working on R. So that's good.
20:34: What sort of optimization does net
20:36: incorporate and what should we be seeing
20:38: in the resonite? Yeah, so we actually
20:40: talked about this like a last stream as
20:42: well. Um there's a video clip like going
20:44: over the benefits of .NET 10. So I
20:46: strongly recommend going on our YouTube
20:48: channel, checking the latest videos and
20:49: watching the .NET 10 one because uh you
20:52: will get you know you'll get a lot of
20:54: answers there. Um
20:56: in general like we've noticed like you
20:58: know there's been performance
20:59: improvements. Some people got like uh
21:01: more, some people got less. Something
21:03: specific things got particle improvement
21:05: like for example particle systems are a
21:07: lot smoother. Um, and if you want to
21:10: know like you know what, uh, sort of
21:12: optimizations.net 10 did, there's a lot
21:14: of them. Like there's a super long
21:16: article that like, you know, covers
21:18: that. Um, and it's actually been leaked
21:20: in our release notes in change like,
21:22: which is another thing. You know, do we
21:24: recommend checking the sources because a
21:26: lot of times you'll find answers to
21:28: these kinds of questions we already
21:30: provided. Um so if you want to know go
21:32: to the change log find like you know
21:35: where we updated the the build with net
21:37: 10 and there's a link to the article
21:38: listing all the performance improvements
21:40: in net 10. It's quite a long technical
21:43: read so
21:45: you you also like you asking like what
21:47: performance improvements it has. So that
21:49: will give you the answer. Uh in short
21:51: there's like a number of things that
21:54: like you know are specific to us like
21:55: highlights. Uh one of the um one of the
21:59: things is like you know improvements to
22:00: the JIT compiler which is what takes our
22:02: code and transforms it into machine code
22:04: and has done it has a lot of new
22:07: improvements which allow it to do
22:08: optimizations that like you know oh my
22:10: god thank you be
22:16: I'm going to I'm going to point it this
22:18: way so they're kind of flying off
22:20: >> the direction
22:23: there so there's so many
22:25: >> there's so I
22:30: hold on. What if I put it here?
22:32: There we go. It's going to be exploding
22:35: floating through us.
22:37: Yeah, particles better performance. Um
22:43: uh but yeah, it's um
22:46: it's like um there's a lot of
22:49: improvements. The JIT compiler
22:51: essentially can take the same code
22:52: [music] and it generates more efficient
22:54: code. So we essentially get you know
22:57: performance boost without us having to
22:59: change our code. Uh one of the things
23:02: for example that helps you know it can
23:03: do a lot better diverization which is
23:06: like you know it removes some of the
23:07: overhead of like calling methods. it
23:09: does a lot better. Um
23:13: um there's like improvements to the
23:14: libraries as well like for example some
23:16: of the [music] zip systems and net frame
23:17: like the net like for example um the
23:22: thread scheduling which is one of the
23:23: things that helps like you know the
23:24: particles be smoother because we use
23:26: those libraries for our code and when
23:28: those get improvements you know we
23:29: benefit from them. Uh it also does uh
23:32: there's like a number of improvements to
23:33: the garbage collector itself, but also
23:36: one of the things I'm super happy about
23:37: the improved is they add something
23:40: called escape analysis. And what it does
23:43: is it looks at code and if you're
23:45: allocating new objects, it can figure
23:47: out uh at least in some cases if those
23:49: objects will end up being used after or
23:52: they only exist within the method. So
23:54: essentially it takes like if they escape
23:56: that method or if they don't and if they
23:58: don't instead of um allocating them on
24:01: the st on the heap it's going to
24:03: allocate them on the stack which is a
24:05: little more efficient and it essentially
24:07: makes it so they don't they don't put
24:10: like they don't create something called
24:12: GC pressure which is essentially giving
24:14: the garbage collector more work to do
24:17: and that in turn like improves
24:18: smoothness and reduces you know
24:19: hitching. So, there's a lot of like
24:22: improvements. Um,
24:24: am I going to just adjust a bit? There's
24:26: a lot of like improvements. Um, and if
24:29: you want to like, you know, know more
24:30: like in detail, I do recommend I do
24:32: recommend like uh reading the technical
24:35: article at least like skimming through
24:36: it because there's there's a lot like
24:38: every year they do tons and tons of like
24:42: performance improvements like and it
24:45: just uh overall it works out, you know,
24:47: to some uh some general performance
24:50: improvements across the board. And again
24:52: some things get more some things get
24:54: less but u
24:56: all we had to do on our end is change
24:58: few numbers from 9 to 10. So
25:03: it's it's essentially free like you know
25:05: it's like very low effort on our end and
25:07: we get like a whole year of you know
25:10: work by this large developer community
25:12: on the net frame like on the .NET 10. Uh
25:15: and next year like you know similar
25:17: things going to happen like this has
25:18: been pretty consistent like with every
25:20: net release like they did a lot of
25:22: performance improvements. Uh so every
25:24: year we'll just get like extra
25:27: performance without having to do you
25:29: know much we just change a number.
25:34: Uh
25:36: next question.
25:39: Uh where to put this? This is pretty
25:41: long one. We also ask like generally try
25:45: to keep the questions more succinct if
25:47: you can. Uh,
25:50: somebody with the fox emoji. Uh, I'm
25:53: aware of topic. Why can't you just
25:54: implement X to fix uh implement X mode
25:57: to fix XY issue or just let the
25:59: community work on the game has been
26:00: discussed many [music] times before and
26:01: I totally get concerned about mod
26:03: quality being at times dreadful. But
26:05: assuming most of it was if not maybe the
26:08: way you would have done it but still
26:09: good enough. Walter road and putting
26:11: concerns about legal conflicting work
26:12: that might have been turned aside. Would
26:14: you be willing to work with uh such a
26:16: developer to integrate such work or even
26:18: put out community bounties at the focus
26:20: community working groups? How big change
26:22: would you be willing to accept this way?
26:23: Small bug fixes would be different from
26:25: someone for example with Holio
26:27: overnight.
26:28: I mean I guess it's kind of what's
26:30: happening with the render project and
26:31: assume how that goes will influence what
26:34: happens with this. But I'd love to hear
26:35: more regarding the Taipon city. Uh so
26:39: yeah it's uh generally we will not
26:41: integrate like mods themselves because
26:43: they they are very hacky about how they
26:45: kind of approach things. Sometimes we'll
26:47: see if somebody makes a mod or something
26:49: we'll be like you know okay this works
26:51: really well. Uh we're going to make that
26:53: like an official implementation. Uh the
26:55: for example happened you know with a PDF
26:57: support. Um
26:59: because like PDF support is something I
27:01: wanted to add but I never like you know
27:03: really had the time to investigate the
27:05: libraries [music] for working with PDF
27:06: files. Um,
27:10: and [music] somebody made a mod and they
27:11: like, you know, published it like where
27:13: essentially they added like, you know,
27:14: third party PDF support. And I look at
27:16: the code, I was like, "Oh, this library
27:17: is actually super easy. I can just get
27:18: the bitmap data. That's all I need." Um,
27:21: the only thing the mod was doing it in a
27:23: very hacky way where essentially it
27:24: would like it would like generate like a
27:27: bit map, then it would save the bit map
27:29: and it would load the bit map from the
27:31: procedural texture and like, you know,
27:33: then push it push it in. And so there
27:34: was like a lot of kind of like hoops and
27:36: jumps that were like unnecessary. But it
27:38: showed me like okay this API for this
27:40: library is super simple. I can like I
27:42: can do implement this in a day
27:43: officially just like you know from
27:45: scratch. Um so that happened. So then
27:47: mod actually helped get the official PDF
27:49: support even though we haven't used any
27:51: of its code just by just kind of you
27:53: know showcasing things. So it is very
27:56: case specific. Um
27:59: definitely smaller bugs they like you
28:02: know they can be easier to handle
28:04: because like you know it's not as a big
28:06: change if it's like a really big change
28:07: that overhauls something that like you
28:09: know there's a lot of architectural
28:11: considerations. Is it going to work you
28:13: know with the things we're planning to
28:14: do in the future? Is it architecturally
28:16: sound? Is it like a strong foundation
28:17: and that's a lot more involved figuring
28:20: that out? And especially if it's like
28:22: you know just some code then like you
28:24: know it can be hard to figure out like
28:26: what is the architecture of this how
28:27: does it fit with things because the way
28:29: resonates designed is you know we plan
28:32: very very very very far ahead. We have
28:34: like plans for you know just generally
28:37: how things and systems are going to fit
28:39: together far into the future. And here's
28:41: the bus again. Um
28:44: so
28:47: that can be a lot harder. Um
28:51: even then there can be exceptions
28:52: because sometimes there's like you know
28:54: there's some bugs which seem like a
28:56: small bug but it actually requires a lot
28:58: more complex solution and sometimes like
29:00: sometimes we find people like either
29:02: suggest or do like fixes that are very
29:04: hacky that like we wouldn't do ourselves
29:06: because those will cause problems down
29:08: the line. Um, so even like small bugs,
29:12: you know, it might get complicated and
29:14: we had it to happen even internally
29:16: where somebody was like, I'm going to
29:17: fix this small bug and then it just
29:18: blows into this a little more complex
29:20: thing. Uh, so it's kind of, you know,
29:24: very case by case. Um, the renderer, um,
29:29: that is definitely like one of the
29:30: things, you know, like we're sort of
29:31: testing the waters, seeing like how this
29:33: kind of helps. Um and because we want to
29:38: like you know lean more like into the
29:40: community and we're like thinking about
29:41: like you know gradually open sourcing
29:43: the engine so we can expose some parts
29:45: of it and have people like you know help
29:47: fix things, add contributions, add new
29:49: features even or maybe just make like
29:51: you know forks uh for like some some of
29:53: the systems. Um and actually be talking
29:56: about this a little bit later too. Um
29:59: but
30:00: the main issue I see right now and the
30:03: thing I'm kind of concerned the most is
30:05: like you know we do have certain
30:06: standards for code quality. We have we
30:09: need things you know to follow certain
30:12: principles because like there's multiple
30:14: ways you could do things and it would
30:15: technically work but then it's going to
30:17: cause like issues down the line or maybe
30:18: it doesn't like fit the philosophy of
30:20: the project because you know for example
30:23: one of the big things about Resonite is
30:24: things just stay synchronized. you don't
30:26: have to think about it. But to make sure
30:28: it works that way, you need to design
30:30: things certain way. And sometimes when
30:33: we see people like pushing things that
30:34: like would break that principle, you
30:37: know, or would break the principle of
30:38: backwards compatibility like you know we
30:40: are very making sure content keeps
30:43: working is very important to us. That's
30:45: one of our like you know core
30:46: principles. So if somebody some change
30:50: would break that like you know generally
30:53: it's not going to be accepted and if it
30:55: were to be accepted that's going to be
30:56: like there needs to be a really strong
30:57: reason for it. Um
31:01: and the problem I kind of have is like
31:03: and the part I'm kind of concerned about
31:05: is like that like this
31:08: having like you know contributions like
31:09: that is going to lot a lot of overhead
31:11: where we have to kind of keep enforcing
31:14: you know
31:15: we have to keep enforcing you know those
31:17: principles and we have to kind of you
31:20: know come through the code and make sure
31:22: like it's not breaking that [music] and
31:24: the thing that like I'm worried right
31:26: about right now is like whenever we do
31:27: like for example you know, stuff with
31:29: the renderer.
31:30: A lot of people don't like read the
31:32: instructions. Like a lot of the times
31:34: like [music] people will end up posting
31:35: things in the wrong place or post
31:37: things, you know, we ask them not to
31:38: post or not to focus on. Um, and I just
31:41: get like feeling that like there's very
31:44: few people who actually kind of
31:47: take time to like you know properly
31:50: fully like read the instructions and
31:51: like [music] you know then follow them.
31:53: Uh and the if we like you know start
31:56: like getting more contributions that's
31:58: going to become even more important
31:59: because if they don't like then we spend
32:01: a lot of time you know just like sort of
32:04: moderating you know stuff around this
32:06: and that takes a lot of time from that
32:09: we could have been spending [music] like
32:10: you know developing. So
32:13: if you're like in the community like
32:15: this is like one of the things I feel
32:17: people should focus on and like you know
32:18: even among [music] themselves like if
32:20: you see somebody like you know breaking
32:22: some of the like requirements uh maybe
32:25: ask them you know please like do this
32:26: thing you know do like um
32:29: because if we see people are more um
32:34: what's the word um
32:37: what's like a word like when people like
32:39: somebody
32:40: diligent like people are like a little
32:42: bit more diligent with stuff that will
32:44: give us like more confidence that this
32:45: is, you know, worthwhile kind of
32:48: endeavor and this is actually going to
32:49: help save us like a lot of time. Um,
32:54: so and there's like lot of like you know
32:57: good like talent in the community. There
32:59: is like you know people can make like
33:00: really cool things but when it comes to
33:02: big project like making sure to
33:05: cooperate is very you know [music] and
33:07: making things sure are aligned that
33:10: becomes very important. Uh just kind of
33:13: like you know keeping everything
33:14: together. So
33:18: yeah that's kind of I'm going to talk a
33:19: little bit more like about it in the
33:21: future and we do have like a video
33:23: [music] on open sourcing as well that's
33:24: like a little bit older but like it kind
33:26: of goes over a lot of this. Um but like
33:28: you know we're kind of testing the
33:30: waters like seeing you know how do
33:33: people react like you know how do people
33:34: kind of like contribute
33:37: um and there's like a lot of good things
33:39: but there's also like you know things
33:40: we're [music] kind of concerned about
33:41: and it's like you know how do we improve
33:43: those things to give us more confidence
33:46: you know pushing this even like more and
33:48: having like more community
33:49: contributions.
33:54: Uh next question is from
33:59: uh let's move to senior
34:02: uh from uh computer user which is a fake
34:05: user. Um would you be able to talk more
34:07: about how photo works? Reading some form
34:10: of text post would also work if talking
34:12: is the best option. Particle system
34:13: alone is like magic to me and it would
34:15: [music] love to know more about it like
34:17: how you made it, how it works behind the
34:18: scenes, stuff like that. I'm especially
34:20: amazed by how particles [music] slow
34:21: down to make her life less. I love that
34:23: so much and I wonder why summing any
34:25: other particle system that I know
34:26: [music] Fel has imple similar. Um so
34:29: there's kind of two things to this. Um
34:32: one thing I love about particle systems,
34:34: they're actually like relatively simple
34:36: in principle in how they work. Uh so
34:39: what photon does does in background um
34:44: essentially like you can think of each
34:45: particle uh you know it's like an
34:47: element. It's like a piece of data. And
34:51: um let me just grab a brush. And
34:54: actually there is
34:56: I've done actually a video on photo dust
34:58: and how it works. It should be on the
35:00: YouTube channel, but I'm going to just
35:01: do like a quick one. Um
35:04: let's see line brush. Uh I do recommend
35:08: checking out like YouTube channel
35:09: because there there is a long video
35:10: about F on this when it was first
35:11: introduced and we kind of talk in detail
35:13: you know how it works. But you can think
35:15: of each particle as like a piece of data
35:17: and like if you have a particle you know
35:20: like that particle uh it can have like a
35:22: position which is like you know just 3D
35:24: vector
35:26: uh and then it can have like you know
35:28: for example size that's another piece of
35:31: data
35:34: size and you can have like you know
35:35: color you can have all orientation you
35:38: have like few pieces of data that
35:39: parameterize each particle and you can
35:42: have like you know lots of them in the
35:45: So what happens is like you know the
35:48: photon does it actually has like big
35:49: buffers that like fit all the particles.
35:52: It's essentially just arrays of these
35:53: values and then has modules and what the
35:56: modules do is they will somehow compute
35:59: or mutate these properties. So for
36:01: example there's position simulator. The
36:03: position simulator is going to add
36:05: another one which going to add velocity.
36:07: It actually has a few more like in the
36:09: background that sometimes used, but
36:10: that's not like too important. But it it
36:12: adds like a velocity to each particle.
36:13: So now each particle also has velocity,
36:15: which for example tells it it's moving
36:16: this way and this one's moving this way.
36:19: And then each simulation thing like for
36:21: example the position module position
36:23: simulator module what it does it looks
36:25: at the velocity um it looks you know
36:27: this is the current position and it's
36:29: going to compute the new position. It's
36:30: going to update it and then you can also
36:32: have like you know for example color
36:33: over lifetime. So lifetime is actually
36:35: another thing of the another of the
36:37: property.
36:40: So the particle will have like a
36:41: lifetime property and it's like you know
36:43: whole buffer of those.
36:45: Um
36:47: so there can be module which looks at
36:48: the lifetime and it computes a new color
36:51: based on that you know for example
36:52: changing over time. Uh and essentially
36:55: you have like a system where you have
36:56: like bunch of modules that are all like
36:57: you know reading and mutating these
36:59: properties. Uh you also have the emitter
37:01: system which are essentially like
37:03: systems which add new particles into the
37:05: system and initialize them. So like an
37:07: emitter can be like you know a sphere
37:08: emitter and for example every tick it
37:11: can you know emit bunch of new
37:12: particles. It just creates new particles
37:15: initialize this position so they're
37:16: within the emitter can initialize the
37:18: size can give them some starting color
37:20: and then you know the modules take over
37:22: and keep updating the particles. uh one
37:25: of the core functions is the lifetime
37:26: that keeps actually decreasing over time
37:29: and once it like reaches zero the system
37:31: will remove the particle from the system
37:33: and the particle will disappear.
37:35: Um there's a fair bit like more like you
37:38: know once you kind of get into the
37:39: modules but that's kind of like the core
37:40: principle of it is you know you have
37:42: like lots of pieces of data and have
37:43: modules which work on those data and
37:46: mutate them somehow or you know do
37:48: things with them and then we have
37:49: systems which introduce new particles
37:50: and they have mechanism for the
37:51: particles to die uh to essentially you
37:54: know be removed from a system.
37:57: um
37:58: pretty asynchronous nature. is actually
38:01: like one of the things like one of the
38:02: principles of Resonite and FRS Engine in
38:04: particular is because this is like user
38:08: you know content platform for VR and VR
38:10: like you don't want to like user if
38:12: using something like Unity editor for
38:15: example and you run expensive task you
38:17: know the whole editor like will lock up
38:19: for a while um or in Blender you know
38:21: you apply modifier everything locks up
38:22: that's annoying [snorts] but like you
38:24: know you can still use your other apps
38:26: in VR when it happens
38:29: it's bad because your and hard world
38:31: freezes. So from the ground up, Resonite
38:35: and FR engine like you know it's
38:37: designed to be strongly asynchronous in
38:40: nature and I think like a lot of like
38:43: engines they don't really take this
38:45: approach because you know they kind of
38:47: didn't need to for VR and like even like
38:49: VR platforms they they're generally like
38:52: you know um built on the existing tools
38:57: which were like you know very heavily
38:59: synchronous. like they you know just
39:01: even if they wanted to it would be a lot
39:03: harder for them to like you know switch
39:05: those principles but because engine you
39:07: know we cannot build measure our own
39:09: engine
39:11: it was designed from the ground up to be
39:13: very synchronous for a lot of the things
39:15: to prevent you know those kinds of
39:17: things uh from happening and from the
39:19: user getting like you know locked up and
39:22: you know the same thing happened when we
39:24: were our particle system was the unity
39:26: based one it would lag like if it was
39:29: too heavy maybe it would like you
39:30: because that's how the particle system
39:31: works in Unity. You know, that's how it
39:33: works in most engines. It wasn't until
39:35: we made our own system that we're
39:37: actually able to make it asynchronous
39:39: and follow, you know, one of our
39:41: principles that we use when designing
39:43: this platform. Um, and it's just it it
39:47: was a lot of work. You know, it takes a
39:49: fair amount of work to like, you know,
39:50: just build something from scratch. Um,
39:53: but it's like, you know, work like I'm
39:54: I'm really happy with it. like Photon
39:55: does is like one of the things I'm most
39:57: proud of and I wanted to do for a long
39:58: while. Um there also like another aspect
40:02: is like sometimes you know making
40:04: systems asynchronous it it makes it a
40:06: little bit harder to control you know
40:07: making sure they kind of stay
40:11: in sync because like you know like um if
40:15: it starts like lagging like you actually
40:16: had to spend a lot of time like you know
40:18: tweaking and tuning the system to make
40:20: sure you know I introduce like multiple
40:22: levels of buffering just to make sure
40:25: the particle system
40:28: if you have enough buffer performance,
40:30: making sure it kind of stays running
40:32: with the same performance you have. And
40:34: that can become quite tricky. Um,
40:38: and that's actually I think like another
40:40: reason like other engines don't do it
40:42: because like they want to keep
40:43: everything in sync and they don't want
40:45: you know they don't want like you know
40:49: the particle system like temporarily
40:50: becoming like you know out of sync
40:52: because that can lead to some visual
40:53: artifacts. But in our case, the visual
40:54: artifacts are generally more acceptable
40:57: like you know than the user fully
41:00: lagging. Um if the particle system
41:04: freezes, that's you know a lot less
41:05: charring than ever freezing. Uh so we
41:09: kind of made you know the design
41:10: decision. But if you're like making say
41:12: some AA game,
41:15: you know, you you won't that's not going
41:16: to be that important to you. Uh if you
41:19: if you're like, you know, a game studio
41:20: and you're making a game, usually you
41:22: will have like, you know, some kind of
41:23: performance budget and you're actually
41:25: going to tune the particle system so it
41:26: doesn't lower your frame rate. Like
41:28: you're not going to, you know, make
41:30: things just explode in way too many
41:32: particles than like the hardware you're
41:33: targeting can handle. You have your
41:35: designers be like, you know, yeah, we
41:37: need to like reduce this and make sure
41:38: this keeps it within performance budget.
41:40: But user generated content, you know,
41:42: that's not going to happen. People are
41:43: going to be like, oh, particle system
41:44: going to add few zeros and, you know,
41:46: just explode in particles. Um so for us
41:49: this is a lot better kind of you know
41:50: decision to make um and it's just
41:53: combination you know it's combination of
41:55: of that that for us with user generated
41:59: content that's much better approach it's
42:00: much better approach for VR and we are
42:02: able to take that approach because we're
42:04: largely building our own engine which
42:06: most other platforms don't do so
42:10: that's that's kind of like you know this
42:12: kind of for the details of the photon
42:13: dust I do recommend that YouTube video
42:16: because I do I go into a lot more
42:17: details on how the simulation works and
42:19: such. So, uh, check that out and but I
42:21: hope this helped.
42:24: Oh, we got another one. This is a very,
42:26: very long one. I'm not sure if this even
42:28: going to be readable on the stream. Um,
42:33: I might not read the whole thing. like
42:34: generally
42:37: please keep your questions sane like you
42:39: know we don't um
42:44: let's see uh Venport is asking have you
42:46: ever considered making groups being able
42:47: to share storage with groups more in
42:49: general accessible supporter I
42:51: personally think there are a lot of
42:52: users who can afford supporter tier but
42:54: they have friends that could afford
42:55: lower tiers of storage and don't tend to
42:57: useful amount of their own so because of
42:59: that they don't ever really get higher
43:01: tiers because they don't need to I think
43:03: maybe if more supporters could give
43:04: storage to groups and make groups we
43:06: would see higher demand for storage
43:07: since those people could share their
43:09: storage with their friends who can make
43:11: more reactive in building but currently
43:13: like the space I'm asking this because
43:15: my friends and myself Bri have wanted to
43:17: work on projects together but now this
43:19: [music] justify group memberships which
43:21: means to collaborate projects we would
43:22: have to expose publicly being released
43:24: them was unable [music] to contribute to
43:27: frog because uh someone with a very high
43:28: tier given extra storage while they had
43:30: been [music] working on it and nearly
43:32: running out of space it picking groups
43:34: and sharing storage with groups. I
43:35: developed average supporter. We would
43:36: have made use of my 25 GB of storage.
43:39: I'm only using 7 GB without having to
43:41: depend on someone random generosity. I
43:43: think that one of the biggest limiting
43:45: factors for high quality final worlds is
43:46: like shaded cove, the frog book is fax
43:49: storage groups as they right now
43:50: incredibly limiting creativity. This
43:53: would be major step toward making big
43:54: purchase like these possible services
43:55: weren't val but want to contribute. Um,
44:00: I'm actually not sure what exactly
44:01: you're asking, like if you're asking for
44:03: groups to become free or if you're like
44:05: just asking for people with lower tiers
44:06: to be able to, you know, share storage
44:08: with a group. So, a feel for the sharing
44:12: the storage on lower tiers. That's a
44:15: maybe
44:17: like, you know, maybe we could like let
44:18: people with lower tiers like contribute
44:20: their storage, you know, to a group. um
44:23: making groups free, we probably wouldn't
44:25: do that like you know or like making it
44:26: like at lower tiers because right now
44:29: things are sort of priced you know to
44:31: make sure
44:33: um because essentially two things that
44:35: are pushing against each other. It's
44:36: like one ideally if you wanted to just
44:39: from the pure creator you know
44:41: perspective we would give everyone like
44:43: you know unlimited free storage
44:44: unlimited groups unlimited everything so
44:47: people can just go creative not be
44:48: limited by anything. The problem is
44:53: it costs money. It costs money on our
44:55: end and you know the development of this
44:57: platform cost money. We need to you know
44:58: keep the lights on. We need to keep you
45:00: know make sure people you know working
45:02: on this platform can be paid. So that's
45:05: the kind of other thing that's pushing
45:06: against this where we need like you know
45:08: some source of revenue. Um,
45:13: and if we make certain changes, you
45:16: know, to the Patreon, for example, and
45:18: those changes would lead to losing
45:20: revenue, you know, because people now
45:22: like dropped their tears, um, that could
45:25: harm us and that could harm, you know,
45:28: our ability to kind of work on this
45:30: platform in the first place.
45:33: And maybe that wouldn't affect you right
45:35: away, but like, you know, eventually
45:37: that would affect the community. So what
45:40: we have to do is you know find the sort
45:42: of right balance you know between like
45:45: the business needs um you know and
45:48: making sure we keep going and keep like
45:50: developing this platform and like you
45:52: know making things available and
45:53: accessible and those things are sort of
45:55: like you know pushing against each other
45:58: like they're like you know to sort of
45:59: like opposite you know goals. Um
46:05: so and that kind of becomes difficult
46:07: you know like it's something this is
46:08: something we would have to sort of
46:09: evaluate and see would this you know
46:13: would this make people drop their tears
46:15: because if it would make a lot of people
46:16: drop their tears
46:19: we probably wouldn't make that change
46:20: because right now you know we don't have
46:24: much of like you know um wigler or
46:28: what's the word
46:30: we don't have like um our budget is
46:33: pretty tight essentially. So, you know,
46:35: making changes that can be risky. We're
46:38: going to be kind of averse to that
46:39: because of that because, you know, if
46:41: that risk doesn't pay off, that could be
46:43: worse. And like it's also like a lot
46:46: worse because say like we made it, you
46:48: know, at lower tiers and we'll be like,
46:49: "Oh no, this is, you know, this is now
46:52: causing us like lose a bunch of revenue
46:54: and like now, you know, we're going to
46:56: go in into the red. We need to bring the
46:58: prices back." That could make things
47:00: even worse because like you know if you
47:02: it's generally people you know will like
47:04: if things like you know prices are lower
47:08: for things but they don't like when they
47:10: go up and that makes it a lot harder to
47:13: make that initial decision. So unless
47:15: like we're really really sure this is
47:17: not going to affect us you know
47:18: negatively
47:20: we're probably not going to make that
47:21: change. Um and I feel like you know
47:24: maybe sharing the space that feel has
47:29: lower risk um because it's still like
47:32: centralizes people like and some like
47:33: you know people to have a tier where you
47:35: can like you know have groups
47:37: um
47:40: but even then like you know we would
47:42: want to be sure that like it doesn't end
47:45: up as like losing a bunch of like you
47:47: know funding for the project. uh you you
47:50: know as much as we want you know to
47:52: provide people you know with the tools
47:54: and space and things like to like you
47:56: know be creative and make like really
47:58: cool worlds. So that is a pretty complex
48:00: problem and like it's
48:03: I would probably recommend for the you
48:05: know being able to share the groups your
48:07: space with the groups make a GitHub
48:09: issue we can like you know then like
48:11: discuss it and evaluate like would this
48:13: be a good change or not. Um and I'm not
48:16: promising you I'm actually going to make
48:17: the change. It might be like you know
48:18: this is too risky or maybe we need like
48:20: you know more data but
48:23: that's generally what this comes down to
48:25: and model of the decisions you know with
48:27: the what is like you know behind like a
48:30: p year you know comes down to and
48:33: generally we want to approach it like
48:34: you know so like the paid things are
48:35: things that kind of make sense you know
48:36: that are like extra storage because
48:38: there's monthly cost we don't want to
48:41: like one of the things like the way we
48:42: have it structured is like we don't
48:44: actually have any actual features like
48:47: they are behind a pay wall like all the
48:49: features accessible to everyone. Um
48:53: at least like most of them there's like
48:54: you know few exceptions like you know
48:56: like there's things like you know extra
48:57: batches but it's like you know vanity
48:58: feature. Um the groups are you know like
49:01: another one but uh it also kind of ties
49:03: to the story because this additional you
49:05: know kind of calls on our end. Uh but in
49:08: terms of like the building features what
49:10: components can use what tools you can
49:11: use you know that is like not limited
49:14: and we kind of intentionally structure
49:16: it that way but that means we need to
49:18: charge for some other things like you
49:20: know especially cloud things.
49:22: So I hope this kind of helps you know
49:24: understand this a bit more and feel free
49:26: to make the GitHub issue again no
49:28: promises we will make the changes but we
49:31: might discuss it at least.
49:36: Uh
49:38: next question is from spob
49:41: um fruits. Did you know that the in
49:44: capital of Brazil most of the trees in
49:45: the city are mango trees? They stay in
49:47: season for most of the year and anyone
49:49: can take as many as they wish for free
49:50: at any time.
49:53: How much are how much are plane tickets
49:55: to Brazil?
49:57: [laughter]
49:59: I'll eat all of them. It's actually
50:00: funny because there's a there's a place
50:02: uh here there's like this mountain range
50:05: called PvE and in the summer it's
50:08: covered with bilberry bushes and you can
50:10: just go there and just be like there
50:12: like you can literally collect buckets
50:14: of them and it's free. Um and I really
50:17: like like you know I really like like
50:18: you know just getting fruit for free in
50:20: the in the nature. It's a
50:23: It's beautiful.
50:26: It's free fruit. Never going to say no.
50:29: Um,
50:32: next question is from Abysmol. Uh, under
50:34: the topic of Thunder particle systems,
50:36: how far along is the system compared to
50:37: Unity and other engines? Is it possible
50:39: to affect particles over a lifetime or
50:41: spawn new types of particles and
50:42: collision after a set amount of time? Um
50:45: so in terms of how far along like I I
50:48: feel that's kind of hard to compare
50:49: because like you know there's like
50:50: features we have like for example the
50:52: async nature that a lot of systems don't
50:54: have. Um also generally like people have
50:58: mentioned like you know our particle
50:59: system it's like higher performance than
51:01: the unity one uh at least like for
51:03: equivalent things. So some things like
51:05: we'll say we are ahead but like you know
51:07: uh some of the things like for example
51:09: the spawning target particles on
51:11: collision um that's essentially sub
51:13: emitters we don't support it yet but
51:15: it's something that I really want to add
51:18: uh and it would al like you know
51:21: I would want to kind of like you know
51:22: integrate because that's kind of the
51:23: cool effects in terms of affecting them
51:25: over the lifetime. There's a bunch of
51:27: modules that can do that. Depends what
51:29: kind of effects you're looking for
51:30: specifically, but there's a number of
51:32: them already. Like you can do size over
51:33: lifetime, color over lifetime, you know,
51:35: there's there's there's a bunch. So, you
51:37: need to be a little bit more specific
51:38: like which which modules you want. There
51:40: might be, you know, more that we can
51:41: add. And actually feel free to like, you
51:43: know, just make like if you want like,
51:44: you know, something affected by lifetime
51:46: or something like make a GitHub issue
51:48: and like a lot of the modules they might
51:51: be very simple to add.
51:53: uh submitters. That's a big bigger one,
51:55: but I already like I already know how
51:56: I'm going to implement it technically.
51:58: So like I might end up like doing that
51:59: soonish
52:01: maybe. Um
52:04: so with that
52:06: uh that's all the discord questions. Uh
52:09: we actually that took quite a bit. Um,
52:12: so, uh, let's look how many how much we
52:17: have in terms of, uh,
52:20: there's a good chunk of questions in the
52:23: Twitch chat. Um,
52:26: I'm actually going to
52:29: So, we're going to go through the Twitch
52:31: live questions. There's
52:35: actually not too crazy. There's a lot of
52:37: the subscriptions. Thank you. Um,
52:44: yeah, I think we can kind of go through
52:45: this first because I do want to get into
52:47: the bigger topic. Um,
52:51: once I get into the bigger topic and
52:52: there's probably going to be a bunch of
52:54: questions of that, but we're also going
52:55: to be talking about it for a while. So,
52:57: I'll let like you know questions pile
52:58: during that. So, let's go. We're going
53:01: to go through questions for a bit and
53:03: then we're going to talk about like the
53:04: announcement like one of the things. Um
53:08: so the first question is uh
53:13: from Grand UK which is surprisingly not
53:15: a schnoit. Um Tik is asking I saw that
53:18: J4 got a client headless bing with
53:19: CI/CD. How much does this help with
53:21: getting work done? That's huge. Um like
53:25: that's something like we needed for a
53:27: while. Uh so I'm like you know very
53:29: happy J for like managed to get this
53:31: like working and they've been working on
53:33: it for a good while. Um, so this is this
53:37: is like I'm very happy with this. Um,
53:39: it's also going to like you know
53:42: like uh it's going to help like you know
53:44: once we have like molecule because like
53:46: essentially what we need like we make
53:48: comets we push them and it's going to
53:50: make you know deterministic build it
53:53: push to the system it like removes a lot
53:54: of manual steps we have to take every
53:56: time like I make a build. So this is
53:57: pretty huge.
54:02: Uh, next question is from Jack the Fox.
54:05: You've added holes to polygon
54:06: trigulation, but can you use polygon
54:08: trigulation to fill holes in your ears?
54:11: I'm technically, well, I couldn't on
54:13: this avatar because this is actually
54:14: just a texture. It's not geometry, so
54:17: that wouldn't work. Um, in case you
54:19: haven't seen like I made like a deflog,
54:20: like one of the small things I've kind
54:22: of wanted out for a while is like a
54:23: triangulation algorithm. I'm adding one
54:26: that is called um let me actually see I
54:29: have a video saved uh so I can show you
54:33: um it's called constraint donate
54:36: triangulation
54:37: and what essentially does is like you
54:40: the algorithm uh I'm going to play the
54:42: video so you can kind of see it live.
54:46: What the algorithm does is you give it a
54:49: loop like a vertices and essentially it
54:51: fills it with triangles and you can see
54:54: you know I'm just drawing like a loop
54:55: with a brush and it's making like this
54:56: like shape
54:59: and this is like a very important
55:00: building block for like you know bunch
55:01: of future features like it's going to be
55:03: a feature of its own like I'm going to
55:05: expose that brush so I can like draw
55:06: like these dibly loop shapes but it's
55:08: also going to be used like you know for
55:09: procedural generation for like mesh
55:11: editing and lots of other things like
55:12: procedural text. So if you have like a
55:14: loop say like you know just like this
55:16: shape and this is composed of vertices
55:18: you essentially give it this loop and
55:20: it's going to figure out okay I'm going
55:21: to put triangles like this to fill you
55:23: know fill that with triangles. um the
55:26: algorithm it also supports like when you
55:28: give it a loop
55:30: you know you can give it more loops that
55:32: are within the shape and it's going to
55:34: you know it's going to fill this but
55:37: keep those holes
55:40: but uh it essentially works on those
55:42: loops like you know of those things you
55:43: can't take like you know existing
55:45: geometry to add holes to that would be
55:48: more like a boolean modifier and that's
55:49: like a different thing which might end
55:50: up like using this algorithm like if it
55:53: generates you know loops that need to
55:55: triangulate it. That might end up being
55:57: a thing, but this on itself will not do
55:59: that. It's like a more like a building
56:02: block.
56:04: And next question [music] is from uh
56:06: Rash 86. They're asking what world is
56:09: that? Uh this is called the Sunset
56:12: Galaxy. Um it's one of the MMC entries.
56:15: It's in the featured world, so I
56:17: strongly recommend checking it. It has
56:18: bunch of like areas. There's like this
56:19: bus that so just like fly by that takes
56:22: you to different planets. Uh it's very
56:24: cool. It kind of reminds me of outer
56:25: outer uh outer wilds. Almost said outer
56:30: worlds.
56:33: We got a cheers. Thank you. Uh modify
56:36: arc is asking uh since chat control
56:38: passed in Europe, what will I need to
56:40: change in order to comply with the new
56:41: digital surveillance laws? Um we're not
56:44: sure yet. That's like a thing like you
56:46: know need to figure out like with like
56:47: lawyers and stuff like that. So don't
56:50: have like anything
56:52: anything to like uh
56:54: announce like on this end right now.
56:58: Uh Navy 3001 is asking will bubble wars
57:02: be able to be added onto items like the
57:04: the TARDIS? Um that's not quite bubble
57:08: worlds. Um that's more like you know
57:10: having like embedded like sessions which
57:12: is a bit different. It's kind of
57:14: similarish like you know having another
57:16: session within something but the point
57:18: of bubble worlds is like you just kind
57:20: of create like extra session on top of
57:23: existing world to like you know just do
57:24: maybe some editing when you don't have
57:26: permissions uh or maybe you don't want
57:28: like you know bug people.
57:30: It's going to be using same underlying
57:32: systems. But the bubble world
57:33: specifically, you know, are more like um
57:36: it's more like just like you know like
57:37: you have like an overlay on top of
57:39: existing world almost like think of it
57:41: like you know augmented reality layer on
57:44: top of another world that's also like
57:46: its own world. Um rather than like you
57:48: know a world that's within an item. But
57:51: the same systems that are like kind of
57:52: going to be used for some of that are
57:54: actually going to also like you know be
57:55: eventually for like you know the domain
57:57: system which will let you do that kind
57:59: of stuff.
58:04: Um so please don't bump issues like we
58:06: if you if you had a question mark like
58:08: you know it's going to show up which
58:09: just take a bit you know show to through
58:11: things just be patient please.
58:15: Um,
58:19: Master Master mentioned, uh, since you
58:21: mentioned that you plan on building new
58:23: PC, what is your opinion on PC RAM
58:25: places lately? I haven't actually
58:26: checked like I I haven't even gotten to
58:28: planning new PC stage because there's
58:30: like some things I want to like get
58:31: first. Uh, so like um I don't know. I
58:34: heard like they are higher, but I I
58:35: haven't really looked.
58:39: Uh Zimmercus is asking how far should
58:42: people depend on slot naming and
58:43: structure of generated slots such
58:45: context menu. Generally you shouldn't um
58:48: usually it's better to like use like
58:50: dedicated systems to access you know
58:51: structure of things because the actual
58:53: slot naming and structure can change.
58:59: Uh K is asking
59:02: what are any stoppers from you moving to
59:04: Linux. So one of them is like um I use
59:07: Visual Studio for development. Doesn't
59:08: really work on Linux. I would probably
59:09: have to switch there either which is
59:11: like a commercial license. So there like
59:13: additional cost I have to worry about.
59:15: Um there's some other software like for
59:17: example um for like some of the like 3D
59:21: scanning stuff and like some of my work
59:23: I use like uh uh some of the Adobe
59:26: software. Unfortunately, I've been like
59:27: looking into alternatives, but there's
59:29: like one function particle for 3D
59:31: scanning that I haven't found yet
59:34: uh which is the noise removal. There is
59:37: one software which might have like a
59:38: really good like noise [music] removal.
59:40: Um
59:42: but I haven't like like had chance to
59:44: kind of like
59:46: like see how well it works and so I
59:48: would need to like kind of make switches
59:50: there too. Um and then it's also like
59:52: just generally VR support. Um, right now
59:55: like it seems to be like you can get it
59:58: to work but like it's a lot of work and
01:00:00: I don't necessarily have the time to
01:00:01: like get things to work. I use the wife
01:00:03: Bry like iting and I hope been like you
01:00:06: know getting stuff to work and but it's
01:00:08: just it's all it's very involved just
01:00:11: kind of you know for upkeep and getting
01:00:13: things working and I don't necessarily
01:00:16: have the time to like you know make sure
01:00:17: I kind of keep things like working like
01:00:19: I kind of need them to work more out of
01:00:21: the box. Um,
01:00:30: next question is, um, G is asking, uh,
01:00:34: have you seen the PL post trackers? Uh,
01:00:37: they since open up on Kickstarter, broke
01:00:38: their goal within minutes and then broke
01:00:40: 1 million pounds within a day or two.
01:00:42: Yeah, actually back them. Uh, I got
01:00:44: like, uh, the um the pro kit, like the
01:00:47: eight trackers. I know Sarah's pretty
01:00:49: excited about them, too. They backed
01:00:51: them, too. So yeah, like we're really
01:00:53: excited about them.
01:00:54: >> It's actually going to help like like um
01:00:56: like with the IK rework like having more
01:00:59: trackers like that's going to help
01:01:00: because one of the things I for example
01:01:02: wanted to add with the new IK is like so
01:01:03: you can track your shoulders and do like
01:01:05: you know shoulder shrug. Um so having
01:01:08: eight like that's going to help with
01:01:09: stuff like that and having elbows that's
01:01:11: going to be cool because like that's
01:01:12: that adds a lot of immersion.
01:01:16: Oh
01:01:16: >> yes I believe flex pose is now at 2
01:01:18: million.
01:01:19: >> Yeah, it's very exciting.
01:01:27: Uh,
01:01:29: it's actually from Syro. Uh, do you want
01:01:31: to read this?
01:01:33: >> Yeah, sure.
01:01:35: It says to Cyro. Is there a reason why
01:01:37: the Linux script uses Net installer
01:01:39: intended for CI/CD instead of running
01:01:41: the regular installer? Well, uh, it
01:01:44: means I don't have to show the user any
01:01:47: install screen and it will just kind of
01:01:48: do it on [music] its own. Um,
01:01:52: that's really the main reason it gets
01:01:54: younet just the same. And I figure
01:01:59: even though it's meant for CI/CD, it
01:02:02: kind of works for this use case. And
01:02:04: like I don't really foresee it breaking
01:02:06: because it's it it's still kind of
01:02:08: conducive to the intended usage of that
01:02:10: script, which is which is an unintended.
01:02:13: So, uh, that's primarily the reason.
01:02:22: There we go. Uh,
01:02:25: this VR is asking, "Are you going to
01:02:26: take my Discord question?" Did we like
01:02:28: miss a question? What was your Discord
01:02:30: question?
01:02:32: If you ask about uh
01:02:36: if you ask it like after we started
01:02:38: stream like we like we only bring it
01:02:40: like before the stream starts. Uh, we
01:02:43: might want to ask it here instead.
01:02:47: >> Just like we can like copy and paste.
01:02:50: >> Yeah, it looks like they asked it after
01:02:52: the stream started. Sorry.
01:03:01: Uh, yummy def tool is asking
01:03:05: uh question about area and delta clock
01:03:08: world. As you're probably aware, having
01:03:09: one user with bad internet connection
01:03:11: can ruin the game for everyone as audio
01:03:12: zones critical for private conversations
01:03:14: can break. Do you think there's
01:03:16: implement tools that make specifically
01:03:17: games that rely on audio and secret
01:03:19: information more reliable? Um, there's
01:03:22: some things you can do like for example
01:03:24: like one of the things you want to do is
01:03:25: like the user can figure out who they
01:03:27: should be sending their audio stream to
01:03:29: and just not send any audio data. But
01:03:31: you're still going to run into like a
01:03:33: whole lot of different issues. Uh
01:03:35: because the user going to be like behind
01:03:36: like for example, you know, the voting
01:03:38: system in the game, they're going to be
01:03:39: behind on that. When they get, you know,
01:03:41: pulled into the cabin or pulled
01:03:42: somewhere, they're going to be behind on
01:03:44: that. They might see people, you know,
01:03:45: disappear. They might see people where
01:03:46: they're not supposed to be. So the main
01:03:50: thing is, you know, just like
01:03:53: making sure like it like lowering the
01:03:55: requirements on the connection. But like
01:03:56: if somebody has like internet issues and
01:03:58: the internet is like dying, there's like
01:04:00: not much you can do because you know
01:04:02: you're kind of hitting the limits of the
01:04:04: connection and like there might be
01:04:05: losing lots of packets.
01:04:08: So
01:04:09: I would say like it's still kind of like
01:04:11: you know
01:04:13: limited.
01:04:24: Um, okay. So, we're getting a bunch more
01:04:27: questions. Uh, uh, I think probably move
01:04:31: to the announcement because like there's
01:04:32: probably going to be questions piling
01:04:33: in. Um,
01:04:37: there's going to be like questions
01:04:38: piling in. So, we're going to get back
01:04:39: to them like after this. Um,
01:04:43: so, uh, let me open a document.
01:04:49: And I figure there's probably going to
01:04:50: be a bunch of questions about this as
01:04:52: well. So, I'm going to open this up.
01:04:55: So, for the past few weeks, uh I've been
01:04:59: kind of working I kind of started like
01:05:01: working on something that essentially I
01:05:03: made like my current
01:05:06: priority. Um
01:05:10: and like where do I start?
01:05:15: So, um like you know like I haven't like
01:05:17: really doing like too many like in terms
01:05:20: of feature work. I've been kind of
01:05:21: focusing on some like fun project and
01:05:22: it's sort of like related to that. Um,
01:05:25: but I'll spend a lot of time, you know,
01:05:28: putting together like documents, writing
01:05:29: down ideas.
01:05:31: uh because the thing I've been kind of
01:05:33: focusing on and then we'll spend a bit
01:05:35: more time focusing on as the team and
01:05:37: now starting to implement some of the
01:05:40: changes is um changes to our process to
01:05:45: improve essentially the sort of
01:05:47: positivity and mental health as part of
01:05:50: the development. Uh because for a while
01:05:54: like we kind of just kind of left things
01:05:55: [music] as it is and it's been kind of
01:05:56: getting a bit more kind of difficult
01:05:58: like you know just kind of keeping with
01:06:00: updates because we kind of like
01:06:03: for a long time been just kind of in
01:06:04: this like daily grind of like you know
01:06:06: bug fixes features you know adding
01:06:09: things um you know like responding to
01:06:13: feedback like and it just it's just
01:06:15: constant like you know it's constant
01:06:16: grind and it kind of becomes difficult
01:06:18: and so that loop just kind of becomes
01:06:21: more [music] like you know draining and
01:06:23: that kind of makes it more difficult to
01:06:24: work on things and it kind of got you
01:06:26: know to the point where like we need to
01:06:29: prioritize certain things now to just
01:06:31: improve the mental health improve you
01:06:34: know the positivity [music]
01:06:36: um make things you know kind of exciting
01:06:39: you know again uh so what we'll be doing
01:06:42: is uh we're going to be making a number
01:06:44: of changes we're going to publish uh
01:06:47: sort of a discussion and a bunch of
01:06:49: documents and things where there's like
01:06:52: several initiatives
01:06:54: um you know to just change the process
01:06:56: and improve the process. Uh and that
01:06:59: overall should be you know
01:07:02: should be making changes that like
01:07:04: change the whole development loop into
01:07:06: something that is like you know less
01:07:08: draining and more positive and gives us
01:07:09: more energy and makes them more excited
01:07:12: to work on features. Um and the way we
01:07:15: want to approach this is like you know
01:07:16: open up as a discussion as well with
01:07:18: like your video community because we
01:07:19: want you know also your ideas what would
01:07:22: make things
01:07:24: you know feel better what makes things
01:07:26: kind of more fun and more exciting but
01:07:28: we have a lot of ideas of our own. Um
01:07:31: this is going to be published soon so
01:07:33: we'll be able to like read everything
01:07:34: but um we wanted to sort of bring it
01:07:37: bring it up you know through the live
01:07:39: stream uh so you can kind of you know
01:07:40: ask us questions and we can kind of you
01:07:42: know sort of clarify it because we know
01:07:45: people like you know will kind of skip
01:07:46: through things uh you know
01:07:51: and sort of don't read something so we
01:07:53: figure oh my thank you thank you video
01:07:55: discord um so many more subscriptions
01:07:59: Um,
01:08:02: oh my god, there's so many.
01:08:05: Thank you,
01:08:05: >> bro.
01:08:07: >> But yeah, there's there's a number of
01:08:09: changes and I kind of want to go over
01:08:10: them, you know, so we have like uh this
01:08:12: probably going to end up like, you know,
01:08:13: being cut into like some smaller videos
01:08:15: as well, so you can like, you know,
01:08:17: people don't like to read like there's
01:08:18: something to watch. Um,
01:08:22: so there's a number of ideas like going
01:08:24: to kind of have like how [music] to
01:08:25: improve, you know, the overall sort of
01:08:27: like positivity of development, how to
01:08:29: make things like feel better, how to
01:08:31: like improve our processes and
01:08:33: development group. Um, so one of the
01:08:37: things is we're going to be adding two
01:08:39: new issue templates. Uh, there's going
01:08:42: to be uh because I mean one of the
01:08:44: things I've been kind of doing is, you
01:08:46: know, sort of looking at things. How do
01:08:48: we actually develop this? How do we like
01:08:49: work on this? How do we publish updates?
01:08:51: How do we process feedback and sort of
01:08:54: and I got like this advice from uh from
01:08:56: actually like has kind of been dealing
01:08:58: with some like issues like as well in
01:09:00: the past. He has a lot of experience and
01:09:02: he just to me look at this as a project
01:09:04: you know like this is like a a bug to
01:09:07: fix in a way uh or it's like a feature
01:09:09: to add you know like but just kind of
01:09:11: take take the same approach with this as
01:09:14: I would take like you know solving
01:09:16: technical problems. Um and one of the
01:09:19: things is like you know uh for example
01:09:21: with GitHub uh there's two things that
01:09:24: often times you know I feel like the two
01:09:26: biggest sources of kind of like you know
01:09:28: frustration is one um a lot of times we
01:09:31: ask people you know to focus more on
01:09:34: like the underlying issue certain like
01:09:36: specific solutions because it becomes
01:09:38: kind of difficult for us to decipher
01:09:41: um decipher like you know what is
01:09:43: actually the problem because we see like
01:09:45: you know the solution they want but
01:09:46: maybe the solution doesn't quite work or
01:09:48: we're kind of confused why they need it.
01:09:50: Um, so what we're going to add, we're
01:09:51: going to add a issue template that's um
01:09:55: right now we're calling it a friction
01:09:57: point observation.
01:09:59: And what it's going to be is essentially
01:10:01: just documenting, you know, be like the
01:10:03: user, you know, which can be yourself,
01:10:05: it could be somebody else, you know, it
01:10:07: could be a new user uh who you noticed,
01:10:09: you know, struggling with something. you
01:10:11: notice them, you know, they want to do
01:10:13: something, you know, like for example,
01:10:14: they want to bring their avatar in or
01:10:16: they want to join people, they have
01:10:19: certain goal and then, you know, could
01:10:21: be like things. What did they try to do
01:10:23: and what was the friction point? What
01:10:24: did they like where did they get stuck?
01:10:27: And that's, you know, the information we
01:10:28: need like we don't need to focus right
01:10:30: away, you know, what what the solution
01:10:32: is. We just need to understand where
01:10:34: people get stuck. Uh so now we'll have
01:10:37: like you know this issue template where
01:10:39: if you notice this in your users if you
01:10:41: notice in yourself if you get stuck on
01:10:42: something you wanted to do something um
01:10:46: create like this type of issue and we
01:10:48: can look at like you know these issues
01:10:50: and be like we could think of like you
01:10:52: know those features
01:10:54: um that will solve these problems
01:10:57: because big part of our development work
01:10:59: is actually you know being kind of
01:11:01: creative figuring out you know new
01:11:02: features figuring out solutions to
01:11:05: problems. But with existing GitHub
01:11:07: issues, we kind of get like um
01:11:12: we almost like you know like kind of
01:11:14: robbed of that process where it's like
01:11:16: you know very focused on like this is
01:11:17: the solution like we want like you know
01:11:18: and like we just kind of implement like
01:11:21: things like you know people want and
01:11:22: like it kind of drains a lot of the fun
01:11:25: and a lot of the kind of creativity from
01:11:27: the development process. So by having
01:11:29: issue that's specifically for this
01:11:31: purpose
01:11:32: feel this might kind of you know help
01:11:35: you know direct people like you know
01:11:36: providing that kind of feedback. Uh so
01:11:39: that's the one type of issue. The other
01:11:41: type of issue is like uh it's stemming
01:11:43: from under observation I kind of made is
01:11:45: like where GitHub is pretty much like
01:11:47: you know all about things that are
01:11:48: wrong. It's like you know there's this
01:11:50: bug there's um you know there's like a
01:11:54: missing feature there's like something
01:11:55: that's hard to do. it's all focusing on
01:11:57: the negative stuff and to sort of
01:11:58: balance things the other type of issue
01:12:01: is going to be a positive observation.
01:12:03: So if there's something some change we
01:12:06: made because essentially right now like
01:12:08: GitHub is like letting us know all the
01:12:09: things that are wrong but to balance it
01:12:13: also helps us you know to know what what
01:12:15: things we actually did right what things
01:12:18: helped you you know what things improved
01:12:20: your workflow what features like excited
01:12:22: you um so you can have like another
01:12:25: issue for it and if you have like you
01:12:26: know any feedback if something helped
01:12:28: you um
01:12:31: you know if if something helped you and
01:12:33: improved like our workflow. Um this
01:12:36: would be a good issue type and it would
01:12:37: be good to let us know because one it
01:12:39: helps to balance the mood but also we
01:12:42: will want to do more of that you know if
01:12:44: if we see like you know this is working
01:12:46: this is making people happy this is
01:12:47: making people excited this is improving
01:12:49: things
01:12:51: we want to do more of that like like
01:12:52: whenever like I see for example people
01:12:54: you know making cool things at photon
01:12:56: dust I'm like I want to add more photo
01:12:57: modules I want to like you know let
01:12:59: people do even more things uh and that's
01:13:02: like a much better place to be you know
01:13:04: coming at things from features and
01:13:06: improving things you know than like the
01:13:08: more kind of negative aspect. Um so
01:13:13: I feel this will kind of help like you
01:13:15: know in kind of multiple ways and also
01:13:17: like let us know you know
01:13:20: because you want to you want to know
01:13:22: like you know these things are wrong and
01:13:23: you know none of that's going away. It's
01:13:25: still very important for us to know
01:13:26: things that need to be fixed that need
01:13:28: to be improved. Um, but it's also
01:13:30: important to know the things that went
01:13:32: right because that helps us, you know,
01:13:35: both like mentally like you know, like
01:13:37: it's not all bad. Like there's things
01:13:38: that we did change that like are good
01:13:41: and we want to do more of more of that.
01:13:43: And it's also like you know giving a
01:13:45: better direction because we do want to
01:13:47: keep doing things that keep making
01:13:48: people happy and that keep making you
01:13:50: know um
01:13:54: it's like
01:13:58: it essentially just gives like it's much
01:14:01: better kind of like you know motivator.
01:14:03: So those are going to be two new issue
01:14:05: types that going to be adding to GitHub.
01:14:07: They're going to appear soonish. Uh and
01:14:09: there's also going to be written
01:14:10: description so you can kind of you know
01:14:12: see more like they're meant to be
01:14:13: before. Um one more thing I'm going to
01:14:15: mention for the friction point
01:14:17: observation the important thing for
01:14:20: those issues is to keep it objective
01:14:22: like you know keep emotion out of the
01:14:24: issue because what it does it just kind
01:14:27: of adds you know noise and we want to
01:14:29: focus on fixing the problems and fixing
01:14:31: fixing the friction points. So, we're
01:14:33: going to be asking people, you know,
01:14:35: keep it neutral, keep focusing, you
01:14:37: know, this is what I wanted to do or
01:14:38: this is what somebody wanted to do. This
01:14:40: is where they got stuck. That's like,
01:14:42: you know, what we need to do to actually
01:14:44: fix the issue. Um,
01:14:47: and that's going to be kind of mentioned
01:14:48: in those things. The So, that's one of
01:14:52: the one of the changes we're planning.
01:14:54: Another thing that we want to do
01:14:56: introduce uh and actually kind of
01:14:58: started doing it a bit uh is something
01:15:01: that I'm currently calling like a
01:15:02: creative experimentation day because a
01:15:05: lot of the work um
01:15:09: a lot of the work uh we're doing is you
01:15:12: know stuff that needs to be done you
01:15:14: know it's like GitHub issues you know
01:15:16: bug fixes like things broken adding
01:15:17: features like this needs to be done this
01:15:19: needs to be done this needs to be done
01:15:20: and it's just like you know all of that
01:15:21: and it kind of one thing I noticed that
01:15:24: pushed out like, you know, all the fun
01:15:26: stuff, you know, stuff that's like
01:15:28: really like the just like cool things to
01:15:30: do that necessarily don't have like, you
01:15:32: know, like be like this is the the
01:15:35: priority thing and I feel that kind of
01:15:38: like, you know, shifted the bonds where
01:15:39: it's kind of become unhealthy. Um and to
01:15:43: kind of because like development like
01:15:46: especially a platform like this
01:15:48: it's meant to be fun you know like this
01:15:50: is like it started as a passion project
01:15:52: and if we don't have you know we only
01:15:54: have like things that really really need
01:15:55: to be done it suffocates a lot of that
01:15:58: passion so we need to bring you know a
01:16:00: bunch of that back and have have like
01:16:03: some time that we dedicate to just you
01:16:05: know having fun with it like making cool
01:16:07: features where essentially the only
01:16:10: prioritization
01:16:11: is going to be like, is it fun? Do we
01:16:13: want to work on it? We're not going to
01:16:14: care like, you know, how many apples it
01:16:16: has. We're not going to care, you know,
01:16:17: how many people are asking for it. Is it
01:16:19: fun? Do we want to make it? Because
01:16:21: often times those things also like, you
01:16:24: know, lead to things that people don't
01:16:26: end up like like li like li like li like
01:16:26: li like li like li like li like li like
01:16:26: li like li like liking a lot. Um, you
01:16:29: know, because
01:16:31: a lot of things that kind of stem from
01:16:32: from, you know, from passion,
01:16:36: it's kind of, you know, it kind of like
01:16:39: always reminds me of like, you know,
01:16:40: that quote from Henry Ford is like, you
01:16:42: know, if he if he asked people like, you
01:16:44: know, what they wanted, you know, he
01:16:47: would have built a faster horse because
01:16:50: there's like certain ideas, you know, we
01:16:51: have that people will not like people
01:16:53: won't be asking for them because people
01:16:54: [music] don't even think to ask them
01:16:56: because, you know, there our ideas.
01:16:58: They're like, you know, what sort of
01:16:59: drives the project. So,
01:17:02: what we're going to do is we're going to
01:17:04: have one day of the week. It can be
01:17:06: different for each developer, but one
01:17:08: day of the week, um, we're just going to
01:17:10: spend on fun things and we're going to
01:17:13: like, you know, stick to it. Sometimes
01:17:16: there's going to, you know,
01:17:17: complications. Sometimes maybe we need
01:17:18: to deal with you know emergency or some
01:17:20: deadline that's [music] going to move it
01:17:23: you know if that sac like requires uh us
01:17:26: to sacrifice that fun thing um we're
01:17:29: going to take like you know two the next
01:17:31: week.
01:17:32: So
01:17:35: the idea is essentially you know like if
01:17:37: something is a fun creative
01:17:38: experimenting feature
01:17:41: there's like one day dedicated to it. we
01:17:42: still have, you know, 4 days of the week
01:17:44: working on things that need to be done,
01:17:45: but there's like, you know, that one.
01:17:47: Um,
01:17:49: when something is in that [music] stage,
01:17:51: we also going to ask people, you know,
01:17:53: please keep in the spirit of
01:17:55: experimentation. And if you have like
01:17:56: you know for example concerns um you
01:18:00: know or things you want make your
01:18:02: feedback encouraging because like you
01:18:04: know just kind of
01:18:08: if you get excited about something
01:18:12: and like people are just like no I
01:18:13: shouldn't be doing that like it kind of
01:18:14: kills a lot of the excitement and that
01:18:16: can be like you know very damaging. Um,
01:18:22: so we're going to ask people and we're
01:18:24: going to like also try to make sure that
01:18:25: those things are marked. You know, this
01:18:26: is our experimentation fun thing.
01:18:29: There's the other side of this is like
01:18:31: if something is in that phase when we're
01:18:32: just kind of experimenting, it doesn't
01:18:34: necessarily
01:18:35: there's no expectation that it actually
01:18:37: gets merged like it might not even make
01:18:39: it, you know, to the like, you know, to
01:18:40: the builds. It's just like, you know,
01:18:42: going to play around. Maybe the idea
01:18:43: works out, maybe it doesn't. If the idea
01:18:45: works out then it moves into normal
01:18:47: feature and you know at that point like
01:18:49: we're going to be like okay there's
01:18:50: these concerns we need to make sure you
01:18:52: know compatibility like it [music]
01:18:53: doesn't break things and so on. That's
01:18:55: kind of where it becomes a little more
01:18:56: involved but not before it exits you
01:18:59: know the creative experimentation stage.
01:19:02: Um, so that's going to be another kind
01:19:04: of big change. And actually I got this
01:19:06: idea like you know uh I know like some
01:19:09: companies actually do it like you know
01:19:10: where they would like dedicate like uh
01:19:13: um actually comes from uh the biggest
01:19:16: example is from Unity where I don't know
01:19:18: if they still do it but like they would
01:19:21: dedicate every Friday where developers
01:19:23: just work on whatever you know like they
01:19:25: just experiment with ideas and [music]
01:19:26: like there's a lot of cool projects for
01:19:29: Unity that actually stemmed from this
01:19:30: Friday like you know experimentations
01:19:33: where it's just free to explore and you
01:19:34: know experiment experiment and so on. Um
01:19:38: so I wanted to kind of you know
01:19:39: introduce something similar.
01:19:42: Uh there's uh
01:19:45: let's see.
01:19:50: So that is another thing that we want to
01:19:52: do. Um, another [music]
01:19:55: thing we want to do is like encourage
01:19:56: people in the community
01:19:59: um to essentially share more positive
01:20:01: experiences, you know, on the SNI
01:20:03: because we want to see like, you know,
01:20:04: when we make features, when we improve
01:20:06: things or just people generally using
01:20:07: the platform, we want to see people are
01:20:09: having fun, people are like enjoying the
01:20:10: platform and as you know, even we know
01:20:13: there's going to be, you know, friction
01:20:14: points, there's going to be problems.
01:20:16: Not everybody's going to like it, but we
01:20:18: need to know there's both. is not I know
01:20:20: just the um
01:20:25: it's like
01:20:28: we need balance for it. So we want
01:20:30: people to encourage people to share you
01:20:32: know more on social media uh share more
01:20:34: like you know like just publicly showing
01:20:36: things they're building and showing the
01:20:38: fun people are having on the platform
01:20:39: and there's a few ways we want to do
01:20:42: this like you know and one of them
01:20:44: actually we kind of started you know on
01:20:45: the last resonance is like we just go
01:20:47: through a bunch of posts on blue sky
01:20:49: people showing stuff on you know stuff
01:20:51: they done on there night we showcase it
01:20:54: um you know we want to encourage more
01:20:55: people to do it because the thing you
01:20:57: made it might end up phenomenal streams
01:21:00: and then we bring the like really
01:21:01: coolest ones we bring them you know to
01:21:03: the recap streams as well. Um that way
01:21:07: you know there's there's more of an kind
01:21:09: of incentive like to doing this kind of
01:21:10: sharing. Um there's more um things like
01:21:14: for example one of the small things I
01:21:15: want to implement that's going to help
01:21:17: is like having like blue sky embed. So
01:21:18: like you can just copy the link and it
01:21:20: paste it shows all the video the text of
01:21:22: the post and so on. this going to make
01:21:24: it very easy like you know to do this
01:21:26: regularly uh instead of just you know
01:21:28: screenshotting my dash. Um we also want
01:21:31: to eventually like and I'm not saying
01:21:33: we're going to priorize this one right
01:21:35: now. At some point though we want to add
01:21:37: like additional features uh where for
01:21:40: example you know you um
01:21:46: for example you know say like you take
01:21:47: screenshot um want to make it so you
01:21:49: could do a video this way. So you could
01:21:51: just like trigger a quick video
01:21:52: recording here pops out a video and then
01:21:56: another feature is like you could like
01:21:57: you know tie Resonite into your social
01:21:59: like media account for example to blue
01:22:01: sky and the directly on the video can
01:22:03: just post it you know maybe write a
01:22:04: little thing and post it and handles it
01:22:06: for you lower the friction of doing that
01:22:09: because you feel by reducing the
01:22:11: friction
01:22:13: um
01:22:15: you know if you reduce the friction of
01:22:18: doing that people will do it more And
01:22:20: people do it more, we'll both like, you
01:22:22: know, have material to share. We'll have
01:22:23: like more we'll see more cool things
01:22:26: that people are doing on the platform.
01:22:27: Uh that's going to help motivate us, you
01:22:29: know, who like uh do more and also it
01:22:32: helps us, you know, grow the community
01:22:34: because the one of the big problems we
01:22:36: have is there is a lot of people on the
01:22:38: platform who are having fun, who are
01:22:40: doing a lot of cool things, but a lot of
01:22:42: people outside of Resoni don't really
01:22:44: know about it. And by show showcasing
01:22:47: you know some of the positive things
01:22:48: some of the fun people are having we
01:22:52: um you know we
01:22:56: um
01:22:58: we essentially kind of you know like
01:22:59: encourage more people to check like
01:23:01: there's a night out [music] and grow the
01:23:03: community which in turn you know just
01:23:05: helps everything.
01:23:07: Um
01:23:11: so that is that is that is another thing
01:23:13: that we want to do is you know
01:23:14: essentially encouraging everyone to
01:23:16: share and we also would want to know
01:23:17: once the discussion opens what would
01:23:20: help you like what would like make you
01:23:21: want to share things you know more
01:23:29: uh the next thing we want to do this
01:23:31: also going to help this is more kind of
01:23:32: like on team but also like part of the
01:23:34: community we want to encourage people to
01:23:36: like you to ask things in the right
01:23:38: channels. So essentially put together a
01:23:41: list of like you know if somebody has uh
01:23:42: this kind of issue go to hit hit up uh
01:23:45: if somebody has this kind of issue you
01:23:46: know find a mentor. If somebody has this
01:23:48: kind of issue make a moderation ticket
01:23:50: or make a support ticket you know or
01:23:51: bring it to office hours. Uh if you have
01:23:54: like a list like you know sort of a
01:23:55: guide like direct people to these
01:23:57: places. We're going to have it both for
01:23:59: our team so like you know our team knows
01:24:01: like to direct people and also for a
01:24:02: community. So if you see somebody know
01:24:04: asking in the wrong place, you can
01:24:05: suggest like this might be good thing to
01:24:07: bring to the office hours. That way you
01:24:09: know there's better kind of
01:24:10: communication and people know there's
01:24:11: like [music] specific points where we
01:24:13: are going to be answering our questions
01:24:15: and we can learn more about the platform
01:24:16: and instead of like you know relying on
01:24:18: like a lot of hearsay you know a lot of
01:24:21: like rumors that can be spreading around
01:24:23: people can get the question answered
01:24:25: like you know from the actual official
01:24:27: sources.
01:24:28: So documenting that and having that like
01:24:30: you know as a things anybody can link
01:24:33: and point [music] to like I think that's
01:24:34: going to help that as well. Um,
01:24:39: another thing that's uh uh we might
01:24:41: actually end up like prioritizing
01:24:42: soonish like as a feature is doing parts
01:24:45: of the molecule system and like you know
01:24:46: J4 has started been like working on the
01:24:48: CI/CD which is actually going to flow
01:24:49: into that because right now publishing
01:24:52: [music] builds there's a fair amount of
01:24:54: manual steps involved uh which takes you
01:24:57: know time away from actually developing
01:24:59: it also is more errorprone like
01:25:01: sometimes like I make mistakes like when
01:25:03: pushing the buttons and you know then
01:25:05: have to deal with that and that's
01:25:06: stressful.
01:25:07: It also makes it difficult to run
01:25:08: multiple pre-releases and as we have
01:25:10: more uh engineers on the team, you know,
01:25:13: we only have one pre-release channel
01:25:14: right now and it's kind of harder to do
01:25:17: um we have like
01:25:23: it's it's difficult like you know it's
01:25:24: difficult to just random things and then
01:25:26: like when when I'm reviewing you know
01:25:28: team members like contributions we need
01:25:30: to be a lot more careful before like
01:25:31: pushing the updates out and even then
01:25:33: some stuff still [music] slips. Uh so
01:25:36: with the molecule and the CI/CD every
01:25:38: time a team member makes a PR that can
01:25:41: essentially end up being you know a its
01:25:43: [music] own pre-release branch for a
01:25:45: specific feature the team member can
01:25:47: bring it to the community and be can you
01:25:48: do a bunch of testing on this. So before
01:25:50: it even gets merged we can get a bunch
01:25:52: of testing make sure it's as stable as
01:25:53: it can be before it gets merged. Um and
01:25:56: overall I feel it's going to help like
01:25:58: the process. Uh
01:26:01: so it's going to like you know lead to
01:26:03: like less bugs. It's going to lead like
01:26:06: you know to less like disruptions like
01:26:07: in the main branch and it's going to
01:26:08: reduce a lot of the overhead that's like
01:26:10: you know on me specifically too with PRs
01:26:13: because I can be like you know like this
01:26:14: got pre-released this got tested with a
01:26:16: bunch of people in the community. I
01:26:17: don't have to you know I don't have to
01:26:19: like read through the code and think of
01:26:20: like what possible bugs might happen
01:26:22: with this. So, that's going to be
01:26:25: another thing that's just going to help
01:26:26: improve our overall process, you know,
01:26:29: with resite.
01:26:31: And then, um, I was going to mention
01:26:33: like, you know, I'm going to be like
01:26:35: talking about this a fair bit. Um,
01:26:38: one of the,
01:26:42: uh, one of the things that I also going
01:26:44: to help like long term is doing gradual
01:26:47: open sourcing of Resonite. And I'm not
01:26:49: making announcement right now like of
01:26:51: like exactly when we're going to do it
01:26:54: like under license stuff like that. It's
01:26:55: still kind of like um we need more
01:26:58: discussions internally. But generally
01:27:01: what we want to do is like you know open
01:27:03: pieces of Resonite you know piece by
01:27:06: piece and allow community to make um
01:27:12: allow community essentially to make like
01:27:14: you know contributions back fixes um
01:27:19: and reducing you know some of the
01:27:21: pressure like on us. Um the way we want
01:27:24: to approach it is like you know we going
01:27:26: to do it first for things like you know
01:27:29: where it's like we don't have to worry
01:27:30: too much about like you know breaking
01:27:32: compatibility for example. So for
01:27:34: example we want to do like import export
01:27:36: modules you know so for example if
01:27:39: there's issues with importing certain
01:27:40: models people can make like you know
01:27:42: contributions to those make back fixes
01:27:44: there um or we can like even add your
01:27:48: own importers. So like we can we will
01:27:50: allow you know for modules like for
01:27:54: importers to be essentially loaded more
01:27:55: like plugins where they don't you know
01:27:58: they don't break the compatibility
01:27:59: between builds and they just introduce
01:28:00: new support for new formats that you can
01:28:03: now bring into Resonite and even if
01:28:06: something is something we wouldn't
01:28:07: include [music]
01:28:09: officially um
01:28:13: you know like it's it's going to be
01:28:15: something like you install like as a
01:28:16: third party or maybe like you you need
01:28:18: to modify importer, you know, for the
01:28:20: studio specific needs for a project
01:28:22: you're working on. You can make a fork,
01:28:24: you know, build of our own and [music]
01:28:26: make whatever customizations you need.
01:28:28: So stuff like it would help and it
01:28:30: doesn't like, you know, affect
01:28:31: compatibility because it's just going
01:28:32: to, you know, the sort of barrier
01:28:34: between bringing content in and out.
01:28:37: Another one that I feel is going to
01:28:38: benefit from that hugely is uh device
01:28:41: drivers. So if there's like an issue
01:28:43: with some hardware, you know, face
01:28:44: tracking, trackers, you know, haptics,
01:28:48: we allow like, you know, community to
01:28:50: like make uh contributions and fixes. If
01:28:52: you want support for new hardware or if
01:28:53: you want the hardware to be supported
01:28:55: differently, you'll be able to do that
01:28:57: as well.
01:28:58: So I think that that also will like you
01:29:00: know help um that will help
01:29:05: reduce some of the pressure on us and
01:29:07: kind of help like you know lean more
01:29:09: into the comments and give give you in
01:29:12: the community kind of more control over
01:29:14: you know parts of this platform while
01:29:16: still keeping [music] like you know
01:29:17: probably going to keep the core closed
01:29:20: for longer. I don't know exactly how
01:29:23: it's going to look for that one yet
01:29:24: because we the one thing we do want to
01:29:26: avoid is like you know fragmentation
01:29:28: where like if we open the whole thing
01:29:31: right now it'll fragment into like you
01:29:33: know a bunch of different versions that
01:29:34: are not compatible with each other and
01:29:37: I feel with the size of the community we
01:29:39: have right now think the gear for great
01:29:42: with the size of the community right now
01:29:44: that would um
01:29:48: like it might be too risky to do right
01:29:49: now. So I feel that's a good thing for
01:29:51: once we kind of grow more and once we
01:29:52: have kind of more um developed
01:29:57: um once we have kind of you know more
01:29:59: developed
01:30:03: sort of like you know processes for some
01:30:05: of the things and some of the technical
01:30:06: things too.
01:30:08: Um so yeah this kind of covers uh I'm
01:30:12: just kind of checking the document
01:30:14: um and all of this you know everything
01:30:16: that we kind of announced like that uh
01:30:18: we plan to do some of this we'll be
01:30:19: doing right away like so in the upcoming
01:30:22: weeks and some of it like you know
01:30:23: features for a bit later uh but overall
01:30:26: essentially the
01:30:28: main focus right now is you know
01:30:30: improving the mental health improving
01:30:32: the like positivity because that's going
01:30:33: to make it much easier to work on future
01:30:36: things and we've kind of reached a point
01:30:38: where it needs to be a priority. It
01:30:40: needs to be something like that's not
01:30:42: just, you know, in the background on the
01:30:44: side because it kept getting, you know,
01:30:46: just pushed off for so long
01:30:50: and it needs to be like, you know,
01:30:51: focused on right now so we can kind of
01:30:53: keep going and we can keep working on
01:30:54: this platform for like, you know, years
01:30:56: down the line.
01:30:58: Um, so all of this this is going to be
01:31:02: uh
01:31:04: another actually one one more thing I
01:31:06: kind of missed. We're going to we're
01:31:07: going to publish also like more
01:31:08: documents like uh one of the things I
01:31:11: wrote is like a technical manifesto and
01:31:13: sort of design principles. So by for
01:31:17: like you know by writing those down I
01:31:19: feel and sharing them with everyone I
01:31:21: feel it's going to make it easier for
01:31:22: people to sort of understand the
01:31:23: philosophy of how this platform is
01:31:26: developed and how like you know what
01:31:27: sort of principles we follow and what
01:31:29: principles we stick to. So that's going
01:31:31: to be another thing you know we're going
01:31:33: to share as part of this. Um
01:31:38: so yeah uh I'm going to publish the
01:31:40: document uh soonish might not be next
01:31:43: week.
01:31:45: Um
01:31:47: because next week I'll be like at MF and
01:31:49: I'll be traveling. Uh it's probably
01:31:50: going to be like the week after that.
01:31:53: Um and it's going to like you know have
01:31:55: everything kind of written down. It's
01:31:56: going to be like discussion so you can
01:31:57: like you know help contribute as well
01:31:59: like if you want you have ideas or you
01:32:01: like you know um things
01:32:04: but overall this is you know what will
01:32:07: uh what I've been kind of like you know
01:32:09: focusing on
01:32:11: uh myself especially and what I'm not
01:32:14: going to be like focusing on you know
01:32:15: like putting some of these things like
01:32:18: uh in place
01:32:20: um because if we have like you know
01:32:22: better processes if we have better you
01:32:25: you know, development loop that's going
01:32:27: to help everything that kind of comes,
01:32:28: you know, everything that comes
01:32:30: afterwards.
01:32:32: Um,
01:32:34: so I think that kind of covers
01:32:36: everything. Um, we kind of like we
01:32:37: answer like probably a bunch of
01:32:39: questions as well. So, we're going to
01:32:41: like go through those. Um,
01:32:44: but, uh, thank you like, you know, for
01:32:47: for for listening to this. I hope this
01:32:49: kind of I know it's kind of like you
01:32:52: know not the feature focus right now.
01:32:56: Well, there's going to be some features
01:32:57: are related to it like more kind of
01:32:59: smaller for some of the some of them. Um
01:33:04: but um this is going to help us you know
01:33:08: like make the whole process more like
01:33:10: healthier.
01:33:11: Um so with that let's go to the
01:33:14: questions.
01:33:16: Uh, there's a lot of subs again. Thank
01:33:19: you.
01:33:22: >> That's a lot of money.
01:33:24: >> There's a lot of money. Thank you.
01:33:33: So, uh, there's probably going to be a
01:33:35: few questions that are not related to
01:33:36: this, but we're just going to We have uh
01:33:39: How much time do we have?
01:33:44: Actually, wait. What time? uh
01:33:47: >> about like
01:33:48: >> 25 minutes.
01:33:50: >> We might skip the social thing because
01:33:51: this was like a longer announcement. Um
01:33:54: so we're going to go through the
01:33:55: questions uh as fast as we can because
01:33:58: we don't have as much time. So like at
01:33:59: [music] this point the questions might
01:34:01: not get answered if there's too many. I
01:34:03: don't know how many there is. I try to
01:34:04: go through them as fast as I can. Uh Zar
01:34:07: is asking with perflex as an asset. What
01:34:09: do you think about perfax worklets like
01:34:10: the web standard which run separately
01:34:12: from main game like audio worklets for
01:34:14: customary effects perhaps even mesh
01:34:16: worklets for procedial custom meshes. Um
01:34:20: so
01:34:23: the so there's like a different things.
01:34:25: So like
01:34:27: one thing I kind of wanted to do with
01:34:28: perflex is like where you can actually
01:34:30: build something that's like you know web
01:34:31: like request response. So like once we
01:34:33: introduce more stuff on the cloud, for
01:34:35: example, some database stuff, you know,
01:34:37: you could maybe have like something that
01:34:39: processes and like you know, updates
01:34:40: things and you could just build some
01:34:41: prototyp
01:34:43: like, you know, a web thing. Um,
01:34:48: but like you know doing stuff like for
01:34:50: example uh they call it audio work
01:34:52: class. We have like the audio DSP uh or
01:34:55: mesh DSP that's going to like you know
01:34:56: be able to generate those things. Um
01:34:59: there something that's already planned.
01:35:01: uh we have like issues for those and
01:35:03: actually the way protolex is designed so
01:35:05: like unless it's using stuff in the
01:35:07: fruits engine you can actually run it
01:35:09: separately and outside of it so one of
01:35:12: the planned features is you could
01:35:13: potentially have you know the audio DSP
01:35:16: and if it's not tying into fruits engine
01:35:19: um you could run it externally you could
01:35:21: like you know just export it as a thing
01:35:23: or you could even run it like a you know
01:35:24: web there's like lots of different ways
01:35:26: so there's definitely going to be some
01:35:28: of
01:35:31: It doesn't even need to be like, you
01:35:32: know, protolex as an asset. There's like
01:35:33: multiple ways to kind of serialize it,
01:35:35: but it's going to make it easier. Um,
01:35:41: uh, there's some discussion with this.
01:35:42: I'm going to skip that.
01:35:46: Uh, this one's for S. Alexp is asking,
01:35:48: sir, how does it look currently with
01:35:50: integration of things like Blender NFmpe
01:35:52: on Linux?
01:36:05: Um,
01:36:08: sorry, I realized I had accidentally
01:36:10: muted myself while I was reading that
01:36:11: out loud.
01:36:12: >> Um,
01:36:16: I
01:36:22: >> Are there issues open on those? I'm I'm
01:36:24: I've admittedly not
01:36:26: >> open open GitHub issues for it like if
01:36:28: there's not [music]
01:36:29: uh GitHub issues.
01:36:32: >> Yeah, I would I would definitely open
01:36:33: issues for those if there aren't already
01:36:34: because I don't think I've seen them and
01:36:36: if I haven't I'm sorry.
01:36:39: >> Uh
01:36:43: boy doing listing safe uh recent mental
01:36:46: yes but multiple questions. I'm kind of
01:36:48: kind of covered it like a lot with the
01:36:50: big announcement. So, I'm going to skip
01:36:52: that one because I got like not too much
01:36:54: time. BD is asking if flex post is going
01:36:57: to help with I rework. Does that mean I
01:36:59: rework won't come before Q3 26? Not like
01:37:02: this. Um, no, this doesn't like we can
01:37:04: like I still use like you know the
01:37:06: normal trackers. Uh, so it's not
01:37:09: dependent on that.
01:37:11: >> Yeah, full body does exist. We can we
01:37:13: can still work on it's okay.
01:37:18: Uh Var 120 is asking any plans to expand
01:37:21: physics engine currently uses? Yes, we
01:37:24: do plan to add rigid body support at
01:37:26: some point. Uh there's a good for it
01:37:28: like uploads if you want. Um we also did
01:37:30: like videos on it in the past. Uh there
01:37:33: should be some like on YouTube channel.
01:37:36: Uh Kab is asking where inventory update.
01:37:39: Uh can skip that. Um
01:37:43: there's uh this going to be part of like
01:37:45: the UI rework. Uh we don't have like an
01:37:46: announcement on that one.
01:37:52: Uh
01:37:55: skipping that. Uh Brassert's asking
01:38:01: uh you mentioned it's a friction point
01:38:02: template but described as getting stuck.
01:38:04: I consider friction points to be much
01:38:05: more general than just getting stuck.
01:38:07: For example, friction point for me lack
01:38:09: of kill for reducing uh repeated key
01:38:12: presses and inputs to reduce hand pain.
01:38:14: So comp mode is it something that fits
01:38:16: into the friction point category? Is
01:38:17: friction point much more limited
01:38:19: definition getting stuck working with a
01:38:21: system? No, it can be that too like um
01:38:24: is essentially like friction doesn't
01:38:26: mean necessarily just getting stuck. It
01:38:28: might be like you know this thing you
01:38:29: want to do is difficult or like you know
01:38:33: like it could be either you didn't
01:38:35: figure out how to do it or like it's
01:38:37: just too complicated to figure out. It
01:38:38: was too much pain. So like the like I
01:38:41: would say it fits the definition. This
01:38:43: essentially, you know, something
01:38:46: that is a that is general um
01:38:53: dynamic
01:38:56: collections [music] can be implemented.
01:38:57: Um that's just question of
01:38:59: prioritization. So they need to be
01:39:01: prioritized.
01:39:07: Uh there's a lot of questions within the
01:39:10: chat. Please, please keep like the
01:39:12: question if you're like just talking
01:39:13: about themsel like yourself like please
01:39:15: keep it to minimum because uh it pops on
01:39:17: our thing.
01:39:22: Uh modify arc will users get a new badge
01:39:24: or bonus storage for contributing code.
01:39:26: Um I mean if you do introduce like you
01:39:28: know like ways to contribute like that
01:39:30: this definitely a thing we would do like
01:39:32: we love giving badges. uh we haven't
01:39:34: like like I said like this is still we
01:39:36: need to more discussions before we
01:39:38: actually do this but like you know I see
01:39:41: us doing that because we do it for for
01:39:42: example for translators we have like
01:39:44: translator get a badge so
01:39:47: um
01:39:58: get another question but uh someone is
01:40:01: mentioning about bringing mods on
01:40:03: mainline I that wireless itself my
01:40:04: library for Linux vent was burned into
01:40:06: YDMS GitHub group might eventually be
01:40:08: burned into mainline for Linux users I
01:40:10: might mention that yes yeah this is
01:40:11: another good example um it actually
01:40:14: shows one thing like where we end up
01:40:16: like using similar code is if you make a
01:40:18: library uh and actually another example
01:40:20: is the uh the open visim like analyzer
01:40:23: uh by Kyu because on Linux their issue
01:40:27: was you know the library for vice
01:40:29: analysis it only works on Windows they
01:40:31: don't make Linux binaries Um so Kaio be
01:40:34: like they they made their own library
01:40:36: and then they made a mod to you know
01:40:37: addite. What we did is we added the
01:40:40: support officially using the library
01:40:41: they have created. So this another good
01:40:43: way you know to kind of contribute is
01:40:44: like if you make something as a
01:40:46: self-contained library it has like you
01:40:47: know good license we can use then your
01:40:49: work might end up like being integrated
01:40:51: that way. Uh similar with this because I
01:40:53: know like you made like um
01:40:56: we're kind of working on that one I
01:40:57: think uh where we made like you know the
01:40:59: wrapper for the library. So things like
01:41:01: that definitely help. we still make sure
01:41:03: like you know we actually make the
01:41:04: integration you know properly with our
01:41:06: like code base and like using the mod
01:41:09: code but if it's based on a library then
01:41:11: that definitely helps us and we will you
01:41:14: know use that if we can
01:41:27: uh Kro is asking uh is molecule part of
01:41:29: improving death process just curious yes
01:41:32: Uh I don't know if this was asked like
01:41:33: when I was still explaining. No, this is
01:41:35: what I recent. Um I kind of talked about
01:41:37: it a bunch like but yeah it's it'll help
01:41:39: improve the processor. There's a lot of
01:41:41: stress. There's a lot of overhead. It's
01:41:42: also going to help improve things for
01:41:43: the community because we can run you
01:41:45: know multiple pre-leases and make sure
01:41:47: to test more features before they
01:41:49: actually hit the main line. Uh so that's
01:41:51: going to help like you know especially
01:41:52: with more developers on the team.
01:41:59: And actually we kind of shoot through
01:42:01: the questions pretty quick. Um Shylo is
01:42:04: asking uh any chance we could add some
01:42:06: search function within the UI update for
01:42:08: inventory settings per flex inspector
01:42:10: searches would be on my wish list. Yes,
01:42:12: that is one of the plannings. We
01:42:13: actually already have like sort of
01:42:15: groundwork for that because the settings
01:42:17: UI when we reworked the settings UI that
01:42:19: was actually laying groundwork for a lot
01:42:22: of the future UI rework and that's going
01:42:24: to make reworking those future UI much
01:42:25: simpler. Um it uses something we call
01:42:28: data feeds and that makes it much easier
01:42:31: to build UIs uh for tonight. Uh it makes
01:42:34: it so we can build them faster and we
01:42:37: can like you know make them better
01:42:38: because no longer we have to construct
01:42:40: the entire UI from the code. We just
01:42:42: focus on code that just provides the
01:42:44: structure and the functionality and the
01:42:45: actual UI uses reusable templates that
01:42:49: our AR team makes in game. Uh and part
01:42:52: of the data feeds is the natively
01:42:53: support search functionality. Um it's
01:42:56: something I haven't not like added to
01:42:57: settings yet but even like the settings
01:42:59: they would support like you know search
01:43:01: um and the inventory components you know
01:43:04: like all the other stuff it's also going
01:43:06: to be um it's going to be like using
01:43:09: data feeds which has you know structures
01:43:12: necessary for search functionality.
01:43:14: So um it's just going to call me to all
01:43:17: those UIs.
01:43:24: Uh, next question is from modify arc.
01:43:26: Uh, when will Purple Prime get a break
01:43:29: from business obelisk? Um, I remember
01:43:32: asking him in his office hours like on
01:43:34: Tuesday. Um, I think last time he
01:43:36: mentioned like they can expect stuff to
01:43:37: be done sometime January, maybe through
01:43:40: March. So, but it's better question to
01:43:43: ask him.
01:43:45: >> If you make a pentagram out of
01:43:46: mozzarella cheese, maybe.
01:43:49: >> Oh my god. Um, Blue Garder is Portfax
01:43:51: update still a priority? Uh, I'm not
01:43:54: sure what do you mean because uh right
01:43:56: now that's not a priority and I don't
01:43:59: know what you mean by protolex update.
01:44:00: It's going to mean a lot of different
01:44:01: things.
01:44:05: Uh, Demo is asking, I don't know is uh
01:44:07: covered, but is there a deep dive on
01:44:09: molecule or will there be one in the
01:44:10: future? Uh, there actually is a bunch in
01:44:12: the GitHub issue. I recommend checking
01:44:15: it out because it actually spells out,
01:44:16: you know, a lot of the things that it
01:44:17: will do. And there's also going to be
01:44:19: more like once we make the post about
01:44:21: you know the priorities there's going to
01:44:23: be a link to that but you can check the
01:44:24: GitHub issue right now just search
01:44:25: molecule on the GitHub and you will just
01:44:28: find you know you will find like a lot
01:44:31: of info.
01:44:36: Uh Chris is asking uh would it be
01:44:38: possible to allow plugins to provide
01:44:39: data feeds usable inside regular
01:44:41: sessions? um not without like everybody
01:44:44: having the same plugin because the data
01:44:45: feed like you know everybody in the
01:44:48: session needs to like have access to the
01:44:50: data feed source which means it needs to
01:44:51: be inserted into the data model so
01:44:54: everybody needs to have the plugin
01:44:57: only way would be like if it's like
01:44:59: something more like a dynamic system but
01:45:01: that's
01:45:03: depends what exactly want to do
01:45:07: on the host only I guess you really want
01:45:10: to
01:45:11: >> that breaks things like like that's
01:45:13: that's not going to work.
01:45:21: Uh J Fox is asking how we're going to
01:45:24: enforce people taking the creative day
01:45:26: are going to send them emotion manipulat
01:45:28: stickers if they skip them. No, that's
01:45:30: Prime's job. He he actually mentioned
01:45:32: like doing something like that during
01:45:34: the meeting that he's going to send like
01:45:35: people like you know sad cat once. It's
01:45:38: technically thing like you know
01:45:39: necessarily going to so what we're going
01:45:41: to more focus on enforcing is like if
01:45:44: people don't respect it. So if you know
01:45:46: say either people on the team or people
01:45:48: on the community like you know they will
01:45:51: um
01:45:52: if anybody's like you know like oh like
01:45:54: you shouldn't be like you know working
01:45:55: on these things you know uh you should
01:45:57: be like working on this we'll be like no
01:45:58: this is their day you don't own their
01:46:01: creative experimentation day. they own
01:46:03: that this is what we're doing because
01:46:05: our you know mental health hold is
01:46:06: important. So
01:46:09: that's kind of like where we're going
01:46:10: to, you know, stick to like where we if
01:46:12: anybody pushes against this, we're going
01:46:14: to make sure no this is this is a thing
01:46:16: they're doing. It's not up to a debate
01:46:18: like you know like we as developers we
01:46:21: need that one day. It's one day you
01:46:23: still get you know the four other days
01:46:25: like are generally kind of focused you
01:46:26: know on things that community needs and
01:46:28: the priorities of the community. But let
01:46:30: let us let us have you know that one
01:46:32: day.
01:46:36: Uh the redneck favorite enam uh the
01:46:40: dummy enamor
01:46:45: asking halfife 3 tomorrow I wish.
01:46:49: >> No we only got gabe cube.
01:46:55: Uh would team consider a way to
01:46:58: distribute trusted plugins made by
01:46:59: community and open source and built by
01:47:00: the team to ensure it's safe to
01:47:01: distribute. Depends what it is like it
01:47:04: it adds a lot of like pixster process
01:47:06: because we need to like you know review
01:47:07: the code and every change you make you
01:47:10: know potentially could sneak something
01:47:11: in and I'm not sure like you would do it
01:47:13: but eventually someone would do it. Uh
01:47:17: so that's a lot of process. So and as
01:47:19: the community grows there's going to be
01:47:20: no more code to review. So
01:47:24: I don't know that depends like what it
01:47:26: would be for.
01:47:31: Uh JF Fox is asking uh how long until I
01:47:35: can write scripts forite in Cobalt. Um
01:47:38: once we get a web assembly integration
01:47:39: you will be able to because uh
01:47:42: Cloudflare has made cobalt to web
01:47:44: assembly compiler and it's called co
01:47:46: web. So once we have web assembly
01:47:48: support, you'll be able to code in
01:47:49: cobalt for resonite. And now we have to
01:47:52: live with that cursed knowledge.
01:47:55: >> We we can live in the cursed reality
01:47:56: right now because there exists visual
01:47:58: cobalt at this very moment.
01:48:02: >> Like in game and somebody made it. What?
01:48:05: >> It's not in game, but it is cobalt that
01:48:07: compiles.net. [music]
01:48:11: >> Uh you can make a plugin for that. I
01:48:13: mean you can with plugins you can make
01:48:15: like anything but it's not like
01:48:16: official. Uh Shy look is asking curious
01:48:18: what's the st behind the holes in your
01:48:20: ears. Um so my character like he's kind
01:48:23: of like sci-fi. So like he's not like
01:48:26: organic but he looks organic. Um but
01:48:29: it's kind of like you know sort of made
01:48:31: out of like uh like a phento machines
01:48:33: which is like you know sort of nanom
01:48:34: machines but more on the level of like
01:48:36: more like like elementary particles. uh
01:48:39: which is actually a concept because it's
01:48:40: stole from uh from Greg Egan's books.
01:48:43: It's very hard sci-fi and um the idea of
01:48:46: the character is like you know it's it's
01:48:48: sort of technology but it's not like you
01:48:50: know it's not android it's not like
01:48:51: [music] you know a robot cyborg whatever
01:48:54: it's technology like it's like at the
01:48:57: point like where it just mimics biology
01:48:59: so like looks very biological behaves
01:49:01: like biological but there's like you
01:49:02: know little hints that like it's not
01:49:04: quite and like one of them is like you
01:49:05: know the stripes that are like very
01:49:07: precise and it's also like the ear holes
01:49:09: they're also like you know very precise
01:49:10: that you wouldn't really find in
01:49:12: organic.
01:49:14: So that's kind of the the gist of it.
01:49:17: >> I want to like I want to like put my
01:49:19: fingers to them.
01:49:22: >> Next question. Also just kind of
01:49:24: speeding through because of like 7
01:49:25: minutes left. Uh modify arc is asking
01:49:27: will other team members be able to push
01:49:29: model updates with their bug fixes
01:49:30: features? Um
01:49:33: so technically with molecule like that
01:49:34: like it would become uh easier for like
01:49:36: other team members to push things but
01:49:39: generally like the things that kind of
01:49:42: part of that is like you know it still
01:49:43: needs to go through kind of through
01:49:44: review and get like merged. So I would
01:49:47: say probably not like there needs to be
01:49:48: like you know
01:49:50: some of the review process. Um but if if
01:49:54: there's like a really
01:49:57: if there's like something really urgent,
01:49:58: for example, not available, um the team
01:50:01: could be like, you know, like we need to
01:50:02: push this emergency update. This will
01:50:03: provide them tools to do that. I
01:50:05: technically could do it right now, too,
01:50:08: but you know, it's just part of that is
01:50:10: like more like, you know,
01:50:14: the process, you know, like we need
01:50:16: certain like processes to make sure like
01:50:17: things don't explode and we don't have a
01:50:19: bad scenario. Generally we want to
01:50:21: follow the process and part of the
01:50:22: process is like you know making sure
01:50:24: things get merged properly and they're
01:50:25: properly reviewed.
01:50:28: Uh someone is asking when is plugging to
01:50:32: be rewritten in cobalt? No.
01:50:36: Check the focus is a replicator u lower
01:50:39: level than that
01:50:42: sortish.
01:50:44: I don't know.
01:50:48: Uh the written echo V has V was added as
01:50:52: advisory member for the game awards
01:50:54: hoping manard I haven't heard of that I
01:50:56: don't know what's is that for Halfife 3.
01:51:08: Uh J4 is asking CS education can waste
01:51:12: $30 a year. the GitHub actions plugin
01:51:14: for brains
01:51:16: for I don't know
01:51:20: how it's $30
01:51:22: is not much but the dusk bob
01:51:28: we need uh just the sprinkles in
01:51:30: reference to my question about groups do
01:51:31: you think you'd be more open to trying
01:51:33: it if you had some general survey
01:51:34: community sentiment I think most users
01:51:36: would be for it but I can understand
01:51:38: there is risk involved they might help
01:51:40: like understanding you know how people
01:51:42: would like change things, but like we
01:51:44: need to get like we need to be really
01:51:45: kind of confident like you know it's not
01:51:47: going to have negative effects. So we
01:51:50: will need like a lot of people
01:51:51: participate in the survey and
01:51:55: understand like you know
01:52:01: so that that's all the questions we have
01:52:04: 5 minutes left. Let's see if we can do a
01:52:07: very quick blue sky post.
01:52:11: Uh
01:52:15: oh, actually which is asking a question
01:52:17: for both. Are you both excited for the
01:52:19: holidays? Yes, I'll be I'll be visiting
01:52:22: with people in the in the US and um
01:52:25: spending time and spending time with the
01:52:26: glitch. So, I'm kind of excited for
01:52:28: that. It's always nice. Actually, those
01:52:30: things you you're going to be there.
01:52:33: >> Yes, I'm going to be there. I'm going to
01:52:35: look at you with my meat eyeballs.
01:52:39: Maybe we'll do like a like resonance or
01:52:42: something.
01:52:44: >> Oh yeah, I'll be there from the 25th to
01:52:46: the 6th though time.
01:52:49: >> We'll we'll see. No promises.
01:52:57: Mer city. I'm sorry. I don't know how to
01:52:59: read the name. Uh what gaming chart do
01:53:01: you use? I don't. I have some weird
01:53:03: chair.
01:53:07: Uh let me see the car if there's
01:53:11: anything interesting. I want to bring at
01:53:13: least a few polls before we end it. And
01:53:15: we can do a little over because like we
01:53:17: started like a few minutes later, but uh
01:53:21: Grant said it's December now. She is
01:53:23: flying out. Run.
01:53:24: >> Oh,
01:53:26: okay. The problem is the top post right
01:53:28: now are mine hunted and blue sky. Uh
01:53:34: ooh. So making an avatar. Uh let's see.
01:53:38: I'm going to that actually really good.
01:53:40: That's quite a bit engagement too. So
01:53:46: So I still have to do it this way
01:53:47: because we don't have you know the embed
01:53:49: but it's one of the things you know we
01:53:50: can add. Uh [music]
01:53:51: looks like fluid. They're making an
01:53:54: avatar like a bird avatar. Um
01:53:59: actually looks pretty neat. like quite
01:54:00: like detailed headers
01:54:02: and they got it to work in the Resonite
01:54:05: 68k triangles. That's pretty cool. I was
01:54:07: always like collecting more avatars
01:54:10: and I'm sure a lot of people will enjoy
01:54:11: bird.
01:54:15: Oop, I clicked the [music] wrong thing.
01:54:23: See posts.
01:54:26: Okay. Anything else?
01:54:31: There's this one. Uh,
01:54:34: Oracle VM Virtual Fox.
01:54:37: Uh,
01:54:40: let me bring this index. This actually
01:54:42: has a video in it.
01:54:45: Uh,
01:54:52: importer is behaving weirdly.
01:54:59: So, this is the post. Um,
01:55:02: I don't know quite what to expect. Let's
01:55:04: watch the video. And um, let me bring
01:55:07: [music] the audio up.
01:55:15: Let's see what's happening.
01:55:18: Oh. Oh, they're getting like the effect
01:55:20: where the buffer doesn't clear.
01:55:25: That is fun. Kate,
01:55:34: that's
01:55:36: you know that's like it's one thing to
01:55:37: have like a visualizer but now the
01:55:39: entire world is the visualizer.
01:55:42: I think I don't know if it's like a bug
01:55:43: or something but [music] something like
01:55:45: went wrong.
01:55:47: They look stupid though.
01:55:50: Uh
01:55:52: let's see. We got the Okay, let's see.
01:55:58: And then we got we got a funny post um
01:56:01: from Colin.
01:56:06: Big thongs only happening on Resonite.
01:56:09: Yeah, just big big big big thongs
01:56:12: only in Resonite.
01:56:18: Okay. Uh, let's see any more post is one
01:56:22: of mine again. Oh, we got one from um
01:56:26: service Thanksgiving. Like I don't
01:56:28: really we don't celebrate Thanksgiving
01:56:30: over here, but uh I figure like a lot of
01:56:31: you guys probably do. Uh
01:56:40: let's see if this loads. Uh it's a
01:56:42: Thanksgiving video from uh
01:56:46: Autumn Blessings. So let's you the world
01:56:56: on a magic turkey ride. A whole new
01:57:00: world.
01:57:02: What is my life?
01:57:04: Only on Resonite.
01:57:07: And this is the poster in case you want
01:57:09: to check it out.
01:57:14: >> Okay.
01:57:15: I like that. I can see you taking the
01:57:17: picture and like the background of of
01:57:19: those pictures the screenshots.
01:57:21: >> Yeah, it's kind of because my D is like
01:57:23: transparent. So, we're going to take
01:57:25: like two quick ones and then we're going
01:57:27: to end the stream. [music] Um U1F 98A is
01:57:31: asking, do I do I get to submit a bug
01:57:33: report live on stream? No. Bug reports
01:57:36: go to GitHub.
01:57:39: We might talk about the bug, but if if
01:57:41: it's not reported and like uh we're
01:57:43: probably going to forget like after the
01:57:44: stream ends. So if if you want bugs
01:57:47: fixed, they need to be reported on
01:57:49: GitHub. And Shillock is asking question
01:57:51: if you're still taking them. Is there
01:57:52: plans to integrate new Steam frame on
01:57:54: terrorite or is it native uh because of
01:57:56: Steam VR? Um yes, we would love to. We
01:57:59: applied for a deficit. So Valve, please.
01:58:02: Um
01:58:04: we actually talked about it like on the
01:58:05: last resonance. Uh I recommend going on
01:58:08: our YouTube channel uh on thereite and
01:58:10: there there's like a video about our
01:58:12: thoughts on Steam Crame. um it kind of
01:58:15: goes like over it like we don't have
01:58:17: time anymore. Um but you'll be able to
01:58:20: learn more about autos and what we want
01:58:22: to do with it. So with this um thank you
01:58:25: everyone for watching. Um I hope like
01:58:27: you enjoyed like this on ends. Uh
01:58:29: there's not going to be one next week uh
01:58:32: because I'll be at MFF. Um
01:58:36: so there's probably going to be one
01:58:38: after that. I don't know how it like
01:58:39: works out time wise, but uh you'll see.
01:58:41: Um,
01:58:43: I'm going to like uh let you know uh in
01:58:45: case like that was canceled too. Um, so
01:58:48: I guess we'll see you in 2 weeks. Uh,
01:58:50: thank you everyone, you know, for
01:58:51: watching, for all the questions. Thank
01:58:52: you everyone for like, you know, using
01:58:54: Resonite, supporting us. Thank you so
01:58:56: much for the subscriptions as well. This
01:58:57: like helps the development too. Uh,
01:59:04: and yeah, like everybody like you know I
01:59:07: hope like um thank you for listening in
01:59:11: on the like [music]
01:59:13: what we're going to kind of you know
01:59:14: focus on. There's going to be more
01:59:15: information coming out to do probably
01:59:18: the week after the next one. Um
01:59:22: but yeah um thank you for watching.
01:59:24: Thank you for like, you know, supporting
01:59:26: this platform and like, you know, just
01:59:27: kind of being part of it and making cool
01:59:29: things. And I guess we'll see you in two
01:59:31: weeks. And we're going to check if
01:59:34: there's any interesting channel to rate.
01:59:38: Uh, we like to like rate any like
01:59:39: Resonate streamers around this time. Um,
01:59:45: often times there's just creator jam. So
01:59:47: like if you if you if you want to stream
01:59:49: around this time, this might be a good
01:59:50: time because you will get raided.
01:59:52: Actually, there's not even creator jam.
01:59:53: So unfortunately
01:59:55: this this ends here. Uh we don't have
01:59:59: anywhere cool to send you guys. So thank
02:00:03: you again very much for watching and uh
02:00:06: see you in two weeks probably. Bye.
02:00:12: >> Bye-bye.