Difference between revisions of "NightCry"
From PCGamingWiki, the wiki about fixing PC games
m (updated template usage) |
(→Framerate uncapper: migrated to fixbox format (Needs references)) |
||
Line 32: | Line 32: | ||
==Essential improvements== | ==Essential improvements== | ||
===[http://www.mediafire.com/download/c7vu8y75x7v8uch/SweetFX+1.5u+Boulotaur2024.rar Framerate uncapper]=== | ===[http://www.mediafire.com/download/c7vu8y75x7v8uch/SweetFX+1.5u+Boulotaur2024.rar Framerate uncapper]=== | ||
− | If the framerate seems capped at 30FPS, try using this solution to allow for 60 FPS | + | {{ii}} If the framerate seems capped at 30FPS, try using this solution to allow for 60 FPS. |
+ | {{Fixbox|1= | ||
+ | {{Fixbox/fix|Instructions|ref={{cn|date=July 2016}}}} | ||
+ | Extract [http://www.mediafire.com/download/c7vu8y75x7v8uch/SweetFX+1.5u+Boulotaur2024.rar Framerate uncapper] to the installation folder. | ||
+ | |||
+ | '''Notes''' | ||
{{--}} There is a possibility this may cause game crashes, so please be aware of this. (If this solution causes crashes, you may want to try the recommended solution below): | {{--}} There is a possibility this may cause game crashes, so please be aware of this. (If this solution causes crashes, you may want to try the recommended solution below): | ||
− | + | {{++}} SOLUTION 2 (Recommended) : If you don't want to use framerate uncapper, try to set a custom D3D9 renderer with this [[Glossary:Command line arguments|command line arguments]] <code>-force-d3d9</code> | |
− | {{++}}SOLUTION 2 (Recommended) : If you don't want to use framerate uncapper, try to set a custom D3D9 renderer with this [[Glossary:Command line arguments|command line arguments]] <code>-force-d3d9</code> | + | }} |
==Game data== | ==Game data== |
Revision as of 08:37, 27 July 2016
Cover image missing, please upload it | |
Developers | |
---|---|
Nude Maker | |
Engines | |
Unity | |
Release dates | |
Windows | March 29, 2016 |
Key points
- Some players report different framerate caps. It may be 60 FPS for some immediately, while it will be 30 FPS for others. If it is locked at 30 FPS, try the solutions below.
- Some poor optimization and heavy on performance.
- No controller support.
- The game is running with D3D11 renderer which causes slow down and poor performance.
- Switching from D3D11 renderer to D3D9 renderer with this command line arguments
-force-d3d9
caps the framerate at 60 FPS with no known issues.
General information
Availability
Source | DRM | Notes | Keys | OS |
---|---|---|---|---|
Steam |
Essential improvements
Framerate uncapper
- If the framerate seems capped at 30FPS, try using this solution to allow for 60 FPS.
Instructions |
---|
Game data
Configuration file(s) location
Template:Game data/row
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/427660/pfx/[Note 1] |
Save game data location
Template:Game data/row
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/427660/pfx/[Note 1] |
Save game cloud syncing
System | Native | Notes |
---|---|---|
Steam Cloud |
Video settings
Input settings
Audio settings
Localizations
Language | UI | Audio | Sub | Notes |
---|---|---|---|---|
English | ||||
Japanese |
System requirements
Windows | ||
---|---|---|
Minimum | ||
Operating system (OS) | 7, 8, 10 | |
Processor (CPU) | Intel Dual-Core 2.4 GHz AMD Dual-Core Athlon 2.5 GHz |
|
System memory (RAM) | 4 GB | |
Hard disk drive (HDD) | 10 GB | |
Video card (GPU) | NVIDIA GeForce 8800GT AMD Radeon HD 3830 Intel HD Graphics 4000 512 MB of VRAM |
Notes
- ↑ 1.0 1.1 Notes regarding Steam Play (Linux) data:
- File/folder structure within this directory reflects the path(s) listed for Windows and/or Steam game data.
- Use Wine's registry editor to access any Windows registry paths.
- The app ID (427660) may differ in some cases.
- Treat backslashes as forward slashes.
- See the glossary page for details on Windows data paths.