Hi mates,
I just release on Helix blog the DID F-22 Total Air War fix
[url]https://helixmod.blogspot.com/2019/04/f-22-total-air-war.html[/url]
TAW is an old 1998 directx 5 game, made to run with 3Dfx Glide boards to get its best. It have one of the best compromise between Dynamic Campaigns and a sim playability until today. This is why we love it.
Today, to run it well and with good resolution we need a Glide wrapper. This last dgvoodoo2 runs it at Dx11 and with the same good visuals as an old 3Dfx glide board. Being "now" a Dx11 game, 3Dvision and 3Dmigoto can push it to a real stereo 3D game! Just a impossible thing before.
Here some pics:
[url]https://www.dropbox.com/s/chetw4kx8syqjrw/1af3e5d3U-vb.jps?dl=0[/url]
[url]https://www.dropbox.com/s/hsqzlg9nk9pplt1/1af3e5d3D-vb.jps?dl=0[/url]
[url]https://www.dropbox.com/s/catd7pfbix9b1os/1af3e5d3E-vb.jps?dl=0[/url]
Good hunt into the sky!
Rubini.
TAW is an old 1998 directx 5 game, made to run with 3Dfx Glide boards to get its best. It have one of the best compromise between Dynamic Campaigns and a sim playability until today. This is why we love it.
Today, to run it well and with good resolution we need a Glide wrapper. This last dgvoodoo2 runs it at Dx11 and with the same good visuals as an old 3Dfx glide board. Being "now" a Dx11 game, 3Dvision and 3Dmigoto can push it to a real stereo 3D game! Just a impossible thing before.
Well I was wondering why we need to use the EXE you provided and not the one from TAW 2.30?? I was getting that old error cleaning up and exiting that was fixed in TAW 2.30..
Well I was wondering why we need to use the EXE you provided and not the one from TAW 2.30?? I was getting that old error cleaning up and exiting that was fixed in TAW 2.30..
[quote="Th3_N3philim"]Well I was wondering why we need to use the EXE you provided and not the one from TAW 2.30?? I was getting that old error cleaning up and exiting that was fixed in TAW 2.30..[/quote]
Hi mate,
Because taw 2.3 uses the F22.DAT and not the F22.EXE (note that we are not speaking about the launcher that is the _f22.exe file). The F22.EXE is needed to be used on the nvdia profile as its TAW hook executable. You cant use F22.dat on nvidia profile.
On the readme of the fix i also explain that i hexedit the launcher _f22.exe to look for F22.EXE (not more F22.DAT). So you need both from the fix: _f22.exe and F22.exe to all works well. I didnt tested the fix with any other executable than the ones that I provide but I don't see why not.
Then here a second choice:
1. uses the _f22.exe (launcher) from the fix
2. rename your glide F22.DAT from taw 2.3 for F22.EXE and it also must work.
If you need any clarification on the matter just ask.
Th3_N3philim said:Well I was wondering why we need to use the EXE you provided and not the one from TAW 2.30?? I was getting that old error cleaning up and exiting that was fixed in TAW 2.30..
Hi mate,
Because taw 2.3 uses the F22.DAT and not the F22.EXE (note that we are not speaking about the launcher that is the _f22.exe file). The F22.EXE is needed to be used on the nvdia profile as its TAW hook executable. You cant use F22.dat on nvidia profile.
On the readme of the fix i also explain that i hexedit the launcher _f22.exe to look for F22.EXE (not more F22.DAT). So you need both from the fix: _f22.exe and F22.exe to all works well. I didnt tested the fix with any other executable than the ones that I provide but I don't see why not.
Then here a second choice:
1. uses the _f22.exe (launcher) from the fix
2. rename your glide F22.DAT from taw 2.3 for F22.EXE and it also must work.
If you need any clarification on the matter just ask.
OK I see thank you for the explanation.. I did not see the readme sorry but I will have a look thank you for your fix.. I used to have 3D working back when we had the fly ins back in 2007-2009, I used the dgvoodoo dx9 thos but this is cool being able to play in 3D again with the wrapper..
OK I see thank you for the explanation.. I did not see the readme sorry but I will have a look thank you for your fix.. I used to have 3D working back when we had the fly ins back in 2007-2009, I used the dgvoodoo dx9 thos but this is cool being able to play in 3D again with the wrapper..
[quote="Th3_N3philim"]OK I see thank you for the explanation.. I did not see the readme sorry but I will have a look thank you for your fix.. I used to have 3D working back when we had the fly ins back in 2007-2009, I used the dgvoodoo dx9 thos but this is cool being able to play in 3D again with the wrapper..[/quote]
Cool. Let me know if it will works for you then.
Th3_N3philim said:OK I see thank you for the explanation.. I did not see the readme sorry but I will have a look thank you for your fix.. I used to have 3D working back when we had the fly ins back in 2007-2009, I used the dgvoodoo dx9 thos but this is cool being able to play in 3D again with the wrapper..
I just release on Helix blog the DID F-22 Total Air War fix
https://helixmod.blogspot.com/2019/04/f-22-total-air-war.html
TAW is an old 1998 directx 5 game, made to run with 3Dfx Glide boards to get its best. It have one of the best compromise between Dynamic Campaigns and a sim playability until today. This is why we love it.
Today, to run it well and with good resolution we need a Glide wrapper. This last dgvoodoo2 runs it at Dx11 and with the same good visuals as an old 3Dfx glide board. Being "now" a Dx11 game, 3Dvision and 3Dmigoto can push it to a real stereo 3D game! Just a impossible thing before.
Here some pics:
https://www.dropbox.com/s/chetw4kx8syqjrw/1af3e5d3U-vb.jps?dl=0
https://www.dropbox.com/s/hsqzlg9nk9pplt1/1af3e5d3D-vb.jps?dl=0
https://www.dropbox.com/s/catd7pfbix9b1os/1af3e5d3E-vb.jps?dl=0
Good hunt into the sky!
Rubini.
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Hi mate,
Because taw 2.3 uses the F22.DAT and not the F22.EXE (note that we are not speaking about the launcher that is the _f22.exe file). The F22.EXE is needed to be used on the nvdia profile as its TAW hook executable. You cant use F22.dat on nvidia profile.
On the readme of the fix i also explain that i hexedit the launcher _f22.exe to look for F22.EXE (not more F22.DAT). So you need both from the fix: _f22.exe and F22.exe to all works well. I didnt tested the fix with any other executable than the ones that I provide but I don't see why not.
Then here a second choice:
1. uses the _f22.exe (launcher) from the fix
2. rename your glide F22.DAT from taw 2.3 for F22.EXE and it also must work.
If you need any clarification on the matter just ask.
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Cool. Let me know if it will works for you then.