App crash when opening

[Pauven]

You forgot to include the "bugreport.txt" file, it should be in your root CMC directory.

[p64imp]

Did a star search in the directory but found no result for bugreport. Searched by bug*.* and hit no result in root....

Any config that is needed?

[Pauven]

So you never saw the MadExcept prompt show up to report a crash?

I see that you are running in Admin mode. Except for programming remote buttons, that's not needed. Perhaps you run everything as admin, but if you're doing anything special, please try just running with regular privileges.

Please rename the file "..\Skins\CMC_Default\CMC_Logo.png" to something else, like "CMC_Logo_disabled.png". This will turn off the splash screen. I've seen this cause problems for other PC's a long time ago, perhaps it's having an issue here.

[Pauven]

Just following up on this issue - any progress?

[p64imp]

thanks for the follow up. I returned my flow z13 as it had a screen defect. I'm working on a replacement. When it comes i will provide you with more detail. Thanks!

[p64imp]

Re-naming the logo gave me an access violation error and failed to boot. Re-naming it back made that error go away.

here's the bug report:

Please let me know what you find. I got my flow Z13 back and i REALLY want to get CMC working!

[Pauven]

Looks like the crash is happening when the form is adjusting it's size, probably to fit your screen resolution.

What is your screen resolution? In the crash report, I see something crazy like 1707 x 1067, which makes no sense to me.

EDIT: I just went back and re-reviewed the original debug logs you sent me. I missed it before, but now I see the scaling being adjusted using crazy values:

Code: Select all

[1.9465] Adjusting Scaling
[1.9467]   * PPI = 96
[1.9469]   * Scaling = 1.5
[1.9471]   * Resolution = 1706.66662597656x1066.66662597656
[1.9472]   * XScale = 0.888888895511627, YScale = 0.987654268741608
[1.9477]   * YPos = 53.3333015441895, XPos = 0
[1.9479]   * ImageModeBarYPos = -241.999969482422

It's been a few years since I've even thought about this, but CMC has a bug where certain resolutions and/or scaling cause a crash on startup. I'm pretty sure that's what is happening.

This is not a bug in my code, but rather a bug in the compiler. It showed up years ago in a compiler upgrade, and even now with several years worth of compiler revisions, it still happens. It was was a hard decision at the time, but I finally decided to live with the bug so that CMC could gain the benefits of the latest compiler.

I added logic to report the issue with certain scaling values, but I think you've triggered this bug using a previously working scaling value, probably because of your crazy resolution.

Since this is a HTPC, any chance you can hook it up to 1920x1080 or 3840x2160?

[Pauven]

For reference, here is the error message that shows if you have an unsupported scaling factor:

This CMC version does not support Windows Display Scaling at 175%, 225%, or 350%.

You currently have Display Scaling set to [YOUR VALUE HERE]%, which causes CMC to crash to desktop without any error messages on startup!

After clicking OK below, CMC will silently crash - Sorry!

To fix, please change your Windows Display Scaling to 100%, 125%, 150%, 200%, 250%, or 300%

Your scaling is 150%, so it 'should' be fine. But the one thing I learned about this bug years ago is that it made no sense, so you may also want to try other scaling values, even unsupported ones.

By the way, with my memory now refreshed, I understand why I felt your issue felt so familiar. I can't believe this old dragon rose from the dead, I thought I had slayed it.

[p64imp]

Hoping this is something that can be fixed? Switched to 125% and as you said it started up, though 125% resolution scaling on a flow z13 is microscopic. I really need that 150% scale on this device. It's a pain to switch resolution scale every time i want to open cmc though.

Any thoughts on this being resolved? Thanks!

[Pauven]

This is an issue I've struggled with for years. I've reported it to the compiler developer years ago. I've spent many hundreds of hours troubleshooting and trying to solve it.

My best advice to you is that it is unlikely to be resolved. I will look at it further, but I don't want to get your hopes up.

Instead of going smaller, try going larger. You may find 175% works.