1 00:00:00,000 --> 00:00:05,000 Welcome to prime time, the weekly AMA for me and Neos. 2 00:00:05,000 --> 00:00:08,000 If you have questions, please drop them in the office hours text chat. 3 00:00:08,000 --> 00:00:10,000 That is a few channels above, there is a thread for your questions. 4 00:00:10,000 --> 00:00:13,000 Any questions about Neos will be answered in the order that they appear. 5 00:00:13,000 --> 00:00:17,000 Whilst there are no questions in that thread, we will sit in unimaginable silence. 6 00:00:17,000 --> 00:00:19,000 I hope that you've had a fantastic week. 7 00:00:19,000 --> 00:00:22,000 If you have questions, drop them in the thread and I'll get to them as soon as I can. 8 00:00:22,000 --> 00:00:23,000 Thank you. 9 00:00:23,000 --> 00:00:25,000 Okay, so we have our first question from Lex. 10 00:00:25,000 --> 00:00:29,000 Lex says, is there an in-depth explanation on how the asset variation system works? 11 00:00:29,000 --> 00:00:31,000 There is not. 12 00:00:31,000 --> 00:00:36,000 I can give you a sort of brief overview now, which will help for those people who are just like, what is that? 13 00:00:36,000 --> 00:00:41,000 I'm sure that Lex yourself, you know a little bit about what it does when doing it for the benefit of those who are listening. 14 00:00:41,000 --> 00:00:49,000 So the asset variance system is a system where when you give Neos an asset, an asset being a texture, a model, a sound, 15 00:00:49,000 --> 00:00:55,000 anything that like isn't actually an object, but is like parts of the object and not logics or components, 16 00:00:55,000 --> 00:01:00,000 just like the visual aspects, the models, the textures, the sounds, the videos, etc. 17 00:01:00,000 --> 00:01:06,000 When you give Neos one of those, it will run it through what's called the asset variation system, 18 00:01:06,000 --> 00:01:09,000 or variant system, which is what we usually call it, not variation, 19 00:01:09,000 --> 00:01:16,000 which is basically designed to make it cheaper for us as Neos to store those assets on the Neos cloud, 20 00:01:16,000 --> 00:01:23,000 but also better for you guys to download and witness those assets with inside Neos or inside your sessions. 21 00:01:23,000 --> 00:01:30,000 The notable example of this, which you'll probably see and have seen and wonder what the hell is going on, 22 00:01:30,000 --> 00:01:37,000 is things like normal maps. So in Neos, when you drag a normal map into the normal map square of a material, 23 00:01:37,000 --> 00:01:43,000 you'll notice that it turns from the sort of standard normal map, the blue, into a normal map, which is red. 24 00:01:43,000 --> 00:01:48,000 Turns out that storing a normal map in that red format, technically speaking, there's technicalities here, 25 00:01:48,000 --> 00:01:52,000 but I'm just going to say the colors red and blue a bunch until we move on to the next question. 26 00:01:52,000 --> 00:01:58,000 Technically speaking, storing it in the red format is more optimal and has less storage requirements, 27 00:01:58,000 --> 00:02:03,000 bandwidth requirements, etc. to get to you than in the blue format. 28 00:02:03,000 --> 00:02:09,000 So we're doing that on behalf of you and it honestly is generally better. 29 00:02:09,000 --> 00:02:14,000 There are a lot of cases where I've seen where users are just like deliberately asking the asset 30 00:02:14,000 --> 00:02:19,000 the asset variant system to just not run and it bothers me. 31 00:02:19,000 --> 00:02:24,000 I do have a video about that one on the channel that talks more about the asset system that runs in a world 32 00:02:24,000 --> 00:02:27,000 rather than the one that runs on a cloud, but it's kind of the same thing. 33 00:02:27,000 --> 00:02:32,000 It's like let Neos do what it thinks is best, unless it actually isn't best, right? 34 00:02:32,000 --> 00:02:37,000 You have no reason to overrule the asset variant system or the asset management system within a world 35 00:02:37,000 --> 00:02:42,000 unless you know exactly that you need to do that and have a good reason to do it. 36 00:02:42,000 --> 00:02:45,000 So I'll link that video in the thread. 37 00:02:45,000 --> 00:02:49,000 But there's no like full definition there, hence why I had to gloss over some details. 38 00:02:49,000 --> 00:02:51,000 Some of them I don't really know myself either. 39 00:02:51,000 --> 00:02:56,000 I do know, as I was reading in a conversation later, earlier, I don't know why I said later. 40 00:02:56,000 --> 00:03:01,000 Yes, I was reading in the future that I travel back in time to this office hours to tell you about it. 41 00:03:01,000 --> 00:03:06,000 I was reading earlier in a conversation somewhere else that Fruks is actually very proud of the asset 42 00:03:06,000 --> 00:03:11,000 variant system, so that's good to hear. I'm happy that he's proud of his work. 43 00:03:11,000 --> 00:03:15,000 I do hope that we'll get some documentation on that when we can. 44 00:03:15,000 --> 00:03:18,000 And I understand that that response probably wasn't that good. 45 00:03:18,000 --> 00:03:21,000 Hey, it should have helped those out that don't know anything about it. 46 00:03:21,000 --> 00:03:24,000 Dio says, what's the featured cheese for today? 47 00:03:24,000 --> 00:03:26,000 I don't answer cheese questions. There are no exceptions to that. 48 00:03:26,000 --> 00:03:29,000 I almost did, but I'm like, nope, no cheese questions. 49 00:03:29,000 --> 00:03:31,000 So moving on. 50 00:03:31,000 --> 00:03:37,000 So Zach says, all optimization be prioritized when things pick up again. 51 00:03:37,000 --> 00:03:42,000 Losing words here. There's only like a defined amount of English words one can say in a day. 52 00:03:42,000 --> 00:03:48,000 And when I run out of those, usually five minutes after I wake up, I just start like speaking absolute gobbledygook. 53 00:03:48,000 --> 00:03:54,000 I can't really say what is going to be prioritized when things pick up because priorities change. 54 00:03:54,000 --> 00:03:58,000 And in a lot of cases, priorities are influenced by multiple things, right? 55 00:03:58,000 --> 00:04:05,000 So the way that the roadmap was back when we were doing optimization, sorry, when we were doing stuff before this mess, 56 00:04:05,000 --> 00:04:09,000 we had different priorities because we had two additional team members that we were listening to, 57 00:04:09,000 --> 00:04:13,000 and their priorities were factored into it, et cetera. 58 00:04:13,000 --> 00:04:20,000 Our priorities before this mess were to rework the settings UI simply because we need to. 59 00:04:20,000 --> 00:04:23,000 There's just too many settings that we need to set. 60 00:04:23,000 --> 00:04:28,000 So we needed a new settings UI, and then immediately following that, we're going to look into user blocking. 61 00:04:28,000 --> 00:04:31,000 None of those happened, of course. See the announcements channel for more information. 62 00:04:31,000 --> 00:04:33,000 I'm not going to talk about that right now. 63 00:04:33,000 --> 00:04:37,000 We will endeavor to optimize Neos wherever we can. 64 00:04:37,000 --> 00:04:40,000 Sometimes optimizations appear when you least expect it. 65 00:04:40,000 --> 00:04:46,000 The other day I was editing the volume plane slicer, which is for things like MRIs and stuff, 66 00:04:46,000 --> 00:04:50,000 and I rewrote parts of it to be half the code. 67 00:04:50,000 --> 00:04:55,000 Now, that isn't optimized in terms of performance, but that is optimized in terms of my brain when I read that file. 68 00:04:55,000 --> 00:04:58,000 So, you know, multiple types of optimization. 69 00:04:58,000 --> 00:05:05,000 You can be, I guess, more specific about what optimizations you're looking forward to. I can talk about those for a little bit. 70 00:05:05,000 --> 00:05:10,000 We have a question here from Mr. Very to the point username. Hello, Mr. 71 00:05:10,000 --> 00:05:14,000 Is there any plans on reworking the current main menu, escape menu for a better user interface and user experience? 72 00:05:14,000 --> 00:05:19,000 Every single part of the Neos UI is due for rework. 73 00:05:19,000 --> 00:05:22,000 Even the parts that we have already reworked are due for rework. 74 00:05:22,000 --> 00:05:26,000 None of the UI is like final, and I don't think it ever will be. 75 00:05:26,000 --> 00:05:32,000 But in this particular case, none of the UI has entered even its non-beta stage. 76 00:05:32,000 --> 00:05:35,000 You've got to remember that Neos is early access and in beta. 77 00:05:35,000 --> 00:05:37,000 So, yeah, everything will be reworked. 78 00:05:37,000 --> 00:05:42,000 If you're looking for things like that, head over to our UI remap and just control F the word dark, 79 00:05:42,000 --> 00:05:46,000 and you'll just see it everywhere, because the common question we get is like, can we get dark mode here? 80 00:05:46,000 --> 00:05:51,000 And it's like, yes, you could have dark mode on literally everything once we rework the UI. 81 00:05:51,000 --> 00:05:55,000 And it's all on that UI roadmap, and you can find information about it, such as our plans, our ideas, 82 00:05:55,000 --> 00:06:00,000 what we're thinking about on that UI roadmap more than I can speak to right here. 83 00:06:00,000 --> 00:06:03,000 Projects one, I believe, is the major roadmap property. 84 00:06:03,000 --> 00:06:06,000 I believe they want projects two, which is the UI roadmap. 85 00:06:06,000 --> 00:06:09,000 Yeah, projects two is the UI roadmap. 86 00:06:09,000 --> 00:06:11,000 No worries. Projects one is great too. 87 00:06:11,000 --> 00:06:15,000 In fact, if you just go to like Neos public projects and you just read all of them, that'll be great. 88 00:06:15,000 --> 00:06:18,000 When we get things back up and running, I will be working. 89 00:06:18,000 --> 00:06:23,000 For those who don't know, I am a traditionally trained engineer and product manager now, so hooray. 90 00:06:23,000 --> 00:06:27,000 I've got about five years in each of those disciplines. That's great. 91 00:06:27,000 --> 00:06:32,000 So I'll be reworking that roadmap to be less boards. 92 00:06:32,000 --> 00:06:34,000 I think the multiple board thing is kind of bad. 93 00:06:34,000 --> 00:06:39,000 You also see on GitHub now that our project boards are listed under projects in brackets classic, 94 00:06:39,000 --> 00:06:44,000 and that's because GitHub released a new projects format that allows us to do a lot more things, 95 00:06:44,000 --> 00:06:48,000 including views, tagging, custom fields, all sorts of cool stuff. 96 00:06:48,000 --> 00:06:52,000 And that will let us collapse all those down into one board once we get going again. 97 00:06:52,000 --> 00:06:54,000 There we go. That's all the questions. 98 00:06:54,000 --> 00:06:56,000 I hope that you are all having a fantastic day. 99 00:06:56,000 --> 00:07:00,000 I'm going to go ahead and sit here in unimaginable science until we get more questions. 100 00:07:00,000 --> 00:07:02,000 Okay. We do have a question here. Fantastic. 101 00:07:02,000 --> 00:07:08,000 So we have a repeat. So Ramper says, let me repeat one thing I mentioned during the moderation office. 102 00:07:08,000 --> 00:07:09,000 I knew about it too. 103 00:07:09,000 --> 00:07:12,000 I think there should be enough. 104 00:07:12,000 --> 00:07:19,000 See, just running out of English. 105 00:07:19,000 --> 00:07:23,000 I'll get a handle on it, I promise. 106 00:07:23,000 --> 00:07:30,000 I think there should be an official explanation on the FAQ why Quest Standalone is not yet supported. 107 00:07:30,000 --> 00:07:35,000 Usually when I explain why people snap back with something like, what do you mean? 108 00:07:35,000 --> 00:07:40,000 VRC already did it, and Bonelab is a prime example of running on the Quest Philly. 109 00:07:40,000 --> 00:07:46,000 Those sorts of people, they're asking the wrong question, I think. 110 00:07:46,000 --> 00:07:49,000 It's a very stereotypical thing. 111 00:07:49,000 --> 00:07:53,000 It happens a lot in video games or other products or basically just everything. 112 00:07:53,000 --> 00:07:55,000 You can even take it back to construction. 113 00:07:55,000 --> 00:08:00,000 You drive past on your way to work a bridge that's being built every day for five years, 114 00:08:00,000 --> 00:08:03,000 and you go, why haven't they finished building the bridge yet? 115 00:08:03,000 --> 00:08:06,000 And they just have no concept or knowledge about why that is the case. 116 00:08:06,000 --> 00:08:12,000 So there is certainly something that we can do there to make that clearer in that case. 117 00:08:12,000 --> 00:08:17,000 But for the people who retort with VRC already did it, there's less that we can do 118 00:08:17,000 --> 00:08:20,000 because they're less reasonable. 119 00:08:20,000 --> 00:08:24,000 So if you're answering why and explaining the constraints and the concepts there, 120 00:08:24,000 --> 00:08:27,000 I don't think there's much more that we can do than that. 121 00:08:27,000 --> 00:08:31,000 But we can add the constraints, the reasons, the why to the FAQ, 122 00:08:31,000 --> 00:08:38,000 and that should at least alleviate those people who will read that and understand that. 123 00:08:38,000 --> 00:08:44,000 I could probably, for some of those users, I could sit here around a circle with some campfires 124 00:08:44,000 --> 00:08:48,000 and some s'mores and be like, here's exactly why we don't have Quest support. 125 00:08:48,000 --> 00:08:54,000 And I could get out diagrams and charts and lines and graphs. 126 00:08:54,000 --> 00:08:59,000 What's that image with the conspiracy theory thing from the comedy? 127 00:08:59,000 --> 00:09:01,000 I don't remember what show it is. 128 00:09:01,000 --> 00:09:04,000 You know the one, the meme image. 129 00:09:04,000 --> 00:09:06,000 I don't know a lot. 130 00:09:06,000 --> 00:09:08,000 That one, yes, that one. 131 00:09:08,000 --> 00:09:10,000 I could do that, that image. 132 00:09:10,000 --> 00:09:18,000 I could do that image for hours, and that kind of person might still say that VRC already did it. 133 00:09:18,000 --> 00:09:21,000 And that just means that they don't have the right attitude to listen to us. 134 00:09:21,000 --> 00:09:28,000 So there's certainly more we can do in the FAQ there to lower the amount of them. 135 00:09:28,000 --> 00:09:32,000 You can't win them all, but we could win back a few more by editing the FAQ 136 00:09:32,000 --> 00:09:35,000 to be a little bit more detailed in the area. 137 00:09:35,000 --> 00:09:39,000 Additionally, we sometimes get feedback about why it says on the website that we do support Quest 138 00:09:39,000 --> 00:09:42,000 and we don't support Quest. 139 00:09:42,000 --> 00:09:44,000 You know why that is. 140 00:09:44,000 --> 00:09:48,000 We don't even say what's going on there. 141 00:09:48,000 --> 00:09:52,000 The website also says that we're in a partner with various educational establishments. 142 00:09:52,000 --> 00:09:58,000 And while we do have people that work at those educational establishments who use Neos, 143 00:09:58,000 --> 00:10:02,000 the word partner means that there's some paperwork in place, 144 00:10:02,000 --> 00:10:04,000 and there is not paperwork in place for some of those. 145 00:10:04,000 --> 00:10:05,000 Or there might be, I don't know. 146 00:10:05,000 --> 00:10:09,000 But I know for a fact that there is not paperwork available for some of those places, 147 00:10:09,000 --> 00:10:12,000 so I wouldn't call them an official partner. 148 00:10:12,000 --> 00:10:15,000 But hey, that's the website for you. 149 00:10:15,000 --> 00:10:19,000 I mean, we could buy the logic that is being used to put partners on there. 150 00:10:19,000 --> 00:10:23,000 We could have put Microsoft on there when I worked for Microsoft and said, 151 00:10:23,000 --> 00:10:28,000 yeah, because a Microsoft employee uses Neos and works for it, we're partnered with Microsoft. 152 00:10:28,000 --> 00:10:31,000 It's like, it doesn't work like that. 153 00:10:31,000 --> 00:10:33,000 Like a partnership is a partnership, right? 154 00:10:33,000 --> 00:10:36,000 If you like Google partnership on like a stock image website, 155 00:10:36,000 --> 00:10:40,000 you'll probably see a lot of like people wearing suits shaking hands. 156 00:10:40,000 --> 00:10:46,000 If there's no shaking hands or wearing suits, then it's not a partnership. 157 00:10:46,000 --> 00:10:51,000 Yeah, Zach is a perfect example of partnership, a stock image. 158 00:10:51,000 --> 00:10:55,000 Hey, do any of you work for like a grocery store or a fast food establishment? 159 00:10:55,000 --> 00:10:57,000 We're partnered with those two, because you know, you play Neos. 160 00:10:57,000 --> 00:10:59,000 Yeah, I noticed. I'm glad about that. 161 00:10:59,000 --> 00:11:01,000 It keeps them organized. 162 00:11:01,000 --> 00:11:04,000 I should probably look into Lex's stuff rather than Sounder. 163 00:11:04,000 --> 00:11:08,000 Sounder was great until like, I don't know, I complained about their transcription editor 164 00:11:08,000 --> 00:11:11,000 and then they like appear to have removed the transcription editor. 165 00:11:11,000 --> 00:11:13,000 I don't understand. 166 00:11:13,000 --> 00:11:17,000 I used to be able to basically be like, cool, I'm going to edit the transcriptions and make them better. 167 00:11:17,000 --> 00:11:19,000 And then they're like, it didn't work. 168 00:11:19,000 --> 00:11:24,000 And I tweeted them about it and then they tweeted me back and then they removed the transcription editor. 169 00:11:24,000 --> 00:11:26,000 Oh, God, here we go. Here's a big one. 170 00:11:26,000 --> 00:11:28,000 I'll do my best, Lex. 171 00:11:28,000 --> 00:11:35,000 Lex says, I had a conversation a while back when I found out putting NeosDB links that aren't yours in a URI field 172 00:11:35,000 --> 00:11:41,000 would make the object count that asset link. 173 00:11:41,000 --> 00:11:45,000 That was a card chain towards your storage space. 174 00:11:45,000 --> 00:11:48,000 And that is intentional design with the reasons being here. 175 00:11:48,000 --> 00:11:57,000 In my opinion, I think that having dead links would be better than not having your storage space be taken up due to the possibility of this. 176 00:11:57,000 --> 00:12:04,000 What is your opinion on the duplication of assets for conservation of assets? 177 00:12:04,000 --> 00:12:08,000 I don't have an opinion because I don't really understand what's going there. 178 00:12:08,000 --> 00:12:13,000 I've read like everything you've done on that particular issue like three times and dug into the code a little bit. 179 00:12:13,000 --> 00:12:17,000 I don't understand what's going on there. 180 00:12:17,000 --> 00:12:23,000 I do think that there could be a way to do it that is obviously better for your space. 181 00:12:23,000 --> 00:12:29,000 However, as aligned with the things to avoid list, 182 00:12:29,000 --> 00:12:41,000 using other NeosDB links in URI fields should be a limited thing right now. 183 00:12:41,000 --> 00:12:45,000 I mean, if cloud spawning, sure, but we don't support it right now officially. 184 00:12:45,000 --> 00:12:49,000 But I don't know why that would come up in reality. 185 00:12:49,000 --> 00:12:55,000 Like if you come up with a scenario where it comes up in reality, then we might actually come up with a scenario where 186 00:12:55,000 --> 00:12:59,000 A, we can change that feature because your scenario is impactful, 187 00:12:59,000 --> 00:13:04,000 or B, where we can come up with a slightly different feature that works to solve that gap. 188 00:13:04,000 --> 00:13:05,000 I don't know. 189 00:13:05,000 --> 00:13:09,000 But yeah, I haven't looked into it enough to like really understand what's going on. 190 00:13:09,000 --> 00:13:13,000 I don't think uploading movies is against the guidelines. 191 00:13:13,000 --> 00:13:19,000 It is sort of against the EULA and our like terms of service-y thing and stuff like that. 192 00:13:19,000 --> 00:13:23,000 There is guideline stuff for copyrighted material, of course, as well. 193 00:13:23,000 --> 00:13:27,000 But it's difficult to like, it's difficult for us to enforce that. 194 00:13:27,000 --> 00:13:30,000 Otherwise, we'd have to start enforcing everything. 195 00:13:30,000 --> 00:13:34,000 What I would say for those who are watching movies, if you want to share movies with people, 196 00:13:34,000 --> 00:13:38,000 the worst movie provider is the Neos cloud. 197 00:13:38,000 --> 00:13:44,000 Get a Plex server or some RTMP server, you'll have a much better time syncing files, 198 00:13:44,000 --> 00:13:47,000 keeping everyone up to date, making sure there's no drift. 199 00:13:47,000 --> 00:13:50,000 You'll have a lot better experience with subtitles. 200 00:13:50,000 --> 00:13:53,000 You'll have a lot better scenario with storage as well. 201 00:13:53,000 --> 00:13:55,000 You won't stick your sync. 202 00:13:55,000 --> 00:13:59,000 You won't cause like Cosmos DB 429 errors. 203 00:13:59,000 --> 00:14:02,000 It's the worst place to store movies. 204 00:14:02,000 --> 00:14:07,000 I've also thought, and this isn't an announcement saying we're going to do this, so don't be scared, 205 00:14:07,000 --> 00:14:12,000 but I thought, and thinking is good, remember, theoretical thinking about problems is how you learn, 206 00:14:12,000 --> 00:14:19,000 I thought about how would we maybe like discourage this movie thing. 207 00:14:19,000 --> 00:14:25,000 Well, we could see, hmm, how big is this file and what type of file it is. 208 00:14:25,000 --> 00:14:27,000 Oh, it's a four-hour video? Great. 209 00:14:27,000 --> 00:14:30,000 Must be the latest Marvel film. 210 00:14:30,000 --> 00:14:34,000 So, you know, then we could maybe say like, hmm, maybe we don't want to sync that. 211 00:14:34,000 --> 00:14:39,000 But it's really subjective because there are cases where you might want to sync a very big video file to the NEOS Cloud. 212 00:14:39,000 --> 00:14:45,000 However, in summary, if you want movies in NEOS, I don't recommend the NEOS Cloud. 213 00:14:45,000 --> 00:14:51,000 I recommend like some other form of getting that information into NEOS. 214 00:14:51,000 --> 00:14:53,000 Rampa mentions content ID. 215 00:14:53,000 --> 00:14:56,000 We could, again, this is not an announcement. 216 00:14:56,000 --> 00:15:02,000 We are not doing this, but we could totally do YouTube's content ID on every single video uploaded to the NEOS Cloud, 217 00:15:02,000 --> 00:15:06,000 just so you're aware. We could. We're not, but we could. 218 00:15:06,000 --> 00:15:12,000 Moving forwards to, let's see, any other questions? 219 00:15:12,000 --> 00:15:14,000 Okay, Zach has a question here. 220 00:15:14,000 --> 00:15:23,000 Hey, like, I'm really sorry about this because like 90% of questions I get with syncing are exactly the same problem. 221 00:15:23,000 --> 00:15:29,000 Every time someone reports a syncing issue, I go back to the sync Wiki pages and take a look at them. 222 00:15:29,000 --> 00:15:34,000 And they have the appropriate information on them, so please read the sync Wiki issues. 223 00:15:34,000 --> 00:15:39,000 And if you continue to have issues about that, please post logs in the Bugs and Feedback channel. 224 00:15:39,000 --> 00:15:43,000 Not like screenshots of logs, not segments of logs, whole log files. 225 00:15:43,000 --> 00:15:51,000 And take a look at that because any updates on the syncing issue will be reflected on those Wiki pages. 226 00:15:51,000 --> 00:16:00,000 And that is, like, it's because, like, I'm sorry, but, like, I'm tired of talking about sync issues. 227 00:16:00,000 --> 00:16:06,000 There is literally nothing I can do, and so therefore I'm trying to standardize that any absolute feedback I have 228 00:16:06,000 --> 00:16:13,000 about stuck syncs or sync issues is going to be documented on the Wiki such that I make myself redundant 229 00:16:13,000 --> 00:16:15,000 as a person talking about sync issues. 230 00:16:15,000 --> 00:16:18,000 Like, I want it to be like a one-stop shop. 231 00:16:18,000 --> 00:16:22,000 You know when you go to the doctor and they're like, all right, we're going to take your temperature 232 00:16:22,000 --> 00:16:24,000 and then we're going to, like, I don't know, prod you a bit? 233 00:16:24,000 --> 00:16:30,000 I want, like, sync to be resolved like that as best as I can, because that's all I can do right now. 234 00:16:30,000 --> 00:16:32,000 Like, the real solve for sync is, like, some code updates. 235 00:16:32,000 --> 00:16:37,000 But, you know, it's interesting enough, actually, and here's a random tangent, which is amazing, 236 00:16:37,000 --> 00:16:40,000 because you're going to enjoy this tangent, except those who don't enjoy the tangents. 237 00:16:40,000 --> 00:16:43,000 But if you're here for the tangents, you're going to enjoy this one. 238 00:16:43,000 --> 00:16:48,000 I used to work for a motorsport management software system company. 239 00:16:48,000 --> 00:16:53,000 So we made management systems for motorsports events around the world, Australia, America, the UK, 240 00:16:53,000 --> 00:16:56,000 you name it, I've been there, wherever there's a racetrack. 241 00:16:56,000 --> 00:17:02,000 And we have this problem whereby a motorcycle rider has a bunch of motorcycles, 242 00:17:02,000 --> 00:17:06,000 because they're trying to enter as many races as possible to get as much sponsorship money as possible. 243 00:17:06,000 --> 00:17:15,000 So if you have a 600cc bike and a 1200cc bike, those obviously cannot be entered into the same category of race, 244 00:17:15,000 --> 00:17:21,000 because they're in lightweight and heavyweight classes, as in how big your bike is, how roaring the engine is, et cetera. 245 00:17:21,000 --> 00:17:28,000 Now, we came up with a system which is a questionnaire, and you just fill in what your bike is. 246 00:17:28,000 --> 00:17:31,000 So you say, like, what's the cc of your bike? You enter it. 247 00:17:31,000 --> 00:17:37,000 You're like, does your bike have four legs, three arms, an upside-down sandwich or whatever? 248 00:17:37,000 --> 00:17:43,000 You keep filling in questions. And what the expert system does is it figures out which classes you're for. 249 00:17:43,000 --> 00:17:48,000 And, like, Eclat system is just like a defined computer software algorithm. 250 00:17:48,000 --> 00:17:52,000 And I want to do that with the whole sync issue, because it's driving me mad, basically. 251 00:17:52,000 --> 00:17:56,000 I don't mean to be bad to anyone, but I basically want to go to this website where it's like, 252 00:17:56,000 --> 00:18:04,000 are you experiencing a syncing problem? Yes. Please upload a log file. Log file updated. Next. 253 00:18:04,000 --> 00:18:09,000 All right. We've discovered that in your log file, this has happened. Have you tried doing this? 254 00:18:09,000 --> 00:18:18,000 Yes. Next. And it will just keep going until it spits out, like, the exact answer for you so I can stop talking about them. 255 00:18:18,000 --> 00:18:21,000 So I'm trying to get that going as well. Expert systems are cool. 256 00:18:21,000 --> 00:18:26,000 You will get some resources in the doobly-doos about that. 257 00:18:26,000 --> 00:18:29,000 Oh, a good example of an expert system is the Akinator. 258 00:18:29,000 --> 00:18:33,000 You know, the one that guesses which character you are? That's an expert system. 259 00:18:33,000 --> 00:18:39,000 I will now reread your question, though, as I just went off on a very large tangent about sync issues. 260 00:18:39,000 --> 00:18:46,000 I don't understand what the problem there is. Are you saying that you're confused about why it's so slow? 261 00:18:46,000 --> 00:18:56,000 In which case it's slow, probably, either for internet, which you say it's not internet, although it still might be internet because internet is complicated, depending on where you are in the world, et cetera. 262 00:18:56,000 --> 00:19:04,000 It could also be indexing. Like, we need to know what we're sending, right? So it chunks up the file and then sends it in Prequence. 263 00:19:04,000 --> 00:19:22,000 I actually have no idea anything about bikes. The way that we wrote the system, we had another system, namely called the rulebook for the motorsport organisation we work for, which defined the expert system rules. 264 00:19:22,000 --> 00:19:28,000 So they would say, hey, we're a new customer. And I would say, great, have you got your rulebook? And they would say yes. 265 00:19:28,000 --> 00:19:32,000 And they would give me the rulebook. And based on the rulebook, I wouldn't even understand what I was reading. 266 00:19:32,000 --> 00:19:45,000 I would program the expert system. And then we would put some test bikes through it, and then inevitably when the first event for that motorsport championship would happen, we would get a bunch of calls and emails. 267 00:19:45,000 --> 00:19:57,000 And they'd be like, this motorcycle should be allowed in this race, but your system says it's not allowed. And I'd be like, okay, according to the rulebook, section three, paragraph four, subsection A, that bike isn't allowed. 268 00:19:57,000 --> 00:20:07,000 Could you clarify this, please? And we went backwards and forwards and backwards and forwards and backwards and forwards until we just had an exception system where they could say, here is an exception. 269 00:20:07,000 --> 00:20:21,000 This bike can actually enter this particular race course. And it always had a justification field where we required like clock of the course, which by the way is like the director of the event, to like put in a reason there. 270 00:20:21,000 --> 00:20:33,000 So like worlds are very, very complicated. So I'm going to try and do an example. Again, this is like wishy washy because I haven't read all that code yet. 271 00:20:33,000 --> 00:20:42,000 Neos is huge, right? So let's imagine that you have a really complicated object. So I'm just going to be de facto a meme and say a custom inspector or a custom multi-tool. 272 00:20:42,000 --> 00:20:54,000 That's a really complicated object. There's slots everywhere. It's very, very big. Saving that to your inventory is going to take a defined amount of time because of how big and complicated it is. 273 00:20:54,000 --> 00:21:06,000 Let's now put seven of those in a world. It's then going to have to say the exact state of seven of those in the world. And so it's going to times that object saving by seven. 274 00:21:06,000 --> 00:21:16,000 It will be a little bit lost, so it might be six or five because there are some duplicates it can link up. But it still needs to know like the location of all of those objects, all of those slots. 275 00:21:16,000 --> 00:21:28,000 So if there's a hundred slots, each have individual position rotation scales, and then all of the variables that exist on there, a value field that says two, another value field that says four, it's got to save all those. 276 00:21:28,000 --> 00:21:36,000 And the whole way it works is whenever you save a world, it takes the entire world, serializes it to a big database, and then just shoves it in the cloud. 277 00:21:36,000 --> 00:21:44,000 And so that will take longer for worlds than it does for individual objects simply because of how much stuff is there and how complicated that is. 278 00:21:44,000 --> 00:21:54,000 It's the equivalent of basically saying I would like to ship in terms of a moving company my entire apartment or one room of my apartment. 279 00:21:54,000 --> 00:22:01,000 It's a magnitude bigger because of how much more stuff there is and where that stuff is located. 280 00:22:01,000 --> 00:22:07,000 So if your home is taking a long time, maybe consider removing stuff in your home. 281 00:22:07,000 --> 00:22:13,000 Personally, I don't use my home world. I think it's silly that people do put lots of stuff in their home world. 282 00:22:13,000 --> 00:22:17,000 My home world is basically a diving board into the rest of Neos. 283 00:22:17,000 --> 00:22:25,000 Zach asks, could it be my RAM and CPU? Probably not. Probably not. 284 00:22:25,000 --> 00:22:32,000 OK, moving forwards, Rockman says, what do you think of the Quest Pro and how does Neos face and eye tracking work? 285 00:22:32,000 --> 00:22:37,000 So Neos face and eye tracking, by my knowledge, currently does not work for Neos. 286 00:22:37,000 --> 00:22:45,000 I created an issue for both the HTC Vive focus series and the Quest Pro, which can be tracked at this following link. 287 00:22:45,000 --> 00:22:49,000 And once this issue is closed, we will support those headsets. 288 00:22:49,000 --> 00:22:53,000 As for what I think about them, I am disappointed that the Quest Pro is $1,500. 289 00:22:53,000 --> 00:22:57,000 I'm also disappointed that the Quest Pro is lacking certain features. 290 00:22:57,000 --> 00:23:06,000 I'm also incredibly disappointed that at the keynote for the Quest Pro and related stuff, they had pre-animated demos of some of the technologies there. 291 00:23:06,000 --> 00:23:15,000 I won't be buying any headset before I've seen a hands-on review from people who I can trust, such as the larger VR content creators, 292 00:23:15,000 --> 00:23:19,000 and in some cases, before I can even go and take a look at the headset and put it on. 293 00:23:19,000 --> 00:23:27,000 Headsets are heavy and uncomfortable, and before I drop $1,500 on something, I need to know what's going on. 294 00:23:27,000 --> 00:23:32,000 The last time I did that was with an index, and that was a risk, and it was OK. 295 00:23:32,000 --> 00:23:37,000 We're still talking about Zach's home world. Let's take a look at what's going on. 296 00:23:37,000 --> 00:23:45,000 Saving is different from loading. The CPU freeze during loading is probably a different problem than saving. 297 00:23:45,000 --> 00:23:49,000 Yeah, weight distribution is also massive. 298 00:23:49,000 --> 00:23:55,000 That's why the headsets have so many straps and stuff like that, right? 299 00:23:55,000 --> 00:24:03,000 You need to adjust those. Read the manual for your headset and see if you're adjusting those straps correctly. 300 00:24:03,000 --> 00:24:07,000 Because if you're not, you're probably pulling your face off. 301 00:24:07,000 --> 00:24:13,000 I just got this picture of someone ripping their face off when it's stuck to a headset. 302 00:24:13,000 --> 00:24:18,000 Sometimes I feel like that after 12 hours in VR. Anyway, let's take this question I missed. 303 00:24:18,000 --> 00:24:22,000 Mr. has a question. Fantastic. Sorry I missed it. Thanks, Lex, for linking it. 304 00:24:22,000 --> 00:24:26,000 So after headless was introduced, is there any plans for servers? 305 00:24:26,000 --> 00:24:32,000 Yes. Headless servers aren't servers, and I feel like I should get that on a t-shirt or something. 306 00:24:32,000 --> 00:24:37,000 Headless servers are not our final envisioning for servers. Servers are. 307 00:24:37,000 --> 00:24:41,000 We don't quite know what the gap between headless servers and servers will. 308 00:24:41,000 --> 00:24:43,000 I love these tongue twisters today. 309 00:24:43,000 --> 00:24:50,000 But it would be more tailored to being run in a data center. 310 00:24:50,000 --> 00:25:00,000 And there also might be an opportunity or system or way that Neos runs some servers for you on behalf of the session host and things like that. 311 00:25:00,000 --> 00:25:05,000 There are plans. I think there's some GitHub issues somewhere. You'd have to dig through them, though. 312 00:25:05,000 --> 00:25:11,000 Sometimes, in office hours, I feel like a search engine. 313 00:25:11,000 --> 00:25:15,000 So I'm going to go type the word servers into our issue list and see what I can find. 314 00:25:15,000 --> 00:25:20,000 Yeah, so there's a couple of relevant issues. 315 00:25:20,000 --> 00:25:26,000 There's this, which is like spooling up headless sessions. 316 00:25:26,000 --> 00:25:30,000 You'll see Shifty says here dedicated servers are planned. 317 00:25:30,000 --> 00:25:33,000 So that to me suggests there might be something on the roadmap. 318 00:25:33,000 --> 00:25:36,000 So I'll go take a look at the roadmap. 319 00:25:36,000 --> 00:25:40,000 Probably been a major roadmap here. 320 00:25:40,000 --> 00:25:44,000 It did find that. I only found one. 321 00:25:44,000 --> 00:25:48,000 Okay. Yeah, we need a card for that. 322 00:25:48,000 --> 00:25:52,000 You can find some information there from Shifty and from Fricks. 323 00:25:52,000 --> 00:25:54,000 And with that, I believe we're at the end of questions. 324 00:25:54,000 --> 00:25:57,000 I do apologize for the continual sync issues. 325 00:25:57,000 --> 00:26:02,000 I'm just like, I'm tired of seeing them. 326 00:26:02,000 --> 00:26:06,000 Not because it's your fault, but because it's our fault. 327 00:26:06,000 --> 00:26:12,000 I'm tired of there not being an ability for me to better solve that issue for you guys. 328 00:26:12,000 --> 00:26:15,000 So in lieu of that, I'm trying to make your experience better. 329 00:26:15,000 --> 00:26:19,000 And I want your experience to be you go to a Wiki page and you find your solution. 330 00:26:19,000 --> 00:26:25,000 I don't want you to have to like spam staff or just like say in chat that there's a problem. 331 00:26:25,000 --> 00:26:36,000 But to help me out there, log files, one report, and read the Wiki pages as we develop them. 332 00:26:36,000 --> 00:26:42,000 In the final few moments I've got, I'm going to just point at the Logix channel, 333 00:26:42,000 --> 00:26:45,000 where there's a video of a mathematical problem. 334 00:26:45,000 --> 00:26:49,000 There isn't an AI. I know what you mean. 335 00:26:49,000 --> 00:26:51,000 We'll just stop talking about syncing now. 336 00:26:51,000 --> 00:26:55,000 In the Logix channel, by myself, there is a mathematical problem, 337 00:26:55,000 --> 00:26:57,000 which I don't understand the reason for, 338 00:26:57,000 --> 00:27:02,000 but I am continuing to work with Hamish S.H.F.R. on what the hell we need. 339 00:27:02,000 --> 00:27:06,000 So if anyone has any idea what that video means and wants to speak to me about it, 340 00:27:06,000 --> 00:27:13,000 please do take a look. It is mathematical in nature and AI rotationally in nature. 341 00:27:13,000 --> 00:27:15,000 We appear to be on to something, though. 342 00:27:15,000 --> 00:27:20,000 We've rigged up a new test rig that might show the problem a little bit better. 343 00:27:20,000 --> 00:27:26,000 So if there is a solution there, or at least a problem identification option thingy there, 344 00:27:26,000 --> 00:27:29,000 then I'll update the video or something. 345 00:27:29,000 --> 00:27:32,000 With that, I'm going to go ahead and draw this to a close, 346 00:27:32,000 --> 00:27:38,000 and I will see you guys next week, hopefully for additional questions and awesomeness. 347 00:27:38,000 --> 00:28:00,000 I will speak to you later. Good bye.