This was an issue introduced with a Multi Cursor flag by the Scripting team. The flag has been disabled.
2 Likes
My viewport just disappeared just right now (and usually I fix it by minimizing and then restoring the window), I happenned to be switching places and when I opened another place I got the following qt errors via output, I’m posting them to see if the team working on Qt6 has a clue on the cause:
23:44:45.112 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f9a9931480, name="Qtitan::DockDocumentLayoutPanelClassWindow") , parent: QWidgetWindow(0x1fa244dd350, name="Qtitan::DockSplitLayoutPanelClassWindow") , transient parent: QWindow(0x0)
23:44:45.112 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f9a99313a0, name="Qtitan::DockSplitLayoutPanelClassWindow") , parent: QWidgetWindow(0x1f9a9931480, name="Qtitan::DockDocumentLayoutPanelClassWindow") , transient parent: QWindow(0x0)
23:44:45.112 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f9a99307d0, name="Qtitan::DockDocumentTabbedLayoutPanelClassWindow") , parent: QWidgetWindow(0x1f9a99313a0, name="Qtitan::DockSplitLayoutPanelClassWindow") , transient parent: QWindow(0x0)
23:44:45.112 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f9491655f0, name="startPageDocumentPanelWindow") , parent: QWidgetWindow(0x1f9a99307d0, name="Qtitan::DockDocumentTabbedLayoutPanelClassWindow") , transient parent: QWindow(0x0)
23:44:45.113 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f948f6f3f0, name="QWindowContainerClassWindow") , parent: QWidgetWindow(0x1f9491655f0, name="startPageDocumentPanelWindow") , transient parent: QWindow(0x0)
23:44:45.113 QT ERROR: External WM_DESTROY received for QQuickView(0x1f9487c52e0) , parent: QWidgetWindow(0x1f948f6f3f0, name="QWindowContainerClassWindow") , transient parent: QWindow(0x0)
(I have show QT errors enabled, and I always enable them, there are also sometimes errors about a qt timer, will edit this post when I get that again)
Another info I don’t think I’ve seen, it also affects the 2d viewport on the start screen:
You can still get into a page using the File dropdown
23:54:28.812 ▼ QT ERROR: QWindowsBackingStore::flush: GetDC failed (Invalid window handle.) (x2)
23:54:28.813 QT ERROR: QWindowsBackingStore::flush: GetDC failed (Invalid window handle.)
23:54:29.802 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f92b42aec0, name="Qtitan::DockDocumentLayoutPanelClassWindow") , parent: QWidgetWindow(0x1f98ba6c320, name="Qtitan::DockSplitLayoutPanelClassWindow") , transient parent: QWindow(0x0)
23:54:29.803 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f92b429f00, name="Qtitan::DockSplitLayoutPanelClassWindow") , parent: QWidgetWindow(0x1f92b42aec0, name="Qtitan::DockDocumentLayoutPanelClassWindow") , transient parent: QWindow(0x0)
23:54:29.803 QT ERROR: External WM_DESTROY received for QWidgetWindow(0x1f92b42a4b0, name="Qtitan::DockDocumentTabbedLayoutPanelClassWindow") , parent: QWidgetWindow(0x1f92b429f00, name="Qtitan::DockSplitLayoutPanelClassWindow") , transient parent: QWindow(0x0)
1 Like
Hey there – can you take a look at your Studio version and share that back?
Unfortunately I can’t access my laptop right now, but I believe it is the latest version (since before I launched, Studio decided to update first, or well in my case, it decides to install itself again, I don’t know why Studio keeps reinstalling itself)
I’m still being forced to reset my widget dock layout occasionally:
We have a fix going out this week in v577 that we are feeling pretty good about. It will not force a reset but rather prevent the corruption from happening with hopefully no side effects. If all goes well it will be live at some point on Wednesday 05/24.
Please let me know if you see a difference.
4 Likes
The update accomplished nothing.
It still throws an error and forcefully reset the damn layout!
On restart, it reverts my app to windowed, layouts all messed up.
Now if I lay all my layouts again and go into fullscreen mode, it’ll be reverted on the next restart without any error. Plus the dock layout error is becoming more frequent…
Jokes on you, I never dock any of my windows, it’s all floating just how I like it.
This is frustrating…
Last week’s update brought the number of people affected down from 200 to around 20. I’m sorry to hear you are one of the unlucky few.
- May I ask if you’re running Windows 10?
- Are you saying you float all of your panels and run the main window in full screen?
2 Likes
Yes, Windows 10.
| Edition | Windows 10 Pro |
|---|---|
| Version | 22H2 |
| Installed on | 07/11/2022 |
| OS build | 19045.2965 |
| Experience | Windows Feature Experience Pack 1000.19041.1000.0 |
This is a fullscreen screeshot :
I like my layout to be clean. Floating has just been the way to go for me…
Yeah we determined that this problem only happens in very specific versions of Windows 10… which is a part of the reason why it’s been so difficult to reproduce. But we want you to have your layout how you’d like so we’re going to keep looking at why this config seems to accelerate the problem.
I managed to reproduce it.
It happens when I open find/replace panel and I undock it!
I can type on it, but it won’t find anything and the app just hangs
Sorry to bump, but I can’t get my properties window to dock as of 6/10/2023. My OS if windows 10.
Seems like this bug when closing a place has been reintroduced since a recent update (maybe 3 or 4 days ago?)
I’ve also had the issues with the 3d viewport after either loading plugins or playtesting but that seems rarer.
1 Like
Our tracking of the issue has gotten very accurate over the past month and our most recent releases have drastically reduced the number of affected creators. Unfortunately you are one of the very unlucky few that have just the right combination of factors (specific versions of Windows, combination of plugins, etc.)
The “good” news is that now we have much less people affected, we can take a closer look at the remaining cases and work on additional fixes. So thanks for reporting!
2 Likes
@MeshOfPaul I had my viewport brick on me last night. It went black & got detached from the main studio window, and previously closed widgets were rendering multiple times where the viewport was.
It happened as soon as I opened the animation editor, I will try to get a solid reproduction later today.
Thanks for letting us know. We’ve made great progress on reducing the number of people impacted and how often they see this but we know it is still possible to happen — in particular if you run a lot of plugins and use Windows 10 (certain builds of Win10 are more likely to corrupt than others). We have a plan for a permanent fix that the engineering team is talking through now. But in the meantime, we still suggest a layout Reset for a quick, temporary fix.
1 Like
This excellent quick temporary fix only needs to be done 4 or 5 times a day. pretty embarrassing this has been happening now for nearly a year.
I agree it would be embarrassing if it were as simple as a bug we introduced or it was an error our code was creating. But that is not the case.
We have never stopped working on it. Both quick fixes and deep root cause analysis. Even though it only affects less than 0.01% of our active creators, we are working on some fundamental changes to how Studio docking and management works to prevent the condition(s) from happening. Thanks for being patient with us!
4 Likes
Hi all, just an update on docking corruption. We have drastically reduced the occurrences of this over the past few months, but we know there are still people affected by this daily. We have gathered a lot of data since the most recent changes and have a complete picture as to how this occurs and who it affects. At the current time we’re working to drive our instance count of this to 0 via a series of changes we’ll roll out in the coming weeks. There’s been a number of open threads on this from users experiencing this problem, and we’re consolidating them down to one to focus our messaging here. Please watch this thread for coming updates!
4 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.