Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.10 does not work with multiple monitors #456

Closed
Vexzilla1970 opened this issue Oct 31, 2022 · 15 comments
Closed

1.10 does not work with multiple monitors #456

Vexzilla1970 opened this issue Oct 31, 2022 · 15 comments
Assignees

Comments

@Vexzilla1970
Copy link

I check the box for multiple monitors and it crashes the program and can not be recovered or even copied over with a different version.

@Vexzilla1970
Copy link
Author

THe program starts but immediately crashes. I cannot access the settings to turn multiple monitors off.. The only version that now works is 1.8. I dare not check multiple monitors again for fear of crashing it also...

@dremin
Copy link
Owner

dremin commented Nov 8, 2022

If you close RetroBar and delete the %localappdata%\RetroBar folder that should reset the settings and allow you to use the newer version. I'd like to troubleshoot the crash some more to try and fix the issue you're running into. When it crashes, do you see any error messages? Does an error appear in the Windows application event log?

@Vexzilla1970
Copy link
Author

Vexzilla1970 commented Nov 8, 2022

No error messages, yes, it appears in the event log... Thank you for your help.

@dremin
Copy link
Owner

dremin commented Nov 14, 2022

@Vexzilla1970 What does it say in the event log?

@Vexzilla1970
Copy link
Author

Vexzilla1970 commented Nov 14, 2022

Faulting application name: RetroBar.exe, version: 1.10.2.38481, time stamp: 0x62cf0990
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2130, time stamp: 0xb0fac6c9
Exception code: 0xe0434352
Fault offset: 0x000000000002cd29
Faulting process id: 0x340
Faulting application start time: 0x01d8f277062c7a35
Faulting application path: C:\Program Files\RetroBar\RetroBar.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: c91835c8-5cff-415f-9580-c9c076164377
Faulting package full name:
Faulting package-relative application ID:

The next error stated this...

Application: RetroBar.exe
CoreCLR Version: 6.0.1022.47605
.NET Version: 6.0.10
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception (1816): Not enough quota is available to process this command.
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

@dremin
Copy link
Owner

dremin commented Nov 19, 2022

Thanks @Vexzilla1970, that's exactly what I needed. This is actually a problem I've encountered once but a reboot fixed it so I wasn't able to investigate further. Basically, the app is getting into a loop trying to place the taskbar in the correct position, but Explorer is moving it back.

@Vexzilla1970
Copy link
Author

Yep, it works now... sadly, i have now another problem.... with low resolution full screen games.... retrobar does not like them at all... it freaks out when I open the game and when i close the game it gets stuck trying to position itself on the monitors... I have attached the log files that I believe are associated with this issue...
Logs.zip

@kuwii
Copy link

kuwii commented Jan 6, 2023

@dremin FYI, I can stably repro this when my 2 monitors have different scales (one is 100% and another is 150%).

image

@aahei
Copy link

aahei commented Jan 27, 2023

@dremin FYI, I can stably repro this when my 2 monitors have different scales (one is 100% and another is 150%).

image

Second.

@dremin
Copy link
Owner

dremin commented Feb 3, 2023

Thanks, I can reproduce this reliably now and am working on a fix.

@dremin
Copy link
Owner

dremin commented Feb 4, 2023

Could you please test this build and let me know if it works as expected now? I believe I have fixed the issue. It's an x64 build, let me know if you need a different arch.
RetroBar.zip

@kuwii
Copy link

kuwii commented Feb 4, 2023

Could you please test this build and let me know if it works as expected now? I believe I have fixed the issue. It's an x64 build, let me know if you need a different arch. RetroBar.zip

Thanks for the fix. It works for me.

dremin added a commit that referenced this issue Feb 5, 2023
dremin added a commit that referenced this issue Feb 5, 2023
@dremin dremin self-assigned this Feb 6, 2023
@ThePunisher69
Copy link

ThePunisher69 commented Mar 23, 2023

I've been running Retrobar for awhile now and all of the sudden I am experiencing issues with the notification area icons. Most of them don't even show up.

Those that do show up don't work right. Either I can't interact with them at all (right-click or double click) or the right-click context menu flyout appears in the wrong place.

What I noticed is that these problems all started occuring when I got a new monitor: which involved me messing with my scaling settings in Windows. I initially landed on similar settings as kuwii: A 4k screen @ 200% scaling and a 1440p screen @ 100% scaling.

I set them both at 125% scaling and rebooted and now everything is working as expected.

Not looking for this to be "fixed" per se, just wanted to put it out there in case anyone stumbles across this on Google and has similar issues to me. In my case it was mismatched scaling causing it.

tldr: I think the crashing part is fixed, but there's still some odd behavior with Retrobar on multiple monitors with mismatched scaling.

@dremin
Copy link
Owner

dremin commented Mar 24, 2023

@ThePunisher69 You are correct, there are some issues that I have been working on in this area. I'll update this space when I have a new test build ready with those fixes.

@dremin
Copy link
Owner

dremin commented May 7, 2023

The confirmed fix is available in the latest release.

@dremin dremin closed this as completed May 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants