Have you tried installing it in a VM and copying the files from there.

alexanrs wrote:

Have you tried installing it in a VM and copying the files from there.

I didn't....

But when I did install it under Ubuntu (thank you, Wine!), I realized I had all the files I needed - I just didn't know the file structure the program expected. As such, I simply followed the 'instructions' provided by the correctly-installed Final Reality, and BAM! It works now!

Final Reality works fine for me under Windows 10 Pro x64. I installed it in an earlier version of Windows, then copied the files over.
You don't need to do anything special for DX5 (no need for dgVoodoo or whatever). Windows 10 supports all versions of DX out of the box. Not sure why anyone would think differently.

Does Windows 10 support Retained Mode or any of those crazy esoteric rendering codes that depend on older GPU quirks?

Scali wrote:

Windows 10 supports all versions of DX out of the box. Not sure why anyone would think differently.

Supports, but doesn't necessarily behave the same as older operating systems.
A number of games (e.g. Max Payne 1&2) seem to run at an unlocked framerate as if V-Sync was off, but also don't show any screen tearing - as though they're running in borderless windowed mode rather than full-screen exclusive mode.

DracoNihil wrote:

Does Windows 10 support Retained Mode or any of those crazy esoteric rendering codes that depend on older GPU quirks?

No, not out of box. But you can copy the xp version of d3drm.dll into the games directory.
Besides, only a few games use that. I only know of two, which do : Buster by Mr. Hashimoto and Guardian of Paradise.

Another issue is the lack of proper DirectDraw. It's nolonger there in it's native form.
Only the emulation part is still there (handled by D3D). You'll noticed this by the lack of bilinear filtering, for example.
This is because DirectDraw nolonger has the ability to bit-blitt into VRAM (-> Desktop Window Manager).

Speaking of this, I had an issue with VPC 200x and Win7 in conjunction with this (slow screen update).
My workaround was to put a copy of XP's ddraw.dll in the virtual PC directory.
Worked quite well. Doing so forced ddraw to use software-rendering instead of the buggy emulation done by Direct3D.

This reminds me of an issue with OpenGL. You can enable OpenGL in a VM (like VPC) by using the NT4 version of Opengl32.dll.
That one is limited to OpenGL 1.2, but it still has software-rendering..

Nice tricks, Jo22 😀

Deep Thought wrote:

Supports, but doesn't necessarily behave the same as older operating systems.
A number of games (e.g. Max Payne 1&2) seem to run at an unlocked framerate as if V-Sync was off, but also don't show any screen tearing - as though they're running in borderless windowed mode rather than full-screen exclusive mode.

True, but games should be able to handle that, since different hardware/drivers may also behave differently.

Scali wrote:

Deep Thought wrote:

Supports, but doesn't necessarily behave the same as older operating systems.
A number of games (e.g. Max Payne 1&2) seem to run at an unlocked framerate as if V-Sync was off, but also don't show any screen tearing - as though they're running in borderless windowed mode rather than full-screen exclusive mode.

True, but games should be able to handle that, since different hardware/drivers may also behave differently.

Without V-Sync, games will stutter on the display.
And since they appear to be running in full-screen windowed mode rather than full-screen exclusive now, that means G-Sync or FreeSync won't work with them any more.

Deep Thought wrote:

Scali wrote:

Deep Thought wrote:

Supports, but doesn't necessarily behave the same as older operating systems.
A number of games (e.g. Max Payne 1&2) seem to run at an unlocked framerate as if V-Sync was off, but also don't show any screen tearing - as though they're running in borderless windowed mode rather than full-screen exclusive mode.

True, but games should be able to handle that, since different hardware/drivers may also behave differently.

Without V-Sync, games will stutter on the display.
And since they appear to be running in full-screen windowed mode rather than full-screen exclusive now, that means G-Sync or FreeSync won't work with them any more.

I wouldn't know. I haven't experienced this issue. My own DDraw code works with vsync just fine.
So I'd need more information on what happens exactly, and under which circumstances.

Do anyone have installed files from fr101.exe?

I've unpacked it with 7-ZIP. But can't install due to Windows 7 x64.
Any workaround?

spacedrone808 wrote on 2021-01-18, 22:07:

Do anyone have installed files from fr101.exe?

I've unpacked it with 7-ZIP. But can't install due to Windows 7 x64.
Any workaround?

Copy this setup32.exe file http://toastytech.com/files/Is3Engine.zip into your decompressed install directory and run it . Installation should then work on a 64-bit edition of Windows .

Source : https://reactos.org/forum/viewtopic.php?t=10988

EDIT : For some reason, it does not create a Start Menu entry on my Windows 10 x64 machine, but the installation into C:\Program Files\Final Reality (default) worked fine .

darry wrote on 2021-01-18, 22:45:

Copy this setup32.exe file http://toastytech.com/files/Is3Engine.zip into your decompressed install directory and run it . Insta […]
Show full quote

spacedrone808 wrote on 2021-01-18, 22:07:

Do anyone have installed files from fr101.exe?

I've unpacked it with 7-ZIP. But can't install due to Windows 7 x64.
Any workaround?

Copy this setup32.exe file http://toastytech.com/files/Is3Engine.zip into your decompressed install directory and run it . Installation should then work on a 64-bit edition of Windows .

Source : https://reactos.org/forum/viewtopic.php?t=10988

EDIT : For some reason, it does not create a Start Menu entry on my Windows 10 x64 machine, but the installation into C:\Program Files\Final Reality (default) worked fine .

Thank you so much, i will try appointed sollution!

In case this shouldn't work (-I really hope it does-) you can also try to run the 16-Bit installer via WineVDM/OTVDM.
Winevdm

Jo22 wrote on 2021-01-20, 10:24:

In case this shouldn't work (-I really hope it does-) you can also try to run the 16-Bit installer via WineVDM/OTVDM.
Winevdm

Everything worked, thank you for advice!