One time purchase is an awesome thing. But I hope it evolves, world stores should be worlds you can walk in to. Auto genenrated or custom.
And with a future overall persistence system we should be able to buy things we can use without leavibg VRC, to have an inventory and currency. Even being able to do quests and jobs to earn virtual reality currency.
There are so many fun ideas involvibg money, I’m worimried it will go the wrong way. Already happening with VRC+. But making small pyrchases and donations would be great.
You should merge the updates from Merlin to give creators a better experience with the actual parts, rather than making us wait endlessly for your various changes without specific dates. It’s like pie in the sky. We’ve had enough
Sooo from what I’ve been reading in the comments and what I’m understanding this new “Udon2” just isn’t what was announced?
Why? Why change it now? Again what about transparency?
The initial sneak peak advertised performance improvements up to 2x faster and as far as I understand it, more features like generics that after all this time just won’t be there at launch?
Like c’mon, just after we finally get something big like persistence, giving us hope that big features were indeed possible, albeit with immense delay. Now you announce, without saying it as is, that the previous Udon2 concept was completely thrown out. Out of the blue??? After all this time???
I sincerely hope I’m missing something and severely misunderstanding what I’m reading. Otherwise this is a massive let down.
On the other hand persistence is very nice, one time purchases is a very welcome change and the latest smaller features introduced aren’t inherently bad. So as always, it’s not all doom and gloom but this announced is seriously disappointing.
Udon 2 was 10x or more in many cases. And opened up the ability to use Mono’s AOT on supported platforms which would be a further 10x in some cases.
It’s crazy to me that VRC expects creators to trust them on anything at this point if they can’t even describe what at the 11th hour caused them to shift to something else entirely. They’re being vague about resources, but you can go and look at Blazor in a web browser right now and it takes 60MB. That’s 1% of the quest 2’s RAM and 2% of the lowest spec phones you can get. The avatar uncompressed memory limit for a single avatar is 40MB. If they can’t budget for that, that’s not a resource problem.
You can run a whole raytracer on your phone, it’s actually like only 1/4 the perf of desktop for me. RayTracer demo on wasm
Until they give an actual reason my assumption is they don’t have an actual reason that would be justifiable, because if they could justify it they would’ve immediately said exactly why.
So, Soba… Not sure what happened to the proper Udon2 that was planned, but it really sucks that we’re getting a downgrade rather than upgrade from the latest U# that just got released. Not having Generics ? What also happened to the performance gains that Udon2 was going to have thanks to WASM?
Was Udon2 just scrapped as a project due to engineers not being able to pick up where Merlin left of when you fired him ?
Atleast some information about what happened to Udon2 would be great, instead of the “GREAT SILENCE”.
Thanks
Im not a creator per say, but what happened to the 2x performance of udon 2? Now its just “more performant or on par”. Please explain this, im sure most want to know.
Fax, I know that you’re a smart VRChat content creator; you and other engineers at VRChat must have already known and internalized that you are not delivering on the value proposition Udon 2 was set to offer, way before this announcement went live.
None of our macro-feedback matters, I’m sure you already had expressed them, whether it was internalized, or internally.
I hope you’ll be able to prove to us in the coming months where Soba lies on this horizontal axis, but your team has not promoted the impressive performance of Soba as part of this announcement, and you definitely would have had if it were the case, so we’re left to our own vague conclusions.
I mean, they said it’s on par with U# and slightly better in some cases, which tbh does not bring me a lot of hope…
Especially when considering how much more performant wasm was supposed to be.
Considering that interfaces and maybe possibly static field could be implemented in U# by Merlin Soba is just weird useless rewrite of Udon to me. Waste of engineer time and waste of money… Correct me if I’m wrong.
Also what happened to the communication from VRChat ? It’s almost like we’re back to the 2020 level of communications with this whole Udon nonsense, VRChat employees just ignore questions like they don’t exist or they just quote the Dev Update or they in some way or other say they can’t answer anything.
Looks like regression on more than Udon…
It just sounds like to me that whatever engineer/engineers picked up your work on Udon2 couldn’t crack it and didn’t understand enough to finish the work. And instead of trying/learning they just scrapped the project and create something worse in-place of it.
Honestly disappointing.
VRChat devs/staff, I totally understand if you don’t have answers to the negative feedback being presented here.
I think what we all really want to hear right now is a quick reply. All you need to say is: “We have heard your feedback. Let us discuss it internally and get back to you all tomorrow.” Or something like that.
Then once you have had time to talk internally, you can tell us what you can.
If you just tell us that you acknowledge that plans will have to change and you will talk more about it again after the holidays, then it is completely understandable. I don’t think anyone here expects you to suddenly release Udon2 or plans for Soba2 right here and now.
We just need to hear that you know something is wrong, it could be better, and that you will work on it next year.
Okay if that’s the case then this truly is irredeemable…
VRChat, this discussion has been had many times and recently too but where are those efforts in transparency??? Last time I already outlined how slowing dev updates and announced features disappearing into the aether (amongst other things) was seriously raising red flags and now this?
I do agree with what someone said above, we’re not expecting a sudden Udon2 release nor a detailed and comprehensive answer in a day. However this is, in my humble and very own opinion, unacceptable. SUCH a step back for something SO big in scope and importance WITHOUT a hint of explanation is stupid at best. Malicious at worst.
We need something better and I’d argue you’re letting yourselves down by taking this path.
I have been reading this and past updates as well as some of the feedback.
TLDR;
I am just confused, unsure what I should use / look into for development going forward and unsure what can or will be done looking into the future.
Therefore probably wont work on anything until things become clear, since I dont have a lot of time/energy which I can pour into projects.
This year, there have been virtually no updates aimed at enhancing the experience of map creators, only promises that are challenging to fulfill. The rest are merely so-called security restrictions and money-making features. We eagerly await the upcoming 2025, anticipating the jokes the official will bring.
I am reading this once again, it seems like this basically breaks testing in editor? You have no idea what will work if you can only run your compiled code in Unity’s Mono without the actual VM to test against. Then again, they also have U# going to Mono in the editor, which it doesn’t currently. So ??? Maybe whoever wrote the flow chart missed some information.
