I’m releasing my product on Steam on Tuesday, July 26th. I’ve been using 5.3.5p2 which has been great. In preparation for release it was recommended that I switch to Unity 5.4 to get integrated Vive support.
Just tried that, but unfortunately it is not usable because the graphics keeps spiking up to 36ms (dropping from 100+ fps to only 27 FPS). See pic below for detailed info on one spike.
Is there anything that I can do about this? 5.3.5p2 does not do this at all, it’s smooth everywhere. Do I have to choose between Vive support and acceptable graphics performance, or does anyone know a trick to get rid of this? I have changed nothing in my project, I simply updated Unity and now I have show stopping problems.
If anyone knows of an earlier 5.4 version that doesn’t have this problem, but does have integrated Vive support, I’d be grateful to learn about it. I’ve only got a few days until release so have some difficult decisions to make here.
Update: This appears to be caused by my reflection probe in the scene. If I turn that off it’s as smooth as silk and very fast. Is there something new about reflection probes I need to learn? 5.4 apparently has SSR now, so maybe I could just use that instead? It might be preferable anyway.
Anyway, I’ll go find out what I can. If anyone has any ideas I’d be grateful to hear them.
And if that doesn’t work, it’s not releasable. I don’t then want to go monkeying with SSR and all that to fix one problem when another game breaking issue is there. Think I’m just going to revert to 5.3 and skip OpenVR/Vive support until it’s ready. I have a Steam release coming on Tuesday and don’t have time to mess with this.
Ugh, guys, come on… The spikes are not there in the previous version of Unity, only this new one. So this isn’t an optimization issue. The project is identical.
Yes, I’ll try to do a repro after I get some sleep and come back with a bug #. Thanks for popping in. After that you’re on your own though, I’m going to need to revert to 5.3 unfortunately because of the problems. I’m not too miffed about it, this is beta after all. I’m just bummed that I’m going to have to launch on Steam without the integrated Vive support. Bad timing.
It makes no difference at all to the end user where you get the SteamDLL’s from.
Truth is, before you go yelling to hard at the Unity developers, you upgrading your main branch to 5.4 beta, a week before launch, without creating a backup first? That’s a pretty boneheaded move.
@shawnblais Doesn’t sound like he did anything wrong to me. Sounds like he wanted to see if he could get Vive support for the cost of trying out the new build. Doesn’t mention anywhere that I see that he can’t simply revert and release, he was just hoping he wouldn’t have to.
Coulda swore that in yesterday’s version of the post, he was going on and on about how many bugs the 5.4 has (most were not true) and what a hassle it would be to revert to 5.3. Apologies if I mis-remembered.
Any way you slice it though, upgrading to Beta a week before launch is not the smartest of moves. I’ve done it myself, had to revert, and was equally harsh on myself
That’s true, it’s very tempting though to try out the new stuff. I’ve probably switched back and forth 10+ times through 5.4’s beta period, hoping each time for the best. It’s definitely looking a lot better now, than it was.
What’s boneheaded is somehow coming to the conclusion that I did anything of the sort.
“Most were not true?” I recall reporting three bugs and providing screenshots of two of them. I assure you I did not fake the screenshots.
Shawn, I’d love to tell you who advised me to do precisely what I did, the full spectrum of reasons why it was done, and how it differs from what your imagination has apparently invented to fill in the blanks, but can’t due to an NDA. Just add me to your ignore list and call it a day, ok? You’re not helping.
This thread should have ended with my reply to Alex and contained nothing after it except a case #. The Unity staff are adults, they don’t need their members rushing out to protect their precious feelings every time somebody gets upset by finding three game breakers in the first five minutes of trying the beta.
I can’t use 5.4.0f2 myself because in some cases unloading scenes seems to get unity stuck in an infinite loop (every time I break it’s stuck in editor get scene name or flushing dirty scene in unity native code). I can’t get a repo case to work outside of my project and the project is too big, so I can’t report it though, but downgrading to f1 solves the case.
