Search results

...wat. Last I checked, it does work with the Japanese EXE. Also, CSE2 Portable/Enhanced have working Japanese support on English Windows installations.

No.

v1.5.2.1 This is a maintenance release: a bug was found involving weapons appearing far away from the player under certain circumstances. There were also some updates to the music DLL's sound mixer, from early 2019. This project will no longer receive any major updates: any future releases...

As per a user suggestion, I've made 60FPS optional in CSE2E. So if you like widescreen, but don't want to lose the original floaty physics, there you go. v2.0.2 - Enhanced

Thanks to Aar, some more bugs were found in the enhanced branch. They've been fixed in this update: v2.0.1.2 - Enhanced

Darn. Sorry about that: I usually test on Linux, where this issue doesn't happen. It's a really weird bug, actually: there's a bugged command in the Waterway's TSC file, '<FLJ850:0111', which causes the game to read from an invalid place in memory. If what it happens to read is set to 1, it...

Personally, I want to know who holds copyright over Cave Story's original source code.

Thank you

Wouldn't CSE2E hurt the sales of CS+ on Steam? EDIT: NXengine-evo has a Switch port as well. If being based on reverse-engineered source code is a problem, then all CSE2 ports are a problem.

CSE2E exists. I can't imagine I Love Cave Story was considering vanilla CSE2, since its goal is to be literally the same as the original.

Well that was embarrassing. So not only did CSE2E v2.0 ship with a broken Makefile, but it also had a broken frame-limiter. Well, here's v2.0.1. Usually, for a hotfix release like this, it'd be v2.0.0.1 instead, but this update has an extra feature: since v2.0, I've gone through all the game's...

CSE2 v2.0 Geez, has there really not been a release since May? Well, here's v2.0. Why v2.0 and not v1.3? Because we've finally reached the second milestone for the project: ASM-accuracy! The first milestone was making the game completable - playable from beginning to end. Once that was...

How does ID 62 matching the number of source files indicate that the source files are C++? The focus is ID 60, which is specifically the number of object files linked into the EXE that were generated by a C++ compiler. In Cave Story, it's 2, but in CSE2, it's 71. Edit: Also, that source you...

According to the Rich Header, it was C, not C++.

That Sue facepic is amazing.

PrEpArE tO bE dMcA'd

Heisenbug... typical. You could replace 'Debug' with 'RelWithDebInfo' too. That makes a release build, but with enough debug info for gdb to be useful.

If I remember right, the Developer Command Prompt is different from the regular command prompt, extending the PATH and defining some environment variables. They're needed for CMake to detect the compiler properly.

Google's your friend. The Developer Command Prompt can be found in Windows's start menu, in the Visual Studio folder. 'cd' is a command for changing directory - by default, I think the command prompt opens in the root of the C drive, so you use cd to switch to the build folder that you made...

Nope. If you make a debug build, and run it through gdb, you might be able to track down the cause.

I doubt it could be that. Just two days ago, I ran the enhanced branch on a device with only 1GB of RAM.

"My brother, Kazuma, is stuck in an area called Bushlands." It's the town's name, not a description. It makes perfect sense in English.

'Grasstown' wasn't a mistake. The original name was 'Kusamura', with 'mura' being a suffix for villages/towns (heck, the filename for Mimiga Village's music is 'MURA'), and 'kusa' literally meaning 'grass'.

Big bump, but this issue's finally been fixed! ... And I didn't get any credit!

In the next version of CSE2E, you'll be able to change the sprite resolution by just changing a value in CommonDefines.h. In the meantime, you can try backporting the changes to your copy of the engine.