UnityStandaloneFileBrowser: [Bug] Didn't open dialog in unity 2023.2
It seem VistaOpenFileDialog are not working in unity 2023, are there any fix?
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 2
- Comments: 30
It seem VistaOpenFileDialog are not working in unity 2023, are there any fix?
A bug has been registered on the issue tracker. Please vote for early fix. https://issuetracker.unity3d.com/issues/windows-com-throws-the-invalidprogramexception-when-using-ookii-dot-dialogs-library
I have submitted a bug report to Unity regarding this error. Currently under review, there was no problem up to Unity2023.2.0a14, and it was found that an error occurred from Unity2023.2.0a15.
UUM-62035 is included in the Fixes section of the release notes for Unity6000.0.0b15. And sure enough, the dialog comes up and no errors occur.
@achimmihca
Updated my project to 2023.2.20f1 and I confirm the issue is gone for me 😀
Unity2023.2.20 also contains UUM-62035 in the Fixes section.
“Fixed in 6000.0.0b14” and “Fix In Review for 2023.2.20f1” on issue tracker
@anonymous2585 I tried it with Unity2023.2.12f1 and the dialog worked. This is that Unity project. https://www.dropbox.com/t/52h90sq5zGbxrvvf
“In progress” on issue tracker🙏
Backports also merged into 2023.2 and 2023.3.
Yes, that is exactly what that PR fixes 😃.
Perhaps https://github.com/Unity-Technologies/mono/pull/2003 will fix it.
@anonymous2585 Yes, unfortunately in the mono version of FileDialog, the AutoUpgradeEnabled property does not work, so the old style dialog is displayed. https://github.com/Unity-Technologies/mono/blob/unity-main/mcs/class/System.Windows.Forms/System.Windows.Forms/FileDialog.cs#L387-L392 Therefore, you have two options: use Unity 2023.1 or earlier, or wait until the bug is fixed.
Also, the mono version of System.Windows.Forms.dll exists in the following path.
@zadinvit You can use OpenFileDialog with System.Windows.Forms.dll. However, the old style dialog is displayed.
@Thaina I deleted the Ookii.Dialogs.dll and replaced it with the source, but the same error occurs, so I don’t think it is caused by the dotnet standard update.