That is incredibly strange, I am completely unable to recreate that following the video exactly. The only other thing I can think would be if you would send a link to or post the "output_log.txt" file located in: "C:\Users\Username\AppData\LocalLow\Rising Sun Interactive\slaveRPG"
You could also try starting a new game with the quickplay option and seeing if that works, or try to use different options when creating a character.
The quickplay as almost the same problem but it doesn't show me any menu. I aslo tried different options, the problem is the same.
Here is the output log :
Initialize engine version: 2018.4.32f1 (fba45da84107)
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: AMD Radeon(TM) Vega 3 Graphics (ID=0x15d8)
Vendor: (null)
VRAM: 2032 MB
Driver: 26.20.15017.1005
Begin MonoManager ReloadAssembly
- Completed reload, in 0.239 seconds
<RI> Initializing input.
<RI> Input initialized.
<RI> Initialized touch support.
UnloadTime: 2.029200 ms
Desired mouse axis is out of range. Mouse axis will be clamped to 2.
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)
Desired mouse axis is out of range. Mouse axis will be clamped to 2.
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)
Setting up 3 worker threads for Enlighten.
Thread -> id: 34e4 -> priority: 1
Thread -> id: 2bc8 -> priority: 1
Thread -> id: 2564 -> priority: 1
This output log does not show any errors and I still cannot recreate the issue, unless it continues with others and we get more reports we don't see any issue on our end which makes me believe it's an issue on your end.
From the output log it appears as if you are using an integrated graphics card which leads me to believe the processor you are using is not the most powerful either. What I believe is happening then is that when the game starts there is too much information being passed at once for your system to be able to handle, especially considering that once again, there are no error reports here and I cannot recreate the issue using multiple game versions and multiple machines.
It is possible that releasing a 64 bit version of the game could solve this issue, but that is not a guaranteed fix or something that we are looking into adding to the game, unless of course there is a large outcry for it.
We apologies for the inconvenience.
