Patch for two issues.
I've been having the same issue and haven't updated any drivers, applications or OS. Totally locked down, no updates.
Above a certain size the canvas (and preview) will render black. Collision shape outlines are still visible but nothing else. I believe issue started occurring during the last beta cycle. My workaround has been to keep the search window docked under the canvas window to control the size it's drawing at.
The issue occurs with no other software, browser-based or otherwise.
Graphics driver issues can appear under essentially random circumstances. It's entirely possible that we made some perfectly valid and correct changes to Construct, and some buggy graphics drivers stopped working. Unfortunately in this case the problem is in the graphics driver and it's infeasible for us to work around. It's a common problem in the industry. The best way to try to fix it is to install any available system software updates, or try updating your graphics driver.
Ashley... if your update is breaking GPU drivers (in my case, nvidia 3080) for paid subscribers, it doesn't really matter if your changes are technically valid or "correct." You've still broken GPU drivers for paid subscribers.
This is a not complex thing to get.
Oh, I thought it was my graphics card being outdated that was the issue with an ancient GTX 560 Ti (I haven't really played games in a long time) on an outdated system (Win 7) and not being able to get a driver that's more up to date.
But reading this it seems that upgrading wouldn't necessarily help even. C317 still works perfectly fine, but can't get C327 to work no matter what I do (initialising WebGL fails).
I'm afraid in the situation I described, the problem is categorically with the GPU driver, not Construct. This is a widely recognized issue in the industry and has repeatedly come up with both Construct 2 and Construct 3 through my career. Not everything that goes wrong with everyone's system is our fault! Please note our Forum & Community guidelines mention that continually insisting something is our fault despite our explanations comes under bad faith discussion and may result in moderation action.
So, here's the thing.
If all other software is working, including other software built upon the same tech to render graphics, but one piece of software is not? That's a software issue. Even if, from your POV, you've done everything by the book. Pretending workarounds, finding other ways to accomplish the same output, etc aren't part of software development doesn't help anyone, most of all paying users.
I'm afraid if you continue to insist we do the impossible even after the situation has been explained to the best of our ability and understanding, there is no satisfactory response we can provide and there is no use continuing the conversation. This is covered by the Forum & Community guidelines and I must remind you once again that moderation action may be taken if you continue down this path.
Please explain to me how this is a driver issue:
imgur.com/a/VH5DvzA
Those could certainly be graphics driver issues. Any kind of visual glitch often is related to a driver problem. The technology involved is extraordinarily complicated and often such issues are entirely unexplainable by outsiders. If that is the case then it is impossible for us to help and insisting we do so will mean you are pursuing the wrong solution and only make it more difficult and time consuming for you to resolve the problem, and also once again it is against the Forum & Community guidelines as it puts us in an impossible position - please note this is your third warning and if you continue to demand impossible things regardless of repeated warnings then we may proceed to temporary bans in order to enforce our Forum & Community guidelines.