Don't open! )Some people might get upset of what this spoiler contains :mad:Don't tell me that I didn't warn you!Ok, here it isit's Project X (). If you are an experienced user, you can also experiment with the settings in ini file, but only if you're sure what you're doing!įor the best effect i recommend to combine this with Renderer #2. The frontend will be fixed, and in-game there should be no lags (depending on the system see #2 if having issues). Install it as a wormkit module (put the three files into your folder). Kawoosh has also fixed the white fields of frontend overlaying as Windows Controls. This is the best emplementation of a windowed mode I've ever seen. The windowed mode () library by VEG, a modified menopem's d3dhook with customizable settings. Question: What are the renderers and where can I get them?Īnswer: I am aware of two renderers compatible with WA. Question: How are we supposed to prevent these lags manually?Īnswer: We need a custom renderer for Worms Armageddon. Disabling LandInVRAM inproves this to 7 FPS, but still hard to play. Once you start a match, the in-game process will run at 2 FPS, pausing through every second. Also, a slow frontend issue persists here (the built-in fix won't help). The problem here is that the "real" window is in the front of the graphical one, making the frontend messy. The problem is that WA's frontend (menu system) is coded in a specific way that it consists of two windows: the graphical one (that you see and work with), and the "real" one (aka Windows 'Controls'), which listens to mouse and its position, and which is made of these white gaps like you said. Hi! I've ran Windows 8 Release Preview on two real machines, and got the same issues you mentioned ().įirst, the Windows 8 RP and RTM run all old games in a 32-bit virtual window (no palette distortion anymore, and delete wkColorFix.).
0 Comments
Leave a Reply. |