I can't find any helpful results when searching this issue, but for some reason, CaveStory+ is running super slow. The music is playing fine, but I noticed stuttering and some screen tearing that's making me sick. I'm forcing VSync in the Nvidia Control panel, but nothing changed. I'm running on a GTX 1660, 16 GB RAM, and an Intel Core i7. I also saw that using multiple monitors causes the issue, but I unplugged my monitor to no avail.

Having the same problem. The Steam version runs fine for me.

Has to be some sort of timing issue. I have the same issue trying to run this in Windows, sound is playing normally but the game runs at about half speed.

Running the game under Linux via Wine works perfectly.

I am also having the same problem. I've tried playing around with the few options available but nothing is helping. I'm really hoping this gets resolved soon.

Same happens to me, the first day i played it after installing it ran fine and smoothly, but suddenly the next day it started going as if it had a stuttering slo-mo effect, but the music plays fine.

I'm in the same boat now! First day everything's fine, second one slo-mo.

Okay, been testing several things, ans uninstalling it completely and reinstalling it seemed to fix the problem (For now).
I think it may be some error related to the achievement troubles (they seem to reset after relaunching the game), maybe having and not having them at the same time causes any kind of error, but i'm no tech expert so i'm just trying to blame it to any other possible error. On a side note, getting the 'toroko wins' achievement and deciding not to continue makes the game get 'visually' stuck on the introduction screen (i say visually because the menu seems to work on the background, i can hear the menu music and sounds when selecting options), maybe giving more proof that ahievements may be one of the main culprits.

Just tried the updated version 1.0.1.0: game still runs at 31~32FPS (same as 1.0.0.0).
Both the CPU and GPU are < 10% loaded while the game runs.
Tested on the same day, the Steam version runs at 60FPS and I observed no issue with other games / applications.
Re-installing the game did not solve the problem.

Windows 10 19043.1415
AMD Ryzen 7 3700X
NVIDIA RTX 3070 (472.39)
16 GB RAM

Edit 26.02.2022: solved by updating graphics driver to 511.79

I asked for direct support from gog and they replied me with a solution that helped me, so I'll just attach here the message they sent me in case it helps anyone else (but also first try to uninstall it completely and reinstalling, its faster and easier than what i'm pasting below):

For that, please try a few more suggestions:
1) Reinstall the June 2010 DirectX runtime package: http://files.gog.com/support/Directx_Jun2010_redist.exe
You will have to extract the files into some folder, then open that folder and launch the DXSETUP.exe file in order to proceed with the installation.

2) Please update your graphics device drivers:
http://www.intel.com/p/en_US/support

3) Please make sure that no third-party applications are interfering with the game. Please try to install and run the game in “clean boot mode”. Instructions on how to do that can be found here:
http://support.microsoft.com/kb/929135
Make sure the account you create for clean boot mode is granted Administrator privileges.

Edit: it seems this 1.0.1.0 update unfixed whatever i did, so i'll have to try again. However, this update fixes achievements getting re-locked and the missing holiday textures.

Edit2: repeating the two first steps again fixed the game, now it runs perfectly smooth

I had the same problem, the game was running at like 20-30fps, unplayable.
i7 6700k, GF GTX 970, 16GB RAM
The solution on my end was very simple actually - I updated my graphics card drivers to the latest version and the sluggish 30fps was gone, but after the driver update and on a 144hz monitor the game started to run twice as fast, looks like it's somehow connected to monitor refresh rate. So I had to manually limit the game to 60fps in NVidia Control Panel which turned out to be the final solution to the problem.
This version of the game is a bit sloppy and rough around the edges if I'm honest, too bad there is no PC port of the Switch version.

I had the same problem. The only solution I found was to install the doukutsu-rs mod which greatly improves the game and can be found on github https://github.com/doukutsu-rs/doukutsu-rs

Hi, there.

I've managed to isolate the cause for this issue (Cave Story +, as the classic version runs well on my system without any changes), at least on my Linux-based setup. However, the solution is based on Windows (wine in my case), so I'll describe it briefly here. I'd expect everything I describe below to work on Windows (exceptions noted when needed).

The cause I've managed to pinpoint is related to the system's "uptime" when the game is started. For example, doctoring the "uptime" to a low value (as if the computer had been recently booted up) and changing nothing else magically made the game run as fast as it could (on one of my systems, because of vsync, that was capped to 144 fps on my external monitor), so then it was necessary to cap the fps to 50 (for a speed akin to the original,Cave Story (not "plus")), or 60 (for the speed at which the CS+ game seems to have been designed to run).

I'll describe my solution briefly here:

1. Install and configure UptimeFaker to report a low, yet "realistic" uptime value to the game (config file example further below):

1.1. Copy uptimefaker32.dll to/as uptimefaker32.asi in the game's topmost directory (the one containing the file CaveStory+.exe).

Note: In my early attempts, I've tried to install the uptimefaker32.asi file to a subdirectory ("scripts", "plugins", "update", as that's the preferred method to install ".asi" files for "ultimate asi loader") of the game's topmost directory, but that seems to have somehow confused CaveStory+.exe into using/loading the ".asi" file itself, yielding crashes that had me scratching my head and going into a few rabbit holes for a few hours, but I ended up putting the ".asi" file in the game's topmost directory (also supported by "ultimate asi loader"), and all the problems were magically gone. This is the first game for which I've had to do that! :-)

1.2. Create a text file named uptimefaker.ini in the game's topmost directory with the following contents:

; ===[ begin ]===
; Configuration file for Uptime Faker utility
; In this file you can configure how much uptime should be added to time functions
; and which functions should be hooked

[AddedUptime]
; How many uptime days should be added to all hooked time functions
; Windows checked builds add approximately 49 days of uptime
AddUptimeDays=1
; When ProcessTime is set to 1, timers will start ticking from the time the process
; was started, instead of PC uptime
ProcessTime=1

; Below you can toggle on/off hooking of each specific time function
; Sections correspond to libraries those functions come from originally,
; while keys correspond to specific functions from this library
[kernel32]
QueryPerformanceCounter=1
GetTickCount=1
GetTickCount64=1

[winmm]
timeGetTime=1
timeGetSystemTime=1

; ===[ end ]===

2. Use ultimate asi loader to inject uptimefaker32.asi into the game process:

2.1. Use a DLL name that would accomplish an early injection using a safe-ish DLL placeholder. I've chosen version.dll with excellent results. In simple terms, just copy dinput8.dll (download/use the win32 (windows in/for 32-bits mode) file) to/as version.dll in the game's topmost directory.

3. Cap the fps to 50 or 60, using the appropriate method for your real operating system:

3.1. Windows: refer to other posts (see post #10 in this thread for a solution that works for nvidia cards), or just google for your particular case;

3.2. Linux: I've used libstrangle (I've built it from source) with excellent results;

Even though this solution works perfectly with regards to delivering the expected fps, I will say that the game does seem to show a somehow "shaky" screen refresh when the game viewport scrolls/shifts in any direction. I can't compare this to how it'd behave on native Windows, so I don't know if this behaviour is just a consequence of how the game was coded, or if there are issues that would remain to be solved.

I will say, though, that both NXengine evo (available and working perfectly as a "snap" on native Linux) and doukutsu-rs (available as a "snap" and as a "flatpak") both work perfectly on every computer I own (Lenovo Thinkpad X240 with Intel graphics, HP EliteOne 800 with Intel graphics, Lenovo Idea Legion Slim 5 with both Intel and nvidia GPUs). YMMV :-)