Mercenaries 2 Pc Download Windows 10

[Gigí Ruais]

AtMicrosoft, we believe that digital technology has incredible potential to improve lives across the world, support democracy, and protect and promote human rights. That is why, at the second Summit for Democracy, we were proud to join the international coalition of over 150 companies that make up the Cybersecurity Tech Accord individually and collectively pushing back on the cyber mercenary market by committing to a set of industry principles.

Moreover, it is only a matter of time before the use of the tools and technologies they sell spread even further. This poses real risk to human rights online, but also to the security and stability of the broader online environment. The services they offer require cyber mercenaries to stockpile vulnerabilities and search for new ways to access networks without authorization. Their actions do not only impact the individual they target, but leave whole networks and products exposed and vulnerable to further attacks. We need to act against this threat before the situation escalates beyond what the technology industry can handle.

Hello, I'm trying to use DXWND to run MechWarrior 4: Mercenaries in windowed mode on Windows 10 with a GTX1080 all on the latest updates/drivers. DXWND appears to work right since it actually enables the game to run and perform fine, normally it just crashes on Windows 10, but it only starts in fullscreen regardless of my settings. I know it's also not borderless windowed because my monitor clearly changes modes. It does work windowed if I use ALT+Enter, I don't know if that's the game's own function or DXWND's, but I want the game to launch windowed, the changing of display modes is what I'm trying to avoid as games that run in lower resolution (and MechWarrior 4's menus or intros or startup or similar seem to only run in low resolution even though in the 3D in-game part it's fine in higher resolution) at times re-arrange my desktop windows to fit in the lower resolution and I don't want them to do that, I have OCD and want it neat and have to fix it! These are the settings I tried last but I've tried lots more variations of the relevant options.

Any help would be appreciated :)

The Alt+Enter sequence is not supported by DxWnd, so it must be a game own feature. Then, probably the game starts in fullscreen mode and can be switched to windowed: likely in some setup option there could be some setting to tell the game to start windowed. Right now, with no game and no logs I can't guess more than this, but I'm going to verify and tell you more as soon as possible.

Testbed is ready. Of course, since the game has a Win10 unsupported protection it was necessary to use also a No-CD crack.

The game is weird and I think it will be a good excercise for a while: with DxWnd default settings it crashed a few times and at dfferent stages before being stabilized and run a mission (without changing anything, just restarting the game! Probably it downgraded the "High performance" settings that I picked as first attempt). Then, when in mission it was a blaze of z-order and texture color problems.

I think I will need your logs.

I should say I'm using the game's MekTek edition that was distributed for free legally some decade ago and therefor it needs no nocd crack (or had it implemented). It was modified according to MekTek to offer higher resolution options and compatibility (at the time for XP/2k I guess, not newer OS) alongside content additions with new custom MekTek mechs. I doubt it changed the game behaviour all that much but just in case. I get none of the issues in your screenshots, it runs and performs fine, which is why I know DXWND works, since without it, it crashes. This is how it looks for me (my 1080p monitor died the other day so 1280x1024 for now):

I saw this version is offered on moddb actually, but I don't know how good a distribution that one is, hopefully it's a plain compressed folder rather than require special file readers like it originally did at the time, let me know if you want me to try and find it elsewhere.

-4-mercenaries/downloads/mw4-mercs-mektek

Also I saw that I didn't share the Hook tab before, it's set with Hook checked and Inject Suspended Process selected, maybe that will make it work for you too, if you hadn't done that already of course.

I didn't mess with other tabs. I've also confirmed the menus do switch back and forth a lower resolution, probably 800x600, since now that I set my GPU to not scale/stretch the image to fit, they're all with black borders all around, unlike the in-game parts (that first screenshot is just the mission intro trying to be cinematic with in game rendered borders). The game's screenshot key didn't work in menus to make sure. Where do I generate/get these logs to give you :)

The MekTek version doesn't behave too differently from base version, but requires "Hook / Hot patch" option to trigger the windowing. Doing that, you get the game in window, with sw emulation rendering (the game doesn't tell that, but you can clearly see it with your eyes) and the same texturing problems of MW4. There's plenty of things to fix.

However I turned on "DirectX(2)" tab option "No HAL device" and now the game starts in a window and in software rendering. However the software rendering does not seem to work very well.

Edit:

After removing the "No HAL device" flag now the game is running in a Window with Dxwnd and appears to be using D3D again (at least it looks much better). However the problem is that I have no idea how the game managed to fix itself to work with Dxwnd.

I think that the game must be changin some settings automatically. In the main game folder there is the file "options.ini" and another place is in the registry at:

[HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\MechWarrior Mercenaries]

When I enable the hot patch settings (while leaving everything else as I mentioned/showed in the images) the game won't launch at all for me. No crash report or anything, Windows just halts for a sec like it's trying to load something but nothing comes up.

I couldn't reproduce the No Hal device thing on my version, it did have a pop up from the game saying my hardware is incompatible but it didn't run windowed and I'm pretty sure it was still using 3D acceleration. Maybe the game's originally just too hacked together for you to fix it :(

First big problem: despite the hot patch flag, some functionalities of the renderer seem unreached: though the window and the menus are properly scaled, for some reason the gameplay is not. You can enjoy a correct scene only when the window size corresponds to the resolution (800x600 in my screenshot below), otherwise the scene is cut.

It is a situation similar in games that use OpenGL that is not properly hooked, but here I wonder if it's the same reason.

@Riitaoja: can you confirm that in your testbed the game is scaled properly when run in a window bigger or smaller that the selected game resolution (game video option screen or something alike...) ?

If this is not done the game will run in some weird mode that looks like software rendering with graphical bugs like shown in your previous screenshots and in that case the dxwnd window does not scale.

And this is a screenshot showing how the game looks when configured to run at 800x600 resolution in a 1024x768 dxwnd window. You can also see how the rendering should look like when it works properly. (compare this to your "train1.png" screenshot)

@Riitaoja: I'm puzzled. You're right, going through the "autoconfig_MERCS.exe" fixes the scaling problem (and perhaps makes the game much slower and laggy), but looking at the previous logs the game unconfigured wasn't making any illegal operation: it selected a SYSTEMMEMORY 3D surface as big as the supposed screen resolution, handed it to D3D CreateDevice and started the rendering loop, an operation that works perfectly on fullscreen mode (without DxWnd running) and then should work also with DxWnd.

The curious thing is that this rendering surface is used but never moved to screen (at least, according to DxWnd logs) so I don't see an event where to place the scaling hack. Maybe I'm missing some unhooked D3D7 method? Or (scary idea) does D3D brings this surface to screen without offering a possible hook?

The way I understand it is that when the graphics card and resolution is not properly detected or manually configured by the user with "autoconfig_MERCS.exe" the renderer reverts to some crappy emulation mode that sucks. So I doubt it would be much joy to try and fix the dxwnd window scaling in that fail safe mode. You can view the file "VideoCard.txt" in the game directory that has some lines about the various graphics modes that the game uses to configure itself in case of certain graphics cards are detected.

As for the game running slower for you after using "autoconfig_MERCS.exe" did you try changing the Direct3D tab "Force Vertex Processing" to "hardware" or "mixed"? That seems to be a common cause of slowdowns with old D3D games on Win10 as it reverts to software by default.

MekTek edition doesn't have .ICD files as it came without CDs as free download so I don't have it set up like you say, I only have the exe in the path. Enabling Hot Patch option the game doesn't launch at all. Removing it, it launches as in my first post.

I noticed something else. I think the game might be running in some kind of borderless fullscreen mode, yet it still changes my monitor's resolution/mode and alternates between low and high res modes for menus/in game like normal fullscreen. The reason I think it might be borderless is that when I press my media volume keys, the Windows 10 little sound volume gauge shows up on top of the game. I haven't seen that happen in fullscreen apps outside borderless fullscreen. Just a thought, still no clue what's happening. Ignore this if that's standard with DXWND.

3a8082e126