Sharangad, I do not NEED anything of this. Your work is awesome and I love it. But there is nothing that I NEED(!). It'd be nice, but that's it. Being able to play ICR2 at such a resolution is already more than could ever be wanted. You did an awesome job here and I'll try to keep track on your work, but please don't feel urged to implement anything based on my request...

I can play it the way it is and that's fine for me. 😀

supererwin wrote on 2025-01-11, 14:48:

Okay, I disabled AA and I disabled Line rendering, still the GPU gets about 35% load.

The fact that there is no window positioning is a bit annoying as with my setup (three monitors), the "fullscreen window" sits on the left monitor. 😀

It should be on the primary monitor.

supererwin wrote on 2025-01-11, 15:15:

Sharangad, I do not NEED anything of this. Your work is awesome and I love it. But there is nothing that I NEED(!). It'd be nice, but that's it. Being able to play ICR2 at such a resolution is already more than could ever be wanted. You did an awesome job here and I'll try to keep track on your work, but please don't feel urged to implement anything based on my request...

I can play it the way it is and that's fine for me. 😀

Checkpoint10 on the icr2.net forums wants positioning as well. It *should* be a simple thing to add. It won't work for vhexen2 though that has its own window centering.

It should be easy enough to add to add a position. I hope.

*********************************************************************
RReady Alpha, January 12, 2025 (Untested Alpha Release,)
*********************************************************************
https://nirvtek.com/downloads/RReady.Alpha.20250112.001.7z
MD5: 18983b8a716eab970f813b74327bc754

- Window positioning/centering controls in RLauncher with support from the wrapper.
(Note: Position (0,0) is the top left of the primary monitor. Anything to the left/top of the primary will have a negative x/y coordinate or possibly both.
********************************************************************

Works just fine, log attached.

Is it possible to get a real "Window" which you can touch with the mouse at the top in order to drag it around?

Thanks again,
supererwin

supererwin wrote on 2025-01-11, 23:33:

Works just fine, log attached. […]
Show full quote

Works just fine, log attached.

Is it possible to get a real "Window" which you can touch with the mouse at the top in order to drag it around?

Thanks again,
supererwin

For the dos stuff I can add a feature for that. How badly do you need it?

https://nirvtek.com/downloads/RReady.Alpha.20 … BENTERbugfix.7z
MD5: 2bdc27f53bbc7ad5b7a0eb3a484ee706

- Corrects bug with [ALT+TAB] or [ALT+ENTER] when running Speedy3D apps in windowed or fullscreen mode.

I bought the Rendition Wrapper to be used for ICR2
Build date 5-1-2025
Wotks fine but with frame generation white flashing screen
What I am doing wrong?
This is culprit errot

12:12:41.208 1468 [0] GL Error GL_INVALID_ENUM (1280) : RenderToMultiTexture::StartCapture entry

Canadair wrote on 2025-01-12, 06:44:

I bought the Rendition Wrapper to be used for ICR2 Build date 5-1-2025 Wotks fine but with frame generation white flashing scree […]
Show full quote

I bought the Rendition Wrapper to be used for ICR2
Build date 5-1-2025
Wotks fine but with frame generation white flashing screen
What I am doing wrong?
This is culprit errot

12:12:41.208 1468 [0] GL Error GL_INVALID_ENUM (1280) : RenderToMultiTexture::StartCapture entry

I understand an updated version is on the way
I tested demo alpha builds and they seem ok, but how to update?

Canadair wrote on 2025-01-12, 06:52:

Canadair wrote on 2025-01-12, 06:44:

I bought the Rendition Wrapper to be used for ICR2 Build date 5-1-2025 Wotks fine but with frame generation white flashing scree […]
Show full quote

I bought the Rendition Wrapper to be used for ICR2
Build date 5-1-2025
Wotks fine but with frame generation white flashing screen
What I am doing wrong?
This is culprit errot

12:12:41.208 1468 [0] GL Error GL_INVALID_ENUM (1280) : RenderToMultiTexture::StartCapture entry

I understand an updated version is on the way
I tested demo alpha builds and they seem ok, but how to update?

I'm sorry about that.

I'm testing the next build. Unfortunately I've been sidetracked a bit. I'm planning on releasing it to the store in another 18 hours roughly. The store takes between a few hours to 3 days to actually release stuff, but usually just a few hours. I've actually been repeating my testing the dos stuff a few times because of a few problems.

[EDIT] Most of the tests have passed, multiple times. I should be able to push it out to the store this afternoon.

sharangad wrote on 2025-01-12, 07:35:

I'm sorry about that. […]
Show full quote

Canadair wrote on 2025-01-12, 06:52:

Canadair wrote on 2025-01-12, 06:44:

I bought the Rendition Wrapper to be used for ICR2 Build date 5-1-2025 Wotks fine but with frame generation white flashing scree […]
Show full quote

I bought the Rendition Wrapper to be used for ICR2
Build date 5-1-2025
Wotks fine but with frame generation white flashing screen
What I am doing wrong?
This is culprit errot

12:12:41.208 1468 [0] GL Error GL_INVALID_ENUM (1280) : RenderToMultiTexture::StartCapture entry

I understand an updated version is on the way
I tested demo alpha builds and they seem ok, but how to update?

I'm sorry about that.

I'm testing the next build. Unfortunately I've been sidetracked a bit. I'm planning on releasing it to the store in another 18 hours roughly. The store takes between a few hours to 3 days to actually release stuff, but usually just a few hours. I've actually been repeating my testing the dos stuff a few times because of a few problems.

[EDIT] Most of the tests have passed, multiple times. I should be able to push it out to the store this afternoon.

actually never bought anything form MS store, so I am not familiar. How to update?

this will be updated itself, when you try to launch RReady and ms store have updated version.

Canadair wrote on 2025-01-12, 08:06:

sharangad wrote on 2025-01-12, 07:35:

I'm sorry about that. […]
Show full quote

Canadair wrote on 2025-01-12, 06:52:

I understand an updated version is on the way
I tested demo alpha builds and they seem ok, but how to update?

I'm sorry about that.

I'm testing the next build. Unfortunately I've been sidetracked a bit. I'm planning on releasing it to the store in another 18 hours roughly. The store takes between a few hours to 3 days to actually release stuff, but usually just a few hours. I've actually been repeating my testing the dos stuff a few times because of a few problems.

[EDIT] Most of the tests have passed, multiple times. I should be able to push it out to the store this afternoon.

actually never bought anything form MS store, so I am not familiar. How to update?

I've submitted it to the store. I've repeated the whole test suite 3 times last week testing minor changes, I don't think it needs anymore testing.

The store has to certify the release and that can take between 3 hours to 3 days.

I'll post here and on youtube when the update gets pushed out. It might still take short while for the update to actually get pushed out to their deployment servers and be actually available to you.

To update it:

Run the Windows Store up and click on the downloads button (cloud icon) at the bottom of the bar on the right. Check that the update has installed or click the "Update now" button next to RReady Rendition Verité.

Once this is done run the store based RLauncher (RLauncher.exe icon on the desktop, I think) and launch dosbox (or dosbox staging if that's what you're using) from there. This should update the dosbox execution folder (If you followed @gplaps guide, this is the ICR2 folder). The game should run. The next time you run this, the updated version should be in the ICR2 folder, where you installed it. If you're using Dosbox-Staging-Rendition to update the folder that version runs from you need to launch it from the RLauncher.exe icon on the desktop (the store based RLauncher).

It might take a while for the update to be certified. It's Sunday afternoon here and I don't know where the Microsoft testers are based. They do sometimes certify stuff on Sunday. I've had updated roll out on Sundays before.

Once the update has installed the RLauncher icon's info page should show something like this:

Has anyone run ICR2 with RReady frame interpolation at a refresh rate that wasn't an even multiple of 60 Hz?

I've got a user who's getting a rather strange error I've never seen before. It's not a DMA stability GPU performance issue. It's a very very fast machine with a fast GPU, but mem read is failing not with DMA access, somewhere else.

He's running it at 1024x768@75 with frame interpolation which might be the problem. I've asked him to try it at 60 Hz. This is very very weird.

sharangad wrote on 2024-11-27, 00:34:

Myloch wrote on 2024-11-26, 20:34:

Oh gosh I wish something like this exists for S3D (Destruction Derby for S3 Virge).

I think somebody's working on S3D support.

This:?
S3d wrappers

BEEN_Nath_58 wrote on 2025-01-12, 13:32:

sharangad wrote on 2024-11-27, 00:34:

Myloch wrote on 2024-11-26, 20:34:

Oh gosh I wish something like this exists for S3D (Destruction Derby for S3 Virge).

I think somebody's working on S3D support.

This:?
S3d wrappers

Nope. I think @RaVeN-05 linked to a Hardware accelerated version somewhere on this thread.

I can never find it when I need to.

no hardware accelerated s3d wrappers known to me.
there is emulation in 86box and PCEm which you can use video card S3 Virge compatible.
this is very slow.
probably Tuxality tried to make wrapper at some point. but nothing is released.
and now we have s3d software rendered wrapper

RaVeN-05 wrote on 2025-01-12, 16:03:

no hardware accelerated s3d wrappers known to me. there is emulation in 86box and PCEm which you can use video card S3 Virge com […]
Show full quote

no hardware accelerated s3d wrappers known to me.
there is emulation in 86box and PCEm which you can use video card S3 Virge compatible.
this is very slow.
probably Tuxality tried to make wrapper at some point. but nothing is released.
and now we have s3d software rendered wrapper

But the software renderer could be accelerated?

sharangad wrote on 2025-01-12, 16:52:

RaVeN-05 wrote on 2025-01-12, 16:03:

no hardware accelerated s3d wrappers known to me. there is emulation in 86box and PCEm which you can use video card S3 Virge com […]
Show full quote

no hardware accelerated s3d wrappers known to me.
there is emulation in 86box and PCEm which you can use video card S3 Virge compatible.
this is very slow.
probably Tuxality tried to make wrapper at some point. but nothing is released.
and now we have s3d software rendered wrapper

But the software renderer could be accelerated?

The first thing I would need is to get the wrapper to work somewhere at least. It hasn't yet worked with dxwrapper 😀.

The only wrappers left now, are Creative CGL, PowerVR api, Paradise Tasmania 3D? And the ati wrapper is incomplete

Edit: missed NV1