Project

General

Profile

Bug #1973

App init failed: CreateDirError (1.14.5)

Added by Incantator over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Defect
Target version:
-
Start date:
2015-02-12
% Done:

0%

Tags:
Unicode

Description

I installed the latest stable Doomsday engine, which also had Snowberry ver 1.6. I installed it successfully and tried to go for Ultimate Doom. But this error message poped up:

App init failed: CreateDirError cannot create directory in C:\Users\????

something like this (I cannot duplicate this error message anymore so I couldn't upload the screenshot but this is the most of the original error message). The current username in my PC is in Korean so I guess that is the cause of this problem. Now this time I tried it as an administrator; the previous error message does not pop up anymore but it just crashes automatically when I try to play Ultimate Doom (~ has stopped working). Lastly, I tried it without the administrator prompt, but still it just crashes without the error message. Now I'm a bit confused.

I think the problem is mainly due to my Korean username, but couldn't find a way to solve this in the Wiki. This might not be a serious problem with the Doomsday engine, but I hope I can play this awesome engine without making a new account. Thanks.

Related issues

Related to Bug #1097: [Snowberry] Errors when running from a non-ASCII folderClosed2012-10-30

Related to Bug #1094: [Win32] RSP not passed to Doomsday with non-ASCII usernameClosed2012-10-16

History

#1 Updated by skyjake over 9 years ago

  • Tags set to Unicode
  • Subject changed from App init failed: CreateDirError to App init failed: CreateDirError (1.14.5)
  • Category set to Defect

#2 Updated by skyjake over 9 years ago

  • Related to Bug #1097: [Snowberry] Errors when running from a non-ASCII folder added

#3 Updated by skyjake over 9 years ago

  • Related to Bug #1094: [Win32] RSP not passed to Doomsday with non-ASCII username added

#4 Updated by skyjake over 9 years ago

Unfortunately this is a known bug with 1.14. As a workaround, you could try the latest 1.15 unstable build and bypass the frontend by starting Doomsday.exe manually. If this works, you can then use the "-iwad" command line option to tell Doomsday where to load the IWAD files (for instance by creating a shortcut to Doomsday.exe and adding the option "-iwad your\iwad_path\" in its properties).

Even when 1.15 is released, the frontend will likely still have issues with non-ASCII characters in file paths. We are planning to get rid of the launcher entirely so no time is being allocated for improving it any more.

#5 Updated by Incantator over 9 years ago

Thanks for your kind explanation: I didn't expect you to reply this soon.

#6 Updated by skyjake over 9 years ago

  • Status changed from New to Closed

#7 Updated by skyjake over 9 years ago

Closing as duplicate.

Also available in: Atom PDF