GitHub.com/elishacloud/dxwrapper/releases (http://github.com/elishacloud/dxwrapper/releases)
Follow instructions.
And in the config file:
Wrappermode = d3d8to9
D3d8to9= 1
DDrawCompat = 1
DDrawCompat20 =1
ForceSoftwareMixing =1
I made the changes, but did not notice anything different. Did I miss something?
Thanks.
Quote from: kidnasty on April 07, 2023, 10:01:48 PM
I made the changes, but did not notice anything different. Did I miss something?
Thanks.
Were you able to use ffedit with edit in game before? It never worked for me with win10 until now.
Yes, it has worked for me on win10. Tip is appreciated.
Thanks.
good find bearded. Will have to check this out later.
I just checked the compatibility of the exe in Win10 x64 to 640 x 480 and for reasons it just worked after doing that. Noted I have DX enabled in my OS's Legacy component settings as well, that works around "most" DX based glitches.
I'm not talking about ffedit2 for :ffvstr:. I mean the original.
Wow just ran into this and tried it and it worked! Thank you so much. I was running a seperate windows xp vmware instance, mostly to run ffedit...then copy the .dat file I changed over to windows 10, lol. This is awesome.
Any solution to FF1 quitting after 1 danger room session yet? Maybe I missed that or this works for that problem as well?
I'm currently using ollydbg along with voodoo2 and dxwrapper to make everything function, as well as vm winxp for 3ds max 4.2.
I don't use the danger room, but it should work for that.