(2014-10-19, 16:45)Angelscry Wrote: (2014-10-18, 22:43)M4tt0 Wrote: Have been trying to get Colin McRae 2005 running via the standalone launcher but does not work. I think because of resolution issues.
Kodi/XBMC is set to run on 720p on my HD ready TV. CMR runs on 1080i in compatibility mode. When I launch it from within Kodi I can see that the TV tries to switch the resolution to 1080i but then gets stuck. The picture returns to Kodi and Kodi wants to use 1080i too (which is sub-optimal). CMR continues to run in the background but I get no picture.
Running Helix Alpha 3 on a Win 8.1 system. I'm using XBMC Launcher to boot into kodi directly.
Any advice appreciated...
Even if XBMC is started into Windowed mode?
Thanks for your help, guys!
@S3N1L3AN1MAL: I unfortunately could not find such settings with my integrated Intel HD5000 graphics driver, so got stuck there.
@Angelscry: Using windowed mode has not resolved the issue but helped to improve the situation to some extent because I could then see what was going on on the desktop:
(1) CMR2005 seems to be launched correctly in 1080i (the ONLY compatible resolution for the game / TV combination), my AVR recognizes the resolution switch and I can see CMR starting filling the full screen
(2) Apparently XBMC Launcher regularly tries to enforce the focus to be on XBMC, so CMR keeps running in the background, but loses focus.
(3) When XBMC is refocused it "thinks" it should run in 1080i and asks me whether I want to switch the resolution. When I decline (as I want to keep 720p), XBMC sets the resolution correctly, but the AVR keeps the TV in 1080i (I see XBMC but it is too small for the screen). Resetting the resolution in XBMC "fixes" the situation only that CMR still runs in the background ideling.
I figured that I can "register" CMR in the XBMC Launcher GUI settings and, thus, prevent the application from trying to refocus on XBMC. Now I can actually play (the sound is still missing but I guess that is due to WASAPI settings and exclusive mode). However, when I quit the game issue (3) above persists. Any idea how to resolve that?