spideyfusion/akiba

A small utility for adjusting the resolution and framerate in AKIBA'S TRIP.

AkibaInterceptor

AkibaInterceptor is a small utility for adjusting the resolution and framerate in AKIBA'S TRIP. It tricks the game into thinking that it's calling its own configuration utility and then performs fancy voodoo magic.

Features

• Skip the game's configuration window and jump straight into the game.
• Unlock the game's framerate to anything you want. Who wants to play at 30 FPS anyway?
• Experience the game at resolutions beyond 1920x1080. Yes, even in UHD!
• Make the game controller friendly by hiding the cursor and prevent the system from falling asleep.
• Run the game in a borderless window to get rid of those Alt + Tab issues once and for all!

Requirements

• AKIBA'S TRIP (GOG and Steam versions of the game are supported)
  • ⚠️ Please use version 1.3.4 of AkibaInterceptor if you intend to run the demo version of the game
• Microsoft .NET Framework 4.8
• Windows Vista or greater

NOTE: If you obtained the game via some other distribution method, tough luck! :-)

Installation/Upgrading

Just place the downloaded binary in the game's root directory and then run it. The utility is smart enough to do everything else by itself. Don't forget to edit the configuration.yaml file before starting the game.

Configuration

Here's a list of settings you're able to override though the utility's configuration.yaml file:

• framesPerSecond [int] - How many FPS you want to game to run at. Anything above 60 hasn't been tested, so keep that in mind.
• renderingResolutionWidth [int] - The resolution width at which the game is going to be rendered.
• renderingResolutionHeight [int] - The resolution height at which the game is going to be rendered.
• screenMode [string] - In what kind of window the game should be ran. The following options are available: Borderless, Fullscreen, Windowed
• verticalSynchronization [bool] - Should VSync be enabled or not. It's recommended to turn it off if you run the game at anything other than 30 FPS.
• antiAliasing [bool] - Should anti-aliasing be applied or not. It's recommended to turn it off if you're going to take advantage of downsampling.
• hideCursor [bool] - If enabled, the cursor will be positioned off the screen when the game starts. This is useful if you're running Big Picture.
• preventSystemSleep [bool] - This will prevent your system from falling asleep (monitor too). Super convenient if you're playing with a gamepad (which you should).
• disableMovies [bool] - Enable this if you want to skip the opening cinematic and go directly to the start screen when you start the game.

NOTE: Configuration values are case-sensitive. Be careful how you type them out.

Downsampling

You can take advantage of setting the rendering resolution beyond your monitor's supported resolution since the game makes the fullscreen window be as big as your current resolution. Try playing the game at 3840×2160. :-)

Borderless window

• If you set screenMode to Borderless you can still achieve downsampling as renderingResolutionWidth and renderingResolutionHeight are still taken into account.
• AkibaInterceptor will try its best to figure out on which monitor you're playing the game and expand across it. Whoosh!

Accessing the game configuration window

Even though this utility will make the game launch immediately, you can still access the original game configuration window by launching AkibaUU_Config.exe directly from the game's root directory.

NOTE: The listed configuration values will always override the game settings, regardless of what it's set in the configuration window of the game.

Reporting issues

Use GitHub's issue tracker to report any issues you might have. You may also add me on Steam, I don't bite.

Credits

• Previous versions of AkibaInterceptor used memory patching in order to alter the framerate. The relevant memory locations have been taken from this guide. Thanks to X37, You Schmuck!, Nyan~ and Conker for finding them.
• The utility icon has been created by Yusuke Kamiyamane.

License

See the LICENSE file for license rights and limitations (MIT).

akiba's Issues

Unable to launch game via original config window (AkibaUU_Config.exe)

After tuning configuration and hit play (プレイ) the program crashes with following message:

---------------------------
AkibaInterceptor
---------------------------
System.ComponentModel.Win32Exception (0x80004005): Unknown error (0x80041002)

   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)

   at System.Diagnostics.Process.Start()

   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)

   at Akiba.Core.Utilities.LaunchSteamGame(UInt32 applicationId)

   at Akiba.Program.LaunchConfigurationUtility()

   at Akiba.Program.Main(String[] args)
---------------------------
OK   
---------------------------

I can't seem to be able to change the game language setting with the patch installed.

Add the memory address for Windows 10 1809

The new memory address seems to be 0019FDEC.

Doesn't work on GOG version

It tries to open the Steam version exclusively. I bought this game on GOG, therefore it can't be used unless I knew how to change it. Considering I don't know how to code, it makes it a bit difficult to figure out how to fix this issue.

Input timing not changed with framerate

There are many people reporting this on Steam, and I figured this should be actually put on the github. The input timings are not matched with the set framerate. From my own test with 60 FPS, I can safely say that this makes the game almost unplayable since the regular attack timings are so slim that I was accidentally attempting stripping every time I hit any of the attack buttons.

Implement more robust window locator

Figure out a better way to locate the game's window which doesn't involve waiting an arbitrary amount of time.

not functioning

i followed every procedure and still cant get 60fps even though the frame rate is set to 60. is it because this program is too old?

Game has been update today

Will the utility got update too?

Camera bug at supersampled resolutions

When playing at rendering resolutions higher than the screen resolution (in my case rendering 1440p, screen 1080p), when using the camera to take pictures, the synthisters caught on camera are visually displaced.

Improve cursor hiding

Currently, hiding a mouse will actually position it at the very edge of the screen. A more ideal implementation would make the cursor disappear completely while AKIBA'S TRIP window is in focus.

Verify the framerate variable memory location on Windows 8/8.1

I got a report from a Steam user who's running Windows 8 that his memory location for the framerate variable is 0x0018FE00. It's possible that Windows 8 and Windows 8.1 don't share the same memory location.

I'll have to verify this by testing AkibaInterceptor on two separate OS installations.