The fix for that is to get the latest version of the xlive.dll file, which I've also done and at that point I can get to the stage where there are no errors - I try to launch the game via the dirt2.exe file which apparently is a SecuROM launcher, but that doesn't work either.
I've had easy success running the installer, launcher, and game with proton. No effort required at all, in this case. Just make sure you install proton from steam. I wrote a quick and dirty script to invoke the latest installed version of proton to run whatever I want. Be sure to change STEAM_COMPAT_DATA_PATH to wherever you'd like to store your pfx data.
File corruption, missing, or deleted dirt3.exe files can result in EXE executable errors, most commonly seen during the startup phase of DSS Launcher. The primary way to resolve these problems manually is to replace the EXE file with a fresh copy. Furthermore, keeping your registry clean and optimized can prevent invalid file path (like dirt3.exe) and file extension references, so we recommend running a registry scan cleanup regularly.
Most of your dirt3.exe problems should be resolved if the file is placed in the correct file path directory, but it's a good idea to verify it is fixed. Test the outcome of the file replacement by loading DSS Launcher to see if the error still appears as it did before.
These EXE error messages can appear during program installation, while a dirt3.exe-related software program (eg. DSS Launcher) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your dirt3.exe error occurs is a critical piece of information in troubleshooting the problem.
Q: Why did you re-add sponges?
A: Sponges are cool. Really cool. In classic, they were pretty much the only block beside water and lava with any form of functionality, and that functionality, we felt, was still right at home in Alpha 1.1.2_01. Anyone who has tried draining any body of water knows exactly how irritating it is to fill a basic with sand or gravel or dirt and then tediously dig it back out. Sponges make draining water, as well as constructing cool underwater bases, much easier.
With the manifest file completed, you can now start adding custom content to Minecraft. Let's get started by applying a new texture to the Vanilla dirt block. The first part of the process involves creating a folder structure to hold the custom texture.
Pack Stacking is how content is loaded on top of Vanilla content, causing each object that has the same name in both packs to be overwritten by the latest applied pack. In our example, the original dirt texture is overwritten by the custom texture.
**Derail I do not. Well.... maybe just a tad... Advice: Make Recovery Station on USB by windows function (It's some sort of PE windows with rollback options). I think you need a 16Gb stick minimum. These are dirt-cheap.
This program will quickly test for user input, then deal with the hardware. Then it'll sleep for 100ms, while your gui is non-responsive, then it'll check in with your GUI again. I fully realize this is a crude way of doing things. We're talking dirt simple stuff without trying to use threads, etc to 'get it right'. It's for demonstration purposes.
e2b47a7662