The PlayGround DFX2 Forum

I just happened to play around with the crashing issue with the BO med 260. What I am finding out is that you might be able to get it to work with changing your resolution. It really isn't a fix but it is a workaround if you want to use your Windows 10 version. Hopefully the spring version fixes this..

Now I have a 4k monitor so you guys might have different results.
Sometimes you can run BO Mod 260 Med editor with no compatibility settings and other times you have to to get it to work on that resolution. Here are my results.

800 x 600 crashes
1024 x 768 crashes
1152 x 864 Ran once but crashed
1176 x 664 crashes
1280 x 720 crashes
1280 x 768 crashes
1280 x 800 crashes
1280 x 960 crashes
1280 x 1024 crashes
1360 x 768 crashes
1366 x 768 crashes
1440 x 900 crashes
1600 x 900 crashes
1600 x 1024 crashes
1600 x 1200 Works!!!!! No compatibility settings.
1680 x 1050 Works sometimes. Crashes most of the time on startup.
1768 x 992 Works majority of the time.
1920 x 1080 crashes
1920 x 1200 Works!!!!!! No compatibility settings.
1920 x 1440 crashes
2048 x 1536 crashes
2560 x 1440 crashes
3840 x 2160 Works!!!! no compatibility settings

So for me the resolutions that worked are.....
1600 x 1200
1600 x 1050 Works Somtimes if you can keep Override DPI compatibility check marked. Wants to remove itself.
1920 x 1200
3840 x 2160

Let me know if you run any of the resolutions above that worked for me worked for you!

huntor,

Not that I use the the med, but I have a Win 10 machine that came with a clean install of Win 10 that was upgraded to the Fall Creators edition. It is connected to an older Samsung monitor with native 1920x1200 resolution. Replaced the video card that came with the machine with an EVGA nVidia Geforce 9500 GT. Med starts at 1920x1200 and 1600x1200 without compatibility settings. All other available resolutions crash the med.

My top resolution is 1920 X 1080. Is there a way to change resolutions to something other than what is available in "Settings/Display"?

Bubba,

The short answer is, no.

Looks like you have an HD monitor if you are running at 1920x1080 which would be its native/recommended resolution. Unless you are running a very old video card, your monitor is limiting your ability to go higher than 1920x1080. That would be the maximum number of pixels the monitor is capable of displaying. You may, however, be able to go down to 1600x1200. If that resolution is not available in Display Settings, then it is your video card placing the limits on that.

Can go down to 1600 X 900 but not 1600 X 1200. I tried running the med at 1600 X 900 and it worked fine the first time. I closed the med and reopened it with the same resolution and encountered the same problem.
The monitor is a Benq GW2250 LED and is only a couple of years old and the video card is about 4 years old. It's a MSI R7770, GDDR5.

Your Benq monitor is limited to 1920x1080. My HD monitors are limited to that as well, however, in display settings, 1600x1200 is an option. All the video cards are nVidia. I would guess that your video card is limiting this choice. Lots of info on the web about your card but can't find the specs on supported resolutions. If you still have spec sheets that came with the card , you may find that info. It's odd that the 1600x1200 resolution is not available. It is possible that Windows updated your graphics drivers which may have removed that resolution. You can check this by typing "View Installed Updates" in the search box and click on the "Driver Updates" section.

I'll post again if I find anything that may be helpful.

Did the search but didn't find anything like "Driver Updates".

Hopefully the Windows 10 Spring Edition will fix this issue. But who knows if they will. They tried to make windows better at scaling and that is what is causing the program to crash. They used to leave it up to the developer to support the different resolutions. But microsoft tried to make it easier on the developer to make it scale better on high resolution PCs.

Bubba,

One final thing to look at. Open display settings. At the bottom, click on "Display Adapter Settings". In the window that comes up, at the bottom left, click on "List All Modes". If 1600x1200 is not present in the list that is displayed, then it is likely that your monitor does not support it. If it is in the list, you can set your desktop to 1600x1200 by selecting it in the list, then click OK. The window will close. Click apply on the display adapter properties window. You will be given the choice to use this resolution or revert to the previous setting.

Well I just tested this issue with Server 2019 beta which was released to the insiders group today. I changed my resolution to all the difference sizes available from virtualbox 1600 x 1200, 1280 x 1024, 1152 x 864, 1024 x 768, and 800 x 600.

The med ran in each. Hopefully that means this change is in the Spring Creators edition.