SM64-Rom-Manager/SM64-Rom-Manager
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

Not starting with Custom UI font #4

New issue
Closed
opened 2022-05-16 20:20:32 +00:00 by pilzinsel64 · 20 comments
pilzinsel64 commented 2022-05-16 20:20:32 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Just as the title says, starting SM64 ROM Manager on Windows 7 (64-bit, Service Pack 1) will just result in a "Application has stopped working" error, with the only option being to close the program. Yes, I have .Net Framework 4.8 installed. Reinstalling it doesn't help. Does this program no longer support Windows 7?

image

Just as the title says, starting SM64 ROM Manager on Windows 7 (64-bit, Service Pack 1) will just result in a "Application has stopped working" error, with the only option being to close the program. Yes, I have .Net Framework 4.8 installed. Reinstalling it doesn't help. Does this program no longer support Windows 7? ![image](/uploads/fdf16f43b93bba4897fc89439202e385/image.png)
pilzinsel64 commented 2022-05-16 20:23:15 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

changed the description

By SK on 2022-05-16T20:23:15 (imported from GitLab)

changed the description *By SK on 2022-05-16T20:23:15 (imported from GitLab)*
pilzinsel64 commented 2022-05-29 14:11:05 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Well, should work with .NET Framework 4.8 installed.
Did you extracted the whole ZIP file before you started it?

The extracted program folder should look like this:

grafik

By Pilzinsel64 on 2022-05-29T14:11:05 (imported from GitLab)

Well, should work with .NET Framework 4.8 installed. Did you extracted the whole ZIP file before you started it? The extracted program folder should look like this: ![grafik](/uploads/3072a952c071ca8c8bd68ba56897bbb1/grafik.png) *By Pilzinsel64 on 2022-05-29T14:11:05 (imported from GitLab)*
pilzinsel64 commented 2022-06-02 04:32:28 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Yes, I extracted the full ZIP before running the program. The folder looks the same.

image

By SK on 2022-06-02T04:32:28 (imported from GitLab)

Yes, I extracted the full ZIP before running the program. The folder looks the same. ![image](/uploads/84fb4965df992e122836de3dc357c426/image.png) *By SK on 2022-06-02T04:32:28 (imported from GitLab)*
pilzinsel64 commented 2022-06-02 06:24:37 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

With a Windows 7 VM (officially from Microsoft for Testing IE) I've installed .NET Framework and Microsoft VC++ 2015.
But still it seems that I get an error at opening an Area in the Level Editor. But I'm not sure, if this happens only because I'm on a 32-bit system.

Could you answer me that three questions, please?

  • ❓ When do YOU you get your error?
  • ❓ Did you try with Microsoft VC++ 2015 installed?
  • ❓ Are you on a 32 or 64 bit system?

Screenshot of dying SM64 ROM Manager by opening the Level Editor:
grafik

But basically everything else (what I've tested) works fine.
grafik

Anyway, I should look into Windows 7 and 8 support. Because my plan is still upgrading to .NET 5+. It would drop support for Win7/8 but I could add support for Linux and Mac. An often asked feature.

By Pilzinsel64 on 2022-06-02T06:26:44 (imported from GitLab)

With a Windows 7 VM (officially from Microsoft for Testing IE) I've installed .NET Framework and Microsoft VC++ 2015. But still it seems that I get an error at opening an Area in the Level Editor. But I'm not sure, if this happens only because I'm on a 32-bit system. Could you answer me that three questions, please? - ❓ When do YOU you get your error? - ❓ Did you try with Microsoft VC++ 2015 installed? - ❓ Are you on a 32 or 64 bit system? Screenshot of dying SM64 ROM Manager by opening the Level Editor: ![grafik](/uploads/5af1698664eb6e3d06782a8ad71151a9/grafik.png) But basically everything else (what I've tested) works fine. ![grafik](/uploads/4dbc5d1e4d1250b0977996e329caedf2/grafik.png) Anyway, I should look into Windows 7 and 8 support. Because my plan is still upgrading to .NET 5+. It would drop support for Win7/8 but I could add support for Linux and Mac. An often asked feature. *By Pilzinsel64 on 2022-06-02T06:26:44 (imported from GitLab)*
pilzinsel64 commented 2022-06-04 01:12:46 +00:00 (Migrated from git.pilzinsel64.de)
Copy link
  1. The error occurs about 15-20 seconds after I launch the program. Oddly, the program's window doesn't even appear.
  2. I already have MSVC++ 2015 installed.
  3. 64-bit CPU and OS.

If you'd like, I can record a video of what happens when I launch the program, so you know exactly how long it takes before it crashes.

By SK on 2022-06-04T01:18:20 (imported from GitLab)

1) The error occurs about 15-20 seconds after I launch the program. Oddly, the program's window doesn't even appear. 2) I already have MSVC++ 2015 installed. 3) 64-bit CPU and OS. If you'd like, I can record a video of what happens when I launch the program, so you know exactly how long it takes before it crashes. *By SK on 2022-06-04T01:18:20 (imported from GitLab)*
pilzinsel64 commented 2022-06-04 06:59:05 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Alright, thank you! @SKCro

First of all, of course you can make a video. The most time this helps a lot. ^^
You can upload it here, if you want: https://cloud.pilzinsel64.de/s/J5Br7r7w4Q448NH
Password: bugreportfiles

Well, before the main window shows and about 15-20 seconds after starting it, that could be a lot of things, but one you can still try:
Remove the file "Settings.json" to reset all settings for the SM64 ROM Manager and try again if the problem still exists. You'll find it in %appdata%\SM64 ROM Manager\Settings.json
image

If this doesn't fix your problem, then please help me with getting some more informations:

  • Make the video, you said. ^^'
  • Does this problem still exists on Version 1.14.1.1? In v1.14 there was a bug with the updated but that shouldn't end like this and just do nothing. Well, it's a try. :D
  • Where is the ROM Manager app directory located? On Desktop/Documents, on a second hard drive or on a network share? Could you tell me please the path (without real username)?
  • Does one of the other programs start? If yes, wich ones does start and which not?
    • Apply PPF.exe
    • SM64 Model Importer.exe

By Pilzinsel64 on 2022-06-04T06:59:05 (imported from GitLab)

Alright, thank you! @SKCro First of all, of course you can make a video. The most time this helps a lot. ^^\ You can upload it here, if you want: https://cloud.pilzinsel64.de/s/J5Br7r7w4Q448NH \ Password: `bugreportfiles` Well, before the main window shows and about 15-20 seconds after starting it, that could be a lot of things, but one you can still try:\ Remove the file "Settings.json" to reset all settings for the SM64 ROM Manager and try again if the problem still exists. You'll find it in `%appdata%\SM64 ROM Manager\Settings.json` ![image](/uploads/800936f9dec15de596a70c8d14d46f2a/image.png) If this doesn't fix your problem, then please help me with getting some more informations: - Make the video, you said. ^^' - Does this problem still exists on Version 1.14.1.1? In v1.14 there was a bug with the updated but that shouldn't end like this and just do nothing. Well, it's a try. :D - Where is the ROM Manager app directory located? On Desktop/Documents, on a second hard drive or on a network share? Could you tell me please the path (without real username)? - Does one of the other programs start? If yes, wich ones does start and which not? - Apply PPF.exe - SM64 Model Importer.exe *By Pilzinsel64 on 2022-06-04T06:59:05 (imported from GitLab)*
pilzinsel64 commented 2022-06-04 16:13:12 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Heya! Thank you for being so willing to help. It turns out the problem happened because I changed my system font (specifically, I changed it to Source Sans Pro), and ROM Manager didn't like that for some reason. Changing it back to the default font (Segoe UI) seems to fix the issue. If you'd like, I can create a separate issue that outlines this, or we can continue using this issue if you'd like. I feel a little bit stupid about this, to be honest.

By SK on 2022-06-04T16:15:27 (imported from GitLab)

Heya! Thank you for being so willing to help. It turns out the problem happened because I changed my system font (specifically, I changed it to Source Sans Pro), and ROM Manager didn't like that for some reason. Changing it back to the default font (Segoe UI) seems to fix the issue. If you'd like, I can create a separate issue that outlines this, or we can continue using this issue if you'd like. I feel a little bit stupid about this, to be honest. *By SK on 2022-06-04T16:15:27 (imported from GitLab)*
pilzinsel64 commented 2022-06-05 07:43:16 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

changed title from {-SM64 ROM Manager won't start on Windows 7-} to {+Not starting with Custom UI font+}

By Pilzinsel64 on 2022-06-05T07:43:16 (imported from GitLab)

changed title from **{-SM64 ROM Manager won't start on Windows 7-}** to **{+Not starting with Custom UI font+}** *By Pilzinsel64 on 2022-06-05T07:43:16 (imported from GitLab)*
pilzinsel64 commented 2022-06-05 07:47:19 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Ah, nice! ^^
Well, then let me test this out myself and try to fix it. Probably an issue with DotNetBar.

Don't worry btw. It's normal that so a minor thing does so intersting bugs. xD
We will keep this issue, I guess. I just renamed the title.

Will add notes to here if I got any infos/fixes.

Just a last question @SKCro: Does the problem happen with every font or just with this (or a few) selected one(s)?

By Pilzinsel64 on 2022-06-05T07:47:19 (imported from GitLab)

Ah, nice! ^^ \ Well, then let me test this out myself and try to fix it. Probably an issue with DotNetBar. Don't worry btw. It's normal that so a minor thing does so intersting bugs. xD \ We will keep this issue, I guess. I just renamed the title. Will add notes to here if I got any infos/fixes. Just a last question @SKCro: Does the problem happen with every font or just with this (or a few) selected one(s)? *By Pilzinsel64 on 2022-06-05T07:47:19 (imported from GitLab)*
pilzinsel64 commented 2022-06-05 18:37:29 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

I'm not sure. I forgot to mention I used Winaero Tweaker to change the UI/System font. Maybe you can use that and attempt to change the font on the VM?

By SK on 2022-06-05T18:37:29 (imported from GitLab)

I'm not sure. I forgot to mention I used Winaero Tweaker to change the UI/System font. Maybe you can use that and attempt to change the font on the VM? *By SK on 2022-06-05T18:37:29 (imported from GitLab)*
pilzinsel64 commented 2022-06-05 21:29:29 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Ah, thanks! That's a good hint. Will try it with the Winare Tweaker (like to use it myself).
Well, I'll try with the VM. Hope I can reproduce it. Just need a little bit time the next few days. :D

By Pilzinsel64 on 2022-06-05T21:29:29 (imported from GitLab)

Ah, thanks! That's a good hint. Will try it with the Winare Tweaker (like to use it myself). Well, I'll try with the VM. Hope I can reproduce it. Just need a little bit time the next few days. :D *By Pilzinsel64 on 2022-06-05T21:29:29 (imported from GitLab)*
pilzinsel64 commented 2022-06-13 19:05:51 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Alright. Have you been able to test it? It's been about a week. Sorry I didn't reply for so long.

By SK on 2022-06-13T19:05:51 (imported from GitLab)

Alright. Have you been able to test it? It's been about a week. Sorry I didn't reply for so long. *By SK on 2022-06-13T19:05:51 (imported from GitLab)*
pilzinsel64 commented 2022-06-14 05:45:10 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Ah, no problem. Sorry from me, because I had to wait for my new SSD drive. xD

I did a quick test now by installing the whole font family "Source Sans Pro". After chaning the system font, message font and title bar font to the default Source Sanse Pro font using the latest version of Winareo Tweaker, I restarted the system.

Well, it seems to work:
grafik

Some UI elements still uses the default font, but that's more a problem by DotNetBar.

What font did use for what?
Are you able to reproduce your problem with the Win7 VM from here (IE11)? (If you don't have the requierements for running VMs, don't worry - just If you can. We should get it also without.)

By Pilzinsel64 on 2022-06-14T05:45:59 (imported from GitLab)

Ah, no problem. Sorry from me, because I had to wait for my new SSD drive. xD I did a quick test now by installing the whole font family "Source Sans Pro". After chaning the system font, message font and title bar font to the default Source Sanse Pro font using the latest version of Winareo Tweaker, I restarted the system. Well, it seems to work: ![grafik](/uploads/f829e0a281193bb8b9fdb46f8750fb5c/grafik.png) Some UI elements still uses the default font, but that's more a problem by DotNetBar. What font did use for what? \ Are you able to reproduce your problem with the Win7 VM from [here](https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/) (IE11)? (If you don't have the requierements for running VMs, don't worry - just If you can. We should get it also without.) *By Pilzinsel64 on 2022-06-14T05:45:59 (imported from GitLab)*
pilzinsel64 commented 2022-06-14 21:24:33 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Have you tried changing the menubar font in Winaero Tweaker? That may trigger the error in ROM Manager.

image

By SK on 2022-06-14T21:24:45 (imported from GitLab)

Have you tried changing the menubar font in Winaero Tweaker? That may trigger the error in ROM Manager. ![image](/uploads/af07773f04341e4c16fdec5e8e1bd369/image.png) *By SK on 2022-06-14T21:24:45 (imported from GitLab)*
pilzinsel64 commented 2022-06-15 05:04:05 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Ah, yes I did that too, everywhere, where possible in Advanced Appearance Settings.

Now I also changed the font size (where available) to check out if this does something.
Still works:
grafik

By Pilzinsel64 on 2022-06-15T05:04:05 (imported from GitLab)

Ah, yes I did that too, everywhere, where possible in Advanced Appearance Settings. Now I also changed the font size (where available) to check out if this does something. \ Still works: ![grafik](/uploads/b5e636fc713d0c8c244675ce1762e61f/grafik.png) *By Pilzinsel64 on 2022-06-15T05:04:05 (imported from GitLab)*
pilzinsel64 commented 2022-06-19 23:44:39 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Odd. I have changed my system font back to Source Sans Pro and it crashes. I will experiment with the font options and tell you which specific option causes ROM Manager to stop working. I will record a video of what happens as well.

By SK on 2022-06-20T03:35:25 (imported from GitLab)

Odd. I have changed my system font back to Source Sans Pro and it crashes. I will experiment with the font options and tell you which _specific_ option causes ROM Manager to stop working. I will record a video of what happens as well. *By SK on 2022-06-20T03:35:25 (imported from GitLab)*
pilzinsel64 commented 2022-06-27 14:37:06 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Sorry I haven't been on in a while. I am physically away from my PC and cannot test. I may be able to test in a few days. I'm so sorry to keep you waiting.

By SK on 2022-06-29T05:20:44 (imported from GitLab)

Sorry I haven't been on in a while. I am physically away from my PC and cannot test. I may be able to test in a few days. I'm so sorry to keep you waiting. *By SK on 2022-06-29T05:20:44 (imported from GitLab)*
pilzinsel64 commented 2022-07-04 01:37:01 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

So it turns out setting the system font back to Source Sans Pro triggers the crash, again. I'm not sure what's going on. Is there a log file I can send that could help you? I'll also record a video and upload it to the link you provided earlier.

By SK on 2022-07-04T01:37:01 (imported from GitLab)

So it turns out setting the system font back to Source Sans Pro triggers the crash, again. I'm not sure what's going on. Is there a log file I can send that could help you? I'll also record a video and upload it to the link you provided earlier. *By SK on 2022-07-04T01:37:01 (imported from GitLab)*
pilzinsel64 commented 2022-07-04 05:47:03 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

Thank you very much! Well, sadly, I also don't know what's going on.
Sadly I also haven't a full qualified log system in ROM Manager yet.

Well, the error can only happen before the visual theme has been setted. That helps a lot already.

So, I created a quick debug build that shows a bunch of message boxes after some jobs at startup. Please tell me the text of the last message box you'll get. Download it here: https://cloud.pilzinsel64.de/s/XppKPWc2em4Y6pX

By Pilzinsel64 on 2022-07-04T09:56:17 (imported from GitLab)

Thank you very much! Well, sadly, I also don't know what's going on. \ Sadly I also haven't a full qualified log system in ROM Manager yet. Well, the error can only happen before the visual theme has been setted. That helps a lot already. So, I created a quick debug build that shows a bunch of message boxes after some jobs at startup. Please tell me the text of the last message box you'll get. Download it here: https://cloud.pilzinsel64.de/s/XppKPWc2em4Y6pX *By Pilzinsel64 on 2022-07-04T09:56:17 (imported from GitLab)*
pilzinsel64 commented 2022-07-06 21:46:12 +00:00 (Migrated from git.pilzinsel64.de)
Copy link

So it turns out, I forgot to mention that I have all my fonts set to Source Sans Pro SemiBold (because Windows doesn't antialiase the font for whatever reason), not regular Source Sans Pro, which might be causing the crash (since you only tried normal Source Sans Pro). I will try the the build you sent and make a video of when exactly it crashes.

Edit: I tried the debug build, and it's instantly crashing (with no message boxes other than "This program has stopped working") even with the default font. However, the non-debug build isn't crashing. Any ideas?

By SK on 2022-07-07T00:37:14 (imported from GitLab)

So it turns out, I forgot to mention that I have all my fonts set to Source Sans Pro **SemiBold** (because Windows doesn't antialiase the font for whatever reason), not regular Source Sans Pro, which might be causing the crash (since you only tried normal Source Sans Pro). I will try the the build you sent and make a video of when exactly it crashes. Edit: I tried the debug build, and it's instantly crashing (with no message boxes other than "This program has stopped working") even with the default font. However, the non-debug build isn't crashing. Any ideas? *By SK on 2022-07-07T00:37:14 (imported from GitLab)*
pilzinsel64 (Migrated from git.pilzinsel64.de) closed this issue 2024-08-13 19:17:19 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
stable/1.14
v1.14.14
v1.14.12
v1.14.11
v1.14.10
v1.14.9
v1.14.7
v1.9.15
Labels
Clear labels   
bug

   
critical

   
discussion

   
documentation

   
duplicate

   
enhancement

   
invalid

   
new module

   
refactoring

   
suggestion

   
validating

   
wontfix
No labels
bug
critical
discussion
documentation
duplicate
enhancement
invalid
new module
refactoring
suggestion
validating
wontfix
Milestone
Clear milestone
No items
No milestone
Version 1.15
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SM64-Rom-Manager/SM64-Rom-Manager#4
No description provided.