Reply 2220 of 2285, by RaVeN-05
- Rank
- Oldbie
RReady.Alpha.20250110.004.AMDTest
logs
RReady.Alpha.20250110.004.AMDTest
logs
Let me just say: it works fine!
I love your work! Perfect! Thank you oh so much!
supererwin wrote on 2025-01-10, 17:38:Please find attached the logfiles I just generated from your last upload. […]
Please find attached the logfiles I just generated from your last upload.
Sorry, I've been busy all day long and could not keep up with your posts here in the forum...
I suppose, you know the settings of your tool from the logfiles. If not, let me know, I will make a screenshot.
Sill, I got the problem of not being able to use accelleratrion or custom keymappings within dosbox - just to say this. 😀
All the best,
supererwin
No problem.
@supererwin I see no errors in the logs, just like Raven-05's logs.
Does it work without a problem? Do you get frame interpolation? From the logs it looks like it's working. i suspect Raveb-05's machine is working as well without a problem.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
supererwin wrote on 2025-01-10, 22:46:Let me just say: it works fine!
I love your work! Perfect! Thank you oh so much!
Thanks!
I have one final build for testing:
https://nirvtek.com/downloads/RReady.Alpha.20 … .001.AMDTest.7z
MD5: fee774a66f8f0ec57a14d65e71b62fad
This one has all the error checking disabled and should be marginally faster and I mean marginally.
If this works, we're home free and this will go into testing over the weekend.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
supererwin wrote on 2025-01-10, 17:49:Just a quick info, as I cannot edit my posting before - the keybindings have been adjusted. All my fault. Problem between monitor and chairback 😁
Plus: I also found the dosbox-mapper file: It's in C:\Users\USER\AppData\Local\DOSBox
I think the folder %localappdata%\Dosbox for settings and %localappdata%\temp for logs is a bit confusing. It's the preferred location for these things, but the folder itself is hidden away from users, i..e. there's no shortcut.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
RaVeN-05 wrote on 2025-01-10, 18:14:RReady.Alpha.20250110.004.AMDTest
logs
Good news Raven-05, your frame interpolation is in fact working, like you said. I suppose you don't need me to tell you that.
What kind of performance do you get with interpolation turned on? Just curious. The vast majority of bug reports I get are from either GTX1050s/1060s and GTX1650s/GTX1660s, so it's quite refreshing to see logs from other machines.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
Scorched Planet doesn't even install off the cd with dosbox or staging. The batch file does run with daum. In dosbox I had to copy the files out of the rendition folder. I did manage to get it to run on the Stealth II, but the colours were off, full screen palette effects in dosbox I guess. It runs just fine on the 3dblaster.
At some point there'll be daum and X support.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
@Raven-05 I'll add the option to disable Rendition AA for all games. Can't do it for this release.
Oh BTW, vquake at 800x600/16 with 16 MB of VRAM is a lot smoother on easy, literally buttery smooth. I guess the game spends less time loading textures. It seems to have very good memory management.
The timedemos not so much. But actual gameplay with regular settings (with d_mipscale 1 and witout d_amip) is very fluid, a lot better than before.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
I think I noticed a small bug. When running MecWarrior 2 with RReady. the game scales up to a resolution which is 64 times that of my monitor. I have a fake 16K resolution configured in and it goes to that resolution. The App Specific Settings in the Windows APPS panel in not available.
Another glitch I noticed is, the RReady configurator had frozen in the middle of it working, since Windows decided to run a late Cloud check instead of doing it before launch
previously known as Discrete_BOB_058
BEEN_Nath_58 wrote on 2025-01-11, 09:05:I think I noticed a small bug. When running MecWarrior 2 with RReady. the game scales up to a resolution which is 64 times that of my monitor. I have a fake 16K resolution configured in and it goes to that resolution. The App Specific Settings in the Windows APPS panel in not available.
Another glitch I noticed is, the RReady configurator had frozen in the middle of it working, since Windows decided to run a late Cloud check instead of doing it before launch
There's an option for high DPI which you need to uncheck in DxWnd (SetDPIAwareness under Video. I have it set because I have a high DPI monitor at the moment). I guess I'll have to provide two different distributions with and without high DPI support for DxWnd. The link I gave you on sourceforge has it turned on. I still can't run i'76 on my UHD620 with RReady and DxWnd. I can run ICR2 now which makes for a nice change. Need to retest my old HD2000 to see if it can handle it now, but I have a lot of other things to do.
I have a malware warning issue with Dosclient, even the store based version ends up being zapped as being malware even though Microsoft themselves check the binary for malware and would never release it if it were malware. Submitting a report fails, the Microsoft false positive website reports its not malware but them closes the ticket and i never get the analyst's report. I used to get those. Then I started getting emails saying they only test binaries if a significant number of users report it as not being malware and now nothing. Maybe they get a lot of reports and can't handle the load. It's a bit of a show stopper.
I don't know to control the cloud check. Isn't that a Windows setting or it it manifest related?
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
you could release RReady at MS Store temporary without dosclient.exe and write warning in RLauncher app and in documentation , something like : it false flagged and you can get this file elsewhere , sorry for inconveniences , this hopefully will be solved in future.
tested RReady.Alpha.20250111.001.AMDTest evrything works.
i have somewhat 45 fps average, somethimes i hit less than 30 not often, and hits 60 fps sometimes. its great optimizaton. i now can play it with pleasure.
RaVeN-05 wrote on 2025-01-11, 10:12:you could release RReady at MS Store temporary without dosclient.exe and write warning in RLauncher app and in documentation , something like : it false flagged and you can get this file elsewhere , sorry for inconveniences , this hopefully will be solved in future.
tested RReady.Alpha.20250111.001.AMDTest evrything works.
i have somewhat 45 fps average, somethimes i hit less than 30 not often, and hits 60 fps sometimes. its great optimizaton. i now can play it with pleasure.
I can't do that, nobody would download it.
Phew! I'm glad that works, I've already started testing the build. Ran into a bit of a problem with frame interpolation. I started checking the code and retested stuff wondering why this wasn't working. Turned out the Win 11 24H2 update did a clean reinstall of the video drivers which reset the power profile. Aaaargh! I can't believe I didn't check that sooner, getting old and slow.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
Makes sense , you right, and recoding it so it not detects almost impossible since this isn't a few bytes as i trough .
i split file to 500 bytes and then to 1000, each piece of file isn't detected.
sharangad wrote on 2025-01-11, 09:37:There's an option for high DPI which you need to uncheck in DxWnd (SetDPIAwareness under Video. I have it set because I have a h […]
BEEN_Nath_58 wrote on 2025-01-11, 09:05:I think I noticed a small bug. When running MecWarrior 2 with RReady. the game scales up to a resolution which is 64 times that of my monitor. I have a fake 16K resolution configured in and it goes to that resolution. The App Specific Settings in the Windows APPS panel in not available.
Another glitch I noticed is, the RReady configurator had frozen in the middle of it working, since Windows decided to run a late Cloud check instead of doing it before launch
There's an option for high DPI which you need to uncheck in DxWnd (SetDPIAwareness under Video. I have it set because I have a high DPI monitor at the moment). I guess I'll have to provide two different distributions with and without high DPI support for DxWnd. The link I gave you on sourceforge has it turned on. I still can't run i'76 on my UHD620 with RReady and DxWnd. I can run ICR2 now which makes for a nice change. Need to retest my old HD2000 to see if it can handle it now, but I have a lot of other things to do.
I have a malware warning issue with Dosclient, even the store based version ends up being zapped as being malware even though Microsoft themselves check the binary for malware and would never release it if it were malware. Submitting a report fails, the Microsoft false positive website reports its not malware but them closes the ticket and i never get the analyst's report. I used to get those. Then I started getting emails saying they only test binaries if a significant number of users report it as not being malware and now nothing. Maybe they get a lot of reports and can't handle the load. It's a bit of a show stopper.
I don't know to control the cloud check. Isn't that a Windows setting or it it manifest related?
Would it be possible to encrypt/obfuscate the dosclient and only unlocked when one of the DLLs (verite.dll?) is called on runtime?
previously known as Discrete_BOB_058
than when dosclient.exe tried to be accessed its will be detected on fly.
BEEN_Nath_58 wrote on 2025-01-11, 11:38:sharangad wrote on 2025-01-11, 09:37:There's an option for high DPI which you need to uncheck in DxWnd (SetDPIAwareness under Video. I have it set because I have a h […]
BEEN_Nath_58 wrote on 2025-01-11, 09:05:I think I noticed a small bug. When running MecWarrior 2 with RReady. the game scales up to a resolution which is 64 times that of my monitor. I have a fake 16K resolution configured in and it goes to that resolution. The App Specific Settings in the Windows APPS panel in not available.
Another glitch I noticed is, the RReady configurator had frozen in the middle of it working, since Windows decided to run a late Cloud check instead of doing it before launch
There's an option for high DPI which you need to uncheck in DxWnd (SetDPIAwareness under Video. I have it set because I have a high DPI monitor at the moment). I guess I'll have to provide two different distributions with and without high DPI support for DxWnd. The link I gave you on sourceforge has it turned on. I still can't run i'76 on my UHD620 with RReady and DxWnd. I can run ICR2 now which makes for a nice change. Need to retest my old HD2000 to see if it can handle it now, but I have a lot of other things to do.
I have a malware warning issue with Dosclient, even the store based version ends up being zapped as being malware even though Microsoft themselves check the binary for malware and would never release it if it were malware. Submitting a report fails, the Microsoft false positive website reports its not malware but them closes the ticket and i never get the analyst's report. I used to get those. Then I started getting emails saying they only test binaries if a significant number of users report it as not being malware and now nothing. Maybe they get a lot of reports and can't handle the load. It's a bit of a show stopper.
I don't know to control the cloud check. Isn't that a Windows setting or it it manifest related?
Would it be possible to encrypt/obfuscate the dosclient and only unlocked when one of the DLLs (verite.dll?) is called on runtime?
Wouldn't the store reject a binary like that. I guess Microsoft have tools for that?
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
Everything works very fine, also with your last release, please find the log attached.
Only thing I cannot do is to have it run in a window. It's always fullscreen. If I go to "Windowed Mode", it uses one of my three screens in fullscreen, if I turn off "Windowed Mode", it mirrors one fullscreen to all three monitors.
But still, full framerate, it just works. The load of my GPU goes up to 35% - if that's of any interest to you... (seem quite a lot to me, as this GPU is really a fast one).
All the best and thanks again for your perfect work,
supererwin
supererwin wrote on 2025-01-11, 14:12:Everything works very fine, also with your last release, please find the log attached. […]
Everything works very fine, also with your last release, please find the log attached.
Only thing I cannot do is to have it run in a window. It's always fullscreen. If I go to "Windowed Mode", it uses one of my three screens in fullscreen, if I turn off "Windowed Mode", it mirrors one fullscreen to all three monitors.
But still, full framerate, it just works. The load of my GPU goes up to 35% - if that's of any interest to you... (seem quite a lot to me, as this GPU is really a fast one).
All the best and thanks again for your perfect work,
supererwin
If you're using windowed mode you need to change the resolution setting (second one from the top) to the window size. Unfortunately I haven't added window positioning controls so it'll be at the top left of the screen.
The 35% is a lot. I can think of two reasons why that could be :
1) the vertex and pixel (fragment) shaders are a complex supershader which internally handles all Rendition vertex data with lots of branching code, depending on Rendition modes.
2) icr2 carries out Rendition triple buffering and this is implemented with an opengl double buffer and a framebuffer (texture) copy. If you disable rready's implementation of Rendition aa, which doesn't work very well in icr2 there should be a significant drop in gpu usage.
3) rendition dos games (speedy3d) are very physical cpu heavy, being limited largely by single core performance.
If you run vquake2 with rready* with vsync disabled from RLauncher, it should go at over 300 fps., depending on CPU speed. With the dos apps dosbox talks to dosclient via a named pipe. The rendition wrapper is loaded by dosclient and renders into its window.
To be honest I haven't done a whole lot of gpu analysis on this, not had a whole lot of time. But I did make it go as fast as I could.
[EDIT] the reason I didn't use a permanent render to texture mode for this, which would've reduced the need for framebuffer copies is that it had issues with the three Intel HD graphics gpus I have access to, an HD 2000, 4000 and a uhd 620.
[EDIT2] To put things into perspective, I can run icr2 at 4k 60 fps on a geforce 1060 gtx, which is a relatively old gpu. The load fluctuates between 20-60%. That's another heavy game. But generally I don't monitor that stuff all that much. That might be where I'm going wrong. I'll do some load monitoring when I get the time. Nvidia's performance tools only work for the core profile and I'm using opengl 3.2 (glsl 3.3 compatibility profile). Also the latest and greatest analysis tools target gl 4.0
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda
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. 😀
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. 😀
I'll add that in at some point. Do you need monitor selection as well? I can't do this within the next 3-4 weeks. It's been on my list of things to do for a while. You might be able to get a utility which can move the window anywhere for now, maybe even in ccc. The old nview extensions for nvidia could do that before they made them workstation only.
The gpu load might be structural overhead.
Developer of RReady - Rendition Verité Wrapper.
https://www.youtube.com/@sharangadayananda