[LogiCow]

I've been working on a DirectX 11 renderer for mzx.
It skips the scaler and doesn't filter anything.
It supports layers (and therefore unbound sprites).
It runs in its own thread.
A single shader handles both non-smzx and smzx modes.

I could add a step to render in 640x350 and scale it up, or split up regular and smzx modes to skip a condition in the shader but I think it runs well enough the way it is at the moment.

Let me know if you've got a windows PC supporting DirectX 11 that can't reach 60 frames per second at your desktop's native resolution, has rendering errors or has significantly worse performance compared to other renderers.

https://github.com/l...ee/d3d11_branch

As a side note, the shoddy threading code has an SDL_Delay(0) loop checking for updates, which should probably be changed before merging to the master repository as it wastes ~15% CPU not doing much.

This post has been edited by LogiCow: 21 May 2018 - 04:25 AM

[LogiCow]

Here's an executable compiled and set up to use d3d11 with the framerate counter enabled.

Update: fixed row pitch issue on textures, tweaked scaling, threads use conditions and signals, fixed transparency on colors above 255, fixed SMZX indices

Attached File(s)

•  mzx291c-x64-d3d11_4.zip (4.51MB)
  Number of downloads: 2

This post has been edited by LogiCow: 24 May 2018 - 09:41 AM

[Graham]

Hmm. Well it appears to not currently support indicies files in MZX mode 3. at least that's what it looks like to me.

this is how the screen should look
 screen0.png (27.1K)
Number of downloads: 17


But this is how it appeared when I tested it
 Untitled.png (182.87K)
Number of downloads: 24


I wasn't able to use F12 to grab a picture. The picture it grabbed looked correct. That is the photo I included of the correct image. I had to print screen and copy to paint and save it.

[Graham]

also my player sprite did not appear on screen when I tried walking around. I think he was below other layers of sprites.

[KKairos]

Graham, on 22 May 2018 - 09:26 PM, said:

But this is how it appeared when I tested it
Untitled.png

I don't see the problem

[LogiCow]

I made the renderer force update the palette and indices texture every frame and it solved the issue for now, since at the moment there's no good way to know if/when indices changed.

[Graham]

That fixed it. Performance seemed comparable to GLSL that i'm currently using. I wasn't sure how to bring up the framerate counter, could you elaborate? There was a lot of screen tearing with DirectX; I don't experience any with GLSL.

[LogiCow]

for tearing It's using the "gl_sync" config var, which defaults to false. (Doesn't apply on windows 10 in a window, where everything is triple-buffered)

Framerate counter shows up in the window title at the top, but it's not visible when full-screen.

[Graham]

LogiCow, on 27 May 2018 - 11:54 AM, said:

for tearing It's using the "gl_sync" config var, which defaults to false. (Doesn't apply on windows 10 in a window, where everything is triple-buffered)

Framerate counter shows up in the window title at the top, but it's not visible when full-screen.

Oh ok gotcha. I always use full screen. Just a habit. I’ll try windowed mode.