I just don’t see why the original would be struggling like that while the copy with all the more complex objects deleted and then added back in runs smoothly. I’ve hacked up the original again so there are now only a few simple objects with most of the physics elements removed but it has made no difference this time. Not sure what it was I removed to get it back to normal in the copy but I don’t see that it would be a matter of polygon count on this basis.
The performance hit doesn’t just happen while running the project and adding it in the editor. It persists when reloaded. As far as older machines are concerned, the 2017 MSI laptop with NVIDIA GTX 1060 runs no better than the 2012 Dell Latitude with integrated Intel graphics.
Having had another project run up against a similar problem today, including a published version that I’m sure was running smoothly when I built it a few weeks ago, I tried running the problematic projects in Chrome instead of Firefox. In Linux Chromium and Windows Chrome on the MSI, and Linux Chromium on the Dell, they all work smoothly.
Firefox on the Dell is actually working a bit smoother than the MSI, but not as well as Chromium. However, I am also noticing that Chromium is running the graphics at a lower quality with no vsync resulting in a lot of tearing if the camera moves out of its existing viewing area (full quality on the MSI though). Not as noticeable when moving forwards and backwards.
On the MSI in both Windows and Linux it encounters the dramatic framerate drop on these particular projects. At the worst extreme it feels like there’s an after-image as though it’s blending a semitransparent copy of each frame over the previous. Despite this the camera movement kind of still feels smooth so it’s hard to put my finger on exactly what’s going on if it’s not just a matter of low framerate
Firefox and Chrome on my Galaxy S9 both run smoothly. Yet to try these in the Quest but both the built-in browser and Firefox Reality have run everything else perfectly so far.
As a further experiment I switched the MSI to Intel mode in Linux and tested Firefox and Chromium. Chromium was slightly less responsive but still very smooth, while Firefox maintains the same jerky rendering. However, I then came back and tried a second time in Chrome a while later to find similarly rough rendering, worse than the Dell but still with the higher quality graphics and no tearing. Perfect again after rebooting into NVIDIA mode. Poor performance in Firefox persists.
The editors don’t suffer a performance hit at all on any combination of OS and browser.
Tried setting Fill Mode to None, disabling antialisaing, and then unchecking Prefer WebGL 2.0. There’s probably a slight improvement under some of those combinations but the problem persists. Disabling physics collisions and entire batches of entities also makes no difference. I thought maybe there’s something in one of the scripts but I’m using the exact same ones in other projects that are all working fine.
So apart from Chromium in Intel mode struggling a bit on the MSI, the common factor here seems to be Firefox on PC. But it’s still weird that there are specific projects that do this while others run fine.