One slight modification of your routine was the addition of a boolean flag to tell the patcher wwheter to operate only on the first matching sequence or, on the contrary, to repeat the search & replace until the end of the block. I tried the activation of the hack within the routine that intercepts a Direct3DSession object, it seems a convenient place to do the trick, and passing the d3d version as argument to pick either d3dim or d3dim700. On the contrary, placing the hook in DxWnd take advantage of working directly on the system library, but it is necessary to find a convenient place to activate the hack.
Reshack rar full#
With this tecnique the weak point is that the application may easily decide to link to the dll using a full pathname pointing to the system libraries, so that the proxy is bypassed.
In your dll the hack was placed in the DLLMain routine executed at the module loading, so that there's no doubt that whenever the module is loaded the hack is activated. Unfortunately, I've got no good enough resources to make a test with very high desktop resolutions, and that's why I'm asking your collaboration: may I send you some stuff (essentially an alpha release of DxWnd and some instructions) and hope in some testing made by you? ) but the use of a hooker rather that a proxy dll introduces many differences in the hack activation, so that I think I'd need some testing will be necessary before telling the work is complete. Of course, the hack itself was left almost untouched (I'll talk about this later. I wonder if this could be fixed finally I found some time to make a tentative integration of your hack in DxWnd code. I guess it's a Desktop Window Manager bug, if you suspend winlogon.exe and terminate dwm.exe, then they can start successfully, though they don't come back properly if you tab out, unless you can toggle to windowed and back to fullscreen mode. If you have multiple monitors active and the desktop extended through all of them, games either error out or if they don't, they're unplayable with all the screens blinking. There is another problem with disabling maximized windowed mode for ddraw.dll based games that seems specific to Windows 8.1 (and probably 8 too, but haven't tested).
Reshack rar windows 10#
That setting is active on Windows 10 for all games, with older versions, it only gets activated if there is an entry for the game in the compatibility database that enables it. Seeing you're aware of the infamous maximized windowed mode on Windows 8+, I'd like to point out that a similar issue exist with Direct3D 8 on Windows 10, see:
Also, Drakan has an option for windowed mode.
Reshack rar mod#
There is 10th anniversary in the name, is it related to Drakan 10th Anniversary Mod? That mod has issues on its own. I'm curious about what is it supposed to fix. Regarding Drakan, I noticed there is a profile for it included with DxWnd, but the game doesn't work as long as DxWnd is intereferring. It would also work with Soulbringer if it wasn't for the proxy issue.
Reshack rar drivers#
If you go VMware route, it's also important to test with Windows XP, it seems drivers for it behave differently and won't block resolutions that exceed real screen size.īesides Drakan, I know it works with 3D Mark 99, 3D Mark 2000 and Project IGI. So if the user doesn't have bigger monitor or perhaps more than 1 monitor in surround/eyefinity mode, it's another option for testing.
Its virtual hardware exposes fixed larger resolution list. I came across the issue when testing Drakan in VMware virtual machine. Would be nice if someone confirmed its purpose. Proxy DLL isn't always picked up because in some cases, the full path is specified when LoadLibrary is called internally.Ībout the second occurence of the pattern, I'm aware of it, I just didn't touch it because we don't know with 100% certainity if it's related to resolution issue. So, I never bothered to expand it any further due to the fact that there is plenty of tools tackling legacy DirectDraw/Direct3D issues so it could be included with any of them. I see that my little project was noticed around here.
0 kommentar(er)
