Cho Ren Sha 68K 1.10 windows just droped

[Nate123]

New year new 68k goodness https://yosshin4004.github.io/x68k/crs6 ... index.html same as the 68kz update so yea the game has real backgrounds now.

[BulletMagnet]

Thanks for the heads-up; methinks revisiting this one after quite awhile will serve as a good way to ring in the new year.

[BIL]

Saw his tweet earlier, beautiful as always.

[copy-paster]

What a way to celebrate 30th anniversary of the game!

Now I wonder if there's a way to access debug menu in the newer windows ver? Using the old method doesn't work.

[hyp36rmax]

Love this game! Modernized enought to be compatible. Aspect Ratio just works on my ultrawide 49" none of this streteched madness. Controls detected. LFG!

[Daytime Waitress]

Thanks for the heads-up

Seconding this.
Haven't been back in a very long while.
Always grand to see devs that care enough to put in this kind of effort, too.

[Lander]

Nice I had a grand time with the X86K update when it came out.

I wonder if they managed to fix up the Windows port's speed with this release - it used to force 60hz, so ran a bit faster than the 55hz original.

[Necronom]

Nice I had a grand time with the X86K update when it came out.

I wonder if they managed to fix up the Windows port's speed with this release - it used to force 60hz, so ran a bit faster than the 55hz original.

Doesn't look like it. You can display FPS but it shows average of 60. Can't find an option to change that.
Btw, AI-translated:

Method of operation.

Movement of the ship.
Joystick
Cursor keys
Numeric keypad

Firing a shot
Joystick trigger A
Left CTRL or Z key on keyboard

Bomber fire
Joystick trigger B
Left SHIFT or X key on keyboard

Pause the game.
START button on joystick
PageUp on keyboard

Forced Game Over
START SELECT on joystick Simultaneous long press
Keyboard PageUp PageDown Simultaneous long press

End of game
ESC key

Frame skip speed setting (only available during replay playback)
Keyboard F1 - F12

Translated with DeepL.com (free version)

[XoPachi]

Does this game have a quick restart button?
Also what's the new build he put out today?

[Ms. Tea]

There's two things in the changelog; it seems like it's a minor release.

・フレームスキップ機能をキーボードの [F1]～[F12] から [1]～[9] に変更
・エラー終了時に詳細な動作ログを保存するように修正

・The frameskip keys were moved from F1-F12 to 1-9.
・Fixed writing errors to the log when a bug occurs.

[Nate123]

Does this game have a quick restart button?
Also what's the new build he put out today?

hold Start and Select on keyboard the PageUp and PageDown keys

[Marc.bret.87]

Is there a way to get auto fire?

[copy-paster]

Is there a way to get auto fire?

Select "Configuration" and turn on "Full Autofire".

[Marc.bret.87]

Is there a way to get auto fire?

Select "Configuration" and turn on "Full Autofire".

Many thanks

[CaptainKraken]

Proper backgrounds, full autofire, and no input lag?!
Merry Christmas and Happy New Year, I guess!!

I can actually make it into the powerup rings now

[Lander]

Doesn't look like it. You can display FPS but it shows average of 60. Can't find an option to change that.

Ah, shame. Probably one of those "everything's hardcoded" situations if the patchnotes don't explicitly call out any timing changes.

Still, it's quite playable, and beats putting up with the stutter or tear of 55-on-60. Folks with adaptive sync displays can probably force-limit it to 55 via GPU control panel or wrapper DLL to recover the original speed, too.

[deLima]

Just got to the final boss on Stage 0 (the scoreboard says stage 2-0), loving this game!!

[scrilla4rella]

excellent excellent news!

I was able to limit the fps to 55 via the Nvidia control panel without issue as far as I can tell. However I haven't had much luck getting the game to recognize my xbone controller. I'm probably just missing something obvious, I'll play around with it more when I get he chance.

[UD2]

If any of you want to make this run on a Mac, it can be done via CrossOver (needed for DirectX12 support which vanilla Wine on macOS doesn't have), just make sure to choose D3DMetal and install a native D3DCOMPILER_47.DLL (the Wine replacement one seems to have a shader parsing bug of all things). Enabling ESync seemed to get rid of some odd stuttering I saw without it. Make sure to run windowed as it's the wrong speed fullscreen. It's still a bit quirky, and the BG scrolling isn't 100% smooth (not exactly sure where the issue lies), but it's nice to see this will at least run again after years of it being totally broken under Wine (at least on macOS).

[emphatic]

Anyone playing it in TATE, or is that a 68K exclusive still?

[eksratu]

Trying to play this on a W11 machine---it was recognizing my Xbox controller just fine for several sessions, but has since started to either not recognize anything other than keyboard or inputting random buttons. Not sure what changed.

EDIT: One of several attempts to play this game WITHOUT Steam running in the background (doing Steam Input things) just happened to work. Funky.

[Necronom]

Anyone playing it in TATE, or is that a 68K exclusive still?

You can set your desktop to vertical, but since it has big black boarders at top and bottom I guess that there is no real tate mode here.
Would love to see a remake in a modern engine and lots of options. The game itself aged like fine wine

[Warp_Rattler]

Poking my head out of lurking mode to ask: have any of the other sickos who run Linux gotten this version to work under WINE? There was a previous topic headed up by Lander that included discussion about getting the old 2017 version running.

That one still runs flawlessly for me with no special finessing, but 1.10 doesn't seem happy no matter what I do. Running it gives a brief debug window that opens and closes in a flash, along with some assorted maybe-error messages. My patience for fighting with WINE's "is it a bug or just normal output?" 'fixme' terminal vomit is nearly non-existent. I've made sure I've installed the D3DCOMPILER_47.DLL as per UD2's post, and I've tried switching to both win10 and win11 compatibility via winetricks, to no avail. The fact that they got it running in CrossOver means there must be some magical configuration what allows it to run; I just haven't stumbled on what it is yet.

[Steven]

Poking my head out of lurking mode to ask: have any of the other sickos who run Linux gotten this version to work under WINE? There was a previous topic headed up by Lander that included discussion about getting the old 2017 version running.

That one still runs flawlessly for me with no special finessing, but 1.10 doesn't seem happy no matter what I do. Running it gives a brief debug window that opens and closes in a flash, along with some assorted maybe-error messages. My patience for fighting with WINE's "is it a bug or just normal output?" 'fixme' terminal vomit is nearly non-existent. I've made sure I've installed the D3DCOMPILER_47.DLL as per UD2's post, and I've tried switching to both win10 and win11 compatibility via winetricks, to no avail. The fact that they got it running in CrossOver means there must be some magical configuration what allows it to run; I just haven't stumbled on what it is yet.

Use Proton-GE. It runs flawlessly.

[Lander]

Anyone playing it in TATE, or is that a 68K exclusive still?

Isn't that moot, since CRS is a square-aspect game? I know it had a dedicated mode on 68K, but don't recall it making much difference beyond moving the score readout.

Poking my head out of lurking mode to ask: have any of the other sickos who run Linux gotten this version to work under WINE? There was a previous topic headed up by Lander that included discussion about getting the old 2017 version running.

That one still runs flawlessly for me with no special finessing, but 1.10 doesn't seem happy no matter what I do. Running it gives a brief debug window that opens and closes in a flash, along with some assorted maybe-error messages. My patience for fighting with WINE's "is it a bug or just normal output?" 'fixme' terminal vomit is nearly non-existent. I've made sure I've installed the D3DCOMPILER_47.DLL as per UD2's post, and I've tried switching to both win10 and win11 compatibility via winetricks, to no avail. The fact that they got it running in CrossOver means there must be some magical configuration what allows it to run; I just haven't stumbled on what it is yet.

It worked first try for me using the Bottles launcher and its soda-9.0.1 runner, with dxvk-gplasync-v2.5.1.2, vkd3d-proton-2.13, and latencyflex-0.1.1 though I also have the following dependencies installed via its UI from running other games:

d3dx9
d3dx11
d3dcompiler_42
d3dcompiler_43
d3dcompiler_46
d3dcompiler_47
dx8vb
quartz
vcredist2019
vcredist2022

This is all installed from Flatpak, so should work nicely regardless of distro too.

[Bassa-Bassa]

since CRS is a square-aspect game?

Is it, though? The original version was displayed at 4:3, being an X68000. (3:4 if tate, but that never looked to me as the intended ratio.)

[lpslucasps]

since CRS is a square-aspect game?

Is it, though? The original version was displayed at 4:3, being an X68000. (3:4 if tate, but that never looked to me as the intended ratio.)

The "internal resolution", so to speak, is 1:1. You can verify that by looking at anything that's supposed to be a circle (say, the bomb effect) and seeing how it's a bit stretched at 4:3. However, if you're trying to emulate the experience you'd have on genuine hardware, you'd play it with a little of stretching anyway, since the Sharp X68000 monitor was a standard 4:3 monitor. It's a similar situation to the one we have with the SNES, where the graphics were internally drawn at 8:7 but supposed to be displayed on a standard 4:3 TV.

[Bassa-Bassa]

^My point, in fact. The "internal resolution" thing is an arbitrarism when talking of anything from the CRT era.

[Warp_Rattler]

Use Proton-GE. It runs flawlessly.

I haven't gone much beyond using Steam's integrated Proton versions, since things have mostly Just Worked™ on that front, so I'm pretty ignorant of what that process entails. I always had the impression that setting up external Proton builds and running non-Steam games took quite a bit of work. Is it annoying to set up?

It worked first try for me using the Bottles launcher and its soda-9.0.1 runner, with dxvk-gplasync-v2.5.1.2, vkd3d-proton-2.13, and latencyflex-0.1.1 though I also have the following dependencies installed via its UI from running other games:

d3dx9
d3dx11
d3dcompiler_42
d3dcompiler_43
d3dcompiler_46
d3dcompiler_47
dx8vb
quartz
vcredist2019
vcredist2022

This is all installed from Flatpak, so should work nicely regardless of distro too.

Thanks for this list--it will give me something to compare with on my own installation and see if I'm missing any of these items. I'm off my main computer for a few days due to my house being torn apart to have windows (the architectural feature, not the OS) replaced, so I can't check for sure, but I suspect I may at least be missing the 2022 VC Redistributable and possibly DX11 as well.

I haven't used Bottles--I always thought the "use a different WINE prefix for each title" advice was wildly impractical from a disk space perspective; does Bottles just put a nicer interface on the same process?

[lpslucasps]

^My point, in fact. The "internal resolution" thing is an arbitrarism when talking of anything from the CRT era.

I mostly agree, but for CRS specifically I prefer to play at the "internal resolution (1:1). I find the stretched circles too distracting in this case, and the pixel-aspect ratio more pleasant to my eyes.