This is a transcript of The Resonance from 2025 June 8.
00:00: Start recording. Make sure everything is
00:02: going.
00:03: Okay. Seems to be
00:06: green. Uh, let me actually make sure. Do
00:09: I
00:10: have Okay, there's plenty of space. Um,
00:14: hello.
00:16: Hello.
00:18: Hello. Do we have people? Oh, I need to
00:21: post the announcements actually.
00:27: Hello. Post this one.
00:31: Hello beautiful people in my computer.
00:34: They're in your computer, but they're in
00:36: my computer.
00:38: They're in our shared data model.
00:40: They're in the shared data model.
00:42: They're we get to share them. Hello.
00:45: Hello. Hello, Jack. Hello,
00:47: Marsh. But she is saying that we are the
00:50: people in on on their
00:52: monitor. How does that work?
00:56: I mean, it's all shared, really.
01:00: It's all shared. It's all shared
01:02: reality. That's what this platform is
01:03: about. Oh, and we got schnopit.
01:07: Actually, we got we got a schnopet this
01:10: week. We got a
01:14: schnoit. We missed the ground
01:18: schnoets or we've gotten them late.
01:20: Okay. Uh, posting one more announcement.
01:25: Time to more time to see Jack. I just
01:28: totally didn't totally didn't see you
01:30: like like at least like 5 minutes ago.
01:34: Oh my god.
01:36: More like 15 minutes, but whatever.
01:39: Well, you see the time just gotten long
01:41: because uh they selected a time and
01:43: stretch along the
01:45: Z-axis, possibly the X axis. I thought
01:48: it would be more wide. A Z Z Z Z Z Z Z Z
01:50: Z Z Z Z Z Z Z Z Z Z Z Z Z is
01:51: long
01:53: a based word choice. Yes, I wanted to do
01:57: this one for a bit, but like every time
01:59: like I was like I'm going to do this
02:00: world. Thank you for the subscription
02:02: like
02:03: every time I was about to like do this
02:05: world like it would be like a bunch of
02:06: like technical issues and stuff and I
02:09: was like I need something simpler for
02:12: now. Um but now I'm back home. Um so I
02:15: picked this world. Don't did run into a
02:18: world.
02:20: Um, no. Sorry. I did run into an issue
02:23: with this world. There's no seats in
02:25: this area. There's like some legally up
02:27: there, but it doesn't have like nice
02:29: views. So, I had to like sit on this
02:31: speaker here. And so, I was just
02:33: standing here. And I was like, Sarah,
02:35: I'm just going to make like, you know, a
02:36: thing for you or something so you can
02:37: stand on. And Sarah was like, nah, I'm
02:39: crouch. Anyways, so this is this is our
02:42: setup now. Thank you for subscription.
02:46: Thank you very
02:47: much this time. Yeah, to get the stand,
02:50: but we kind of
02:52: like in a ping distance. I'm in ping
02:56: distance.
03:00: Just a camera a little bit. It does give
03:01: like nice view and can
03:05: well subscribe it probably prime. Yes.
03:09: And we got ton x. There's two
03:11: types. Anyway, uh welcome to resonance
03:14: everyone. And this is a weekly usually
03:18: stream where we can ask anything about
03:21: our pretty much like whatever we want.
03:22: It can be technical things. It can be
03:24: you know whatever the philosophy of the
03:26: platform is you know like where we are
03:28: going like what our motivations like
03:30: what do you want to you know do you can
03:32: ask about theme we can ask like whatever
03:34: like even if we just want casual
03:35: questions those are kind of fun too. Um
03:38: the only thing make sure when you ask a
03:40: question put a question mark in it. That
03:42: way it kind of pops on our thing. I can
03:44: actually show you in a sec.
03:46: And you can see my
03:48: hair. Uh, let me fix that.
03:53: So, you can see like like the questions
03:55: kind of, you know, pop on the thing. So,
03:56: we make sure not to lose them. Uh, and
04:01: should all sound like I'm here with Syra
04:03: was also from an engineering theme. Uh,
04:06: and we should be ready to get started. I
04:09: think uh we're going to go through
04:12: questions we got from Discord first. Uh
04:15: there's actually not as much as last uh
04:17: week. Um so we get through those and
04:21: then we get to the questions from
04:22: Twitch. So uh feel free to ask like your
04:25: you know Twitch questions right now.
04:26: Like we're going to go through them. Uh
04:29: I'm going actually make a camera anchor
04:31: so like it's not kind of floating around
04:32: too much. Um especially when I put the
04:35: text on the screen. So you ready? Yeah.
04:38: Uh can get started. So the first
04:41: question is uh oh
04:45: boy. The first question is from missing.
04:49: Uh since you guys seem to enjoy rambling
04:52: about Doctor Who last time, least
04:54: favorite Doctor Who episodes and
04:57: why? Um I don't I don't know if I don't
05:00: know if that works. No, I have one. Love
05:03: and Monsters.
05:06: Okay. I always skip that one. Even some
05:10: sometimes even like when I was showing
05:11: Dr. Hoo people like I'm just like we're
05:13: going to skip this one.
05:16: [Music]
05:17: Which one is that? Is that from the new
05:19: new one or That's like um which is which
05:23: season was it? I actually see I don't
05:26: like it so much I don't remember which
05:27: season it's from. I think it's
05:29: like third season.
05:33: Doctor Who love
05:35: like it's very Doctor Light episode
05:39: and it's like one it's the one that's
05:41: been like written by like a kid like
05:43: based on the design by like a kid like
05:45: where it was like a thing which they
05:47: kind of did okay with it but it's just
05:49: it's it's kind of
05:51: Oh yeah. This is this is like the tenon
05:53: era like Doctor Who. Yeah. It's like a
05:55: while back and one is just like I don't
05:57: know it's
05:58: something that's kind of ick about it.
06:03: Actually, that's pretty much the only
06:04: one like that's the only
06:08: one I can kind of like think of like
06:11: most prominently. Like the other one uh
06:13: and I know like other people also
06:15: mention this one quite often is Fear
06:17: Her, but I don't like I find it a little
06:20: bit like boring like like it feels a
06:22: little bit like drag to get through, but
06:24: like it's not as bad. Like I do like
06:26: some of the ideas in that one.
06:29: Um, but like the the love monsters that
06:32: once like just escape.
06:36: Yeah, I mean I would have to agree. I
06:37: don't know. I don't I can't think of
06:40: explicitly an episode I don't like. I
06:44: don't know if there is an episode where
06:46: that I explicitly don't like. I mean, I
06:49: don't really care for a lot of like the
06:51: newer seasons of Doctor Who that have
06:53: come out recently just because I feel
06:55: like Yeah.
06:57: I kind of feel like they're just kind of
07:00: like it's just I don't know. They don't
07:03: really feel like they have
07:06: substance like they don't have the hook
07:08: and they just feel kind of like chintzy
07:11: and like their writing and stuff. Yeah,
07:14: it was like for me like a little
07:15: especially a lot of the chibnel era is
07:17: kind of like that. It's just kind of
07:18: like I watch through it. I'm
07:21: like and I don't have like super strong
07:23: feelings. It's just kind of like there
07:26: like some highlights there, but like
07:27: like a lot of it just felt like uh
07:32: yeah, it's just like it just feels it
07:34: just kind of feels like they're
07:35: capitalizing on like the the recognition
07:37: of Doctor Who rather than actually doing
07:39: Doctor Who. It's like wow, look at all
07:41: these wacky characters, you know, in
07:44: love. Then it's just like I don't give
07:47: also like things like like he's like
07:50: been really good like for setting up
07:52: some stuff because like there's stuff
07:54: like where is like ends up being kind of
07:56: intriguing but like then just ends up
07:58: like being super chaotic mess. Yeah. And
08:01: it's and then you're just kind of let
08:02: down by it.
08:05: Um but I feel like if for me the one
08:08: like like really dislike is like
08:10: um love monsters. Yeah. Even if you
08:14: don't remember it, watch it and then
08:15: they won't like it. No, I I remember it.
08:20: Anyways, uh we can move to the next one.
08:23: This one's shorter than the liked one.
08:25: Uh the next question
08:28: uh is from Revy. Rev is asking, could we
08:32: get onetime payment for headless client?
08:35: Um, probably not. Like because this is
08:39: like one of those things is, you know,
08:40: like where it's like sort of like a
08:42: subscription kind of service thing uh to
08:44: help like support a project. Um, how
08:47: much would the onetime price be? You
08:50: know, would we ask
08:52: you, you know, would we ask you
08:54: essentially like, you know, to pay for
08:57: one year ahead of time? Would it be 3
08:58: years? Would it be 5 years? Would it be
09:00: 10 years? like it's it makes it a little
09:02: bit kind of weird like you know where um
09:05: if you're
09:06: like paying like a
09:08: product
09:11: and you know and like then you kind of
09:13: like expecting like you know to get like
09:14: updates on it and so on because like the
09:16: funding like we get from you know Stripe
09:18: and Patreon that helps fund the project
09:22: and for components that kind of keep
09:25: going one of the one of the important
09:27: things like with businesses is like you
09:29: know you need cash flow Well, you need
09:31: like you know because like you have
09:32: bills to pay, you need to pay the
09:33: servers, you need to pay people, you
09:35: need to pay like you know whether other
09:37: companies like accounting company and
09:39: those are like monthly expenses
09:41: sometimes like you know even kind of
09:42: more frequent than that. Uh what's
09:44: frequented but generally they're monthly
09:46: expenses and you need cash flow to be
09:48: able to able to do these. Um so if you
09:51: do like one time payment you know you're
09:54: maybe able to pay like things for you
09:56: know that month or that few months but
09:59: once that is over you know like you
10:01: would essentially need like to
10:02: compensate like you would need to keep
10:05: bringing people on especially if it's
10:07: like you know something perpetual. So
10:08: the only way to keep that going is not
10:11: to just keep existing, you know,
10:13: customers, keep existing people. You
10:15: need to constantly be bringing more and
10:17: more. And if you don't, now you don't
10:18: have cash flow and now your company can
10:21: die as a result.
10:24: So if if we were to do like one time
10:27: payment, like it would probably be
10:29: something relatively high. We actually
10:32: well we do kind of do it for businesses
10:34: but like you know like where the
10:36: business will do like onetime payment
10:38: but like then it's you know in the range
10:40: of thousands like
10:44: dollars or potentially even more like
10:46: especially if it's coupled like you know
10:48: with like the business having its own uh
10:51: you know its own like uh cloud
10:53: deployment and stuff like that.
10:56: So, and even then like you know there's
10:58: like some limits on support. It's like
11:00: you know we'll be like okay we're going
11:02: to support you for like you know this
11:03: many years with this. So generally like
11:06: you don't want to do things which you
11:10: know you need to kind of support in
11:13: perpetuity for like one time payment
11:15: because at some point like it becomes
11:16: like not worth it and we kind of start
11:18: like you know losing money on it and we
11:20: start like losing money then that puts
11:22: the company in bad spot especially if
11:24: like we're small one and we don't have
11:26: as much of a buffer. So, um it
11:32: like it's possible like you know we
11:34: might like figure something out but also
11:36: like if we did like I feel like you know
11:37: it wouldn't be something you would be
11:39: looking for because you would be looking
11:40: for maybe a few like you know few
11:42: thousand worth of license or something
11:45: like that. So I don't think that's like
11:47: you know what you're looking for.
11:50: Yeah. That'd be like a at least after
11:52: we're like much better off on our feet
11:55: and stuff, right? Yeah. Like if so this
11:59: is the thing is like you know like if we
12:01: do have different sources of income say
12:03: like you know um we launch like you know
12:08: like a marketplace and the marketplace
12:09: starts bringing more you know
12:11: substantial kind of funds then we can be
12:14: okay like this is aable revenue stream
12:17: you know this is able to support the
12:19: company now we can you know kind of free
12:21: up some of the things that people wanted
12:22: and make them kind of more accessible
12:25: but until it happens you know we need to
12:27: be careful about our existing revenue
12:29: streams because like if we drop those or
12:31: if we mess those up um that can endanger
12:34: the company because
12:36: like you know we rely on those to kind
12:38: of keep things going.
12:43: Um let's see what's the next one. So the
12:47: next question is uh this a big one. Oh
12:50: boy.
12:53: Um I don't know where to put it. There
12:56: we go. I hope that's readable on stream,
12:58: but I'm going to read it out. Uh, Lex is
13:00: asking, "I've always wondered why the
13:02: dashboard isn't separate from the rest
13:04: of
13:07: the just started reading all the silly
13:10: things. Um, I'm just going to read the
13:11: whole thing first. Uh, I've always
13:13: wondered why the dashboard isn't
13:14: separate from the rest of the world. And
13:16: with the lightest mesh transfer update,
13:18: it seems to be even more negatively
13:19: affected by whatever is going on in an
13:21: instance, preventing interacting
13:22: entirely. This not to say isn't better
13:24: than completely freezing as previously,
13:25: which is appreciated. Specifically
13:27: though, I'm not sure why meshes that are
13:29: are rendering completely fine have to be
13:31: completely freeze and reload themselves
13:33: when joining a new world. Uh are they
13:35: being reuploaded despite not changing?
13:37: Uh that's not to mention accessibility
13:39: issues with dash becoming obscured by
13:40: word entities or floating point errors
13:42: when the user is far away from origin.
13:45: uh with upcoming multipprocess
13:47: architecture will user space will be
13:49: candidate for separating things and
13:50: process since it's technically its own
13:52: world in my opinion a dash is vital to
13:54: controlling session volume essential
13:56: functions of resonite that user needs
13:57: for accessibility so anything that
13:59: impedes it from working is detrimental
14:01: to their
14:03: experience so there's there's a lot in
14:06: this one um so first one like you
14:10: mentioned like you wondered why
14:12: dashboard isn't separate from the rest
14:13: of the world but it actually is dash
14:16: exists in the user space which is like
14:18: isolated from the world you are in and
14:20: it's done for security reasons. So the
14:24: actual you know stuff that controls the
14:25: dash and what represents the dash it is
14:28: separate from the world. It does not
14:29: exist in the world you're in. Uh and
14:32: that's like you know done kind of on
14:33: purpose. Um but what is like you know
14:37: important distinction is like you know
14:40: um there's a difference between you know
14:43: where something is and then like how it
14:45: like pipes the data for rendering
14:47: because everything's render together you
14:51: know like you have like a single
14:52: renderer and like it needs to render
14:54: everything together and um with the mesh
14:57: upload you know you need to push like
15:00: whenever the mesh data changes which I
15:02: also get into in a little bit because
15:04: you mentioned some things about that
15:06: whenever the mesh data like updates
15:09: um you know it needs to be pushed to the
15:12: GPU. problem is especially with like you
15:14: know direct x11 uh with opengl that you
15:18: know those APIs that needs to happen on
15:20: the rendering thread which is it's
15:23: effectively single threaded like you
15:25: cannot be you know pushing new data to
15:27: the GPU while another thread is like
15:29: doing rendering with a GPU it just ends
15:32: up it ends up exploding
15:35: um so even if you have like you know a
15:37: bunch of separate things uh
15:40: say I will Grab a
15:44: brush. Uh where's the brush?
15:47: Brushes should probably grab it at the
15:50: beginning. So say like you know you have
15:52: like lots of like separate things like
15:54: each one of these is meshes you know um
15:57: and say like you know this is one world
15:59: and this is another world and all of
16:02: these are updating and then oh actually
16:05: to turn those there we go.
16:08: So say like you know these are like
16:09: individual meshes they're like get
16:11: loading and they exist in separate
16:13: worlds you know they are they are
16:14: separate but the GPU you have like your
16:18: GPU here let this um I cannot draw
16:22: backwards so I'm just going to do this.
16:24: So you get your GPU and then you go to
16:27: you know
16:28: like direct x
16:34: 11. So you need to pipe your data. This
16:37: all needs to go in a queue because it's
16:39: being piped through the same thing. So
16:41: even though like you know the dash is a
16:43: separate it's separate from the world
16:46: the data it generates it needs to be ped
16:48: through piped through the same interface
16:49: because that's just unfortunately how
16:51: directex works and how the graphics APIs
16:53: work. Uh which means any of these things
16:56: if it wants to push data in it's going
16:59: to block the
17:00: queue. Um now what we can do to help
17:05: with that is uh because like what
17:07: essentially what happens is you know
17:08: like imagine we have a queue of the mesh
17:11: uploads. So let's say this is the queue
17:14: and then we have like a high priority
17:17: queue. So we actually have like two cues
17:20: right now. Um and this is all being you
17:23: know uploaded like you know to the this
17:26: is being uploaded to the GPU. So
17:28: whenever stuff gets put in the queue,
17:30: you know, we have like differently sized
17:32: like uploads. I'm just going to put some
17:34: here. We're going to like here and here
17:37: and here. And it's like there's a big
17:39: upload
17:41: here. So say the top one is the high
17:45: priority queue. This is, you know, for
17:46: like your UIs and so on. So and this is
17:49: the dash dash, you know, update. It
17:51: pushes this in. It uploads it. And maybe
17:54: there's like, you know, uh another one
17:56: after it. So it pushes this one, uploads
17:58: it, pushes this one, uploads it while
18:00: this big upload is waiting. But now this
18:02: queue is free. So what happens? It cues
18:06: up this upload. And this one takes a
18:08: while. Um, and in the meanwhile, as this
18:11: one's kind of, you know, going through
18:13: and it's taking a bit, your dash updates
18:15: again. So it puts this here, but this
18:17: one's already processing this. So it has
18:19: to wait for this big upload to
18:21: happen until it can, you know, push
18:24: itself again.
18:26: So that's like one of the things that
18:27: kind of like you know happens where like
18:29: a big upload like once it starts it
18:31: essentially ends up like clogging up the
18:32: queue for a while. And one of the things
18:35: we've done is like you know that like
18:36: this uploading it's it can actually
18:38: render another frame in between but it's
18:40: still kind of continuing the upload.
18:42: What we want to do is like sort of
18:43: interweave it. So we can you know kind
18:46: of split this one into like smaller
18:49: parts and then as as it's uploading we
18:52: can pause it and if another upload like
18:55: you know comes in we pause this one we
18:57: upload the you know we prioritize the
19:00: mesh uh for the bash again and then we
19:03: continue this one which means it's going
19:05: to slow this one because like you know
19:07: the bandwidth is limited here but at
19:09: least your dash will update you know
19:11: sooner. So that's the approach like we
19:14: want to take to improve the issue uh
19:17: that we're dealing with right now which
19:19: is also like a funny thing because this
19:20: kind of happens with development is like
19:22: when you optimize some things sometimes
19:24: it reveals like you know another issues
19:26: with some systems because they you know
19:29: they were designed when that
19:30: optimization didn't exist. So like we
19:32: didn't need that kind of you know
19:34: behavior and now that like you know the
19:36: behavior has changed now we actually
19:38: need that other system to change how it
19:40: behaves to get rid of another issue. Um
19:44: but it's something like you know that is
19:46: fixable it's just like you know needs
19:47: additional work. Um however you also
19:51: mention you know you specifically
19:53: mentioned specifically to I'm not sure
19:55: why meshes are they rendering completely
19:57: fine have completely freeze and reel
19:58: themselves when joining a new world. Uh
20:00: that's the problem is
20:02: they
20:04: like like I'm a little bit actually
20:06: confused by the question because like
20:08: you're saying they're being a repo
20:09: despite not changing they are changing
20:12: that's the whole point like your dash is
20:15: respond like when your dash is not
20:17: responding and it's just frozen that's
20:20: because it needs to change but the
20:22: changes you know are now being blocked
20:24: by a bigger upload. So like the whole
20:27: premise of that question is wrong like
20:30: like the the mesh is changing to reflect
20:33: the new updates you know to the UI to
20:35: whatever you're doing. Um and those
20:38: changes need to be uploaded through. So
20:40: like what you're seeing is you know the
20:43: mesh that represents the UI whatever
20:45: state it was last time you know with the
20:46: last upload but like to get a new UI
20:49: update it needs to update the mesh with
20:51: the new state.
20:54: Um, so you know
20:58: that's like pretty much like another
21:01: point is like the mesh is changing.
21:03: That's you know why and the fact that
21:05: like you know it's it's frozen means
21:07: that the ch like you know you're seeing
21:09: whatever the last state was. Um and to
21:12: like change that state you need to
21:13: upload updated version of the mesh. Um
21:18: they're also like mentioning like stuff
21:19: like you know accessibility issues like
21:21: entities floating point like those are
21:23: completely separate from the mesh upload
21:25: like that's like a different thing.
21:27: They're different problems. Uh there
21:29: also problems like we want to like you
21:31: know attacks in different ways like one
21:33: of one of them for like the dash um is
21:36: you know ability so you can like you
21:38: know toggle it to be like over
21:41: everything or not overlaid over
21:42: everything. And we kind of experimented
21:44: like with it for a bit. But um there's
21:46: actually one issue like if you have it
21:48: render over everything that we found out
21:50: u that becomes very confusing for users
21:53: is when you spawn things because imagine
21:54: like you're in your dash and you spawn
21:57: something like let me actually
22:01: uh let me actually switch this smooth
22:02: POV uh and also render private UI. There
22:06: we go. So say like you open your dash
22:08: and you spawn something. I click this. I
22:11: see it in front of me.
22:13: The problem is if the dash renders over
22:15: everything, this would be blocked. I
22:17: wouldn't see that I just spawned this
22:19: because this is in world and the dash
22:21: would be rendered on top and that kind
22:24: of becomes confusing like you know
22:27: behavior because like right now if I
22:28: spawn something I can see it right away.
22:30: Oh there it is. But what happened when
22:33: the dash was rendering over everything
22:34: is like you know you would spawn things
22:36: and it'll be like why is this not
22:37: spawning? like why is it and then you
22:38: close dash you'll be like oh there it
22:42: is.
22:43: So it's one of the reasons like we're
22:46: probably going to make it like a toggle.
22:47: So like you know you mostly use it
22:49: in emergency like uh like if you like
22:52: need like you know if there's something
22:54: really blocking you uh and it's probably
22:56: going to be also like semi-transparent
22:57: so you can still kind of tell but by
22:59: default we'll still have it uh
23:02: composited with the world because it
23:04: feels like most cases you know it's
23:05: fine. Um but there's like you know fewer
23:09: cases like where you need it to render
23:10: over everything else and you know then
23:13: that way like we'll have a toggle that
23:15: does render over everything else. You
23:17: just press it and now the dash is like
23:19: rendering over everything else and you
23:20: know takes priority. So it's kind of
23:23: like you know balance with like you know
23:24: UIUX things and so on. Um and like in
23:28: falling point that's like a whole own
23:31: kind of worms like you know it's not
23:32: even specific to the dash.
23:35: Um but uh you also mentioned with the
23:38: upcoming multiprocess architecture we
23:39: use space war beand needed for
23:40: separating to its own process. Um it's
23:43: actually one of the things we could do
23:45: like and one of the things we're
23:46: thinking about doing with there is a
23:47: night overlay where like you know the
23:49: dash and things is actually a separate
23:51: process that's running as a VR overlay.
23:54: Um and you'd be able to run it not just
23:58: over resonate but over other
23:59: applications as well. So that might
24:03: happen like I would like it to happen.
24:05: Um it's not going to happen as part of
24:07: the initial push uh because that would
24:09: kind of add complexity to it but it's uh
24:11: very likely to happen at some point like
24:13: you know later. Um which also might help
24:16: because like in some ways you know that
24:19: um the multipprocess separation like
24:21: helps further kind of isolate things and
24:23: make them more independent of each
24:25: other. Um it does add like additional
24:27: complexity but like I I would like this
24:29: one to happen and it might also make
24:32: like you know neat things where like you
24:33: know you can literally be you know you
24:36: can use your dash in other v other VR
24:38: applications as well. You know it could
24:40: be for example in VR chat and could
24:42: still be messaging people on there night
24:44: or maybe even have like you know
24:45: integrations with that. Um, and you
24:49: could even like maybe like use other
24:50: parts of the overlay where like actually
24:51: you spawn something and it spawns in an
24:53: overlay that's over the other
24:55: application. So there's like a lot of
24:57: kind of potential exciting applications
25:01: there. Uh, I think it kind of answers
25:04: most of everything in this
25:06: one.
25:10: Uh, next question is from uh,
25:14: BD_. Uh I'm going to put the C
25:19: here. So BD is asking in Gab issue 4547.
25:24: I reported issue where measures that
25:26: contain mix of blend shapes with normal
25:27: tension deltas and BL ships without
25:30: those bro mesh up changes. Do you
25:32: consider mesh x data with a mix of blend
25:34: chip configurations like this to be
25:36: broken data and so external tools
25:37: generating mesh should try to normalize
25:39: things or was this simply a bug in the
25:41: unit upload logic asking so I know where
25:44: to reward my work around uh so this one
25:47: I don't consider a bug like um uh we
25:50: made adjustments so like you can
25:52: actually mix uh blend shapes and like it
25:54: is also supported on the rendering end
25:56: so it is okay
25:59: um there might be like you know other
26:02: things like you can do to mesh eggs
26:03: which might like be well malformed like
26:06: data or like you know something that's
26:08: not like fully like supported but this
26:11: this one specifically I would say you
26:13: know it's fine like you can kind of
26:16: um like you you can generate blend
26:19: shapes where only some of them have like
26:21: normals the only thing I would say is
26:23: like uh I don't actually know if you can
26:25: even generate it with a structure is
26:26: like where if you have blend shapes with
26:29: multiple frames where some of them would
26:31: of normals and some of them would not.
26:34: So like if you have a blend shape you
26:35: know specific blend shape either all the
26:38: frames should have normals and tensions
26:39: or you know none of them should. Uh but
26:42: then like you know different blend ships
26:43: you can have blend ships where some have
26:44: normals and some
26:49: don't. Uh next
26:52: question is from Mark
26:57: N. Uh Mark, that's a big one too. Mark
27:01: is asking um an issue for this has
27:04: already been posted on GitHub, but I
27:06: would like to ask a bit of her as well.
27:07: In a war with other users inclines, when
27:10: you grab avatar, you want to change into
27:11: equip from context. New grabber slots
27:13: gets left behind your avatar hand and
27:15: your own grabber disappears. When
27:16: grabber remains on the avatar, you taken
27:18: off avatar no longer grabbed. I've seen
27:21: this confusing other situation.
27:22: Whatever. If you save avatar grabber. Um
27:25: yeah, I would say like uh hold on which
27:28: is per multiple grab in single hand.
27:30: This is very easy to reproduce and it's
27:32: very frequently encountered by Peter.
27:33: I've just started on it. So would
27:34: appreciate we could consider taking
27:35: measures to address this problem. Um I
27:38: don't I can't really like look into the
27:40: issue right now. So like like generally
27:43: like what we recommend if you feel like
27:44: an issue is important is make sure it
27:46: gets up votes on GitHub. That way it
27:49: kind of you know pops up. uh you can
27:51: also provide this in the GitHub issue
27:52: itself be like you know like iron into
27:54: new users getting confused by this um
27:57: you know uh give us like a little
27:59: additional context you know why it
28:01: should be prioritized um but it should
28:03: happen within the issue itself like
28:04: we're not able to prioritize things on
28:06: stream like this
28:14: um next questions from uh Kira
28:19: Kira. Oh no. Is is is this from Is this
28:22: from Deadnouth? Um K's asking
28:26: programming attire. Currently using
28:28: prefer. I usually just have sweatpants.
28:31: I mean I have like these like in game
28:33: but
28:34: um not unfortunately. Um
28:39: um do we have anything like I mean I
28:42: just wear like some kind of stretchy
28:45: fabric pants. not like sweatpants cuz I
28:47: think those are too baggy. I like
28:48: wearing slightly more form fitting uh
28:52: clothes and like a t-shirt or I will
28:54: like be wearing a sweatshirt if it's
28:56: kind of chilly. Yeah. Other than that,
28:58: I'm just wearing more like normal
28:59: clothes. I don't really have programming
29:01: attire. Maybe I'll maybe if I'm like out
29:03: and about, I will be programming with my
29:06: arm armors on, but that's about it. Once
29:09: I get some. But yeah, I I usually do
29:13: like whatever scum fit. like you're
29:15: going to be like sitting like you know
29:16: the chair for a while and do you want
29:18: you want to become f
29:23: uh the next question is
29:26: also from uh also from discord uh mark
29:31: and is
29:32: asking the name for boolean lunch not
29:34: node in the node browser is different
29:35: from the name display on node itself why
29:37: is that um I'm actually don't remember
29:40: like the specific case but often times
29:42: like the name of the fridges so it's
29:43: more readable because the uh the
29:46: component name that's tends to be more
29:49: technical. Um and then like you know
29:51: what we put on the node like we try to
29:53: like you know shorten the name or make
29:54: it like you know it's a bit like easier
29:56: to parse. Uh so it can be like you know
29:59: difference like the because the
30:00: difference we can often times see is you
30:01: know the operator nodes because like if
30:04: you look at the name of the component
30:05: it'll be like you know something like
30:07: add floaters float three but on the node
30:11: you just see the symbol plus because
30:13: like you know you don't need to read all
30:15: the text to know what a node is. So
30:17: sometimes the notes will have
30:19: differences just for like you know
30:21: readability
30:24: purposes. Um and the next question is
30:28: from
30:31: uh
30:32: Papaline. Uh with insight, would you
30:34: consider the big successes, mistakes,
30:37: design of implementation of Protolex uh
30:40: related? If you could go back and redo
30:41: something about how flex works, what
30:43: would it be?
30:44: So it's actually funny because like
30:46: Protolex
30:49: um like Protolex is a lot like designed
30:52: you know on the mistakes I made like
30:53: with my uh previous programming
30:56: languages uh particularly like you know
30:58: like when I developed uh um like before
31:02: called
31:03: logics and you know with that one I made
31:06: like a lot of mistakes and like a lot of
31:09: things I wish I could change like you
31:11: know if I could go go back in past and
31:13: sort of redo things. Um so a lot of like
31:16: per flags it actually is based on you
31:18: know like um it's it's based on my like
31:22: experience designing languages
31:26: um uh designing languages you know like
31:29: and things like where I'm like I if I
31:31: could do it over again like I would do
31:33: it differently. So um I will say in
31:36: general I'm kind of happy like with the
31:38: design of it like it's a little more
31:39: kind of flexible. It's a little more
31:41: powerful.
31:43: Um most of the things you know that like
31:46: I feel like are currently flaws of it uh
31:49: are mostly just things that like need to
31:53: be finished. You know it's not like
31:54: fundamental design things but it's more
31:56: like this needs more work. This needs
31:58: more time put into it um to resolve
32:03: those problems. So um I'm generally kind
32:05: of like happy with it. I'll see like you
32:07: know how I feel like a few years down
32:08: the line because I might like figure out
32:09: like better approaches and things but um
32:13: overall I'm kind of happy with
32:15: it. It just needs more
32:19: work and it's also like a lot of things
32:21: like from its design that are not even
32:22: fully realized yet like for example
32:24: nested nodes because I think this is a
32:26: really powerful feature but like you
32:28: can't use it right now
32:30: yet. So,
32:33: uh, with that, we got all the Discord
32:35: questions. So, we're able to get to the
32:39: Twitch ones. And the first one we got
32:41: from Grand K. Uh,
32:44: oop. Uh, the the first one is from Grand
32:47: and he's asking
32:49: schnopit. And I kind of like I think I
32:51: do have like one schnoit I kind of
32:53: wanted to talk about. Um, it's like a
32:55: thing I've kind of observed like in
32:57: general. And this kind of goes, you
32:58: know, it does happen with Resonite too,
33:01: but also like goes
33:04: uh it goes beyond
33:06: Resonite and it kind of has to do with
33:09: like you know how people sort of
33:10: interact with companies especially when
33:12: the companies you know make you know
33:14: decisions that people don't like. uh
33:18: because you often times like you know
33:19: see people like you know like especially
33:22: lately for example you know like one of
33:24: the big things is AI you know especially
33:28: generative AI and it being integrated
33:31: into products and a lot of people are
33:33: like you know very unhappy about it
33:36: um and you know they will complain they
33:39: will like you know they'll be very vocal
33:41: about it but then a lot of them like
33:44: will just keep using the products and
33:47: that's Like one of the things is like
33:50: where you know like to company like like
33:54: I feel like one thing that people don't
33:55: understand about like companies
33:57: especially really big companies is there
33:59: you cannot really treat them like people
34:02: like you know where if you complain to a
34:04: person that person will feel certain way
34:05: and they'll like you know change their
34:07: behavior. Big companies they don't
34:09: really work like that like you know they
34:11: are very numbers oriented and they're
34:14: numbers motivated.
34:16: So if you complain to them about
34:18: something but then like you know you
34:20: keep using the product you know
34:22: effectively to them like it's like
34:24: you're essentially telling that company
34:27: yeah I will complain but ultimately you
34:29: don't have to care about it because I
34:30: will not change my behavior. I will keep
34:32: using your product and even more so
34:36: people don't like you
34:38: know don't take the effort to kind of
34:40: switch to alternatives that specifically
34:42: avoid those
34:43: things. Um and what you're essentially
34:46: you know what that company sees is you
34:49: know is they can make those decisions
34:51: and they will not lose sufficient amount
34:52: of customers and maybe they can a bunch
34:55: of new ones because they introduce a new
34:57: tech even though like you know lots of
34:58: people don't like the tech. Um and if
35:01: you really want the company to change
35:03: you know change their behavior we have
35:05: to change yours behavior towards that
35:08: company. Um because just kind of
35:12: complaining about it like you know like
35:14: it it
35:16: it's their company unless like you know
35:18: they see the numbers change like they
35:20: will not really care because like
35:22: they're not a person that could like
35:24: care in that way. It's like you know a
35:26: group of people like you know looking at
35:27: the numbers and making decisions more
35:30: like that. And it's actually kind of
35:33: like, you know, the flip side of it is
35:35: like where um often times like feel on
35:39: our end, you know, with resid because
35:41: like we often times we're very like
35:42: principal driven. Uh and often times it
35:46: actually feels like, you know, sticking
35:47: to principles and doing the right thing
35:51: in some cases is actually worse than
35:54: doing the wrong
35:55: thing. And it makes our job harder
36:00: because like you know like
36:02: we like we essentially facing a choice
36:05: you know like where we do the right
36:07: thing and maybe like you know end up
36:08: like maybe end up like you know
36:11: suffering for it or we don't do the
36:13: right thing like you know which a lot of
36:15: companies will not do the right thing
36:16: and they will not do the right thing
36:18: specifically because if they did the
36:20: right thing they effectively end up
36:22: being punished for it by people by their
36:25: behavior. Um one of the example for
36:27: examp one one of the examples is you
36:29: know for example security stuff and this
36:31: is something that happened before where
36:33: we would discover
36:36: uh you know a security vulnerability we
36:39: would patch it as soon as we can and
36:41: then we be open about we would be like
36:42: we discovered this thing this is what
36:44: happened this is what has
36:46: affected
36:48: and you know and this is what we did and
36:51: you know we're being open about it sucks
36:54: it happens but like we did what we can
36:56: and we're trying to like inform you
36:58: responsibly of what
37:00: happened. Um, and one thing that
37:02: happened when we did that a few times is
37:04: like you know some people would be like
37:05: well like you know like now I'm not
37:07: going to use it because you know it has
37:09: it had a security vulnerability. The
37:11: problem is all software will have
37:14: security vulnerabilities like you know
37:16: there's with anything sufficiently
37:19: complex like it's going to happen. So,
37:22: it's one of those things where it's
37:24: like you're not going to be able to
37:26: find, you know, software that really
37:28: doesn't have any because like that's
37:30: just nature of software
37:32: development. What matters
37:35: more is does the
37:38: company, you know, deal with like the
37:41: really big ones and the important ones.
37:42: How do they kind of handle those
37:44: security
37:45: vulnerabilities? Um,
37:48: and like you know in this case like you
37:51: know we kind of felt like we were like
37:53: we felt like this it's the right thing
37:54: to kind of be open about it like be open
37:56: about what happened.
38:01: Um but like you know like with with that
38:04: kind of like uh with this kind of like
38:08: backlash it makes you think you know if
38:10: we just like patched it quietly and
38:13: didn't inform people we would be better
38:16: off and we're not going to do that
38:19: because again like we are a very
38:21: principled company but a lot of
38:23: companies will end up like doing that.
38:24: They will not tell you about
38:26: it. And by people, you know, like if you
38:32: behave like that way towards a company,
38:35: you know, you're essentially encouraging
38:36: that behavior. You're encouraging them
38:38: to be quiet about it because they will
38:42: not only they will not get any benefits
38:44: of like, you know, being open about, you
38:46: know, what happened
38:48: um they will actively get kind of
38:50: punished by it. So if if like you know
38:53: if their principles are not strong
38:54: enough they will not tell you they will
38:56: make the decision to like you know be
38:58: quiet about it or maybe be very vague
39:00: about it maybe be like you know when
39:03: whenever you see you know the change log
39:04: but it's like you know fix some issues
39:07: you know fix some issues and security
39:09: things and they don't
39:11: elaborate that could be behind the
39:13: decision you know like they are trying
39:15: to avoid it kind of like backlash
39:17: um and you know like like kind of
39:20: bringing back to the AI you know is the
39:22: same kind of thing is you know if you're
39:23: a company and you want to be like you
39:26: know we don't want to do generative
39:31: AI and it makes things more difficult
39:34: because like there's a lot of
39:36: opportunities you know we even like you
39:38: know as yellowman studios that we passed
39:41: on just because it kind of involved like
39:44: you know having to integrate like
39:46: generative AI when you you know for
39:50: example like you talk like with people
39:51: in this a lot of them because like this
39:53: the current hype a lot of them will be
39:54: like AI AI AI AI they like and they want
39:57: it and if you and if you do AI you know
39:59: they'll throw money at
40:01: you and it
40:06: takes you know it takes you know a lot
40:09: of kind of like principle to like be
40:12: like you know
40:13: we will avoid it like you know we will
40:15: not take this
40:17: money we'll stick to our principles
40:21: But then like you know under company
40:22: that goes and they say yes we will do it
40:25: they will get funding they will get more
40:26: people you know they're it makes it
40:29: easier for them because people end up
40:32: like you know supporting it even so they
40:34: vocal that they don't like it they end
40:35: up supporting it. So all those times
40:38: like it's effectively, you know,
40:41: saying
40:42: no, you know, like to that support and
40:46: it makes
40:47: things
40:50: difficult. Um, another thing is, you
40:53: know, like where it it
40:56: just there's, you know, like especially
41:00: from the perspective of a company, like
41:01: there's a difference between what people
41:02: say and what people do and the company
41:05: will care what people do.
41:08: So and in general I feel like you know
41:11: if if you really feel strongly about
41:14: something you do want to change your
41:16: behavior because like you know your
41:18: words as bad as it sounds ultimately
41:21: towards companies like it ends up being
41:23: meaningless because it doesn't change
41:26: their
41:28: numbers and but if you do end up like
41:32: you know for example you look for
41:33: companies that are avoiding AI you know
41:35: they're avoiding crypto that are
41:37: avoiding, you know, things you don't
41:38: like, uh, and specifically making their
41:41: stance on it and you support those and
41:43: you stop supporting those companies.
41:45: That actually moves the numbers. And
41:47: what it does, it makes those companies
41:50: viable. And if those companies are
41:52: viable, that makes it, you know, easier
41:53: to kind of like, you know, resist those
41:55: things or maybe do them more
41:56: responsibly. Uh but like you know you do
41:59: need to make change in the
42:01: behavior and it's kind of you
42:05: know what this kind of boils down to
42:07: because it feels like you know often
42:08: times we like especially during
42:11: development of Resonite and making
42:13: decisions for a company is like we've
42:16: been dealing with a lot of kind of
42:17: difficulties for like sticking to our
42:19: principles and we will keep doing
42:22: it but it is difficult because of like
42:25: you know how people kind of behave.
42:28: Because we
42:29: will see, you know, people complain
42:32: about certain
42:34: things, but then they will keep like,
42:36: you know, using those things and they
42:38: will not want to like, you know,
42:40: try solutions that avoid those things.
42:44: And it makes you think is you know like
42:47: would we be better off if we like you
42:49: know forgot about our principles and
42:51: it's a difficult thing like you know
42:53: it's a difficult thing to like you know
42:55: deal with but we keep doing it but it's
42:59: also like you know something that people
43:01: can make
43:02: easier you know if they cannot change
43:05: their behavior if they like you know put
43:08: not their well kind of their money
43:09: sometimes but like you know put their
43:11: actions where their words are and that's
43:14: you know how you
43:15: get how you actually get like you know
43:18: much how you get like you know things to
43:21: change. So it's going to end up like
43:23: being a bit of a like with a
43:26: drramble but I I hope it made some
43:29: sense. Yeah. I mean like honestly I
43:33: think we have a sh a shared schnuppet
43:35: this week because I I agree on much of
43:37: the of the same things. Like I'm I'm
43:41: actively trying to like move away from
43:44: like VS Code and stuff at this point
43:46: just because they're they're they're
43:49: pushing AI and everything and I'm
43:50: starting to see it on GitHub too and
43:52: like I'm I'm kind of seeing the writing
43:54: on the wall. It's just going to be a
43:56: thing that's going to be in my face and
43:58: I don't want it in my face. So, I'm not
44:00: going to I'm not going to be I make it a
44:03: point to not be the statistic that
44:05: sticks around and complains. Like the
44:08: same thing for my Quest Pro. I'm I don't
44:12: really want to use my Quest Pro anymore.
44:14: So, you haven't seen me in VR as often.
44:17: Um, because my other headset I still
44:19: need to get working correctly again
44:21: because I don't want to support meta
44:24: because they are they have like sided
44:29: with the people who want to erase like
44:32: diversity and stuff and I don't want
44:35: that on my face. So, I'm not going to
44:36: have that on my face. I will not be
44:38: another statistic.
44:41: Yeah, it's pretty much it. It actually
44:42: brings another point like I forgot to
44:44: mention like it is difficult you know
44:47: sometimes to move from things because
44:48: like you know that software can have
44:50: things you need or things you want and
44:53: it becomes very difficult to switch it
44:55: becomes very difficult to find
44:56: alternatives to learn alternatives like
44:59: I know like you've been kind of going
45:00: like to links you know getting stuff
45:02: like the vari like working on Linux.
45:06: Yeah.
45:07: But so like I don't like even like you
45:10: know I don't fault people from like you
45:13: know struggling to kind of switch to
45:14: things but I want people to know is you
45:18: know if you don't you know you
45:20: essentially from the perspective of the
45:22: company your complaints don't matter
45:25: because like you keep like using their
45:26: thing anyways and one of the reasons
45:29: companies keep doing this stuff and one
45:31: of the reasons it keeps getting so
45:32: widespread is because people keep using
45:34: it despite
45:35: it, you know, them not liking it, but
45:39: they not like it enough to like move
45:41: away. So, the company will keep doing it
45:44: because, you know, they you're not
45:46: really giving them incentive not to and
45:48: you're not giving an incentive towards,
45:51: you know, companies that avoid this
45:53: stuff, you know, to keep doing their
45:56: business. Because there's also actually
45:58: another thing you can do is like, you
45:59: know, the switch can be kind of gradual.
46:01: You can if you need to use something
46:03: that has stuff you don't
46:05: like, keep using it, but also support
46:09: companies that avoid it. Because if you
46:10: support those companies, you make you
46:13: make the business that avoids those
46:16: technologies or maybe uses them more
46:18: responsibly.
46:20: um you make it more
46:22: viable and by making viable you can make
46:25: these companies
46:26: grow and if they grow you know they
46:29: become better and maybe they become
46:30: better
46:32: alternatives but a lot of the times you
46:34: know it's like it's hard to grow a
46:37: business that sticks to those principles
46:41: because people don't really support it
46:42: as much and becomes you know chicken and
46:44: egg problem.
46:48: So whenever you know you have like
46:50: something like that look at what you can
46:52: kind of do on your end and not just you
46:54: know with Donite like again this is more
46:57: general thing I've kind of observed like
46:59: people do
47:02: um you
47:04: know I just want people to be kind of
47:07: more aware of like you know the
47:08: difference between like what you say and
47:11: what you do and that like what you say
47:14: doesn't matter if your company is as
47:16: much as what you
47:18: do. And it kind of goes, you know, from
47:20: both end like, you know, both from like
47:21: not supporting companies and supporting
47:23: ones that do the stuff or avoid doing
47:26: the stuff like you don't want to do.
47:28: It's actually like there's like another
47:30: part of it is like um because you know
47:33: like we've done a project before like
47:35: that was for example you know involved
47:38: with crypto and after we
47:43: found a lot of kind of issues with it
47:46: like like with how it was kind of
47:48: handled and things we end up like
47:50: dropping that support but we we had a
47:52: lot of people even back then being like
47:54: you know drop crypto drop crypto um they
47:57: would you and
47:59: they would essentially be very angry
48:00: about it. But then when those people
48:04: when we do like you know when if you go
48:07: to the company and tell them you know
48:08: drop crypto and they actually do end up
48:11: like dropping it are you going to
48:13: support them as a result because
48:15: recently I've had like you know some
48:17: people be like you know they even feel
48:20: like we did that and we did that like
48:22: you know at great risk to
48:25: ourselves those people are still like oh
48:27: like you did it in the past you know
48:28: like like like we don't trust you and it
48:31: becomes you
48:34: Like if we didn't like if we didn't have
48:36: those principles because we cannot
48:39: ultimately drop it for the principles
48:41: but if we didn't have those already
48:44: strong there's essentially no incentive
48:46: to do it
48:49: because you know like it's one thing the
48:52: people saying drop it but it's another
48:55: thing like when people then don't go and
48:58: you know support a company like when
49:01: they do actually end up following up on
49:04: that. And and that's kind of like, you
49:07: know, what made me kind of think like
49:08: about this kind of whole thing where
49:13: um made me think about like you know
49:15: this whole thing where like ultimately
49:17: like you know what people say and what
49:18: they do are different things and like
49:20: you like end up like feeling like maybe
49:24: like we didn't listen to those people
49:26: like you know we would be better off
49:28: right now.
49:31: And at least for example,
49:35: financially
49:38: and and I just like look at it and like
49:40: you know because like like we're kind of
49:42: like dealing like and if if we are
49:43: dealing you know with like some of these
49:45: thoughts and some of like these
49:48: decisions you know and we're like you
49:51: know we ultimately do things for the
49:54: principle of it but we also know there's
49:57: a lot of people who wouldn't do that for
49:59: the princip simple and they'll, you
50:00: know, and they'll just keep like, you
50:02: know, that kind of behavior and they
50:05: will see that and they will be like, you
50:06: know, like we don't want to make this
50:08: change because there's nothing in it for
50:10: us. We're just going to, you know,
50:13: hurt. Um whereas like, you know, on our
50:17: end, we make those decisions for the
50:21: principle and we end up often times we
50:23: end up hurting as a result.
50:26: But like you know we're willing to do it
50:28: even with the
50:29: hurt. But there's like you know still
50:32: things that makes like there's things I
50:35: feel people can do to make it easier
50:37: both for us and for other companies if
50:40: you like you know if you want a change
50:42: to
50:45: happen. I think I think it's kind of
50:47: enough ramble I'm like but
50:50: yeah definitely definitely an important
50:53: topic though to be sure. Yes.
50:56: Oh, thank you. Thank you for listening
50:58: for
51:01: this.
51:03: Uh, so next one, we also got the the
51:07: subscription from Nexo. Thank
51:10: you. It's actually well there's actually
51:12: one more thing I want to mention too is
51:14: like you know because I mentioned like
51:16: it is difficult but we also one of the
51:19: reasons we are able to do it is because
51:20: we did actually have enough support from
51:23: our community
51:25: uh from people who helped us you know
51:27: get through some of the stuff we dealt
51:29: with in the past and one of the reasons
51:31: we are here and one of the reasons we
51:33: are able to keep sticking to the
51:34: principles is because we did get enough
51:38: support. So like you know just to kind
51:40: of bring a positive you know side to it
51:44: because if we didn't have that support I
51:46: don't think we'd be able to get you know
51:47: away from that kind of situation.
51:50: Um and it's because like you know people
51:54: people wanted to like support us like we
51:57: were able to be here. So like I'm
51:59: thankful for that and I keep flying off.
52:03: uh and it's you know one of the kind of
52:06: examples you know like where the support
52:08: like it did make a difference and it
52:11: made a change and there's the cases you
52:13: know where we are dealing with
52:15: difficulties and I feel like we're
52:16: dealing with like more difficulties than
52:18: you know other companies would but one
52:20: of the reasons we can keep sticking to
52:22: the principles and keep going is because
52:24: we do have the support we have and we
52:26: have the community we
52:29: have oh let's move
52:34: Um anyway, next question is from Grand.
52:37: He's asking Typo X. Do you have a Typo
52:40: X, no this, you know, this part, the the
52:45: thing I just said, that's my Typo X. All
52:48: right. Um my Typoxunks
52:51: is Let me think here for a
52:56: sec. When
52:59: uh
53:03: I I don't I don't have a good one. I
53:05: guess when a library uh works for the
53:09: most part after you uh make some
53:11: changes. That's my type. Uh
53:15: I got the shared memory like a library Q
53:17: like Q library working
53:20: um pretty good on that standard too. And
53:23: it actually was not that hard. Uh and it
53:25: worked pretty good. So I'm happy about
53:27: that. That's my type punks.
53:30: Yeah, this a good feeling. It's like
53:33: like when something doesn't work and
53:34: then like you keep hacking at it and
53:36: like then suddenly works and you're
53:38: like, "Yay!" Like it's finally works.
53:42: It's I mean it's like you could say, you
53:44: know, like when it doesn't work, it
53:45: makes you snop it and like once it does
53:48: work, it makes you type.
53:50: Yes. It's like the feeling of going from
53:52: like, "God, this is so stupid. I feel so
53:55: stupid to I'm literally God." That's
53:59: there's literally a meme for like
54:01: programmers like that's like
54:03: that. Alo, we need another one because
54:05: ace on Twitch is us asking Typox.
54:09: Um, we just we just do one. I like it
54:13: when all my friends really cool. There
54:14: we go. Yay. Also, thank you Moonace for
54:18: the
54:19: subscription. I think we already said
54:21: like thanks earlier, but it's popped out
54:23: in the history. Uh so the next one which
54:26: is actual questions from from Twitch uh
54:29: is from Jack check the fox author. Uh
54:33: I've asked this on the nested nos get a
54:35: bishu but I figure I could also ask it
54:36: here. Some components expose a reference
54:39: field for functions delegates like the
54:40: custom can grab chickcom component. With
54:43: nested nodes we'll be able to define
54:45: protolex functions that can be used with
54:47: these. Um I mean eventually yes. I don't
54:51: know if it's going to come like
54:52: immediately with nested nodes but the
54:54: nested nodes are necessary component for
54:56: it because nested node it sort of
54:58: defines like an interface and we would
55:01: be able to like you know make a thing
55:02: where if the if it conforms to specific
55:05: interface then you can actually pass it
55:07: as a function. Uh it'll it's going to
55:09: need like you know it needs to be
55:10: wrapped around because it needs to you
55:12: know call into the program reflex system
55:13: and whatnot.
55:15: path.
55:17: Um you know
55:21: um once we have nested nodes like that
55:24: pretty much makes it much easier to
55:25: implement and the goal is like you know
55:28: yes eventually like you'll be able to
55:29: like define a function and if there's
55:31: like a delegate you'll be able to like
55:33: you know pass your nested
55:36: node. Uh next question
55:39: is from VT aros. Uh, first we have some
55:43: sulfur which uh you do not mind parking
55:46: ways. That's a weird question. I don't
55:49: have any sulfur. What? What? I don't
55:53: know. What does it mean? I don't have
55:55: any sulfur either.
55:58: Why would you have a sulfur? What does
55:59: it mean?
56:01: I mean, I don't like I did this to
56:03: collect minerals. I actually had like
56:05: bismouth crystals which I really liked.
56:07: They look very pretty, but I don't have
56:09: those anymore.
56:11: I need to get more bismouth. But I don't
56:13: know about sulfur. I don't know how how
56:15: stable is like pure
56:17: sulfur. Like it's like I don't know if
56:19: it's like ox. I know it's very
56:21: flammable and it's very spooky flame
56:24: because like uh unless it's dark like
56:26: you can't even see
56:28: it, but I I am I'm I'm a bit confused by
56:32: this one. Alo, thank you for the
56:34: subscription. W
56:39: why do I feel like subscribes every
56:41: week?
56:43: I don't know.
56:46: Uh, next question is from Moonbase. I
56:49: had a question regarding the splitting
56:50: prototype that you showed off in your
56:52: latest vid. Notice that on the left the
56:54: hand command prompt, it showed Unity was
56:56: connecting
56:57: via Why did it censor
57:00: that? Um, or something. Isn't it slower?
57:05: Do you know what's the Oh, they said so
57:08: I think it sensored it because they it
57:10: was like TCP. Yes. And it had the
57:13: letters C and P in it. Oh, yeah. Which
57:16: is like an acronym for something very
57:17: terrible apparently. What weird. I don't
57:21: know. Um but yeah, like the prototype it
57:24: actually uses uh right now it uses so
57:27: there's like two parts to the mechanism.
57:29: There's like going to be the shared
57:30: memory which is going to be used to
57:32: change bulk of data but we're actually
57:33: not changing the bulk of data yet. Um
57:36: there's also a communication mechanism
57:38: which is just sending sort of control
57:40: messages and those are very very small
57:42: and they're like you know going to be
57:44: kept very small like on purpose you know
57:46: just so it's kind of fast for
57:48: development purposes it's actually using
57:50: TCP as the transport just like on a
57:52: local host but it's actually going to be
57:54: swapped to a different mechanism very
57:56: likely you know the interprocess library
57:58: that sire got working uh however with
58:01: TCP right now it makes it easier to make
58:04: the initial implementation and it's not
58:06: difficult like you know to swap the
58:08: transport mechanism to something else
58:09: after um so usually when things start
58:13: getting
58:14: developed would like a lot of times like
58:17: I'll use something that's easier to
58:19: debug because it's easier to like you
58:21: know verify the system works the way
58:23: it's supposed to uh and then like you
58:25: know swap it for a better mechanism
58:27: because now I know you know the
58:30: mechanism is working versus if I you
58:33: know use like some more advanced
58:35: mechanism right away. Um, and you know
58:38: there's there would be issues and there
58:39: actually were issues. Um, now I have to
58:42: like figure out are the issues because
58:44: there's issues with the mechanism I'm
58:46: doing or is it the issues with the
58:48: transport protocol and like you know
58:51: that kind of makes diagnosing things
58:52: harder because now I have to kind of
58:54: figure out which one of the two is two
58:56: it is. But if I can like use something,
58:58: you know, that's easier for debug that
59:00: it just removes one of the variables and
59:02: I can kind of focus better on like, you
59:03: know,
59:04: solidifying the other part of the
59:06: system. Once that part is solid, I can,
59:10: you know, swap out the other
59:13: part. Uh, next questions from Grand
59:17: K. Uh, Grand asking,
59:23: uh, why do I get Taskmaster UK TV show
59:26: vibes from these two here with FKS and
59:28: chair and S with none. On the TV show,
59:30: the main host has thrown another host as
59:32: basic chair. I don't know. It was like I
59:35: was offering S like a thing to stand on
59:38: and he didn't want one. I just I just
59:41: want I wanted to stand cuz I cuz I
59:43: usually like I am usually like crouched
59:45: all the time. So like I mean you could
59:46: still stand just a bit higher. Yeah, but
59:49: then my head be off the screen. No, your
59:52: head is like like below like there's
59:54: plenty of space here. Yeah, but then it
59:55: wouldn't be within padding distance.
59:57: Okay, he see he makes a fair
01:00:00: point. He gets ping. Do they do they do
01:00:03: paddling and task master?
01:00:08: Oh no. Oh no. Next question is from
01:00:10: Grand UK. Uh Gerrick is asking favorite
01:00:14: target episode any series. Oh my god,
01:00:17: there's so much. We're going to be here
01:00:19: forever. Um oh my god, dude. We spent we
01:00:22: spent too long on the schnopath like to
01:00:25: really go in depth. Um there's a lot
01:00:28: like I don't even know where to begin.
01:00:32: I
01:00:34: mean, I'm going to like go with it funny
01:00:36: one, which is 200, which is like it was
01:00:38: sort of celebratory episode, which is
01:00:40: like it's very cleverly done, but it's
01:00:42: also like very funny because it's like
01:00:44: doing behind the scenes without really
01:00:45: doing behind the scenes, and it's just
01:00:47: so goofy, but you also needed to have
01:00:50: been watching the show like forever for
01:00:53: it.
01:00:54: Um, but like I like I like a lot of the
01:00:57: kind of like mindblowing episodes and
01:00:59: like or like the weird like um like
01:01:03: weird high concept sci-fi ones which
01:01:05: there's a lot in Stargate. Like I feel
01:01:07: like Stargate is like the Simpsons. It's
01:01:09: like the sci-fi equivalent of like
01:01:11: Simpsons dead because they've done so
01:01:14: many concepts. Like for example, the one
01:01:16: I really like in Atlantis, I think it
01:01:18: was
01:01:19: uh was it season 5 or four? Um it was
01:01:25: the one uh Ghost Ghost and
01:01:28: Machine because that one has kind of
01:01:30: these kind of like spooky like vibes to
01:01:32: it and so on. But you know, stuff like
01:01:35: that. I really like stuff like that. But
01:01:37: like uh
01:01:38: there's too many individual episodes. I
01:01:41: don't actually remember a lot of their
01:01:42: names.
01:01:44: Um yeah, I have to kind of like look
01:01:46: look through the list because like I do
01:01:48: remember like like lots of like really
01:01:49: cool like moments from Stargate. Like
01:01:52: you know there's like like for example
01:01:53: the one like where Carter like blows up
01:01:55: the sun. Well, not the sun like a star.
01:01:58: uh she blows up like a and then like
01:02:02: um and then like you know like she gets
01:02:05: made fun of for that and then like in
01:02:07: Atlantis you know there's the episode I
01:02:09: think actually the one's called Trinity
01:02:10: where they discover you the ancient like
01:02:13: um you know power source thing and then
01:02:16: ends up blowing a solar system and it
01:02:17: goes like oh it's just three three4s of
01:02:20: a solar system um and they like end up
01:02:23: like having a bee with Carter like was
01:02:26: that was also like a really cool
01:02:27: episode, especially like when it's like,
01:02:28: you know, stuff with the ancients. Uh
01:02:31: there was like, you know, like multiple
01:02:32: like two-parters. Like I really like the
01:02:34: one with like, you know, with the um
01:02:36: sort of like when they were like, you
01:02:38: know, trying to like uh follow the
01:02:40: traces of like Merlin and, you know,
01:02:42: find you know, find him and they had
01:02:43: like they were doing like the challenges
01:02:45: and everything. It kind of had like a
01:02:46: cool vibe. And they had like, you know,
01:02:48: the scenes with
01:02:50: um uh which is what uh I'm not sure if
01:02:54: I'm confusing the names.
01:02:58: What was the name of like Valla's?
01:03:01: Um, Adrea. Was it Adria? I think it was
01:03:05: Andrea. I'm confusing with Arya from
01:03:08: artifact I think in my brain. Yeah,
01:03:12: and like and and she kind of had to be
01:03:14: like, you know, member of their party.
01:03:16: It was kind of funny like with the
01:03:17: dynamics.
01:03:18: Um, and a lot of kind of like V like VAS
01:03:22: are like also like fun like you know a
01:03:23: lot of the only Oh, window of Windows of
01:03:26: opportunity. That's like good one too.
01:03:28: Like this the groundhog day one you know
01:03:31: that's like where a lot of like quotes
01:03:32: come from. Uh I also like really like
01:03:34: the one like like audio stuff is like
01:03:37: fun. Um I don't remember which episode
01:03:39: it was. Uh it was one of the like
01:03:42: replicator ones and like you know and
01:03:45: the replicators actually like you know
01:03:47: kicking up gold you know and then like
01:03:50: ball he like projects himself to the
01:03:52: stargate to like sort of ask for help
01:03:55: and you know and
01:03:57: like and he's like just waiting there
01:04:00: you know there's like water and he's
01:04:01: like oh he'll be in in a minute and then
01:04:03: like you know oil comes in and he's like
01:04:05: um and at some point like ball goes like
01:04:08: you know like Um, you
01:04:11: know, like or only like goes like, you
01:04:14: know, like like you know, sort of clicky
01:04:15: way thing, you know. I was like, I was
01:04:16: having a lovely branch and like and B
01:04:19: just goes like impudence and only was
01:04:22: like no tuna
01:04:25: and I forget which the tuna actually.
01:04:27: Yeah. And then like and then like and
01:04:30: then B goes like you cannot be serious.
01:04:34: I know what it was like. I can I just
01:04:36: choose not to most of the time which
01:04:39: which kind of it's a philosophy I live
01:04:41: by as well. Yeah. Um so like
01:04:47: I really like um sorry I don't mean to
01:04:49: interrupt you. No, go ahead. I I really
01:04:52: like one of my favorite ones is like
01:04:54: Teao of Rodney in Atlantis. Oh, there's
01:04:57: a good one too. Yeah. where he gets in
01:04:59: like the machine and and just gets like
01:05:01: superpowers for like an episode and it's
01:05:03: super funny. Yeah, that was a really
01:05:05: good one too. But there's also like the
01:05:07: one um what was it called? Like when Rod
01:05:10: gets the brain parasite thing and like
01:05:12: they think he's about to die because
01:05:13: that's also like very emotional one.
01:05:15: That one is there there that one is very
01:05:18: emotional. I was actually also going to
01:05:20: to reference the the part in that
01:05:22: episode I mentioned where like I I
01:05:25: really like the part where like he like
01:05:29: showed some really like genuine love for
01:05:32: like Ronin and like healed the scars on
01:05:34: his back from the ramps. Yeah. And he
01:05:36: even goes like are you attached to these
01:05:38: scars or like you know like like
01:05:39: anything and he just hugs him and he's
01:05:41: like I heal your scars by the way. Yeah.
01:05:44: I hope you don't mind it just heal them.
01:05:46: Yeah. It's it's such a good show and
01:05:48: like the people like working on it. They
01:05:50: had so much fun with it like you know
01:05:51: like I watched like so much like behind
01:05:53: the scenes. There's al like a lot of
01:05:54: stuff like you know a lot of episodes
01:05:56: with like u Dr. is a link because he's
01:05:58: he's check well the actor he's like
01:06:00: Czech Canadian and he actually speaks
01:06:02: Czech and the times like he swears a lot
01:06:05: or he says like things that are like
01:06:07: Easter eggs like there's like one scene
01:06:09: like where you know stuff is going and
01:06:11: he actually he literally says in check
01:06:13: he's like I cannot work with these
01:06:15: actors
01:06:16: anymore and it's like and I remember I I
01:06:20: remember he was like talking like you
01:06:21: know behind the scenes and according to
01:06:22: a lot of the episodes like the director
01:06:24: was just like yeah just say whatever um
01:06:26: but then like you know when they filmed
01:06:28: the scene a director would go to him and
01:06:30: he's like so what did you
01:06:34: say and like and he gets away with a lot
01:06:38: because like it's in English like he
01:06:39: swears quite a bit like I don't think
01:06:41: you'd be able to get that much swearing
01:06:43: like on you know Yeah Stargate it and
01:06:47: it's so weird for you because you know I
01:06:49: understand languages so like it's it's
01:06:52: really cool yeah you get you get double
01:06:54: the content yeah yeah I get like extra
01:06:56: Yeah, there's like it's best like when
01:06:58: he also combines like the English and
01:07:00: like it just interjects like some check
01:07:02: in it like it just kind of makes me like
01:07:04: dive with laughter. Um also like the
01:07:07: ones like uh I don't remember like a lot
01:07:09: of the episodes like where they just
01:07:10: like do like a roll of really cool
01:07:12: sci-fi stuff like like um like like you
01:07:15: know when they first lost Prometheus
01:07:17: which is like another thing I really
01:07:18: like about Stargate is the progression
01:07:20: you know because like it it feels like
01:07:21: you know they start super simple and
01:07:23: they're like barely making way and they
01:07:25: actually you know tolerate they actually
01:07:27: get like really powerful you know you
01:07:29: start building ships you know and things
01:07:31: and like they start getting up there
01:07:33: like you know on the galactic like
01:07:35: Um, there's also stuff like with
01:07:37: Stargate Universe, it was somewhere like
01:07:38: a really good episodes. Like there's
01:07:40: like one called Time where like, you
01:07:43: know, it's also like one of those very
01:07:44: mind-blowing ones. I kind of really like
01:07:46: those. And especially with the later uh
01:07:49: the second season and the second half of
01:07:51: the second season, it gets really wild.
01:07:54: Um especially once kind of, you know,
01:07:56: like once Dr. Ash like figures out the
01:07:59: mission of
01:08:01: Destiny and I'm like I'm still like it's
01:08:03: been like over 10 years or however long
01:08:06: like maybe even longer and I'm still
01:08:08: like I want to know I just want to see
01:08:10: the conclusion to that story because
01:08:12: like it's it's
01:08:14: um Oh my god. He has ages. Yeah, that's
01:08:17: like
01:08:18: um Yeah, I think that's like one the
01:08:21: fourth or fifth episode of the first
01:08:23: season of Atlantis. It's like I shot
01:08:25: him. I show him and lag.
01:08:28: There's so many good moments. There's so
01:08:31: many good moments like like it's it's
01:08:33: it's so hard to choose and like it's
01:08:35: been a while since I watched so I don't
01:08:36: remember a lot of the names of the
01:08:38: episodes but like it's just there's a
01:08:40: lot of replicator stuff especially like
01:08:42: well the Assuran Replicators like I
01:08:45: don't like those two. Oh those are such
01:08:47: a such a such an emotional conflict with
01:08:50: those ones. It makes me feel stupid like
01:08:52: you know for like uh what was his name
01:08:55: and something
01:08:58: I think I think his name was like uh
01:09:01: like a number. It was a number. It was
01:09:03: some number. No, no, no, no, no, no.
01:09:05: These are replicators. The Asuron
01:09:06: replicators in Atlantis. Yes. Yeah, I
01:09:10: think it was Neam or something like that
01:09:12: blonde guy who's like one of one of the
01:09:15: good ones because I got like an Ober
01:09:18: like who's like very super grumpy like
01:09:20: and did like a good Nam and it kind of
01:09:23: helps them and they then they reprogram
01:09:25: him and felt so bad. I was like he was
01:09:28: one of the cool ones like I was hoping
01:09:30: they would get a replicator body.
01:09:33: Yeah. Oh, and the one uh oh, another
01:09:36: super good one is like first contact
01:09:38: like you know when um it's also two
01:09:41: parter I forget the second name I think
01:09:43: but like you know when
01:09:44: like when when like you know they have
01:09:48: like there's like a ship and they put
01:09:51: the shield and like the shield just the
01:09:53: ship just goes through the shield and
01:09:54: they like you know and they just make a
01:09:55: hole and they just like you know kidnap
01:09:58: like Rodney and you know Daniel Jackson
01:10:02: and and like They just they have
01:10:06: like, you know, pretty much everybody on
01:10:08: Atlantis like they have they just have
01:10:10: no chance against them. And spoiler
01:10:12: alert, you know, it turns out to be like
01:10:14: a faction of the Asgard. But like, you
01:10:16: know, they're in these suits like and
01:10:18: they're just like super overpowered. And
01:10:19: like that's a really cool feeling like
01:10:21: where when they're like, oh, they're
01:10:24: like, you know, they just there's like
01:10:26: stuff out there they have like no chance
01:10:28: against. They just like they're very
01:10:29: like surgical. they like you know go
01:10:31: make a hole you know and also it's cool
01:10:34: because you see attack you know
01:10:36: technology that
01:10:38: like they use
01:10:41: um you know like to
01:10:44: just make a surgical strike and like you
01:10:46: know get out of there and it's like
01:10:48: super quick and like you know it's like
01:10:50: yeah that's what aliens with tech would
01:10:51: do. Um, yeah. Like especially cuz
01:10:54: Atlantis's tech Atlantis's tech has
01:10:56: always been like the trump card. Like
01:10:58: the most advanced tech you've ever seen
01:11:00: in the whole entire series. But then you
01:11:02: just see these aliens coming. And
01:11:03: they're like, "Screw your shield. Screw
01:11:06: your freaking like security systems.
01:11:08: We're taking we're taking we're taking
01:11:10: your guys. Goodbye." Yeah. Well, they
01:11:14: were using ancient tech. True. Because
01:11:16: like True, but even so, like Yeah. The
01:11:19: way they know how it works. Yeah, I'm
01:11:23: just actually think there's like a meme
01:11:24: like, you know, like actually I might
01:11:26: have it saved somewhere. It's like
01:11:28: Stargate Atlantis, you know.
01:11:31: Um, let's see. I have whole fer for
01:11:34: Stargate memes.
01:11:37: Oh my gosh, your your the your inventory
01:11:39: on the main stream is really funny
01:11:42: looking. Oh, I still have this on. Oh,
01:11:46: let me actually turn that off. Where's
01:11:48: my thing?
01:11:50: Don't even Oh, there's going to be a
01:11:51: really good frame in there. I hope
01:11:53: someone clips because there's like a
01:11:54: face on on the uh one of the thumbnails.
01:11:57: I really hope someone gets that. Is it
01:12:00: clipping? Is it this face? Is it this
01:12:02: face? This is an old meme. This is
01:12:06: You're welcome.
01:12:08: You're welcome. Stream. Edges is
01:12:11: probably freaking out right now because
01:12:13: this likes this meme. Um
01:12:16: [Laughter]
01:12:21: Let's see.
01:12:24: Yeah, there's a
01:12:26: classic. And there's like this
01:12:30: meme. Is it this? Is this this this one?
01:12:32: No, this is SG1, but it's also like
01:12:35: funny
01:12:36: one. Let me see if I can find the other
01:12:38: one. True. This is so true. This is so
01:12:41: true. There we go. This is also true.
01:12:47: Yeah, this also sums it up. I really
01:12:50: like on Atlantis because like it feels
01:12:52: like, you know, like with SG1 like you
01:12:54: get like these little nuggets, you know,
01:12:56: like of ancients and like it's also like
01:12:58: ramping a bit, but you only get like
01:13:00: little nuggets and then like Atlantis is
01:13:01: just like ancient stuff, ancient stuff,
01:13:03: ancient stuff. And I'm like, yay.
01:13:07: It's like one of the things like I would
01:13:08: love is like because I know like a lot
01:13:10: of the actors as well. Um they're kind
01:13:14: of like nerdy especially you know like
01:13:16: David Heled like he plays you know he
01:13:19: played like Dr. May and he has VR and
01:13:22: I'm
01:13:23: like I wonder what it would take to like
01:13:26: you know get down here like explore a
01:13:28: bit especially because like there's a
01:13:30: bunch of Stargate nerds and people bing
01:13:32: like Stargate like stuff on here if
01:13:36: you're watching
01:13:37: David we really like you please come on
01:13:41: over we we we will we will we will
01:13:44: totally not freak out and explode with
01:13:47: excitement. And
01:13:50: literally we'll literally explode. We'll
01:13:53: literally explode. Yeah. Like we which
01:13:54: we can do here.
01:14:01: Yeah. We should probably move on. Like
01:14:02: this is this is the dangerous like this
01:14:05: is dangerous question into the stream.
01:14:07: Like ask ask us earlier.
01:14:11: Oh dear.
01:14:15: Um, so the next question is from
01:14:18: actually wait I can put them above you.
01:14:20: There we go. Yes. Um, hey, I do wonder
01:14:24: about the time line about there's how
01:14:26: long until 1.0. Uh, we don't we don't do
01:14:31: timelines like there's too much unknown
01:14:34: like to like really know. So
01:14:38: version numbers work. Yeah. We also like
01:14:40: we don't like it depends what you mean
01:14:41: by 1.0 Oh, like because it means like
01:14:43: does it mean like kind of coming out of
01:14:45: beta. Um because we don't do that kind
01:14:48: of like versioning. So like I would say
01:14:50: like 1.0 is like you know come out of
01:14:52: beta or something which like I would say
01:14:55: at least a year at least
01:14:58: [Music]
01:15:01: probably. Um, next
01:15:04: question is, uh, VT
01:15:07: Ars is asking, "Does Barry Manolo know
01:15:11: you at his wardrobe?" I don't know what
01:15:13: that means. I don't know who that is.
01:15:15: Yeah, I don't know what it is,
01:15:18: unfortunately. Uh, it's in a chat
01:15:25: question. Yeah, if so, if you want
01:15:28: another like, you know, dangerous
01:15:29: questions, ask me about Orville.
01:15:32: But no, probably not the
01:15:34: stream sometime in future. Uh, Nuki's
01:15:37: asking, "Have you an issue with avatar
01:15:38: station where avatars in the back seem
01:15:40: to be making the initial load before
01:15:42: joining in take long time? What causes
01:15:44: wars take longer than the initial load?
01:15:46: What is it doing before brings you in?
01:15:47: How can I optimize the time down?" So,
01:15:50: it's probably to do with like the new
01:15:51: mesh upload because what it does, it
01:15:53: sort of spreads the mesh upload over
01:15:55: time so you don't h as much, but it
01:15:58: means like, you know, the load will take
01:15:59: a bit longer. Uh some of the things that
01:16:01: will help is like once we do the
01:16:03: interweaving so like you know stuff can
01:16:05: kind of you know be done in between but
01:16:07: it still means you know those avatars
01:16:09: will take long longer to load
01:16:11: themselves. The best thing like you
01:16:13: could do like you know with in that case
01:16:15: is
01:16:16: probably would have those avatars load
01:16:19: initially but that might be kind of
01:16:20: tricky to
01:16:24: do like load them in like you know
01:16:26: dynamically or something but uh we don't
01:16:28: have like super good mechanisms for it
01:16:30: right
01:16:33: now. Uh Epic Eston is asking uh can
01:16:38: you Oh, there's like leaves in the
01:16:40: front. Uh, can you perform interpretive
01:16:43: dance of the splithning? Uh,
01:16:47: no. Oh, there we go. That's my
01:16:50: interpretive dance.
01:16:56: Uh, next
01:17:05: question. Next question. There's like
01:17:07: leaves in front. Okay, hold on.
01:17:11: Sorry, I'm having trouble. There we go.
01:17:13: That's better. Um, Ky is asking, "How
01:17:16: much do license paying businesses and
01:17:17: aimedia clients influence features and
01:17:19: direction of the project?" Um, so
01:17:23: direction generally not much. This kind
01:17:25: of given by us, but features they can
01:17:27: have an influence and pretty much
01:17:29: depends, you know, how much they're
01:17:30: willing to pay for it and how big the
01:17:32: feature ask is. Um, we did like
01:17:35: prioritize like some things, uh, you
01:17:37: know, for businesses. So far it's been
01:17:40: like you know stuff where is relatively
01:17:42: smaller and is like um is you know
01:17:46: something that can be done you know
01:17:48: often times by purple prime. So like
01:17:49: prime like he deals a little bit with
01:17:51: the business side of business side of
01:17:53: the stuff and whereas like a feature
01:17:54: request you know often times is for like
01:17:56: improving headless improving like
01:17:58: certain things. Um you know he'll take
01:18:01: those he he'll take care of those tasks
01:18:04: and you know that helps us bring us
01:18:05: additional funding for the project.
01:18:08: So if it will be something bigger then
01:18:11: it's kind of harder. In some cases it's
01:18:13: kind of aligned things like for example
01:18:15: a lot of the businesses and clients they
01:18:18: want better performance. The community
01:18:19: wants better performance. So that was
01:18:21: you know very strongly aligned. Um so
01:18:24: you know the question is like do they
01:18:26: influence it? Like we would probably be
01:18:28: doing it anyways but it's like you know
01:18:30: good kind of synergy with
01:18:32: that but uh it it depends. It depends
01:18:36: both like you know how much like funding
01:18:38: they're wanting to do and like what
01:18:39: their ask
01:18:40: is and um like we kind of was talking
01:18:44: about like earlier my there's definitely
01:18:47: stuff like we've said no to like
01:18:53: already. Uh next question from Ace on
01:18:58: Twitch. How much money would you guys
01:19:00: save if Unity Plus was still around? How
01:19:01: much money would you guys save after
01:19:03: rendering Switch? Uh definitely a few
01:19:06: thousand dollars. Um I feel like Bob did
01:19:09: get us like a good discount like this
01:19:11: one kind of specialties. He's able to
01:19:13: kind of like talk with them and kind of
01:19:15: like get um get us some discounts which
01:19:18: helps a lot. But yeah, it it it does
01:19:22: make it expensive by like a few thousand
01:19:25: a
01:19:29: year. Uh next question is from Nikki.
01:19:32: Nin's asking once we have net 9, what
01:19:34: other features do you expect to see
01:19:36: soon? I'm guessing the physics array
01:19:37: collections. What else? Um, we haven't
01:19:40: like made decision yet. Um, physics is
01:19:42: definitely high on the list. Collections
01:19:44: is high on the list. UI IK high on the
01:19:47: list, but no decision has been made
01:19:51: yet. Well, can I usually like do it
01:19:53: more? Like right now, right now like my
01:19:55: brain is essentially like full of like,
01:19:57: you know, it's full of like spliting,
01:19:59: splitting, splitting. So, I don't want
01:20:01: to
01:20:02: like fill it with like, you know, other
01:20:04: stuff until I'm done with
01:20:09: that. Next questions also from Grand UK.
01:20:12: Grand UK is asking
01:20:14: um uh there are systems made in Reso
01:20:17: that unentionally block bold laser
01:20:19: inside of the dash. Would it be possible
01:20:21: to go option to make dash take priority
01:20:23: over the world? You're in for rendering
01:20:25: and laser interaction. Yes. Yeah, that
01:20:27: is possible. we just need to like make
01:20:29: like a button for it and implement it.
01:20:31: So,
01:20:33: um if if if this is like a common issue,
01:20:36: I would say no, make sure there's a
01:20:38: GitHub issue for it and
01:20:41: um and like getting a bunch of B vaults
01:20:43: on it because that's like often times
01:20:44: like what influences what we
01:20:48: prioritize. Uh next question is from uh
01:20:52: Caster
01:20:55: Blades. Uh, Kster Blades is asking,
01:20:58: where am I going to place this? Uh, do
01:21:00: you expect the procedural mesh system to
01:21:02: be able to handle something like
01:21:03: Paralyives procedural furniture system
01:21:06: where you can, for example, freely
01:21:07: stretch your couch long ways and the
01:21:09: legs and arm everything will stay
01:21:10: proportional. When you hit specific
01:21:12: points, it'll start putting new sections
01:21:14: on the couch. I mean, depends what you
01:21:17: mean by handle. like you pretty much
01:21:18: need to implement that but like other
01:21:21: than that like there's not a reason not
01:21:23: to because the procedural mesh system is
01:21:26: generic like you can generate whatever
01:21:28: mesh data you want. It's just you know
01:21:30: matter of what algorithms like
01:21:31: implemented for particle procedure or
01:21:33: mesh but other than that like it's
01:21:35: generic like it's literally operating on
01:21:37: you know it's generating vertices
01:21:39: triangles and it can do whatever with
01:21:44: those.
01:21:46: Uh next questions oh we can already
01:21:49: answer this one. Uh Mart is asking in
01:21:52: your delog it looks like the IPC between
01:21:53: FR engineer is done using TCP connection
01:21:56: when you're planning to use shared
01:21:57: memory. Yeah, share memory is going to
01:21:59: be used. Uh there's also going to be
01:22:01: well like I said like earlier there's
01:22:03: two mechanisms. There's like one for
01:22:05: changing bulk of the data which is not
01:22:07: being done yet. Uh because we need to
01:22:09: just get the basic communication between
01:22:11: the two. You're essentially going to
01:22:12: have a system that sends like you know a
01:22:13: message saying frame is ready. Here are
01:22:16: the share memory regions where you you
01:22:18: know fill the data from. Um and then
01:22:21: like you know it actually accesses the
01:22:22: shared memory but like we need the s
01:22:24: messaging system for that. right now
01:22:26: that's using TCP for development reasons
01:22:28: so it makes it easier to debug but it's
01:22:29: going to be switched to another
01:22:30: mechanism
01:22:32: later but for that one like I feel like
01:22:35: even with TCP like it's it will be fast
01:22:37: enough because like when I was like
01:22:39: testing it and I was testing it in
01:22:40: editor like it was like you know running
01:22:43: like 1,500 FPS like I don't think that's
01:22:47: going to be like a bottleneck.
01:22:51: Um so even even with the TCP like it
01:22:54: would be likely like you know fine
01:22:56: because like the bulk of the data is
01:22:57: going to be shared over shared
01:22:59: memory.
01:23:01: Um next questions from kisser blaze this
01:23:04: video.
01:23:05: Oh I'm sure we can't we can watch
01:23:09: videos. Uh
01:23:11: we are answering questions from the
01:23:13: discord anymore. Yeah, like like um
01:23:17: yeah, you need to ask in
01:23:19: here. Uh some
01:23:22: conversation can say asking who
01:23:25: maintains mute helper is in essentials
01:23:27: because I think there's a bug with at
01:23:28: least one of the modules that are going
01:23:29: to want to report. Um so one thing is
01:23:34: like if you want to report a bug with
01:23:37: something, it doesn't matter to know who
01:23:39: maintains it. You just report it on
01:23:41: GitHub. Um, generally, you know, that
01:23:44: shouldn't be your job and like it
01:23:45: shouldn't be a thing to do. Like one
01:23:48: thing we're trying to avoid in general
01:23:49: is like, you know, when people go after
01:23:51: specific team members and be like,
01:23:52: there's like a bug with this. The
01:23:54: reports need to be made in general and
01:23:56: then like, you know, the appropriate
01:23:57: team members will decide to pick it up.
01:23:59: Sometimes it can be multiple people. Um,
01:24:02: and I actually don't know who maintains
01:24:04: it, which is, you know, another thing
01:24:05: like like just report a bug. Don't don't
01:24:07: worry about who maintains it.
01:24:14: Um, next
01:24:15: question is from Angel Boy.
01:24:20: Uh, having trouble positioning these.
01:24:22: Um, Angel Boy is asking, "In the context
01:24:24: of using Resonate over other
01:24:26: applications, would that mean I could
01:24:27: finally use my VR face tracking as
01:24:29: virtual face cam while playing
01:24:31: graphically intense games? I don't plan
01:24:34: to get face cam for variety of reasons.
01:24:35: Plus, I perfected my face tracking. So,
01:24:38: I'd like to use that for streams, too,
01:24:39: and such. Uh, so it sounds like you want
01:24:42: to use like Zenoid as a V tubing
01:24:44: software, which is another like another
01:24:46: use case I would like to do, but
01:24:51: um that's a separate feature from the
01:24:53: like, you know, from using it as an
01:24:55: overlay.
01:24:57: Um,
01:24:59: so yeah, like this is going to be the
01:25:02: part of the overlay, but it is also a
01:25:03: thing I would like to implement because
01:25:05: I kind of want to do like streaming some
01:25:07: other games and, you
01:25:10: know, having like, you know, having this
01:25:12: because like it does make it easier like
01:25:14: once you have your avatar fully set up
01:25:16: with face tracking, if you can just hit
01:25:18: a button and like, you know, you have
01:25:20: overlay that you can put over
01:25:21: applications, I think it makes things
01:25:22: much easier because you already have
01:25:25: like supporting avatar with full face
01:25:30: tracking.
01:25:33: Um, so next
01:25:35: question I just want to actually I think
01:25:37: we talked about a bit uh Grand UK mainly
01:25:40: to Sar but also FRS after split if a
01:25:42: session can native Linux.NET I believe
01:25:44: Sarah has demonstrated this. Would the
01:25:46: desktop capture tab in Dash be
01:25:48: eventually updated to be able to use
01:25:49: Linux native capture methods like pipe
01:25:51: wire? Oh, that's actually not where I
01:25:55: thought it would go. I mean like if we
01:25:59: if we are able to run like uh the main
01:26:02: engine like natively kind of like how
01:26:04: like the headless can but keep like the
01:26:06: uni part in like Proton. Um I mean I I I
01:26:10: would I would certainly like to give it
01:26:12: a shot. Well, that's a problem too
01:26:14: because like the part that does the
01:26:16: desktop, that's the part that runs on
01:26:17: the proton because like
01:26:21: um like if you're on the first engine
01:26:23: and native Linux.net, that's not the
01:26:25: part that handles the desktop.
01:26:28: M like that happens on the unit
01:26:31: side. So if the unit side is running on
01:26:33: the proton like that pretty much means
01:26:35: like no like that's not going to work.
01:26:38: We the the unit side we need to run
01:26:40: native Linux for that.
01:26:43: I don't know if it necessarily would. I
01:26:44: would I I I have I do have ideas how
01:26:47: that could work, but that's like I have
01:26:48: no idea how it's going to be structured.
01:26:50: So, but how would you do it? Because
01:26:53: like like the fansion side doesn't do
01:26:59: that. That happens on the renderer side.
01:27:03: I would have to I would have to look at
01:27:05: it more. But yeah, like I personally
01:27:08: think it could be done.
01:27:09: I don't really see how
01:27:12: like I mean like it's something I can
01:27:14: look into but like the the desktop it's
01:27:16: it's like I think the render would need
01:27:19: to run natively for that unless you can
01:27:21: like you know make it unless you can
01:27:23: make it somehow work you know with the
01:27:25: with a proton one.
01:27:29: Yeah I I mean either either way I would
01:27:31: have to look at it anyways. So, or you
01:27:34: would run like a third process that's
01:27:36: like, you know, just passing the texture
01:27:38: over like the spout or something. I
01:27:40: don't know. Yeah, I have no clue. But it
01:27:44: it would have to be looked into
01:27:45: regardless. I would like it to work at
01:27:48: the very least.
01:27:50: Or we just fix it on Proton.
01:27:53: Yeah, make the capture work. Make the
01:27:55: desktop capture work with Proton. Um,
01:27:57: yeah.
01:28:00: And this is solution.
01:28:03: Yeah.
01:28:09: But we actually we actually talking
01:28:10: about like you know having it um around
01:28:12: like the native native like FRS engine
01:28:16: and then run
01:28:19: um you know run the renderer like uh
01:28:23: with
01:28:24: Proton and like S like that script like
01:28:27: kind of look into it like and it was
01:28:28: like looking you're saying like it's
01:28:30: probably the best like having like a a
01:28:32: launcher process that just launches both
01:28:35: because the way it's going to work with
01:28:36: the split thinning is like we actually
01:28:38: going to run the FRS engine first and
01:28:40: the FS engine starts the render. So like
01:28:42: we will need to like start like you know
01:28:43: the
01:28:44: the native one and the native one we
01:28:47: have to start like a proton one but
01:28:48: that's not as easy as just like a proton
01:28:51: one starting a native one.
01:28:53: Yeah like um starting a starting like a
01:28:56: native process from proton is a lot
01:28:59: easier than like starting a proton
01:29:03: process from like the native side. I
01:29:05: mean it's
01:29:06: possible like if you
01:29:08: can if you can like make it uh if you
01:29:13: can like find the instance from the
01:29:15: native side of like the proton like uh
01:29:19: folder like the folder where like it's
01:29:21: contained then maybe you could do it but
01:29:24: like I I have not tried it myself so I
01:29:27: wouldn't know. I just know that it's
01:29:28: easy to do it the other way around.
01:29:32: Yeah. But I mean it
01:29:36: it's cool that the shared memory works
01:29:38: at the very least. Like I I saw that
01:29:40: work and that was really neat. Well,
01:29:42: it's one of those things we'll probably
01:29:43: like, you know, we'll get to it when we
01:29:45: get to it. Uh we probably have it like
01:29:47: you know running like with proton like
01:29:49: completely at first and then like you
01:29:50: know look for optimizing more. Yeah.
01:29:58: Um, Shadow's asking, "Assuming
01:30:00: everything goes smoothly, can you give
01:30:02: super rough ETA on the first MVP
01:30:04: pre-release with split architecture?"
01:30:06: Um, I don't know at this point. Like,
01:30:08: I'm still kind of like sorting through
01:30:09: things and it's like a lot of it's like,
01:30:10: you know, discarding a lot of the small
01:30:12: things that need to be moved around that
01:30:14: need to be kind of ripped and need to be
01:30:15: kind of reworked. So, like right now
01:30:17: it's a little bit too much in flags. Uh
01:30:20: maybe maybe sometime like you know like
01:30:23: after the next week but like like I said
01:30:26: I don't know like I'm rally making a
01:30:27: number
01:30:34: up. Oh no Kaio is asking uh because
01:30:39: Akima plans for fruits GPT to write
01:30:41: protolex until it goes through and eats
01:30:43: all mangoes in the world. No, we need
01:30:46: the mangoes.
01:30:49: The AI is eating the fruit now.
01:30:52: Oh boy. Oh no, you're cryo. Now the
01:30:56: hummer's asking, "So cryo."
01:30:59: I I don't know who this cryo guy is. Um
01:31:02: am I going to switch to him or Emacs?
01:31:04: Probably neither because and this is
01:31:07: where I'm going to make all of those
01:31:09: both of those communities hate me. I
01:31:11: think that uh they need a much better
01:31:14: like new user experience because they're
01:31:16: very very powerful editors, but the
01:31:18: setup experience has been nothing but
01:31:19: terrible and I really hate setting them
01:31:21: up because it's just like config files
01:31:24: and config files and config files and
01:31:26: it's just like it's just it needs a good
01:31:29: default out of the box and it's just not
01:31:31: worth it. I'm looking more into things
01:31:33: like Sublime Text because they're much
01:31:34: easier. And uh Sublime Text is also much
01:31:38: faster um than like VS Code anyways. So,
01:31:41: I'm happy. I'm pretty happy with that so
01:31:43: far. Definitely check out Sublime Text.
01:31:46: It's very cool. And you don't need to
01:31:49: unplug your computer from the power
01:31:50: source to exit those. Yeah, you don't
01:31:53: need to do
01:31:55: that. I made some people very angry now.
01:32:01: Uh, what is the what's up with the
01:32:04: sulfur training? So, Angel Boy asking,
01:32:05: "Fruits, can we get sulfur note for
01:32:07: Pterflies? What's happening?" What is
01:32:09: the sulfur bit, guys? We don't really
01:32:10: get it. Yeah, I don't know what it is.
01:32:13: Oh, wait.
01:32:15: Sorry. I I wanted to use a message to
01:32:17: kill everyone. I'm like, hm. I don't
01:32:19: want to interrupt. H, do you want to
01:32:22: read this one? Yeah, I can read this
01:32:24: one.
01:32:25: Uh, will we ever see Protolex compiled
01:32:28: into IIL in the future? Currently,
01:32:30: Protolux builds an execution sequence
01:32:32: and runs each node's functionality in
01:32:33: order, which can end up being slower
01:32:35: since you have to switch context to
01:32:36: invoke each action individually. My
01:32:39: thinking is that if each Protolux group
01:32:40: was compiled into a delegate at runtime,
01:32:43: the J compiler could chew up the code
01:32:44: and optimize the code much more
01:32:46: efficiently. Curious to hear your
01:32:47: thoughts on it.
01:32:49: Do you want to answer it? Do I want to
01:32:52: answer it? Um, I don't know. Do I mean I
01:32:55: you I think you initially wanted to
01:32:57: compile it to I in the beginning but
01:32:59: whatever library you're using wasn't
01:33:00: working right. No, no, no, no. I um the
01:33:05: goal wasn't to all compile it initially
01:33:07: to IO. It was to do it eventually and
01:33:09: it's just a matter of like you know
01:33:10: time. So like eventually I think it
01:33:13: would be good but um it just requires a
01:33:17: lot of time to be put into it. But it's
01:33:19: also like another thing is like you know
01:33:20: if we have like web assembler and time
01:33:22: maybe it would be like more work like
01:33:24: implementing with that. But like it's
01:33:26: also like a fair amount of work. So
01:33:28: we'll we'll see.
01:33:29: I I think it would be I think it would
01:33:31: be more apt to do it in the IL cuz then
01:33:33: the J compiler could really get a hold
01:33:35: of it and like chew it up real nice. I
01:33:37: mean so can in Viv assembly and that's
01:33:39: the thing you know if you have like a if
01:33:42: you have like a system that's
01:33:44: like you know handling optimization and
01:33:47: generation of code. Do we want to
01:33:49: maintain one system or do we want to
01:33:50: maintain two systems? That's true. So
01:33:52: it's going to it it depends on a lot of
01:33:54: things how things will develop. So yeah,
01:34:00: but eventually but um maybe but details
01:34:05: we'll figure out back swing at the
01:34:07: middle of my back swing. Yes. Yes.
01:34:10: That's the window of opportunity. That's
01:34:11: a very very very famous
01:34:16: quote. And now we're getting to the
01:34:19: Stargate stuff again. Uh it just is like
01:34:22: I love the bit where Rodney gets over Oh
01:34:24: yeah, we talk about this one.
01:34:30: Um UK is asking uh did you notice that
01:34:34: Resonite had a bit of a boost in player
01:34:35: numbers in this morning UK time? Uh
01:34:38: actually not the morning but I know like
01:34:40: VR [ __ ] was down
01:34:44: yesterday. So that probably brought a
01:34:46: bunch of bunch of people.
01:34:49: Um, Adreos is asking, "Do you listen to
01:34:52: music while coding to help you focus? If
01:34:54: so, what type?" Um, depends
01:34:58: sometimes. Problem is with a lot of
01:35:00: music like like it's very
01:35:03: energetic. Um, so like I don't know if
01:35:06: it helps like focus. It's more like it
01:35:08: helps me get like you know what's happen
01:35:10: like I'm going to go this thing. I'm
01:35:11: going to go. Oh my god. Freaks listen to
01:35:14: the kind of music where you open the
01:35:15: door and it screams die at you. Yeah.
01:35:18: There's like literally a song where it
01:35:19: screams
01:35:21: die. That's uh that's My Space by Legend
01:35:23: of Folium. It's very cool.
01:35:29: What about you?
01:35:32: Um sometimes I actually don't tend to
01:35:35: listen to music a whole lot, mostly just
01:35:36: because I don't think to put it on. But
01:35:38: usually I'll try and put on like some
01:35:40: like chill stuff typically without like
01:35:43: lyrics. Maybe maybe like
01:35:47: um piano or like some very light like
01:35:50: light like EDM or something. I don't
01:35:52: know. It really depends on my
01:35:55: mood. I don't do music myself much. Like
01:35:58: it is like just boring me. Like a lot of
01:36:01: music I have is very very active
01:36:03: listening and very
01:36:06: energetic. I did actually do a thread on
01:36:08: Blue Sky like with a thing like where I
01:36:10: posted a bunch of like songs. So like if
01:36:12: you want to find that one like that's
01:36:14: going to give you some
01:36:16: examples. Uh J is saying so mute helper
01:36:20: is maintained by team. Understood. We
01:36:22: didn't say that like I said like I don't
01:36:24: know and if I say like I don't know who
01:36:26: is maintained by
01:36:28: um I don't know. It means I don't know.
01:36:31: It doesn't mean necessarily was
01:36:33: maintained by team. It could like you
01:36:34: know just maintained by somebody else
01:36:36: and team is putting it in
01:36:38: but I don't know.
01:36:46: Um I actually maybe ask you know in the
01:36:49: art
01:36:50: um um I would say ask in the arch team
01:36:54: like office
01:36:56: hours. Uh next question is with Nukun.
01:37:01: Uh you didn't really answer my question
01:37:02: earlier. What does the reason I do in
01:37:04: the time between clicking and joining
01:37:05: session and actually putting you in that
01:37:06: session? What makes initial syncing or
01:37:08: whatever take long? what can we do to
01:37:10: optimize load that I mean I kind of
01:37:13: answered that like it's loading the
01:37:16: stuff there's like you know queue of
01:37:18: like the meshes and so on
01:37:20: so I don't I don't really know like what
01:37:22: else like you're looking for uh for
01:37:25: optimizing it's kind
01:37:27: of you know you need to pretty much
01:37:29: lower the amount of stuff you have um
01:37:33: because like you know the loading is
01:37:35: essentially a function like it needs to
01:37:36: load all the stuff so like the fewer
01:37:38: textures the fewer meshes you have in
01:37:40: there, the faster they'll
01:37:42: load. Uh, and that's about it. I think
01:37:45: like I don't know what else exactly
01:37:48: you're asking for. It really depends on
01:37:51: how like the thing is made and how you
01:37:53: have it set up. It could be other stuff
01:37:54: that like we don't know about that could
01:37:57: be causing it to. It's it's it's really
01:37:59: like something you just have to look at.
01:38:02: Yeah. It's like when you click like
01:38:05: essentially when you click the button
01:38:07: like it it needs to establish a
01:38:08: connection. Usually that's fastish. Uh
01:38:12: then needs to like sync the initial data
01:38:13: which is like the scene. So like you
01:38:15: know again having less stuff in there
01:38:17: will be faster. Um and then like it
01:38:20: needs to load stuff which again like
01:38:23: less stuff will be
01:38:27: faster. Verband is uh asking multiple
01:38:31: questions.
01:38:35: Um uh can you give a few more details
01:38:37: what the split entails? Uh do you have a
01:38:40: timeline for it? Trey was a good boy.
01:38:44: So for the first one the splitting what
01:38:46: it essentially means is like we're
01:38:48: pulling through engine which handles you
01:38:50: know majority of all the like interact
01:38:52: stuff out of Unity into its own process
01:38:55: under net 9 which will make it run much
01:38:58: faster and then like having Unity side
01:39:00: only pretty much mostly only the
01:39:02: rendering and some like interactions
01:39:04: with input hardware for like you know
01:39:06: that's related to um the rendering
01:39:09: window or the rendering hardware like VR
01:39:11: hardware
01:39:14: Um, so,
01:39:17: um, and it's pretty much kind of like if
01:39:19: you want like a lot of details, I
01:39:21: recommend watching the video on
01:39:23: performance that's stored on the YouTube
01:39:24: channel. Uh, that one goes like into
01:39:26: quite a bit detailed, some diagrams on
01:39:28: it, too. Um, the rough time plan we kind
01:39:31: of like, you know, talked about earlier.
01:39:32: Hopefully within a month, but we'll see
01:39:34: how things
01:39:37: go. There's sometimes, you know,
01:39:39: complications with things, so it's kind
01:39:41: of hard to predict.
01:39:43: Uh next question is from Grand K. Uh
01:39:47: Grand is asking with I button components
01:39:49: context menu UIX if you have certain
01:39:51: components next to them like text editor
01:39:53: button and making post trigger how does
01:39:54: that work? Would it possible to make it
01:39:57: explicit like dragging action component
01:39:59: on refield for action? What action on I
01:40:02: button would trigger so they could make
01:40:04: chains of actions and sync delegates
01:40:06: entirely in components.
01:40:09: Um I feel like it's like a good shoe
01:40:11: thing.
01:40:13: Um I usually like they will kind of
01:40:15: trigger all the components with specific
01:40:17: interface that's on the same slot, but
01:40:19: also you have like there's like
01:40:21: mechanisms for
01:40:24: um there's like mechanisms where you can
01:40:28: like you know with per flags you can get
01:40:30: the event and you can like you know do
01:40:31: whatever with impulses. So um it should
01:40:35: kind of cover most of it. Why is the
01:40:37: track going
01:40:40: weird?
01:40:42: Um yeah, I would say like make a good
01:40:45: visual if you want like spec more
01:40:46: specific
01:40:48: thing. Um Bit Crackn's asking a followup
01:40:53: to Dammer's question about whim. Have
01:40:55: you looked at laser whim?
01:40:58: That makes more sense. That's That's
01:41:03: uh Yes. I really I really just don't
01:41:06: find it to be much easier because they
01:41:08: still expect you to uh they still expect
01:41:11: you to set up a whole bunch of config
01:41:12: files. It's like, "Wow, look at all this
01:41:14: shiny stuff except you need to actually
01:41:16: go configure half of it for it to
01:41:17: actually work properly." And then they
01:41:20: don't tell you that, which I think is
01:41:24: really dumb.
01:41:26: I really just don't like the setup
01:41:28: process of Vim. I think it's really
01:41:30: overly complicated and I think it needs
01:41:32: to be better for a new user. Maybe I
01:41:35: mean you can just say like, you know,
01:41:36: that's maybe like cuz it's not like for
01:41:38: me as the target demographic, but I
01:41:41: think they do need a better like new
01:41:43: user experience if they actually want
01:41:46: to reach more
01:41:50: people. That's my opinion.
01:41:54: Uh, next question is from Czech the fox
01:41:57: otter. Uh, check the fox. Uh, saying,
01:42:01: "I'm currently suffering dealing with a
01:42:03: lot of anchors and now I've gotten
01:42:05: pretty good understanding of it, but
01:42:07: feels old and monolithic. Can you
01:42:09: elaborate a bit when the design goes
01:42:10: from the back when I still remember? One
01:42:12: thing I'm curious about is why they have
01:42:14: their own button behavior. Do anchors
01:42:17: predate button events?" I don't actually
01:42:20: remember unfortunately. I'd have to like
01:42:21: check
01:42:22: the we have to check the code and such.
01:42:25: the um that is pretty old system, but
01:42:28: like like
01:42:33: um like I'm pretty much the goal is like
01:42:35: you know you you're able to kind of
01:42:37: constrain you know where the avatar goes
01:42:39: because like you know you can anchor
01:42:41: specific body parts but also the goal is
01:42:44: you know you can say this body part is
01:42:46: constrained to this area but also maybe
01:42:49: like you know it's not just a single
01:42:50: point but it's like you know it can move
01:42:52: within that. So like for example, if you
01:42:53: sit in a chair, you know, you can move
01:42:56: your feet within an area, but like you
01:42:58: cannot move them too far. So if you're
01:43:00: like using full body, so that's pretty
01:43:02: much like, you know, the kind of design
01:43:04: go for it. Um the button behavior, I
01:43:07: don't really
01:43:10: know. I don't exactly know like what do
01:43:12: you mean by that? Um I don't think they
01:43:14: predate button
01:43:17: events, but like I don't know what you
01:43:19: mean by like you know their own button
01:43:20: behavior, unfortunately.
01:43:26: Um, next questions from
01:43:32: Ozie. Oie is asking,
01:43:35: uh, is there plans to expose certain
01:43:37: settings towards space, namely movement
01:43:38: related ones like turning settings, dead
01:43:40: zone settings? Of course, uh, not
01:43:43: everything should be exposed for the
01:43:44: power of security, but a spark of some
01:43:45: useful objects. I would say make a good
01:43:48: like it should be easy to expose them.
01:43:50: Um I think like we just need to like
01:43:52: kind of mark them with an attribute like
01:43:54: at least it's been a bit since I worked
01:43:56: with the setting system but um
01:44:00: um it shouldn't be too hard to do. We
01:44:03: just need to like know which ones people
01:44:04: want
01:44:06: exposed. Oh no one has really to fix the
01:44:10: IK.
01:44:13: Um okay missed the third question from
01:44:16: Verban I think who's a good
01:44:17: boy. more of a
01:44:22: message. Uh, and last question
01:44:27: is from Granny K. Uh, I spoke with
01:44:31: someone someone recently was excited
01:44:32: about workspaces for but disappointed
01:44:34: they were user space only. Uh, is there
01:44:38: any reason why they're user space only?
01:44:39: If this is incorrect, ignore. Yes, it's
01:44:41: because security. uh if they were in
01:44:44: world it would essentially let
01:44:47: anyone vote like save things onto your
01:44:51: account which can be you know very
01:44:53: abusable and load things from your
01:44:54: account without your permission. So that
01:44:57: wouldn't be a good idea. So for that
01:44:59: like it would need like a more kind of
01:45:00: controlled mechanism. Um you know it's
01:45:04: not something like you want to do like
01:45:05: where people can just arbitrarily
01:45:08: um arbitrarily save stuff like on your
01:45:11: account.
01:45:16: Uh, next question. And also we have 15
01:45:19: minutes left, so it's probably time like
01:45:21: for your latest questions. Like if you
01:45:23: still want to ask some, don't ask like
01:45:25: super long ones at this point. We might
01:45:27: not be able to get through those. Um,
01:45:31: uh, anyway, uh, others is asking, "What
01:45:34: is the bug you thought the damas were
01:45:36: for making?" I don't actually remember.
01:45:38: Uh there's been like
01:45:40: a
01:45:41: few sometimes there's like a few like D
01:45:44: things that happen but I just I don't
01:45:46: remember
01:45:47: them like I don't remember the
01:45:49: specifics. I can't really pick out one
01:45:52: either but I can really remember
01:45:56: there. Sorry.
01:45:58: Yeah, there's
01:45:59: like um I know there's like cases
01:46:03: sometimes it happens but just go like
01:46:04: that. It was stupid, but
01:46:06: like not big enough that it kind of
01:46:08: like, you know, sticks to your
01:46:12: memory. Um, next question is from Ace on
01:46:16: Twitch
01:46:17: 17. Uh, they're asking bit of off topic
01:46:20: question just asking to fill up time.
01:46:22: What are your guys thoughts on Nintendo
01:46:23: Switch 2? Me personally, I got it on day
01:46:26: one and it looks more vibrant and smooth
01:46:27: compared to Switch One and I really like
01:46:29: it. Um, I don't really have like one
01:46:31: myself. I don't use Switch or Nintendo
01:46:34: stuff, so I don't
01:46:38: know. I I don't even know like what the
01:46:40: differences are between Switch One and
01:46:42: Switch 2.
01:46:44: So I don't know what you say.
01:46:48: Um I don't really care for Nintendo
01:46:50: products. Yeah, just wholesale. Sorry.
01:46:54: Yeah, I kind of same
01:46:57: information.
01:47:00: Uh, next question is from check the fox.
01:47:04: Anchors don't really seem to use button
01:47:06: events. They use avat touch triggers.
01:47:09: Also, anchor component has its own
01:47:11: hovering
01:47:12: tool. Um,
01:47:14: uh, that's true when you hover over
01:47:16: touch trigger. Oh, okay. Oh, so one of
01:47:18: the reasons is like so like when you
01:47:20: click on something you actually the user
01:47:21: gets prompted to be anchored because we
01:47:24: don't want users to just be like
01:47:27: anchored out of the blue. Um so you
01:47:30: should be able to like like make your
01:47:32: own stuff. You could potentially even
01:47:33: add like buttons for it. So I think just
01:47:35: m like nobody really requested
01:47:39: one like
01:47:42: yeah like it's probably just like people
01:47:44: didn't request the mechanism. I thought
01:47:46: one of the reasons is also uh because
01:47:48: there's like you know multi-anchors and
01:47:50: the multi-anchors they're actually more
01:47:52: complex than just a button because they
01:47:53: let you point to particle spot and it
01:47:56: actually makes an anchor there. So you
01:47:58: can you know
01:48:00: make you can make like you know anchors
01:48:02: that's not just like fixed set of
01:48:04: anchors but like you know there are like
01:48:06: whatever actually dynamically makes them
01:48:08: and you can really do that with but
01:48:15: Oh no. Get a new case. I speak the name
01:48:18: of Schnoid and make FKS insider and
01:48:20: myself
01:48:23: disappear. I don't think it worked.
01:48:25: We're still
01:48:29: here. Oh,
01:48:32: what the [ __ ] No. No. Don't don't don't
01:48:34: import these. Don't do not import these.
01:48:36: I mean, I can't. Okay. I my my freaking
01:48:41: my my my like my like keyboard key
01:48:43: sometimes gets stuck where it like keeps
01:48:45: the control keys down. I don't know why
01:48:48: it does that.
01:48:51: Next questions from Angel Boy VR. Uh
01:48:54: what is your favorite B that end up like
01:48:55: left as a feature due to its usefulness
01:48:57: or something if there were only also
01:49:00: cute? No
01:49:02: denying.
01:49:04: Um, I mean the the one that's my
01:49:08: favorite is not actually useful, but
01:49:10: it's like the the desktop thing where
01:49:12: you can like, you know, rapidly sit, you
01:49:14: know, rapidly crouch where you just go
01:49:17: because people do that a lot in desktop.
01:49:18: It's like one of those kind of desktop
01:49:20: language things, but it doesn't really
01:49:22: have any use.
01:49:24: Oh yeah, UX bomb is a good one that's
01:49:26: actually useful for some things.
01:49:32: [Music]
01:49:36: Long
01:49:37: J23 uh is asking
01:49:42: uh has the last build affect the texture
01:49:44: application to the meshes for Nvidia
01:49:46: driver seems slower texture load and
01:49:47: cloud home from prior builds. It
01:49:49: shouldn't affect texture load but mesh
01:49:52: mesh load mesh loading will take longer
01:49:54: so it doesn't hitch as much. So it's
01:49:56: sort of like you know trading off it's
01:49:58: trading off like the speed of the upload
01:50:00: for the heat chain. Um but it can like
01:50:03: it can make other things longer because
01:50:05: like everything is a queue. So like if
01:50:06: you're pushing data to the GPU you can
01:50:09: only be pushing one thing at a time. Um
01:50:12: which means you know I like if if
01:50:13: there's meshes being uploaded and
01:50:15: textures being uploaded only one of them
01:50:16: can be uploaded at a time. And if
01:50:18: there's like a mesh upload it's taking
01:50:19: longer it's going to hold up the queue
01:50:21: for you know the textures.
01:50:26: Uh, next question from Platypus 744.
01:50:30: Um, once the split thinning happens,
01:50:32: aside from bug fixes and polish, are
01:50:34: there any other things you want to do
01:50:36: for performance before moving to the
01:50:37: next focus? Um, we'll probably update a
01:50:40: lot of the libraries and kind of like,
01:50:42: you know, do like some like posts with
01:50:44: any kind of exams and quick updates, but
01:50:47: um, we're probably not going to do any
01:50:49: major work like on any like other like
01:50:52: performance things. We're going to move
01:50:54: on to some other things for a bit, but
01:50:56: there's definitely like other major
01:50:57: performance improvements that we want to
01:50:59: do in the future. So, um, we definitely
01:51:02: update like, you know, Beu Physics,
01:51:05: um, a lot of like other libraries. We
01:51:07: might maybe like switch some of the data
01:51:08: types and so on for more performant
01:51:10: ones, but we'll
01:51:15: see. Actually, there is like one there
01:51:18: is one thing that I'm kind of
01:51:19: considering is like we might try
01:51:21: switching the unit to build the IO to
01:51:24: C++ and see how fast that runs on Unity
01:51:27: side if that makes like moves the needle
01:51:29: on the performance like making the unit
01:51:31: side faster because right now we can't
01:51:33: really do it because like unit is
01:51:34: running entirely of FS engine and it's
01:51:37: just auto C++ doesn't mesh well but like
01:51:39: with splittening fruits engine's gone
01:51:42: and that's relatively small amount of
01:51:44: code so that could help with things but
01:51:47: we'll
01:51:51: [Music]
01:51:52: Okay, Angel Boy VR is asking, uh, did
01:51:57: anyone else notice photon does getting a
01:51:58: lot of PS earlier than usual since last
01:52:01: update? So, is it just me? My items
01:52:02: these buttons ask and there's a bit like
01:52:04: error.
01:52:06: Um, I don't really notice anything, but
01:52:08: like or hear anything, so I'm not sure.
01:52:12: the these questions always get me cuz
01:52:14: it's cuz like I've heard multiple people
01:52:16: say like does Reset seem laggier today
01:52:19: to you? It's like well barely anything
01:52:22: changed and I don't know how it could it
01:52:26: it sometimes like happens when there's
01:52:28: even no updates and people will say
01:52:30: things and like it can there's like so
01:52:31: many variables that like is not really
01:52:34: actionable on our end and without like
01:52:37: any data like we can't really do much.
01:52:42: um like we would need like you know some
01:52:43: kind of like benchmark or comparison or
01:52:46: something because it's just it's too
01:52:49: vague to like
01:52:50: really do much
01:52:52: on.
01:52:56: Um so K volbs is asking if I recall
01:52:59: doesn't export skin meshes only regular
01:53:01: meshes has been
01:53:03: min something with skin mesh why is that
01:53:05: and is it plan to get skin mesh
01:53:06: expporting working ignore right
01:53:09: now does now yeah it doesn't support it
01:53:12: and it doesn't support because it hasn't
01:53:13: been implemented yet so and at some
01:53:16: point it will be implemented but I don't
01:53:19: know when um like a specific timeline
01:53:24: Fine. Uh, next questions from Jake the
01:53:27: forks. Uh, what do you think would the
01:53:29: next best UI to work with data fees? I
01:53:32: think once performance is no longer the
01:53:33: major blocker for new users, dashboard
01:53:36: UI might be the highest. But depends
01:53:38: what you mean by dashboard
01:53:40: UI like do you mean like the home
01:53:42: screen? Because like the home screen is
01:53:44: not going to use data feeds. Like that's
01:53:46: just kind of like collection of facets.
01:53:48: Um, we'll probably do like inventory or
01:53:52: worlds or
01:53:55: contacts. Um, because we do like the
01:53:57: settings. I think the inventory is the
01:53:59: most commonly used one. So like the one
01:54:00: would benefit the most and probably the
01:54:02: one that people most want.
01:54:05: Um, so I think the inventory is high on
01:54:08: the list. The worlds we already kind of
01:54:10: have like part of it. So like that might
01:54:13: like we might end up like doing that one
01:54:16: first maybe because like there's like
01:54:17: most of the world stuff is already
01:54:19: implemented and it just needs a little
01:54:20: bit more. But we'll see if it's like you
01:54:24: know if it's quick to like just add the
01:54:26: bits for the worlds and have the team
01:54:28: like work on it while we work on bits
01:54:30: for the inventory.
01:54:39: Yeah, pro probably I would say the
01:54:41: inventory is very likely unless the
01:54:43: worlds ends up like
01:54:46: being quicker and like you know to do
01:54:48: because like there are is data feed that
01:54:50: like gives you sessions and uh you know
01:54:54: active sessions and wars you have open.
01:54:56: It just needs to give
01:54:57: you the worlds as well like you know
01:55:00: published ones and once it's there then
01:55:04: the content like the art team can just
01:55:05: like make u they can just make you know
01:55:09: UI for it. Uh so it might be like better
01:55:12: kind of and then like you know while
01:55:14: they do that we work on like making data
01:55:17: fits for inventory and then the thing
01:55:19: like makes UI for
01:55:23: that. Uh, next questions from Adrias and
01:55:27: also just checking on time. We got like
01:55:29: 4 minutes left, so it's probably last
01:55:32: few questions. Um, is asking, "What is
01:55:35: the most frustrating question comment
01:55:37: you keep getting from the community
01:55:40: continuously?" Um,
01:55:43: why are you making the game worse? Why
01:55:44: do you Why is it like this? Why, etc.,
01:55:47: etc.
01:55:48: Yeah, like that's the one is like when
01:55:51: people assume like we're making things
01:55:53: worse on purpose or that we don't care
01:55:56: about things because all the times like
01:55:58: you know we care but there's limits to
01:56:02: what we can do like you know we're
01:56:03: limited on time we're limited you know
01:56:06: there's like number of pressures
01:56:08: um you know things to deal with
01:56:14: um so it's
01:56:16: um It's like
01:56:21: um often times like you know it's not
01:56:23: like because we don't care. It's just
01:56:24: because like you know we're limited or
01:56:26: maybe like you know we don't have the
01:56:27: right tools, resources, whatever like we
01:56:29: kind of need. And in fact, like we do
01:56:32: spend a lot of time, you know, often
01:56:35: times more than is healthy putting into
01:56:38: this
01:56:39: project. And then to hear, you know,
01:56:41: that we don't care. That is pretty
01:56:44: frustrating because like it feels like
01:56:46: it makes it feel
01:56:48: like it doesn't matter that we putting
01:56:50: this much time into it. Like people
01:56:52: don't care. People don't appreciate it.
01:56:54: We could be like we could literally not
01:56:57: care and just spend minimal effort on it
01:57:00: and would still keep getting the same
01:57:02: comments. Like it it makes it feel like
01:57:04: you know that the all of the extra
01:57:07: effort like is for nothing and that
01:57:12: sucks. Um but we know we do keep putting
01:57:15: it into the project because we do care
01:57:18: even though like you know it doesn't
01:57:20: make things perfect or doesn't fix
01:57:22: everything.
01:57:24: Um, next question
01:57:29: uh is from Ace on Twitch. Will the
01:57:32: desktop page ever get a work for data
01:57:34: feeds? One thing I notice when I use
01:57:35: desktop page get issue but cursor likes
01:57:38: leaving a trail and it looks glitchy.
01:57:40: That's not really a data feed thing.
01:57:41: Like that's there's not really a feed of
01:57:43: things. That's just, you know, if
01:57:46: there's if there's an issue with like
01:57:48: the cursor, I would say report it. But
01:57:50: like that's not the desktop is not
01:57:52: specifically not a data feed thing. Data
01:57:53: feed is like when you have
01:57:57: like you know feed of like like items
01:58:01: like that can change but like this this
01:58:03: could be pretty much you have you have
01:58:04: your desktop and it's not a feed.
01:58:09: Um, if it did, I think we can do one
01:58:12: more question, but like we got like a
01:58:14: whole bunch like uh opt out. Uh, Kol is
01:58:17: asking talking about dash. Would you
01:58:20: guys use any like CSS to customize it?
01:58:22: Personally, I hate rounded corners, but
01:58:24: I would you guys think about using CSS
01:58:26: in general for styling resonate.
01:58:27: Probably not CSS. That would be a huge
01:58:29: undertaking and it's not designed for
01:58:30: UIX. it's going to have like its own
01:58:32: styling
01:58:33: system but CSS is like huge and like we
01:58:37: not dep on implementing that like and I
01:58:40: don't think it would match well. Um also
01:58:42: like just this one very quickly. Uh as I
01:58:44: was asking how's Britain going to work
01:58:47: um we unfortunately don't really have
01:58:49: time to get into details because like um
01:58:51: we got like one last minute. Um I do
01:58:54: recommend watching the video on
01:58:56: performance on our YouTube channel. It
01:58:57: goes into quite a bit of details on the
01:58:59: splittening. Uh so they might kind of
01:59:01: give you some answers. If not, like ask
01:59:03: uh next week. Uh with that, uh that's
01:59:08: pretty much our stream for today. So
01:59:10: thank you everyone. Uh thank you
01:59:11: everyone for joining. Thank you for you
01:59:13: know asking your questions like I hope
01:59:15: like you kind of enjoyed it. Um thanks
01:59:18: like you know for being here helping
01:59:20: like answer the questions too and
01:59:22: program like thank you for you know
01:59:24: helping to supporters. So right matter
01:59:25: it's like you know through just playing
01:59:26: the game you know being part of the
01:59:28: community making cool content or uh you
01:59:31: know talking about it on social media or
01:59:34: uh supporting us financially either like
01:59:36: you know through Patreon stripe or you
01:59:38: know the Twitch subscriptions as well.
01:59:40: Um it helps us a lot and if you're on
01:59:43: Patreon uh consider switching to Stripe.
01:59:45: Uh we actually going to be bringing of
01:59:47: beta like very soon. Um, and generally
01:59:51: like you know it's been like very stable
01:59:53: like and generally better experience
01:59:54: than Patreon. Uh, and we actually get
01:59:57: more money out of it because they take
01:59:58: like roughly 5 to 6% with versus Patreon
02:00:01: takes about 15. So if you even if you
02:00:04: support at the same level it actually we
02:00:05: get more money out of it. So thank you
02:00:08: very much. Uh, I'm going to check if
02:00:10: there's anybody to
02:00:11: rate. Uh, let's see.
02:00:16: Twitch. Uh we might just do creator gem
02:00:18: if they're still streaming. But if
02:00:20: you're streaming around this time, uh
02:00:23: it's a this is this is a good time to
02:00:26: stream Resonide because um you will get
02:00:30: raided. Uh looks like it's just creator
02:00:33: jam. So I'm going to send you over to
02:00:36: Medra. Um so tell me Medra hi for us. So
02:00:41: I'm going to do
02:00:44: raid.
02:00:46: creator gem. There we go. So, again,
02:00:50: thank you everyone. Uh, hope you enjoy
02:00:52: the stream and
02:00:54: uh I'm getting excited for the split
02:00:56: ending. Bye-bye.
02:01:00: Bye-bye. Oh, it's not ready. Oh, there
02:01:02: we go. It's ready. Bye, Tom. High. Uh,
02:01:06: goodbye. Don't fall in. They're falling
02:01:09: in.