I have just started using Unreal Engine 5.7 and encountered the following:
After right or middle clicking inside of the scene viewport, the editor will not let me use any options of context menus / popups outside of the viewport.
If i then right and middle click (depending on what i pressed inside) outside of the scene view that seems to release this lock of that specific mouse button, allowing me to use context menus again.
The issue is that I use middle and rightclick a lot to navigate around the viewport so this is a constant issue.
I have confirmed this is not the case in UE 5.6.1
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Stability
Steps to Reproduce
Open fresh project
Add a cube shape via quick add - working fine
Right click in the viewport
Middle mouse button click in the viewport
Open quick add
Try to click Shape → Cube - clicks through the option and selects whatever is behind it in the viewport
Rightclick outside of the viewport
Try to click Shape → Cube - clicks through the option and selects whatever is behind it in the viewport
Middle click outside of the viewport
Try to click Shape → Cube - working again
Expected Result
Left or middle click should not lock up context menu options
Observed Result
Clicking through context menu options
Platform(s)
Windows 11
Video
Additional Notes
I am rightclicking outside of the viewport in the video everytime before it works again
I’m having the same issue on 5.7 as well. It also affects the blueprint editor, making it almost impossible to work with.
I checked on a different computer and that didn’t seem to have the issue so I’m assuming there’s some specific software that might be causing the issue, though I’m not sure what it is. I’ve tried ending different processes but it keeps happening.
Hopefully there’s a fix, but I’m gonna keep messing around with my PC to see if something works in the mean time.
Hey, sorry but the discord overlay issue was a seperate one for me, this bug is still occuring even with the discord overlay turned off (it solved what you described but my specific issue persists)
I tested this exact thing on my work laptop today and could not reproduce this issue so it might have to do with my hardware/software on this pc, if you need further info I am happy to provide details.I also turned off all other software that I could turn off without compromising the stability of my system and the issue still persisted, same test with a different mouse, issue persisted.
You can see the effect of this specific bug in the video above
Would appreciate if somebody could take a closer look, I could not fix this with turning off discords overlay and I think the cause may be something different, the bug behaves different aswell. It prevents me from using UE 5.7 at this point.
Formatting is a viable solution for me right now… Every other Engine version is working for me so it’s something that must be wrong with 5.7 specifically and must be fixed by Epic…
I have the same issue on 5.7.1 (not 5.6.1), though my diagnosis was different. Running Unreal in a window, having a new 3rd person template opened. Everything works until I click the viewport.
If I left-click the viewport and hold a while (to move the view a bit), and then left-click the Unreal window title bar, the window does not move. If I release and left-click the title bar again, now the window moves.
If I right-click the viewport and hold a while (to rotate the view) and then left-click the Unreal window title bar, the window won’t move no matter how many times I left-click the title bar and release. This can be fixed by alt-tabbing out and back in.
If I middle-click the viewport and hold a while to move the view, result (and fix) is the same as with right-click.
If I use RMB or MMB to move the view, then also the Quick add → Shapes → cube (or another shape) don’t work, and also I cannot switch to landscape or any other mode through the drop-down list etc. RMB or MMB outside the viewport also helps, but I didn’t figure out this solution myself. I just noticed alt-tab works.
I have a quite fresh Windows install and I’m not willing to reinstall everything now. This worked though - I conclude somehow the worker thread for raw input is broken.
WindowsApplication.UseWorkerThreadForRawInput 0
PS. Originally I thought this was connected to the Huion drawing tablet driver, but I think I ruled that out.
