updates?

[DR.grEEnThumB]

are the basically just updating the game so people cant use mods anymore?

[Zorro_X]

No, it is an Internal core update to make the game more compatible with all platforms where it is sold. It is good for the game developers. But, from a user level point of view, even without considering mods, those last updates have bring more bugs than enhancements…

[sidrat]

It sure feels like it as who wants to play with the stock maps only? It's a bit silly isn't it.

[Zorro_X]

hi, you can downgrade to the V1.29.1 (before OpenXR) by just going to preferences then click on Beta and choose the V1.29.1 version. You'll get back to a "moddable" version and everyone may get a version with good performances and less bugs !

[sidrat]

Originally posted by Zorro_X:

hi, you can downgrade to the V1.29.1 (before OpenXR) by just going to preferences then click on Beta and choose the V1.29.1 version. You'll get back to a "moddable" version and everyone may get a version with good performances and less bugs !

Huh, I'll try that thank you.

[sidrat]

That's cool, you don't need a password but it does tell you it's failed, which is silly.

[TheUKDude]

Just in case anyone was wondering why the Unity Engine was changed to a new version, this was the real reason.

It was due to Unity Version 2019.4.28.X is no longer supported by Unity Technologies and for the Game Engine to continue to get bug fixes security updates Beat Games needed to upgrade to the latest Unity LTS (Long Term Support) Version, more information later in this post.

I also use Mods myself so I was also shocked when they just didn't work, but just an easy step to roll back to the Legacy via the Beta section to be able to keep using them.

I am not taking sides here, so don't moan at me I am just saying it as it is.

Sure Beat Games should / could of given a more of a heads up (if they didn't) but as a software developer myself you have to make these big changes now and then and you are never going to make everyone happy, and jumping 2 Major Engine versions is a huge jump.

But you also need to stop having a go at the Beat Games Devs for this decision to do that upgrade, it really needed to be done and was the right thing to do, more information below on why.

Also people saying its to force users to buy the DLC's, its so not that reason, if Beat Games were then they wouldn't of added the Legacy version for users that use mods.

So maybe you should also be moaning at the Mod Devs for not updating their mods, its not that hard to look at the Beatsaber source code. Who knows they might even be doing exactly that right now, so just give it some more time.

So meanwhile there is nothing stopping you from rolling back to the Legacy version and keep using that while the Mod Devs work on their mods to work on the new version.

Information on the Unity Engine, Unity 2021.3.x LTS is the latest Long Term Support by Unity Technologies, that will keep getting biweekly until mid 2023 and then monthly updates until April 2024. So we should be fine for another year.

Now if they kept with Unity 2019.x which was released back on 8th April 2019 had all including Security Support end on 16th June 2022, so in fact Beat Games should of updated to a newer version back then.

[TheUKDude]

Originally posted by Zorro_X:

No, it is an Internal core update to make the game more compatible with all platforms where it is sold. It is good for the game developers. But, from a user level point of view, even without considering mods, those last updates have bring more bugs than enhancements…

That was a small part why it got updated, read my previous post as to the main reason it was updated with that huge change.

[Zorro_X]

Thankyou for the details, but the result is, besides modding (I don't mod, yet...), that there are more bugs and less performances (FPS drops). There are many other games using OpenXR without those issues, so the job could have be done better, at least for "not modding" users...

[TheUKDude]

Originally posted by Zorro_X:

Thankyou for the details, but the result is, besides modding (I don't mod, yet...), that there are more bugs and less performances (FPS drops). There are many other games using OpenXR without those issues, so the job could have be done better, at least for "not modding" users...

Oh for sure, things could of been handled a lot better, like when ever we did a huge jump in our code we had 2 versions running (current and new) for ages and we collected loads of logs while testing the new one, one time we had a new version running for 4 months.

The only issue with Beat Saber is that a lot of people use mods and if a new version that broke that, then those people stayed away from that version, but the Mod Devs should be testing their mods the hell out o that version.

As for performance I noticed the newer version running a lot faster and smoother I never really noticed any issues, maybe its where I use the USB Cable and use Oculus Link along with using the Pro Controllers (I hated the Sabers floating off to infinity due to the headset couldn't see it) , but where I use mods and custom maps I went the legacy route until the mod devs catch up.

But you need to assume there will be some huge bugs with an update that jumps 2 Major Engine versions, its just going to be an issue, especially with Unity, things have changed a lot between those, like function names, the arguments to them, hell some have had their namespace / assembly changed.

[Zorro_X]

I understand you well, I'm also a "coder", (used to be in real time embedded systems). But I also know when you need to upgrade some internal library that does not directly concern your customer, if it brings bugs with it, your customer is not happy and may even lose confidence in you. That's why you usually need to get at least your new version as stable as the previous one, and don't deliver it until you've not solved the new problems/bugs.

I also use the link cable, with an RTX 3060 Ti, and when you say "there are no bugs", I'm sorry, but you're wrong : if I start the game throuhg SteamVR (which is the most usual way for users), I got an unplayable game displaying it like a slideshow at ~0.2 FPS. In order to be playabe, I need to start it by killing SteamVR, then it becomes playable. But, during the game, if there are a lot of blocks, like for example in Crazy=Genius / Expert +, the FPS drops to near 15-20 FPS. That did not happen before. Those are the main game current bugs from my point of view, of course without considering the "already known bugs" that weren't there on the previous version neither like the no pause button, or the recentering gone.
I've also tested the alpha version before launch, and with that version there were less bugs, and those one were not present. So it already seems to be possible to get it working in a better way...

I use LIV to capture MVR, which is not the most common usage I know, but there you have more bugs : most difficult to calibrate, principally because SteamVR cannot run at same time, but also because the centering not available and the fact you cannot perform anymore calibrations adjustments during the game. Also, the Z-clipping seems to be ignored : everything pass below the MVR user position that makes it look like there is only a screen behind the user, the immersive capture effect is then not good.

Regarding mods I cannot say (yet), but from that point of view, even if it is a common usage of the game, there is less legitimacy because it is non-official and absolutely not maintained by the development team. It is however a community issue, and nowadays you're nothing without your community, so this shall not be ignored neither from a marketing point of view...

[TheUKDude]

Originally posted by Zorro_X:

I understand you well, I'm also a "coder", (used to be in real time embedded systems). But I also know when you need to upgrade some internal library that does not directly concern your customer, if it brings bugs with it, your customer is not happy and may even lose confidence in you. That's why you usually need to get at least your new version as stable as the previous one, and don't deliver it until you've not solved the new problems/bugs.

Yes I totally agree, they should of had a beta version running for longer time.

Originally posted by Zorro_X:

I also use the link cable, with an RTX 3060 Ti, and when you say "there are no bugs", I'm sorry, but you're wrong : if I start the game throuhg SteamVR (which is the most usual way for users), I got an unplayable game displaying it like a slideshow at ~0.2 FPS. In order to be playabe, I need to start it by killing SteamVR, then it becomes playable. But, during the game, if there are a lot of blocks, like for example in Crazy=Genius / Expert +, the FPS drops to near 15-20 FPS. That did not happen before. Those are the main game current bugs from my point of view, of course without considering the "already known bugs" that weren't there on the previous version neither like the no pause button, or the recentering gone.
I've also tested the alpha version before launch, and with that version there were less bugs, and those one were not present. So it already seems to be possible to get it working in a better way...

I use a ROG STRIX 2080 Ti so I am able to plug the VR Headset directly to the Graphics Card.
Well I just connect it all up, Start the OVRService (yes I don't have that auto running), once booted up then Connect via Link and add Steam as Desktop and click on Beat Saber like I have always done, I have never had any issue, but I have not tried the latest up to date version, so maybe stuff has changed, but when I tried it last it was fine for me. Also I am really OLD LOL and only play now and then, so only at Hard (yeah I know LOL) but I do run some up to 200% speed for fun LOL

I am also running the headset with default settings apart from the privacy settings and a few others.

Originally posted by Zorro_X:

I use LIV to capture MVR, which is not the most common usage I know, but there you have more bugs : most difficult to calibrate, principally because SteamVR cannot run at same time, but also because the centering not available and the fact you cannot perform anymore calibrations adjustments during the game. Also, the Z-clipping seems to be ignored : everything pass below the MVR user position that makes it look like there is only a screen behind the user, the immersive capture effect is then not good.

Well I am not using LIV, I do use Camera2 to get a better view when if recording.
I will have to try the latest version the weekend if I get some spare time.

Originally posted by Zorro_X:

Regarding mods I cannot say (yet), but from that point of view, even if it is a common usage of the game, there is less legitimacy because it is non-official and absolutely not maintained by the development team. It is however a community issue, and nowadays you're nothing without your community, so this shall not be ignored neither from a marketing point of view...

Yeah, would be nice if they added Mod Support, BUT I don't see that happening any time soon. That's what I was trying to say in my other post, people need to also moan at the Mod Devs too.

Just need to give both sides to resolve the issues.

[Zorro_X]

I totally agree ! :)

[KalitaNite]

stop suggestign the legacey roll back. it DOES NOT WORK

[TheUKDude]

Originally posted by Nite:

stop suggestign the legacey roll back. it DOES NOT WORK

It does due to loads and myself are using that version.

[KalitaNite]

i have it loaded and my moids dont work sooo.