[FIXES] All past and current issues

[Arukādo]

ISSUES
------------


[Fixed by Koei Tecmo]

- 100% used CPU, causes overheating

- Sluttering, framerate drops when 3D models are shown

- Missing DLCs

- Framerate drop at menu and cauldron screens

- Missing After Story DLC

- Low resolution 2D assets
http://steamcommunity.com/app/527270/discussions/0/133256240744094157/

[／人 ˵ •̀ ᴗ - ˵ 人＼]

Azusa の投稿を引用：

How to use lily's cauldron and menu fixes? Just drop the .dll in the installation folder?

Edit: Yup looks like that was it, sadly it seems like this makes the game crash when you alt-tab...

Check Syad's comment on page 16, you can fix this with a registry change.

[Mimosa]

Kite の投稿を引用：

When you change something in registry it saves automatically.
After you change registry if you change anything in the game config it will override the values in registry.

Downsampling Method

Here's example, screenshots are taken at the resolution you set to mine is 5120x2880. I resized it to 2560x1440 in paint.
Original 2560x1440: http://i.imgur.com/i9OjY2H.png
5120x2880 resized to 2560x1440: http://i.imgur.com/7ojkv28.jpg
Reg Settings: http://i.imgur.com/G7Q9l95.png

For Nvidia Users: If you want to control smoothness then enable DSR, adjust smoothness slider, change desktop resolution to DSR resolution, set registry to that resolution and start game.

Reshade Method SMAA

SMAA off: http://i.imgur.com/AP496N7.png
SMAA on: http://i.imgur.com/NRiJpfG.png

Have you stumbled on a way to to push beyond 4K in Sophie? I've tried every trick I know. I feel like this game can push to 6400x3600 with 2xsgssaa and maintain FPS over 60. This would give a very clean image.

[Kite]

Nope. The Sophie only has 5 fixed resolutions baked into the exe file. Someone will have to mod the game to get higher resolutions than 4k. Gedosato didn't even work to force resolutions above 4k.

I ended up playing through Sophie at 1440p, 144fps, 4xsgssaa, reshade, G-Sync, performance fix in borderless windowed mode. Sophie has zero issues running at 144fps, it's was a rare treat to play a JRPG like this.

http://steamcommunity.com/sharedfiles/filedetails/?id=865505541

[Silfie]

／人◕ ‿‿ ◕人＼ の投稿を引用：

Azusa の投稿を引用：

How to use lily's cauldron and menu fixes? Just drop the .dll in the installation folder?

Edit: Yup looks like that was it, sadly it seems like this makes the game crash when you alt-tab...

Check Syad's comment on page 16, you can fix this with a registry change.

Thank you!

[sketchyguy]

Syad の投稿を引用：

ネコーち　☆　ツ の投稿を引用：

I play on fullscreen. The dinput8 file works but when I alt+tab or change window, the A17(game window) window turns completely white then crashes.

if you are on Windows8+ use this to remove the crashes on alt-tab

myself page 16 の投稿を引用：

Requirements: Win8,10.
create a registry entry that tells Windows to run Atelier in Borderless Fullscreen

open regedit and navigate to:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Direct3D\Shims\MaximizedWindowedMode


rightclick, create a new 32bit DWORD, and name it the path of the Atelier game, example:
D:\Games\SteamLibrary\steamapps\common\Atelier Sophie The Alchemist of the Mysterious Book\A17.exe


set hex value, 1 for borderless fullscreen, 0 for true fullscreen. This is how it should look: http://imgur.com/a/MqkjS

This works in making the program windowed, but it doesn't remove the border. Do I need to do anything else?

[Mimosa]

Kite の投稿を引用：

Nope. The Sophie only has 5 fixed resolutions baked into the exe file. Someone will have to mod the game to get higher resolutions than 4k. Gedosato didn't even work to force resolutions above 4k.

I ended up playing through Sophie at 1440p, 144fps, 4xsgssaa, reshade, G-Sync, performance fix in borderless windowed mode. Sophie has zero issues running at 144fps, it's was a rare treat to play a JRPG like this.

http://steamcommunity.com/sharedfiles/filedetails/?id=865505541

What did you use for reshade plugins?

[Kite]

Mainly using Lumasharpen to reduce softness of SGSSAA. I might have had HDR on as well.

[Mimosa]

I decided to use Clarity and it seemed to be what I was looking for. Using HDR and Lumasharpen had to much of a performance hit for me. Clairty is a hog too, but it doesn't drop me below 130 FPS. At 4K the softness of SGSSAA isn't that bad. 4xSGSSAA + Clarity give me 130-144 fps depending on the envionment. 8xSGSSAA @ 4K runs at 144fps, but the moment I turn on clarity the framerate tanks to 50-60fps. Plust 8x looks too blurry for my taste.

This game is so well optimized. I feel like I could probably run it on one of my laptops at 144hz if I knocked the resolution down to 1080p.

[Maliquem]

The fix crash my game on the start.

Log:

[TIME] [THREAD] [LOG]
21:18:25.746 00009204 AutoFix for "Atelier Sophie" enabled
21:18:25.746 00009204 Loaded C:\WINDOWS\system32\d3d9.dll
21:18:25.940 00002804 hkIDirect3D9::hkIDirect3D9
21:18:25.940 00002804 hkIDirect3D9::AddRef
21:18:25.946 00002804 HWND 0x00880BEC: ClassName "Static", WindowName: "Dummy D3D9 Window"
21:18:25.946 00002804 hkIDirect3D9::CreateDevice
21:18:25.946 00002804 BehaviorFlags: 00000040 D3DCREATE_HARDWARE_VERTEXPROCESSING
21:18:26.539 00012420 HWND 0x00250DE8: ClassName "OleMainThreadWndClass", WindowName: "OleMainThreadWndName"
21:18:26.545 00005964 HWND 0x001D0F3C: ClassName "CicMarshalWndClass", WindowName: "CicMarshalWnd"
21:18:26.556 00005964 HWND 0x00890B16: ClassName "ElixirFramework", WindowName: "A17 Main Window 1.0.0.11"
21:18:26.795 00002804 hkIDirect3DDevice9::hkIDirect3DDevice9
21:18:26.805 00002804 HWND 0x00890BEC: ClassName "Static", WindowName: "Dummy D3D9 Window"
21:18:26.888 00002804 hkIDirect3D9::Release return = 2
21:18:27.001 00004092 HWND 0x008A0BEC: ClassName "Static", WindowName: "Dummy DXGI Window"
21:18:28.774 00005964 hkIDirect3D9::hkIDirect3D9
21:18:28.910 00005964 hkIDirect3D9::CreateDevice
21:18:28.910 00005964 BehaviorFlags: 00000044 D3DCREATE_HARDWARE_VERTEXPROCESSING D3DCREATE_MULTITHREADED
21:18:29.051 00005964 hkIDirect3DDevice9::hkIDirect3DDevice9

[百合 姫]

Jael の投稿を引用：

The fix crash my game on the start.

Log:

[TIME] [THREAD] [LOG]
21:18:25.746 00009204 AutoFix for "Atelier Sophie" enabled
21:18:25.746 00009204 Loaded C:\WINDOWS\system32\d3d9.dll
21:18:25.940 00002804 hkIDirect3D9::hkIDirect3D9
21:18:25.940 00002804 hkIDirect3D9::AddRef
21:18:25.946 00002804 HWND 0x00880BEC: ClassName "Static", WindowName: "Dummy D3D9 Window"
21:18:25.946 00002804 hkIDirect3D9::CreateDevice
21:18:25.946 00002804 BehaviorFlags: 00000040 D3DCREATE_HARDWARE_VERTEXPROCESSING
21:18:26.539 00012420 HWND 0x00250DE8: ClassName "OleMainThreadWndClass", WindowName: "OleMainThreadWndName"
21:18:26.545 00005964 HWND 0x001D0F3C: ClassName "CicMarshalWndClass", WindowName: "CicMarshalWnd"
21:18:26.556 00005964 HWND 0x00890B16: ClassName "ElixirFramework", WindowName: "A17 Main Window 1.0.0.11"
21:18:26.795 00002804 hkIDirect3DDevice9::hkIDirect3DDevice9
21:18:26.805 00002804 HWND 0x00890BEC: ClassName "Static", WindowName: "Dummy D3D9 Window"
21:18:26.888 00002804 hkIDirect3D9::Release return = 2
21:18:27.001 00004092 HWND 0x008A0BEC: ClassName "Static", WindowName: "Dummy DXGI Window"
21:18:28.774 00005964 hkIDirect3D9::hkIDirect3D9
21:18:28.910 00005964 hkIDirect3D9::CreateDevice
21:18:28.910 00005964 BehaviorFlags: 00000044 D3DCREATE_HARDWARE_VERTEXPROCESSING D3DCREATE_MULTITHREADED
21:18:29.051 00005964 hkIDirect3DDevice9::hkIDirect3DDevice9

Where is it actually crashing (which module name)?
If it's not crashing in the A17.exe folder's dinput8.dll, it's crashing outside of fix code, so it's a compatibility issue on your side.

If it is crashing in A17's dinput8.dll, well, that can happen if we try to hook multiple times, or if it is unable to load the dinput8.dll from the %windir%\system32 folder, possibly because it's already loaded.

I see "dummy d3d9 window" which suggests you're using Special K.
You can try three things and see if it works:
1. Get rid of the fix.
2. Get rid of Special K.

If you want to solve the issue, you'l have to:
3. Integrate the fix into Special K and remove the fix.

[百合 姫]

Hmm, I didn't realize OneTweakNG has support for forcing borderless windowed already. For those of you who play in fullscreen, you can try changing these values in the OneTweakNG.ini file.

[Borderless]
Borderless = true
ForceWindowedMode = true
AllWindows = false
TopMost = false
WindowClass = ElixirFramework
WindowName = 

[Seiji]

百合 姫 の投稿を引用：

Hmm, I didn't realize OneTweakNG has support for forcing borderless windowed already. For those of you who play in fullscreen, you can try changing these values in the OneTweakNG.ini file.

[Borderless]
Borderless = true
ForceWindowedMode = true
AllWindows = false
TopMost = false
WindowClass = ElixirFramework
WindowName = 

Thanks!!

[Bobice]

Game won't start for me anymore. I click start, steam says its running for about 5 seconds. Then, nothing happens and it say's it isn't running anymore.

[百合 姫]

A17modV2_OneTweakNG_Experimental_Fix has now been updated to include an .ini file that automatically turns fullscreen mode into borderless fullscreen mode (hey, if I'm going to break fullscreen, I should at least provide an alternative...).

As a small QOL improvement to the DLL, the fix will no longer try to turn windowed into borderless fullscreen, which looks really horrible.

[Maliquem]

百合 姫 の投稿を引用：

Where is it actually crashing (which module name)?
If it's not crashing in the A17.exe folder's dinput8.dll, it's crashing outside of fix code, so it's a compatibility issue on your side.

If it is crashing in A17's dinput8.dll, well, that can happen if we try to hook multiple times, or if it is unable to load the dinput8.dll from the %windir%\system32 folder, possibly because it's already loaded.

I see "dummy d3d9 window" which suggests you're using Special K.
You can try three things and see if it works:
1. Get rid of the fix.
2. Get rid of Special K.

If you want to solve the issue, you'l have to:
3. Integrate the fix into Special K and remove the fix.

Hummm... There is a way to make Special K don't load in specific games?