[p]We have received various bug reports regarding FireAlpaca SE 3.0. We sincerely apologize for the inconvenience. FireAlpaca SE is developed using the Qt development environment. We recognize that upgrading the development environment from Qt5 to Qt6 during the development of version 3.0 has caused various issues. Until the situation improves, you can use the “previous version 2.x” via Steam's Beta feature. Please refer to this article: [dynamiclink][/dynamiclink][/p][p][/p][p]The issues we are currently aware of are as follows. While there are many challenges and fixes are difficult, most can be resolved by reverting the development environment back to Qt5. Therefore, we are considering abandoning the Qt6 transition and reverting to Qt5.[/p][p][/p][h3](1) Issues with Pressure Sensitivity[/h3][p]In FireAlpaca SE 3.0, pressure sensitivity is no longer detected unless Windows Ink is enabled. While previous versions (2.x) supported Wintab, the adoption of Qt6 in 3.0 made handling Wintab impossible, making it essential to enable Windows Ink from the tablet driver. Since many users prefer Wintab, we are currently investigating whether it can be made compatible with Wintab as well.[/p][p][/p][h3](2) UI Scaling Issue (Resolved)[/h3][p]When setting the desktop UI display scale to 125%, labels and other UI controls became excessively large. This occurred because Qt5 rounded 125% to 100%, whereas Qt6 applied 125% as-is. This issue appears to be resolved in version 3.0.28.[/p][p][/p][h3](3) Application Fails to Launch Issue[/h3][p]We have received reports from some users that FireAlpaca SE 3.0 fails to launch. We are currently investigating this issue. If the application fails to launch, Explorer should open and display the configuration files. A debug log file named StartupLog.txt should be generated there. Please paste the contents of this file into the thread below.
https://steamcommunity.com/app/458750/discussions/0/689742221292886915/[/p][p][/p][h3](4) Auto-Save Issues[/h3][p]Auto-save functions when saving MDZ files, but it was not supported for other file formats like MDP or PNG files. We are currently implementing this to behave as similarly as possible to version 2.x (planned for implementation in 3.0.29).[/p][p][/p][h3](5) Performance Degradation[/h3][p]Some users have reported experiencing slower performance compared to previous versions. Since the changes to the paint engine (the core component) are not significant, there may be another cause. We would appreciate it if you could share how to reproduce this issue.[/p][p][/p][h3](6) Cursor Becoming an Arrow Issue[/h3][p]We've received reports that the cursor on the canvas changes to the OS's default arrow cursor. Since there have been no code changes since 2.x, this appears to be a bug caused by specification changes in Qt6. If this issue persists in 3.0.28, please let us know.[/p][p][/p][h3](7) Window Docking Issues[/h3][p]When using a stylus, there is a bug preventing the docking of the Color Window and Layer Window. As this is a Qt6 bug, it may take some time to resolve.[/p][p][/p][h3](8) Low Frame Rate (Stuttering) When Performing Palm Gestures with a Stylus[/h3][p]Unlike in 2.x, performing palm gestures with a stylus generates an extremely high volume of update events. Currently, it is unavoidable that these update events become congested. As a workaround, the update frequency is limited to 15 fps during stylus operation. We are investigating whether smoother, mouse-like operation can be provided with the stylus.[/p][p][/p][h3](9) Fails to launch due to virus detection[/h3][p]Since we use Qt6, a relatively new development environment, there is a high likelihood of false positives by antivirus software. If you encounter launch failures, please let us know the name of your antivirus software.[/p][p][/p][h3](10) Issues when using a dark theme desktop[/h3][p]If Windows' own dark theme is enabled, setting FireAlpaca SE to “Light UI” will result in a completely dark UI. This is a bug (also caused by specification changes introduced in Qt6). Resolving this is likely to take some time.[/p][p][/p][h3](11) Mouse click positions in the layer window are offset at specific desktop UI scaling levels (e.g., 150%).[/h3][p]Under investigation.[/p][p][/p][p][/p][p]Thank you for your continued support 🙇♂️[/p]