Reply 2540 of 3949, by Dege
I intend this WIP to be the last before the next version.
I'm going to start extensive testing and if no regression bug(s) found or reported then I release it as the new version.
What I changed:
- Some D3D8 bugs fixed (Z Steel soldiers, AIM2)
- A general bug from code refactoring is fixed (can cause crash at startup or exit in some app)
- Some general and D3D5 bug is fixed (Stunt GP, The Creed)
- Revised the readme content and converted from txt to html
- Introduced option 'No filtering' for DX
- Config changes:
- MSAA option 'Auto' is renamed to 'App driven' and made to be the default instead of 'Off'
- Option 'Capture mouse' is enabled by default (not yet sure if it's a good idea, I revert it)
Hey Dege, any luck with SC1 shiny texture bug? […]
Hey Dege, any luck with SC1 shiny texture bug?
I have seen something strange with the options inside the SC1 game.
If i go to the Video options inside the game i can only see the video option up to medium preset. I have tested with GF4 and i can see High and Very High options when using buffer mode.
Is it a bug? If i/can use the ini from the GF4 machine and play without any change, will the game use the High and very High preset? Or the game will use whatever it thinks it can handle?
I'm afraid we limit the details because of the above issue.
Maybe some day I figure it out as I did with shadow buffering... 😐
However, I checked this option issue but found nothing... 'High' and 'Very high' is available for me from main menu and ingame too, and seems to be working, even with 64MB of emulated VRAM.
Works fine here (Win10 64-bit). Maybe copy protection, try finding a crack. […]wrote:
Stunt GP - Rendering issues in D3D mode. Glide works fine.
Sorry for hijacking the thread, but what OS are you using? Neither D3D nor Glide mode works at all here on Win10 64 bit.
Works fine here (Win10 64-bit). Maybe copy protection, try finding a crack.
Anyway, some screenshots, first off Z Steel Soldiers which isn't drawing the ground letting us see the skybox instead:
Second we have Stunt GP which looks to have some palette corruption issue?:
Finally The Creed, which has some texture corruption problem, look at the two white and blue police cars at the bottom:
Just in case any of the screenshots makes you go "oh I know what that is". For The Creed, maybe gho's comments are helpful:
https://sourceforge.net/p/dxwnd/discussion/ge … hread/e9e923db/
StuntGP worked for me out of the box on both Win7 and Win10.
Odd. I just uninstalled and reinstalled from the original CDs and both the Battlezone and Red Odyssey installers work fine on my […]wrote:
-The Red Odyssey
I have problems installing it. On Win7, installer of BattleZone gets stuck for me, so I installed it all in a virtual machine (XP), and the game seems to run fine inside it (sw rendering).
However when I copied the registry keys into Win7 that the installer wrote into the registry, Red Odyssey still sees BattleZone uninstalled. I still couldn't figure out what I missed.
Odd. I just uninstalled and reinstalled from the original CDs and both the Battlezone and Red Odyssey installers work fine on my Win 7 64-bit machine. The BZ setup.exe is dated 1998-01-28.
Are you using a demo version or the original CD?
Edit: Where does it get stuck? There is a radio news report that plays during the installation. It should be possible to simply click past it, but perhaps it needs to complete?
Uhmm, it's just the usual for me: InstallShield sends a broadcast message at startup to all app windows with infinite timeout, and something (an app) doesn't pump its message queue to respond, so InstallShield gets stuck (congratulation goes to the...). I just can't figure it out what it can be as I don't have any special app or pre-installed crap on my computers. Others reported that Logitech mouse can cause this but for me, it's definitely not the case.
Anyway, I was managed to install Red Odyssey on a 3rd computer with Win7 x64 and importing the reg keys from there seems to work.
I checked it, and indeed main menu is rendered in windowed mode (must be a real window placed over the DX one which isn't compatible with DXGI), but the game is usable. I can enter a mission, in true fullscreen, as you wrote, and going back to main menu is not a problem. Saving/loading works. I'll check it on Win10 tomorrow.
I installed BattleZone, then Patch 1.4 and Red Odyssey itself.
any idea why every game is forced vsync on? dgvoodoo has it off, graphics driver has it forced off, still forced vsync for NFS 4 […]
any idea why every game is forced vsync on?
dgvoodoo has it off, graphics driver has it forced off, still forced vsync for NFS 4, NFS 2 SE and every other game is vsynched.
NFS 4 doesnt force to use vsync though. It has just a framelimiter of 64 while driving. ESC menu is uncapped, main menu I remember being uncapped too.
NFS 2 was completely uncapped, even ingame.
Why is now every game with glide forced to use vsync now? And nGlide has the same problem. What is going on here?
Any word on this??
This happens for Glide. I tried NFS 2 non-SE with DirectX8 and there it was uncapped.
That's weird. If it happens with nglide too then it must be some global setting somewhere.
What about other, non wrapped games?
Edit: new WIP version doesn't read the old config files with version 2.53 from previous WIPs. Sorry for the inconvenience....