-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
wxWidgets Debug Alert #6
Comments
Sadly, I haven't found any way to reproduce this. It looks related to the language or locale settings, but neither changing the language of Aegisub nor the display language of Windows makes Aegisub show this message on my machine. I do have one more question, though - does this still happen if you delete your Aegisub config file or move it somewhere else? You said that this doesn't occur on the portable versions, and the location of the config file is the only nontrivial difference between the installed and portable versions. |
Thanks for your help. I'll try reproducing this. I deleted the Aegisub config file but I still got the alert. So, I believe the next step is to figure out which part of my old Aegisub folder in %appdata% was having conflicts with this particular build. |
Turns out that if a script which relies on utf8 library is present, this alert shows up in this particular build of Aegisub. |
Ah - I could reproduce it now, and somehow it seems to have been introduced by merging wangqr's "Time to video" feature of all things. I'll take a closer look soon. |
So I found out two things:
So I sent all the new icon files through ffmpeg once and rebuilt, and the assertion errors stopped. |
Thank you very much for your help. The problematic code seems to be |
After the installation of the releases on Windows 10, every time that Aegisub is opened, the message in the image is encountered twice. Both installations for "Feature Release 04" and "Feature Release 05" face the same issue. Furthermore, the Portable versions work just fine. I also tested all the other major Aegisub builds for windows and none of them return this alert.
The text was updated successfully, but these errors were encountered: