I’m working on a project that just suddenly started to see problems. I have some character models in the scene, and they were working fine. Recently, they started to look like they have some sort of corruption, but I can’t reproduce this issue on my machine…2 of my coworkers are seeing it, and in every browser they try (Chrome, Firefox, Safari, Opera). I have tried in a couple different browsers, but can’t reproduce the issue, at all.
We have tried clearing cache, re-uploading the FBX, and removing recent additions to the scene.
Interestingly, a previous build (from early last week) does NOT exhibit this problem for those 2 coworkers. Perhaps there has been a change in the pipeline?
Unfortunately, I’m not at liberty to make the project public. What seems to be the likely problem, here?
I’ve been digging on the coding side to see if there is anything I can do for this. At the same time, one of my artists re-built the characters with the poses/animations done differently (I don’t know the details, unfortunately). So, we may have made some progress with the display “corruption”.
I guess what’s odd for me is that these assets are re-used from other projects of ours, and they worked fine. And, they worked fine in THIS project only last week.
This is why I reached out to the forums. It seems as though something changed “under the hood”. Any thoughts?
I went to go fork the project, so I could strip it down and make it public, but my artist has already proceed to replace those assets. I don’t think I can replicate this issue anymore, as I could never see it from my machine.
Shoot… I hate fixing a problem when I don’t know what the underlying problem was.
Thanks for the prompt replies, folks. I think we can mark this one ‘solved’.
There appears to be something broken with the latest version of PC regarding safari for desktop 13.1 in the latest version of MacOS. You can easily demonstrate this issue if you have a mac with latest updates. Look at the animation-blending example… The version on that landing page works just fine.
However if you go into the editor it immediately exhibits the same issue as the original poster, as well as the same issue my team is experiencing now.
First one is Chrome: Version 83.0.4103.116 (Official Build) (64-bit)
Second one is Safari: Version 13.1.1 (15609.2.9.1.2)
MacPro(2019): Catalina Version 10.15.5
Confirmed same issue experienced on MacPro2012 running Mojave 10.14.6, as well we MacMini running Catalina 10.15.2. Again, the launch and demo page build of that works on all devices. But if you go into the editor with the link provided at the bottom of the page or the one I linked in my last post, you can see this issue in the editor, as well as when you play from editor. Like-wise we have older projects that work from previous builds, but if I open them in editor and/or republish they now exhibit the same issue.
Our workaround will not be helpful for other developers. I just spoke to my animator, and he ripped out the character rigs, and re-imported the FBXs. So, our “fix” is not generally useful.
