Official release thread for WindowCast core

Well it’s working so even if updates aren’t as forthcoming, you can just use it as it is.

Hello guys, i dont know if other people have this issue too but i have this

You can see my OBS window has not entire in the CRT maximus royale shader (i dont know for what because this is the only shader with this issue) somebody have a fix at this ?

Maybe I’m late to the party, but why don’t I see more posts about this?

This seems to be the evolution of Cast Core and it’s free on Steam.

3 Likes

They’re two different programs, you don’t need Steam or Retroarch for Shader Glass.

2 Likes

I don’t think it is the evolution, WindowCast is better IMO.

1 Like

Why, is it latency related?

IMO, shaders work better within RetroArch and it is better to get they working with games from Windows Cast than from ShaderGlass.

So both will have some lag?

I just download the links at the top, Gitlab has no builds, just source code and dependencies?

For whatever reason this runs less than 1 FPS with the latest Nightly Build of Retroarch and the latest Nvidia drivers.

I have “Preferred DXGI Swapchain” selected.

If I turn shaders off, everything is smooth. Using Vulkan, double checked, with HDR.

I did notice this in the text log output:

swap_interval 0 (vsync off) overridden to 1 because VK_DATA_FLAG_EMULATE_MAILBOX requires non-zero swap_interval.

Edit:

Solved partially, Retroarch was set to 60 hz refresh, when monitor was set to 120, so I had to manually override refresh to 120.

Now a new problem:

When I try and load Megabezel shaders with WindowCast, it isn’t looking in the standard /retroarch/shaders tree for shaders.

Instead, Windowcast is looking in /config/WindowCast/shaders , etc., for everything!

What gives?

I ended up making a symbolic link to the shaders_slang folder under config\WindowCast…

Now I can load shaders, but everything still crashes. And even when I don’t have a shader loaded, when I press ctrl + alt + t, the video freezes in Retroarch, but I hear sounds.

I noticed that the " | | " pause symbol is in the top right whenever I do this. This shouldn’t be pausing. Something has changed in the latest Nightly Build that is breaking this.

Help! Please!

Shaders work fine in everything but this core.

note: the pausing was due to a interface option within Retroarch: “Pause when window not active.” Set that to “off” to fix the pausing.

Other issue remains. Nonstop Vulkan malfunction when using any slang shaders such as MegaBezel.

Okay, Windowcast works perfectly fine in 1.19.1 on this PC.

In the latest builds, however, it constantly spits out:

[Vulkan] Failed to allocate texture memory (VkResult: -2)

This core must be dead and buried, unless someone else can prove to me otherwise.

It doesn’t have to be the Core causing issues. It could be a bug introduced by other changes to RetroArch itself. Why not report it?

Yep, I have on github.

1 Like

After further investigation, it seems as if this core is hitting my VRAM limit of 12 Gigabytes on this particular PC, and causing a hard Crash to Desktop in Retroarch.

Event viewer confirms this crash in Windows 10.

I never had this issue before. Why is this core now creating 12288x12288 framebuffers?

Those are not needed.

Particularly when trying to capture a 320x240 or 640x480 game window.

No other core does this.

It’s not the WindowCast Core that’s doing this…

Use a Standard Preset, don’t upscale or use a DREZ preset.

1 Like

Found it!

shader21 = “shaders_slang/bezel/Mega_Bezel/shaders/scalefx/hsm-scalefx-pass4.slang” alias21 = “” wrap_mode21 = “clamp_to_border” mipmap_input21 = “false” filter_linear21 = “false” float_framebuffer21 = “false” srgb_framebuffer21 = “false” scale_type_x21 = “source” scale_x21 = “3.000000” scale_type_y21 = “source” scale_y21 = "3.000000

the 3.00000 was the culprit!

Not sure where the scalefx shader is manipulated within the MBZ shader settings options, but I manually edited this from 3.0 to 1.0 in the preset file and the problem went away. VRAM usage dropped significantly.

Why are you doing all of that when the shader has already done that for you? That’s why there are different performance tiers. It’s one of the reasons for the DREZ presets as well. I already gave you the recommended solution.

1 Like

I had never messed with the DREZ stuff, til now. You gave me an idea, actually, as for the longest time I was stuck with whatever input res Steam games fed into Windowcast. DREZ settings are brilliant, and now the higher res games are looking proper NES-like @ 224, with a few tweaks in my 1980s Slot Mask presets.

Thanks!

2 Likes

Screenshots/Photos/Videos or it didn’t happen!

2 Likes

Alright, here’s a few…

First is a 1980s style RF connection NES TV that is rather typical of the TV set handed down to kids from their parents:

The next two are your failing late 1970s TV sets that kids were sometimes stuck with, complete with all the color distortion and noise:

All of these were generated with HDR on in Retroarch, so the colors won’t look right in SDR.

I had friends with the ultra shitty set, and the top one is pretty close to what we gamed on in college.

I’m old.

2 Likes

Looks good to me, I only do HDR. Wish I could zoom in though, but I guess I’ll have to download first.

1 Like