Packaged Game gets "Fatal Error!" because has special characters on their name

We know the problem. The Game Crashes on start up due the name of the Windows having a special character (*$&#@) We are 2 days from releasing the game and have no idea how to fix this PLEASE help us!

The game is getting cooked for Windows 64 Bits - Everything goes fine when cooking, but if you try to open the game with a special character windows … “Fatal Error!”

Thank you!

,

If there is an issue due to the special characters being used, please rename what’s using special characters. If you could provide an output error out as a .txt file, that would help me help you figure out what needs to be changed.

Thanks!

The Windows , for instance let’s say your name is Адриан and when you did install your OS or when you created your windows that’s what is crashing the game on start up. We don’t get any info from the that’s why we are so confused by that. :slight_smile: Thanks for the reply!

We will try to get the output .txt from our users!

A way around this crash would be to rename the username in the Windows profile. Is Адриан definitely the name that’s causing the crash? If so, I can begin an investigation on these characters.

Thanks!

The problem is no at the development but when the users execute the our build, many people use non-standard characters on their username. The company that related the error for us was using this username. Their are polish so non-standard characters are common, that’s why they do this specific test. Anything i can do to help just ask. We are trying to get the error log from them.

116188-derpuser.png

Charles,

I am working on this, thank you for being patient.

Charles,

We set up an extra account composed of special characters. I then packaged in 4.13 and 4.14 for shipping/distribution on Windows 64-bit. I have been able to successfully launch each of the projects in the new account.

Are you still experiencing this issue?

Hey Charles,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you!