This is a transcript of The Resonance from 2025 December 20.
00:00: Start recording. There we go. Should be
00:02: live.
00:04: Hello.
00:04: >> Hello.
00:05: >> We're live. Can you hear us?
00:08: Hello.
00:10: We have chat.
00:11: I'm going to post the announcements.
00:14: This one. Post the other one. Where's
00:17: the other one?
00:20: Beautiful chat. Post this one.
00:27: There we go. Hello.
00:32: No wooden
00:36: thing this one. Oh, there we go. Hello.
00:38: It's the ch. Hello.
00:40: Hello.
00:43: Hello.
00:45: >> Ah.
00:49: >> You're cyro now.
00:51: >> No, I'm not.
00:52: >> Greetings from the new play.
00:57: in the new place. Hello.
00:59: >> Greetings.
01:00: >> Can you Can you hear us fine?
01:03: >> Can you hear us? Pretty good.
01:06: >> Too fast. If username sit now,
01:11: >> right?
01:20: My freaking out. I'm right now.
01:26: Hello.
01:27: Hi.
01:28: >> Hello.
01:31: Can you hear us? I don't know if the
01:32: audio is okay because nobody said so.
01:36: >> Yeah. Is the audio doing audio doing
01:38: fine, guys?
01:40: >> Hello.
01:43: Is this is this stream just going to be
01:45: us saying hello for five minutes?
01:47: >> Check the filter. Sounds good. Hello.
01:50: Well, hello and welcome. Welcome to
01:51: another episode of Resonance. Um
01:56: we say is saying sun. Thank you.
02:00: So this is another episode of the
02:02: resonance. User
02:05: and we're going to be answering any
02:06: questions you might have about the
02:08: resite for next two hours or so. Um yeah
02:12: noticed
02:15: we'll be answering your questions. Um
02:18: anything about their resonate? It can be
02:20: technical. It can be philosophical the
02:22: future as like whatever whatever we want
02:24: to know or even if it's just like you
02:26: know personal questions like just
02:27: chatting about stuff. Um let's do
02:32: um
02:34: we Oh my streaming is like freaking out
02:37: right now. I'm on like Wi-Fi.
02:41: >> Yeah, it's uh Oh boy. Oh boy.
02:47: Oh jeez.
02:50: Yeah, the Wi-Fi is kind of Oh, there we
02:52: go. It's clearing up. Sorry. Um
02:55: I've been traveling sol on my quest
02:57: right now and screwing over Wi-Fi is a
03:00: little bit uh not as good as
03:04: um but yeah, welcome. Uh the one thing,
03:07: make sure to put a question mark at the
03:09: end of the your message on Twitch. Uh
03:12: that way it could pop some thing here
03:14: and we can answer the question and we
03:16: don't miss. Uh we also have some
03:19: questions from uh we have some questions
03:22: from uh Discord.
03:26: Uh so we'll be going through those
03:28: first. Um, we kind of skipped like we
03:31: started kind of doing a new section
03:32: where we still show stuff from the
03:34: socials, but unfortunately I'm kind of
03:36: like more limited on hardware now and I
03:38: haven't like done the integration for
03:40: embeds yet, so I can't really easily
03:42: bring them in. Um, so we're going to
03:44: skip that one today, unfortunately.
03:47: Um,
03:50: there's uh
03:53: um this should be everything I think.
03:54: So, we're going to go through Discord
03:56: questions and we're going to go through
03:57: the uh Twitch ones. Um, so I think we
04:02: can get started. I don't think I'm
04:03: forgetting I'm forgetting anything.
04:07: >> Thank you, the new Bobas
04:12: for the Thank you. Hello everyone,
04:16: everyone who just joined. We're
04:17: answering your questions um from Twitch.
04:20: Uh we're also going to ones from Discord
04:22: first. just put a question mark and like
04:24: we'll it pops up our thing and then we
04:27: can answer it. So with that let's get
04:29: started.
04:31: So I will pull the first this is the
04:35: first question from
04:37: Discord. Uh let me just duplicate it so
04:40: I don't read it. Uh F is asking if the
04:44: NDP was deleted does the migration tab
04:46: now serve any purpose? Is the mig tab is
04:50: the migration dash tab going away? If
04:52: so, when? So, this is something we kind
04:54: of get asked about a bit. There's
04:56: actually multiple purposes for it. Um,
04:59: and it definitely does serve purpose
05:01: because one of the things you can do is
05:03: you can migrate one resonic accounts to
05:05: another account. So, if you want to move
05:07: stuff between accounts, that can be used
05:09: for that. It'll migrate stuff between
05:11: two accounts. The whole point of
05:14: migration is it works between any two
05:17: compatible infrastructures. And it's
05:19: actually now like additional usages. If
05:21: you check the devlog, uh per prime has
05:24: been working on uh setting up
05:26: infrastructure for um a business client
05:30: and essentially run you know their own
05:32: infrastructure and in order to make
05:34: things work and test things. He actually
05:36: needs to move stuff from the cloud to
05:38: the uh business uh cloud and the
05:42: migration also serves a purpose. He's
05:43: used that functionality to move some
05:45: some stuff over. So the migration is not
05:48: going away. There's bunch of other uses
05:50: for it. Some are like more business
05:51: related, but there's also like reasons
05:52: you can use it. Uh what we'll do is
05:55: we'll eventually just move it somewhere
05:57: else. Um it's probably going to happen
06:00: like sometime around like when we
06:02: redesign more chunks of the UI.
06:04: Generally the idea is like we're going
06:06: to move it like make like a tab like
06:08: something like tools and something and
06:09: you'll find it there if you need it. So
06:11: it doesn't need to be like a not level
06:13: but um as a functionality itself there's
06:16: lots of reasons for it. Some of the
06:18: business clients even depend on it. So
06:20: the functionality itself is not going
06:22: away. Always going to be accessible in
06:24: some way.
06:29: Uh next question.
06:32: This is a longer one.
06:37: Uh where do I even put it? So okay, so I
06:39: made a space. Uh let's see. Yosh is
06:44: asking when it comes to not breaking
06:46: legacy content there's generally two
06:47: main ways to go about it one making
06:50: legacy loaders that will autocon convert
06:52: content under runtime for each time such
06:54: legacy content is spawned locally two
06:56: doing of all legacy content on server
06:58: side converting legacy content the
07:00: current standards once which can then be
07:02: used without issue at runtime there's a
07:05: nice take form approach most of the time
07:06: I know that ro for recording change
07:08: while keeping a same but not to my
07:10: knowledge this ever been done by team to
07:12: promote legacy content current senders
07:14: and do a bit and time legacy loaders why
07:17: not um separate question my mod optimize
07:22: uh plus
07:24: loss behavior
07:25: >> I think the second separate question
07:28: >> oh one thing if you have two separate
07:31: questions please make them two separate
07:33: messages um otherwise we're probably
07:36: going to like miss that because um when
07:39: editing this um usually go like try this
07:43: like I'll just look like when there's a
07:44: question I'm like okay this is one
07:46: question so it kind of makes it much
07:48: harder to like figure out when the
07:51: second question is um so one one qu one
07:55: one message per question please
07:58: um anyway to the question itself uh
08:02: there's a like there's a few reasons
08:03: like why we actually do the first one um
08:06: one of them is the legacy conversion is
08:09: not necessarily perfect there can be
08:10: edge cases that can is uh there can be
08:13: errors in the conversion. There can be
08:14: things that are missed if you do it like
08:17: one time and you essentially override
08:19: the old content. Any mistakes you made
08:22: during that conversion are now baked in.
08:25: And now like you know whatever original
08:27: you had that is lost forever. Uh and
08:30: it's something we want to avoid. So, you
08:33: know, it only happens like when you load
08:34: the item as long as you don't override
08:36: item yourself. We can still make any
08:39: corrections to the conversion algorithm
08:41: and we can make conversions to like you
08:42: know old content or even like any
08:44: mistakes um and just spawn it again if
08:47: the conversions happen um you know
08:50: without like losing the original data.
08:52: So that's one of the major reasons. um
08:56: we pretty much you know don't want like
08:58: if you like run the conversion like
09:00: globally for everything
09:03: you know there's a lot of content we
09:05: could end up corrupting as a result so
09:08: we're not going to do it uh this way you
09:11: know if there is a problem with
09:12: conversion and you spawn something
09:14: usually you can also you know tell
09:15: during pre-release we tell you don't
09:18: override the content report the
09:20: conversion bug and we'll try to fix it
09:22: and then you can just spawn it And you
09:24: can also yourself spawn it, you know,
09:26: and do manual fixes and save it. But the
09:28: point is we don't want to like corrupt a
09:31: bunch of content. Um, the other thing is
09:35: the other major reason not all the
09:38: content is actually on the cloud. You
09:40: can have, you know, stuff that's
09:41: exported to resize packages and this can
09:44: exist whatever, you know, maybe somebody
09:46: uploads them to camera route. There's no
09:48: way to like, you know, um, upgrade that.
09:51: uh you can have it like stuff that's
09:52: saved locally too. So there's also
09:56: content that is not reachable from um
10:00: you know cloud. So we essentially would
10:02: be saying like oh like all that content
10:04: is now
10:06: broken and you know that's another thing
10:08: we don't want to do. Um, we want we want
10:12: like like one of our biggest
10:13: philosophies is like we design things so
10:17: it kind of works, you know, long term
10:20: and we're kind of like committed to
10:21: doing that. And we're like a lot of the
10:23: mechanisms we have, they actually make
10:24: it like easy to do and maintain that
10:27: because they they form like a
10:30: there like a mechanism for like doing
10:31: the upgrade.
10:33: Um, but yeah, that's uh that's pretty
10:35: much like two main reasons like why we
10:38: do know the first approach. Um and also
10:41: like not the only ones like you know
10:42: like to do it. Um consider lo for
10:45: example Minecraft like which kind of
10:47: went through a bunch of like you know
10:49: bunch of different uh format versions
10:53: u but it'll still like load the old maps
10:55: and usually if you lo like really old
10:56: map what it'll do it'll convert it from
10:59: like you know the old alpha version to
11:01: like the beta version and then like next
11:03: one is just kind of change the
11:04: conversions as well. Um but yeah,
11:07: generally maintaining long-term
11:10: compatibility
11:11: is one of our you know strongest
11:15: philosophies forite and doing the second
11:18: option would break it. So that's why we
11:22: don't go with that option.
11:24: Um for our second question specifically
11:27: more optimized for violation progress
11:28: product loader if legacy behavior have
11:31: some ext for this stuff like legacy
11:34: product loader becoming a maintenance
11:35: burden 3 years in the future and change
11:37: could be made will there ever be time
11:40: when this conser is no longer worth
11:42: maintaining to sweeping conversion
11:43: several legacy assets of it maybe it
11:47: kind of sounds like it just kind of
11:48: broke some things because like generally
11:50: the conversion should be like it's the
11:53: relatively isolated basic process. So
11:56: the way the conversion is kind of
11:58: written and the things are written
12:00: around it is you know it kind of
12:02: consider this like you know
12:03: transitionary
12:05: code but like then the new code doesn't
12:07: need to like worry about it too much. So
12:09: generally it's not like much of a
12:11: maintenance burden. I don't know what
12:13: happened like you know with a mod like
12:14: probably omitted something or something
12:17: was kind of like
12:19: not work like not not being considered.
12:22: So it probably exploded things but uh
12:26: like it'll depend like if if something
12:29: does really become like a big
12:30: maintenance burden then like we can have
12:32: you know conversations like how do we
12:34: like deal with it? Um how do we like we
12:37: would probably maybe like isolate things
12:39: like we would isolate um
12:43: you know the conversion code maybe like
12:45: the conversion utility and you know
12:47: build it into like it's standalone two
12:49: that's now not connected to the code
12:51: base but it's like you know say for
12:52: example separate like separate comment
12:54: like utility if it's like old content
12:56: it's going to like invoke that and we
12:58: don't have to like you know maintain
12:59: that one anymore. Um maybe something
13:02: along those lines, but like it it would
13:04: be it would take a lot for us to like
13:07: you know consider breaking
13:09: compostibility and we work for lots of
13:12: ways to avoid doing that.
13:15: >> So um I just wanted to clarify that Yosh
13:18: did actually send those as two different
13:19: messages. Uh but Discord doesn't show
13:22: the uh name when you send them too close
13:24: together.
13:26: >> Oh, I see.
13:30: I mean we kind of are related anyway so
13:32: that kind of works.
13:36: Uh next question is from Moonbase.
13:40: Moonbase asking due to an expert being
13:41: developer held is there's not
13:42: development essentially halted until
13:44: internal step is searched at all. No, I
13:47: mean if you even look at the
13:51: I don't even know where to begin with
13:52: this one because it feels like like you
13:54: haven't even
13:56: read stuff like with the like little
13:58: stuff with the like what were we going
14:00: focusing on because part of the like
14:01: development held is we're going to be
14:03: focusing more on like fun issues uh you
14:06: know fun features which is still
14:07: personite development but also like if
14:10: you look you know uh at the update
14:13: channel we've released a bunch of
14:14: updates So much I know you're a good
14:18: answer there is also
14:21: like focusing you know on improving our
14:23: processes
14:25: I feel that's still like you know resite
14:26: development we're still improving the
14:28: platform we might not be necessarily
14:30: improving you know features um which we
14:33: still doing because like you know it is
14:35: also part of it we also still focusing
14:37: on things because like for example on
14:38: the creative day um you know we are
14:43: um like that's like one of the days out
14:46: of the week and the four days we're
14:48: still like, you know, focusing on other
14:50: stuff and we've already released a bunch
14:51: of builds, you know, where there's a
14:52: bunch of contributions improving
14:54: different um improving different things.
14:58: Um also like you know the creative stuff
15:00: that's still resonate development that's
15:02: still helping you know the platform
15:04: adding new and fun features. Um and even
15:07: stuff like improving processes that's
15:10: still part of the development because
15:11: that like helps the future like work on
15:14: the code like making platform like this
15:16: is not just you know writing code and
15:18: features it's something like you know
15:19: processes how do we update things how do
15:21: we evaluate things how do we like you
15:23: know work that all comes as a part of
15:26: the development so that's kind of
15:27: contributing to it and I think it's
15:30: healthier to like think of those things
15:32: as part of the development itself and
15:34: that's that was kind of the whole point
15:36: of the,
15:38: you know, of focusing on the mental
15:41: health is making it a project because
15:44: for the longest time we were like like
15:45: oh it's not it's not adding you know
15:47: some of these things are not adding
15:48: features you know some of the stuff is
15:50: like not doing this therefore like it
15:51: just gets dropped on the side and it
15:53: gets addressed and becomes bigger and
15:54: bigger problem one that actually
15:57: affected you know efficiency and slow
16:00: down like lot of features slow down a
16:02: lot of bug fixes created a lot of like
16:03: issues so it was ly affecting the
16:07: development.
16:08: So we need to kind of tackle it as a
16:10: feature itself because that helps with
16:12: overall development process and
16:16: for I think it's like important to
16:18: consider it you know it's just part of
16:21: the project focusing on these things and
16:23: it's part of development making the
16:25: development processes better and making
16:27: the development process more efficient.
16:29: Plus, like I said,
16:32: I recommend like watching the video
16:34: because we kind of go into a lot of
16:35: detail. There's even a lot of features
16:36: that kind of come as a part of this. You
16:38: know, some of it's like fun features. Um
16:40: some other powers is like you know for
16:42: example the social embeds that's also
16:44: like a feature that anybody can use on
16:46: the platform stuff like
16:56: it looks like is uh happened in the
16:58: internet. I think the recording should
17:00: still be going so uh guess we'll wait
17:01: till he's back.
17:04: Uh
17:08: am I back? Hello. Sorry, the lighting is
17:10: really bad. Um,
17:14: oh, hello. Sorry, the Wi-Fi just cut out
17:18: and the headset disconnected completely.
17:20: It's like real bad right now. Everything
17:21: is like very pixely.
17:25: Um,
17:27: okay, I'm back. I can see it again. Um,
17:30: but yeah, like those things are part of
17:33: development as anything else. So now the
17:35: development is not getting halted and us
17:37: focusing on these things that's just
17:39: another part of like you know of the
17:41: development
18:04: Oh jeez.
18:06: Okay, next question is from Coinad. How
18:09: difficult would it be to duplicate
18:10: animated materials like the rainbow
18:12: glint on solid tools since they have
18:14: different fields? Wouldn't that require
18:16: custom shaders? Uh seeing how often Oh,
18:20: separate questions again. Um
18:25: uh this um
18:28: so kind of by nature you can't duplicate
18:32: animated materials because um you can
18:35: duplicate materials if they're you know
18:40: they're the same. They're never going to
18:42: be
18:44: like you know they're never going to be
18:45: like
18:48: unique. But by deriving them, you're
18:50: essentially making them unique, which
18:52: means you can't duplicate them because
18:53: at any point they can be different from
18:56: others, which means you can't merge them
18:57: because it would break them. So it's
19:00: kind of they're like two separate
19:05: like opposing concepts essentially.
19:08: um custom shaders are not really going
19:09: to help you there because um
19:13: if if you're driving the properties to
19:14: be you know diff like if you're driving
19:16: them the system doesn't know like you
19:19: know if they're ever going to be driven
19:22: if they're always going to be driven
19:23: like you know to be exactly the same
19:25: that like you know you can have
19:26: arbitrarily complex logic for you know
19:30: doing that and the system like there's
19:32: not like really automated way to figure
19:34: out all this like complicated code will
19:36: always produce the same results for
19:38: these like materials. So like
19:41: there's not really way to duplicate that
19:43: um because at any point it could produce
19:46: you know different results. The material
19:47: needs to be kept uh distinct.
19:51: And the other question is um seeing how
19:54: often you're getting really long
19:55: questions are considering adding more
19:56: limits questions. Um not sure. It's
20:00: going to be difficult because like some
20:01: questions are quite like longer some
20:03: like some not. Um
20:07: so I don't want like you know like just
20:08: got to hard limit because it kind of
20:10: gets it more difficult to go into more
20:12: details on some things but it more
20:14: depends like you know what why is the
20:17: message long like for some things like
20:19: if it's like focused on like you know
20:20: asking different questions that can help
20:21: but if it's like doing a lot of like
20:25: philosophizing and like you know giving
20:26: like a lot of like story of like things
20:29: like that might not be relevant for the
20:31: question itself. Um I think it's a
20:34: little bit harder. We generally like
20:36: encourage people to keep it like
20:37: sustained as much as they can but uh
20:41: um not considering adding like any like
20:43: fixed limit at this point.
20:47: Okay. Uh
20:49: it's gotten we've gotten we've gotten
20:51: daylight. We can move to this area and
20:53: we could set up another camera over here
20:55: with another view.
20:58: Here we go. Oh, look at the frog.
21:02: pick this Lego pretty world because it
21:04: has a snow theme.
21:09: There we go.
21:12: Okay. So, now that we are done with the
21:14: questions from uh Discord,
21:18: uh we can start going through the
21:20: questions from uh from the Twitch chat.
21:24: Uh we got a few. Um, remember if you've
21:26: got like any questions, uh, put like a
21:28: question mark at the end and, uh, that
21:30: way it kind of pops on our thing.
21:35: Uh, so the first one we got from a
21:39: just jump. Um,
21:44: the first question is from Ace on
21:46: Twitch. They're asking, sh not it. Um,
21:51: I do have a list. I may like pick one
21:53: thing from that.
21:56: So, let me open up my document.
22:00: Should start to have a in the meanwhile.
22:08: >> Hello.
22:11: >> Uh, yeah, sorry, I was I was I was I had
22:14: my mic. Sorry. Um
22:17: Um, do I have a schnop it?
22:21: Let me think for a sec.
22:30: I guess uh
22:33: >> I guess I have a little bit of a
22:34: schnoit. Um
22:38: I've been kind of like
22:41: a little bit like burnt out. Um so like
22:44: if you see me in the world, I'd ask like
22:47: don't come up to me and be like, "Hey
22:49: Syra, did you see this like glitch I
22:50: found? You see this issue I found?" So,
22:52: I'm just going to tell you to report it
22:54: on the GitHub, please, because I'm a I'm
22:56: I'm a little burnt from that. I'll look
22:59: at it when I get to it on the GitHub.
23:02: Actually, I had a different one, but I'm
23:04: actually going to do the same. Like,
23:05: it's kind of like it gets kind of
23:08: difficult because like like when people
23:10: do that, like you can't really
23:13: turn off and then like your brain is
23:15: just like nope. Like I had like the
23:18: issue like where like anything like I
23:19: look at any complex problems or like
23:23: anything like that and my brain just
23:25: goes like no I I I don't know what I
23:28: don't know what programming is anymore.
23:30: It just none of it makes any sense and
23:33: and part of that is like because there's
23:35: just really hard to like have that
23:37: separation like you know between like
23:39: what is like work and what is just kind
23:41: of hanging out and having to just
23:42: constantly worry about problems. I worry
23:44: like about bugs and so on. like kind of
23:47: I guess difficult
23:50: um
23:52: yeah so generally this is actually part
23:54: of like you know the reason like why one
23:56: of the things as you know form of like
23:59: focusing on mental health uh part of
24:02: that is
24:05: um having a document on how to direct
24:07: people to the correct channels and we
24:08: like okay somebody has a bug
24:11: please put on GitHub you know that's the
24:13: proper channel for for that like we
24:15: don't really take reports in DMs or in
24:18: person. Uh
24:37: >> um I guess um Ps will probably come back
24:40: in a second.
24:43: >> Oh, sorry. Wi-Fi died again. Um, but
24:47: like you know if it's like GitHub, like
24:48: if it's a bug, please report on GitHub.
24:50: Like we don't really take reports in
24:52: DMs. We don't take reports like you know
24:54: in person. Um, if it's like you know
24:57: issue with the user, make a moderation
25:00: report. If it's like if you have a
25:01: question for things, um, bring it to
25:04: resonance, you know, bring it to these
25:06: channels because there's also a thing,
25:07: you know, sometimes like we just bunch
25:09: of people and they're like, "Oh, how do
25:11: I do this? How do I do that?" like like
25:12: how do we like you know I've done I've
25:14: done this thing and it's done this thing
25:15: and like you know it's doing this thing
25:16: and you know how how do I like you know
25:18: and it's like and I just came in and I
25:20: just wanted to hang out and like I'm
25:22: like having to like go back into
25:23: thinking about code and figing things
25:25: out and it makes it makes it harder.
25:29: So
25:32: >> is you know just kind of like directing
25:33: people to the right right places to ask
25:36: things.
25:38: >> Yeah. And like I know that some of you
25:40: guys bring it up um in like a friendly
25:42: manner. You're like you're not trying to
25:43: like bring it up as like a GitHub issue,
25:45: but like we deal with it so much it
25:48: still kind of just registers as that. So
25:51: >> yeah.
25:51: >> Yeah.
25:53: >> Like it's just the boundary we need to
25:55: kind of like have
26:00: if like we bring up like something, you
26:01: know, that's a bit different. But like
26:03: when people can like bring up like those
26:05: things, it's uh it's still that same
26:07: kind of same mode of like thinking about
26:09: work and worrying about the bugs and
26:11: worrying about things.
26:18: Oh, looks like the Wi-Fi cut out again.
26:20: He'll be back in a sec.
26:23: I think you can still hear me on the
26:24: recording. Um but I guess he's frozen. I
26:29: guess the the local Wi-Fi is not so
26:31: good.
26:33: Oh, that happened again. Sorry. I might
26:36: like just do like I might just do like
26:38: an hour today because there's not like
26:40: too many questions and the Wi-Fi is
26:42: really bad.
26:44: >> Yeah, I'm okay with doing an hour a day.
26:47: >> Um
26:49: >> thankfully they can still hear me when
26:51: uh when uh that happens.
26:53: >> Yeah. Yeah. Because it's like streaming
26:55: from my laptop, but the connection
26:56: between my headset and laptop is bad.
26:59: which is also asking typons. Um, one I
27:04: would like I don't actually I might have
27:05: done this one already. So sorry if I
27:07: ordered this one, but like the one
27:08: that's most recent is like uh the net
27:12: project because uh one of the things
27:15: that we like did in November is upgrade
27:19: to net 10.
27:22: And what's like super cool about it is
27:24: like you know now that we like we're on
27:25: the modern runtime um I feel like the
27:28: net project is like one of the best
27:31: things to ever come out of Microsoft and
27:33: one of the reasons is also because they
27:35: made open source as a mic and they have
27:37: like a lot of coin contributions and
27:40: every year it gets so many improvements
27:43: uh and all of those improvements are
27:45: performance and now because we like in
27:49: thanks to the spliting we can be using
27:50: the modern runtime time we get to
27:52: benefit from all that work. Uh
27:55: especially by just you know changing a
27:56: number we've gotten like you know
27:58: additional performance boost and we're
28:00: going to get one every year um as the
28:03: runtime improves.
28:06: >> Yeah it's immediately visible on the
28:08: cloud too like when we upgrade like the
28:10: graphs noticeably go down a little bit.
28:12: Yeah, the gravity just like dips a bit
28:15: happened like it happened like going
28:16: from the net 8 to the net 9 happened
28:18: with net 9 to 10 I think happened like
28:21: you know with seven to eight as well
28:22: like it it it's just free performance
28:27: I guess
28:30: >> I have a punk
28:33: >> yeah I was going to say that I like the
28:34: new uh ability to run uh CS files as
28:39: standalone like scripts you don't have
28:41: to have a project. So now I can I can I
28:45: can replace a lot of my batch my batch
28:46: scripting on Linux with net scripts or I
28:49: can prototype projects by just opening a
28:51: file and writing net code in it and it
28:53: just works and I can run it with slash
28:55: thing.cs or whatever and it's it's
28:57: great. It's it's simplified a lot of my
29:00: uh scripting and my prototyping.
29:04: Yes, I I really like that too because
29:07: like I've I've written like command line
29:10: like console apps just to like do some
29:13: quick jobs because it's so easy to for
29:15: me to write in C. But uh you know
29:18: running it less I have to create a
29:20: project to do this kind of thing like
29:21: it's very like very versatile and
29:25: scripting is like one of those things.
29:33: Uh Navy 3001 is asking
29:37: uh when is the updates performance going
29:38: to continue? The list has a lot left. So
29:41: generally as a rule like we don't do
29:44: when questions like complex development
29:46: is complex and we don't like you know
29:48: date on things. Um and also I feel this
29:52: is not like the best way to look about
29:54: it because there's always going to be a
29:55: lot of things on the list. We always you
29:57: know look to like
29:59: build a list like with list a lot of
30:00: things to do. um we're probably not
30:04: going to like, you know, focus any more
30:05: like major performance improvements.
30:08: Um
30:10: for a bit um like we're going to, you
30:13: know, we want to like priorize like some
30:14: other things. Um you know, there's like
30:17: a lot of like things that are like high
30:18: on the list like we want to look at
30:19: stuff, you know, like the IK like uh
30:22: proto collections. We want to look at
30:23: the UI. Um you know, like some other
30:27: things. uh and we already kind of like
30:29: did a did a big chunk that like helped
30:31: massively improve the performance. So we
30:34: kind of you know refocus for a bit uh
30:37: because with any project in there like
30:39: you could just spend the entire time on
30:42: the thing like the with performance
30:44: there's always going to be more things
30:46: to add to the list. There's like always
30:48: going to be things to do. So I don't
30:51: think like you know looking at it the
30:52: way like oh there's a lot on the list is
30:56: you know that's not a good way to go
30:57: about it because there's always going to
30:59: be things on the list like as we kind of
31:01: you know do do like the ones that are
31:03: currently on the list there's going to
31:05: be more that's added uh and a lot of the
31:07: development for a lot of things it's
31:09: kind of like never ending process. The
31:11: main thing is you know is like we had
31:12: like a massive performance booth that
31:14: helped a lot of people. um we want to do
31:16: more in the future but also like we feel
31:18: like we need to focus on some other
31:19: things in the meanwhile both for the
31:21: platform itself um and also
31:25: um you know just for ourselves because
31:27: if you focus on like one thing for like
31:29: really long time it kind of makes it
31:31: difficult so I can't tell you when like
31:34: like I said we generally don't do one
31:36: questions um that's where we're going to
31:39: be for a bit before like we going to
31:40: focus on some other things in the
31:41: meanwhile
31:47: Oh no.
31:49: Uh
31:52: Satan
31:54: De is asking um
31:58: can do this. Why are you upside down?
32:01: We're not. You are.
32:04: Wait, are we upside down?
32:09: The stream going Why? Why? Why aren't
32:12: you, pal? Why aren't you upside down?
32:14: >> I don't know. You were upside down.
32:23: Uh, Tomtown is asking, "Are there any
32:25: tricks for file sharing feature? Like,
32:27: is there something to burn malicious
32:28: files or is that up to users?" Plastic,
32:30: don't click random inter.
32:33: Yeah, that's kind of up to the user. So,
32:34: if somebody like gives you like exe file
32:36: and asks you not to export it and then
32:38: run it like maybe don't like if you
32:42: don't trust them. Um it's like like file
32:44: like any other. So like if you if you
32:47: don't like download and run like a
32:49: random file from the internet like don't
32:50: run a random file then export and run
32:53: random file from the strange. Uh the way
32:56: is the way the system works it requires
32:58: your so like you need to actually export
33:00: it and then like you need to go you know
33:02: to file explorer and actually run the
33:03: file. Um there shouldn't be a way to
33:06: like do this in an automated way. Um,
33:12: but like you know once like once it gets
33:15: into your hands and you're like you know
33:16: like should I run this like exe file
33:18: that I don't know like where it came
33:19: from like you know that's kind of up to
33:20: you and of course like generally the
33:23: recommendation is like you know have up
33:24: to date antivirus on your system like
33:26: you know security tools so that can like
33:29: scan it for things but always use your
33:32: use your like judgment.
33:36: Okay that's actually all the questions
33:38: we have now. So, um, how much time we
33:41: have left? So, we're probably just going
33:42: to do an hour then. Um, which means
33:45: we're going to end in like 20 24
33:48: minutes. So, if you got any more
33:49: questions, feel free to ask.
33:52: Um,
33:55: let's see.
34:00: It's kind of quiet today.
34:03: >> Yeah.
34:03: >> Like a lot of people like traveling or
34:05: something, too. It's going to be
34:08: Christmas one.
34:09: >> Yeah, I'm going to be traveling to
34:11: Seattle in uh 4 days or so. I'm going to
34:14: I'm going to be I'm going to be seeing
34:16: this one and a whole bunch of other
34:17: people in real life.
34:20: >> It's going to be all Christmas.
34:22: >> Maybe we can do a real life residence.
34:24: >> Maybe. Yeah, we could try one. Like I
34:26: have like my
34:28: look around.
34:30: >> Yeah.
34:34: Jalter is asking what ideas do you have
34:37: for the future that will help ease load
34:40: on you the other team members um in
34:43: regards to improving mental health
34:48: and it's like a lot of the stuff is like
34:49: you know like the stuff you're going to
34:50: outlined in the previous stream like
34:52: talking about like you know um hoping
34:56: about like you know going all over
34:58: things we can do um
35:01: so all of them like you know is uh
35:06: we're going to draw a blank. Um what are
35:08: we talking about? See the does the brain
35:10: like doesn't want to
35:13: um like there's like a lot of like
35:15: different things like one of them is you
35:17: know we actually some introduce some of
35:19: them. We have the new issue templates we
35:21: have like you know the friction point
35:22: observation positive observations that
35:24: kind of helps like um but that's not
35:27: like easing the load. I would say I
35:29: would say like one of the things that
35:30: eases the load specifically is molecule
35:33: uh like you know sort of like our update
35:35: system because uh when it comes you know
35:37: especially to having multiple developers
35:39: uh and then make code contributions uh
35:41: there should ideally be tested and
35:44: having a system like where each
35:46: developer can just you know push their
35:47: changes and then like you know create a
35:50: like pre-release like having like as
35:52: many pre-release channels as we want uh
35:55: very easily
35:58: Um
35:59: it's uh
36:03: like it's going to make things much
36:04: easier because we can essentially have
36:06: like you know the like any on the theme
36:08: independently run a pre-release got a
36:10: bunch of feedback got a bunch of like
36:12: back fixes and then we look at merging
36:14: the feature we already know okay like it
36:16: has all these issues are resolved
36:17: otherwise would it like happen on main
36:21: um so I think that will help quite a bit
36:23: um spreading some of the things having
36:25: like more things documented and written
36:27: down I It helps because you know we have
36:29: like our processes documented
36:31: um you know our like philosophy or like
36:34: you know how we can approach things that
36:35: helps inform like any team members like
36:38: you know how things should be written
36:39: and reduce like you know some friction
36:41: some of the back and for which is again
36:43: like you know why these things are
36:44: important part of the development it's
36:46: not just you know all just
36:49: so I think those in part like will help
36:51: quite a bit um
36:57: Um I was kind of thinking if there's
36:58: like any more that like specifically
37:00: like oh the one that was like definitely
37:03: help um hope like well hopefully is um
37:10: one thing that will help is like open
37:12: sourcing parts of it part of the engine
37:15: like gradual open sourcing because that
37:17: way community can contribute you know
37:18: bug fixes and improvement to certain
37:20: things without like you know necessarily
37:23: breaking the core of the thing. So I
37:25: think that one will also help quite a
37:26: bit to give community more control and
37:28: allow for you know kind of more spread
37:30: of the work.
37:33: So yeah those things I think will
37:35: particularly help. Uh I do recommend
37:37: like watching the videos like that on
37:40: the YouTube channel because we can go
37:41: into more details on on these.
37:46: The next question is from uh Ace on
37:50: Twitch is asking, "What do you guys guys
37:53: wish for for this Christmas?" Um,
37:58: so I have like this issue like where
37:59: like I don't know like what to wish for
38:01: Christmas because like the things I
38:03: really want are like generally too
38:05: expensive to be Christmas gifts. Um,
38:10: I usually like I like like gadget like
38:12: electronic things or so on like like one
38:14: of the things I kind of like thinking
38:15: about is you know getting a Raspberry Pi
38:17: but like I don't want to ask anybody for
38:18: Raspberry Pi because that's more
38:19: expensive thing um because I want to
38:22: kind like you know mess with it like you
38:24: know with because J4 like made it work
38:28: on an arm and I'm like um
38:31: I want to kind of mess with it and see
38:33: like you know have some fun with it as
38:34: well and I kind of wanted one for a
38:36: while But um I don't know like I
38:39: actually got like a small like gadget
38:40: thing like for cons um like there's like
38:44: this like like round display thing that
38:46: some like people use as a badge at very
38:48: cons because you can load like images
38:49: and videos on it. So actually I've
38:52: gotten that one. Um and was like
38:54: relatively cheap.
38:58: What about you?
39:00: Um
39:02: I
39:05: I mean my own wish is of course I just
39:07: want to
39:09: I want to enjoy the rest of the year and
39:12: relax and you know be with be with
39:15: friends um who I consider to be my
39:18: family and but moreover I hope that
39:21: everyone else uh can do the same and
39:27: for especially for people like you
39:29: Especially
39:31: for people like uh in um
39:36: especially for people in like the US and
39:38: stuff. Um like even though the the world
39:41: and stuff kind of seems evil um I want
39:45: the end of the year to be a respit for
39:48: everyone to remember that there is still
39:50: uh joy to be had uh in the world with
39:53: you and your friends and family. So,
39:57: I hope that uh all of you go into
40:00: Christmas and have a wonderful
40:04: um
40:05: a wonderful holiday and a happy new
40:08: year.
40:10: Yeah,
40:12: it's very very pretty. Like I said, it's
40:16: kind of like what a Christmas like you
40:17: know like become real is like it's um
40:20: it's more about like spending time with
40:22: people and you know like having fun and
40:24: so on like then
40:26: you know the gift part and such.
40:30: >> Yeah.
40:30: >> You got like good food to like hang out
40:32: like watch some things together.
40:36: It's nice time.
40:39: Jack says, "I get I Syra gets ear
40:41: nibbles for Christmas." Thank you, Jack.
40:43: Well, I can munch.
40:50: Next question. Uh, just
40:55: spin uh from Satan up. Is there a reason
40:58: why you prefer blue sky for getting
41:00: showcases from? I chose Blue Sky is
41:02: because of your showcases. Um it was
41:05: pretty much like the major platform uh
41:09: social like platform. Um there's also
41:11: like Masteron.
41:13: Um then we like start like showing
41:16: things from there too. Uh one thing I
41:18: can say like we will not be doing
41:21: showcases from Twitter because we don't
41:23: want to like promote the platform. Um
41:27: and Blue Sky is pretty much like the
41:28: know the one like where a lot of people
41:30: move to. Um,
41:33: so we will uh we'll probably do that one
41:36: the most like this for like very civil
41:37: version activity. I know there's like
41:39: some of the master instances too, but I
41:41: don't watch that one too closely myself.
41:45: But yeah, uh if there's like any others
41:47: like you want to like showcase from we
41:48: might like do for example some from
41:49: Reddit maybe. Um we can expand it as
41:53: time goes.
42:01: S's eating potatoes.
42:06: >> Mine is asking are there any timelines
42:08: on a network requ.
42:11: Um I'm not actually sure if I understand
42:14: the question because like uh like when
42:17: we generally don't do timelines like we
42:19: don't give out timelines because like
42:20: it's hard to predict like development
42:22: especially like complexities but also
42:24: like I don't actually know what I mean
42:25: about network for data model that's
42:28: already like a thing that's like built
42:31: in into like that's pretty much what is
42:34: like a network protocol data model and
42:36: that's how everything is built.
42:39: So I might need to like clarify the
42:40: question a little bit.
42:45: Um check in the box author
42:49: is asking uh since you mentioned
42:51: molecule in what ways will molecule in
42:52: the future be accessible to creators and
42:54: it'll be cool to have built in
42:56: versioning system for worlds contender
42:57: right now every has their own standard
42:59: for versioning and there's little
43:00: standardization.
43:02: So, molecule like is actually meant to
43:05: be uh I recommend like reading the
43:06: GitHub issue for it because it actually
43:08: goes over a lot of the things. Um
43:12: there's um
43:16: like um how do I put it?
43:22: There's there's actually like like a lot
43:24: of like shared functionality, right?
43:26: Like you know like like making new
43:27: versions and updating and so on. So I
43:29: want to build like a a sharable system
43:32: that can be used for the builds for
43:34: itself but also can be used for items or
43:35: it can be used for protolex nodes. You
43:37: know we can make libraries and other
43:38: things and have like all the shared
43:41: logic behind by the same system and then
43:44: like you know differentiate depending on
43:45: like what it is. Um
43:49: so um
43:52: a lot of it leas it will be like shared.
43:54: We'll probably only have like it usable
43:56: by us first because we like to like
43:58: build more um build more UI and you know
44:04: like interactions on top of it but like
44:06: it's going to be built around the same
44:07: core and the goal is pretty much you
44:08: know like once we have stuff like
44:09: workshop and you can publish things it
44:12: will allow any like user on the platform
44:15: to like use it as well make their own
44:17: channels like for their own creations
44:19: and have the versioning for the
44:21: versioning like for example version
44:22: numbers We'll probably like um encourage
44:26: like or like make it like easy to use
44:28: like um what's it called? Uh what's the
44:32: term? Semantic versioning
44:35: like where you get like you know major
44:36: minor like depending on breaking changes
44:38: but like ultimately it's going to be up
44:40: to like each creator how they like
44:41: because it's just numbers for the
44:43: system. So it's going to be up to each
44:44: creator how they like actually version
44:46: their stuff. Uh
44:49: so um
44:54: so yeah like um there should be
44:57: commercial possible with it but there
44:59: still like might be like differences how
45:00: people like use things.
45:05: Okay, so that's all of our questions
45:07: again. Um, still got like 15 minutes.
45:10: So, if you want to ask any more
45:11: questions, uh, make sure put question
45:13: mark, you know, the thing that pops on
45:15: our chat. Um, it shows up. Um,
45:22: and we can we can like look at it. It's
45:24: going to get dark again. Probably going
45:26: to be ending in 15 minutes because it's
45:28: very slow today. And it turned like the
45:32: Wi-Fi has been pretty bad.
45:38: I could like had like a better headset,
45:40: you know, because I can't do the photo
45:41: or do like the embed for social media.
45:46: Oh, we got a question from Satan dub.
45:52: >> Uh, Satan Dub is asking, "How does cut
45:55: meow in check?" Uh, the meow meow.
46:00: It's spelled differently though.
46:05: Let me write it down.
46:14: It's spelled like
46:17: spelled like this
46:19: was meow.
46:22: Meow.
46:25: >> Meow.
46:28: >> Meow.
46:34: >> That's not
46:35: >> me.
46:38: Sorry.
46:39: >> That's not too different from English.
46:43: Some Some of the animal sounds do get
46:44: like a bit different.
46:50: Next question we got uh from check the
46:52: spotter. Um what's your favorite on this
46:56: module
46:58: H I don't know like favorite one because
47:00: like a lot of them like they're meant to
47:02: kind of work together. I mean I would
47:04: say it's maybe the simp it's I don't
47:06: know it's hard because like there like a
47:08: lot of different looking effects and
47:09: often times like they combine well
47:10: together. I like the simplex like one
47:13: like the force because that like adds a
47:15: lot of like visual complexities or
47:17: particles but there's also like you know
47:19: the one that like makes the force that
47:20: brings them back together but you can
47:22: also use them together so it's um I
47:24: don't know it's it's difficult to pick
47:26: favorites there kind of generally don't
47:28: like picking favorites
47:32: there you go then
47:38: this module.
47:40: Hm.
47:43: I'd have to say my favorite module's got
47:45: to be like
47:47: the like um
47:50: I don't know if I have any any one
47:51: favorite, but I do like the radial
47:53: forceectors and I do like the size over
47:56: lifetimes because little do people know
47:59: that if you use multiple size over
48:01: lifetimes and you give them opposing
48:04: start and end sizes, you can make a
48:05: particle start small, get bigger, and
48:08: then since those modules are
48:10: multiplicative, it will get smaller
48:12: again and then disappear. So, you can
48:14: make start and end particles that get
48:16: bigger and then smaller over the course
48:18: of their lifetime.
48:21: >> I have a fun thing for you. One of the
48:23: small things I've already implemented as
48:25: my like fun creative things is like
48:27: adding a module that lets you contour
48:29: the size by texture.
48:33: >> Just make it do whatever over the course
48:34: of it time.
48:36: >> Yes. Yes. Yes. Yes. a gradient or
48:39: something.
48:41: >> And it can actually like it it is also
48:43: it like RGB to like some you know each
48:45: like values. So like if you make them
48:48: you could put like three different
48:49: gradients for example in each one and
48:51: have it like change the size.
48:56: >> That's insane.
49:06: >> Next questions. uh from Fertex.
49:10: Uh they're asking
49:15: uh what are your thoughts on
49:16: compatibility standalone on Steam frame?
49:20: I mean we would love to do it. Uh we
49:23: currently def
49:25: well please.
49:29: Um we do have like interesting
49:31: architecture because um with uh with
49:35: split pinning
49:37: um it's actually you know we're running
49:40: two processes and we have the native net
49:43: process which runs major things that are
49:45: happening and then the renderer which is
49:46: the unit and on Linux it already the way
49:49: the works is thanks to cyers work it
49:52: actually like runs the main process as a
49:57: native Linux.net net application. So
49:59: like this native like you know like
50:02: proton layer uh with only the render
50:05: actually running under proton
50:08: and what's cool about is like you know
50:10: this kind of gives more performance uh
50:11: because like you know it doesn't need
50:13: social it's getting dark. Let's move
50:15: over there.
50:17: Where did my
50:19: Oh no my the anchor but it went away.
50:23: >> Was it in the in the frog? It's in the
50:25: frog.
50:26: >> Oh no I clicked the frog.
50:29: Oh no.
50:30: >> No. I need to get rid of it.
50:32: >> We have nice slides.
50:34: >> Yeah, the uh the the anchor is inside of
50:36: the frog it looks like.
50:38: >> Oh, hold on. Let me I can just switch to
50:40: it.
50:42: Let me close that dialogue.
50:44: >> There we go. There we go. Now we got you
50:46: know nice light.
50:50: So continuing on this uh because of our
50:53: architecture
50:54: um
50:56: what we could do on steam frame because
50:59: it's Linux R so like by default it's
51:02: probably going to you know if you want
51:03: to run things natively it's going to
51:04: emulate you know x64 on ARM what we
51:08: could actually do is run because net 10
51:11: which we using it supports ARM and
51:14: because thanks to JForce's work we also
51:17: have the native you know libraries that
51:18: we use uh working on ARM. So we can
51:21: actually run headless on ARM, but the
51:23: client uses the same libraries. So we
51:26: could run majority of the engine
51:29: natively on the steam frame and then
51:30: only run the render within, you know,
51:32: the proton and like the I think they
51:34: call it X like the like ARM like X64
51:38: like emulation player. Um
51:40: >> MX.
51:43: So we would love to like experiment with
51:45: it and like you know see how much we can
51:46: get out of it and like what kind of
51:47: experience we can offer. But uh we don't
51:51: have hardware to do it. So I would track
51:55: working. So
51:59: it also be good just to kind of you know
52:00: get make sure it actually works out of
52:02: the box because I think the controllers
52:03: are probably going to work and we need
52:05: to add like nodes for the controllers
52:07: because I feel like a lot of people in
52:09: our community like they're going to get
52:10: one and they will want to experiment
52:13: um you know with like making control
52:15: schemes and stuff. And we have the the
52:18: visual scripting pressure. We expose all
52:21: the controllers um that we support and
52:23: we would love to support a steam frame
52:25: on like because there has like bunch of
52:26: like controls for people.
52:30: So yes,
52:33: I'm very very curious how like it's how
52:35: is it like going to run with it.
52:39: Yes.
52:41: Uh let's see.
52:46: The bone master is asking uh have you
52:49: found any promising renderers so far? Uh
52:52: we're not looking for them yet. We're
52:53: still on the phase one which is
52:55: compiling requirements. Uh once the
52:58: phase is done then the phase two will
53:00: begin which is actually looking at our
53:02: enders. There's like some that like
53:05: these could be potential candidates but
53:07: like until we actually have the list of
53:09: requirements for them we can't really
53:12: you know be like is this promising? is a
53:13: little promising because we don't know
53:15: for sure do they have all the things we
53:17: need because we don't know what are all
53:19: the things we need yet which is part of
53:21: phase one. So there's like a few like
53:24: like they're potential candidates but we
53:26: need to finish the list first um before
53:29: we move to actually looking for them.
53:39: Uh S was asking have you tried Lenovo's
53:41: comm system? Uh I think Lenovos I
53:44: apologize if not uh I I'm not sure what
53:48: it is.
53:49: >> Lo
53:51: >> Lenovo Lenovos Lenovos
53:54: Lenov
53:56: Lexivo you mean? Hello
54:00: who are you talking about? Who is this?
54:02: I had like five different things in my
54:04: head. Yeah, like I don't know.
54:10: Check the box asking any ideas for
54:12: photos and models do you really want to
54:14: add in the future? Um, however, what
54:16: that I'm adding right now is sub
54:18: emitters. It's actually one of the fun
54:20: things I've been kind of like like like
54:23: um that I really wanted to do is like do
54:25: subters. So, you're going to see subters
54:28: soon. I have a already have like a chunk
54:30: of it like working. So, going to get
54:33: subters.
54:34: >> Yeah.
54:36: Yeah, we'll be able to sub him in a
54:37: little more cooler.
54:48: Uh, next questions from um, Cajier.
54:52: They're asking, where do I put this? Uh,
54:55: what are your thoughts on Vers's
54:56: inventory system? More specifically,
54:58: would their company systematically fill
54:59: gaps between your platforms, more
55:01: interesting features and the past year
55:02: from improve interactivity, contact
55:03: points, photo spawning and now inventory
55:06: system. From your perspective, it would
55:07: seem to you actually competed regardless
55:09: of what do you consider them? What are
55:11: your plans and how to differentiate
55:12: their actual uses going forward? So from
55:16: what I understand, their inventory
55:17: system is not really anything similar to
55:19: like Resonate's inventory system. Like
55:21: it's more like a store for things
55:24: because with Resonite like the inventory
55:26: you can literally save anything in the
55:28: world like that you can grab and have
55:30: permission. I can save like arbitrary
55:32: objects, items, you know, avatars,
55:34: everything. And like even though like
55:36: it's named the same, like their system
55:38: doesn't really seem to do the same thing
55:40: as ours does. So I I think it's a bit of
55:43: like you know like a false premise like
55:45: to start with. Like I don't
55:48: like I don't think they're like
55:50: comparable things. Um
55:53: and you can't like you know just like
55:54: spawn like arbitrary props um the way
55:58: like you can do on here. So I think like
55:59: even that itself like it's still you
56:01: know different on the platform. But one
56:05: of the major things of like you know
56:06: Resonite is like the level of
56:08: interactivity you know like you can
56:09: spawn anything anywhere. You can save
56:12: anything anywhere. You can edit things.
56:14: You can like you know collaborate in
56:15: real time. And I don't think that's like
56:17: a thing that would be very easy to
56:19: replicate for other platforms. So some
56:22: things like on the surface you know they
56:23: kind of get like replicated but like
56:26: like it's missing the same depth of it
56:30: and the same you know like same level of
56:32: like interactivity that you can have on
56:34: there like you know on here. Um there's
56:37: like lot of things too like for example
56:39: you know like one of the things you can
56:40: spawn is like you know just we can also
56:41: import content in real time. We can
56:44: bring in pictures, you know, we can
56:45: bring in videos. There's there's a lot
56:48: of uh stuff. But all of our focus in
56:50: general is like, you know, people's
56:52: creativity, the sandbox capabilities,
56:53: the fact that you can edit anything in
56:56: real time. Um, you know, without having
56:59: to like jump out, you can do it in VR
57:01: and you can do it with like other
57:02: people. And that's one of the core
57:04: things, you know, that's part of
57:06: Resonate. And because of how resite
57:07: designed for that, it gives even a lot
57:10: of the other features like for example
57:11: the inventory, it gives it a lot of the
57:13: depth that the other, you know,
57:15: platforms underly able to like
57:17: replicate. So I think there's like a lot
57:20: of like things that are like really
57:22: different about the platform. Um once
57:25: you kind of like you know look beyond
57:26: like the surface and there's going to be
57:29: like a lot of overlap too because you
57:31: know people like if you have like you
57:32: know basic kind of social platform
57:34: there's um going to be a lot of things
57:36: are going to be very similar and a lot
57:38: of like similar kind of like
57:39: functionality because it's just going to
57:41: make sense in ways you know like same
57:43: way if you look at like for example you
57:46: know messaging tools you're going to
57:49: find you know that you have like a
57:50: textbook message you're going to be able
57:52: to send emojis stickers stuff like that
57:54: it's you know similar between a lot of
57:57: messaging applications like you know
57:58: discord, telegram like you know even
58:00: social networks um but there's like lot
58:05: of other things you can do that like are
58:07: not possible on the other place.
58:13: Uh
58:17: but yeah, uh one thing I was actually
58:18: going to still say to that one is like
58:20: uh there's also like a lot of like you
58:21: know creative functionalities we're
58:22: planning in the future as well. You know
58:24: we have like the visual in-game
58:26: scripting system but you also be able to
58:27: do more with it like you know uh doing
58:30: stuff like you know producing music
58:32: textures like you know like turning or
58:34: something like virtual studio. Um we
58:36: want plan to do stuff like you know
58:38: doing in game like vertex editing. Um
58:42: but even right now like there's a lot of
58:44: functionality that is possible on here
58:45: that like you can't really do like
58:47: elsewhere
58:49: and uh some of it like you know very
58:51: kind of high level like being able to
58:52: import content like you know bring 3D
58:54: models bring um you know images, videos,
58:58: music, gian splat um PDFs you know like
59:02: you can just very easily bring content
59:04: to share with others and that kind of
59:06: stems from the you know the way
59:08: personite is made like like the high
59:11: level of interactivity and being able to
59:13: sort of like modify anything anywhere.
59:23: Oh, we're getting all the questions now.
59:25: Um,
59:30: >> yeah, like I don't know what to do
59:31: because like we're supposed to end the
59:33: stream now and now people just kind of
59:35: like, you know,
59:38: questions. We said we were going to run
59:40: for an hour. So,
59:43: >> I can do a few more. Maybe like a little
59:45: bit over. But, uh
59:48: >> yeah, we're probably going to cut it
59:49: after these ones though, guys.
59:52: >> Yeah, we might need to cut it after
59:53: these.
59:57: I mean, these are kind of long ones, so
59:59: I don't We might just
01:00:04: >> Yeah, I would say Yeah, if we're going
01:00:05: to if we're going to end it, I would say
01:00:07: just like if you guys have any
01:00:08: questions, because that one's quick. But
01:00:11: yeah, um
01:00:15: >> we're we're now technically over time.
01:00:17: Um we'll be discussing another unique
01:00:20: nodes for different control type. We
01:00:21: consider a more generic named input
01:00:23: node. Avoid that node proliferation. Um
01:00:26: probably not because like well there
01:00:28: might be like some more generic stuff
01:00:29: like which sort of puts abstraction
01:00:31: layer but abstraction layer can also
01:00:33: hide some of the specifics. you actually
01:00:34: have there is the standard controller
01:00:37: node but the problem you know with
01:00:39: standardizing stuff like that is like
01:00:41: you essentially just provide the least
01:00:43: common denominator of things so you
01:00:45: actually miss out all of the specific
01:00:46: author controllers. So if you don't care
01:00:49: about those, use the standard node. It's
01:00:51: going to work across pretty much every
01:00:52: single controller node. But if you want
01:00:55: to like you know custom tailor um you
01:00:58: know integration for a particular node
01:01:01: then um if you want to like you know
01:01:04: custom tailor it then you want to like
01:01:07: use the node that's you know very
01:01:08: specific to particular um to particular
01:01:12: you know device.
01:01:15: So, uh, the problem is that, um, we said
01:01:18: we're going to like, you know, finish
01:01:19: this at an at an hour. So, uh, we're
01:01:23: going to close it. So, thank you
01:01:25: everyone for joining the stream. Thank
01:01:26: you like, you know, for supporting this
01:01:28: platform and thanks for like joining me
01:01:30: here, too. Um,
01:01:33: >> maybe next week we might do uh,
01:01:36: resonance live resonance. It's not a
01:01:39: hard hard one like like hard like um yes
01:01:42: that will do it but like we'll try to
01:01:44: see if we can make it happen. So um
01:01:48: don't miss that one um if it happens
01:01:52: and thanks everyone you know for for
01:01:55: joining us and supporting this plot
01:01:57: making cool content.
01:01:59: >> Yeah. Um
01:02:01: yeah.
01:02:02: So going to see if there's anybody to
01:02:05: raid.
01:02:08: Let's see.
01:02:11: Also everyone have had holidays
01:02:16: and also please next time don't don't
01:02:18: send all the questions at the end.
01:02:21: >> Yeah.
01:02:31: >> Let's see.
01:02:33: Oh, there's also like a way to ask
01:02:34: questions in advance too if we can't
01:02:36: like make.
01:02:46: Let's see. Somebody stream.
01:02:50: No, it's just us, unfortunately. Okay,
01:02:52: so we're going to end the stream here.
01:02:54: So, thank you very much for joining and
01:02:56: we'll see you next week maybe
01:02:59: >> and have a happy holidays. Have a look
01:03:01: at Christmas
01:03:03: >> and a happy new year.