You could always try using compatibility mode of Win7, that might work.
You could always try using compatibility mode of Win7, that might work.
Thanks for the suggestion Zim. Unfortunately that didn't work...but, I tried some of the other compatibility settings, and checking the "Disable display scaling on high DPI settings" box worked! So it looks properly now in fullscreen mode for me--I just needed the combination of the DXGL program, and that compatibility setting.
Thanks for leading me down the right path.
I definitely need help with this. So, I am using the "Lost Isle Build" of ZC to play, of course, Lost Isle. I am running 64 bit Windows 8 on a laptop. I have tried every suggestion here, but the game either lags on a low framerate and eventually crashes when full screen or crashes whenever I try to alter the screen size.
Using Lost Isle Build I cannot find the option to just click "large" or "small" window instead of booting straight away into fullscreen, which causes the issues. Right clicking the shortcut to force it into a smaller window is not helping. All the instructions here are not helping.
Can someone please help me troubleshoot this? It crashes anytime I try to play... I have played and beaten the game, almost, on the same laptop with windows 8 but had to use the Large Window on the latest ZC build... but that has a lot of compatibility issues that cause wizrobes to toss omnidirectional wind blasts and script errors with text and all that BS so I want to use the proper build.
Thank you for your assistance.
Computer specifications:
Windows 10 Pro x64 | Intel Core i7 @ 2.66GHZ | Asus P6T Motherboard | 6GB DDR3 RAM | Integrated Sound | Nvidia Geforce 560 Ti 2048MB PCI-E | Corsair AX760 Power Supply | Thermaltake Armor+ MX case
Unfortunately DXGL is not currently compatible with High DPI settings, however as icedawg discovered the "Disable display scaling on high DPI settings" compatibility setting can be used to work around this issue. Since this is now an issue for some users, I will investigate fixing the issue so the compatibility setting is no longer needed.
There are currently 2 users browsing this thread. (0 members and 2 guests)