Recent Posts

@M123 said:

@ZemoBladeWalker said:

Just followed your steps. The game boots up but now it crashes at loading screen with memory access error.

Hmm... so far I've found 3 possible causes for memory access errors on loading screens:

  • less than 32MB of VRAM allocated under the DirectX tab in dgVoodooSetup.exe (dgVoodoo 2.53) / dgVoodooCpl.exe (dgVoodoo 2.54) - I suggest setting this to at least 64MB (higher values may be useful if running at a very high resolution or if someone makes a high-resolution texture pack)

  • Videocard set to "dgVoodoo Virtual SVGA Card" under the DirectX tab in dgVoodooSetup.exe (dgVoodoo 2.53) / dgVoodooCpl.exe (dgVoodoo 2.54) - set it to "dgVoodoo Virtual 3D Accelerated Card".

  • texture(s) in unsupported formats in the models folder (seems unlikely in this case)

I'll keep trying different things.

Were you able to get in-game before you installed dgVoodoo 2?
What graphics card and operating system are you using?

I am on Windows 10 64bit and using Nvidia Geforce GTX 750 Ti. I gave 521 VRAM and I use dgVoodoo Virtual 3D Accelerated Card. Still crashes with exact same error. I wasn't ever able to get to loading screen before using dfVoodoo 2. Also I'm not using any texture packs or any modifications (expect from windows XP patch)

posted in Support read more

@M123 said:

Tried Machines on a PC running Windows 10 (haven't updated mine from 7 yet), and wow, that is bad - messed up menu and textures, and very poor performance even on an i5 4690k and GTX970 (running at 640x480 D: ).

Tried a few different things... and found something that seems to work - dgVoodoo 2.

EDIT: Note - dgVoodoo 2 requires DirectX 11 and a GPU supporting at least DirectX feature level 10.1:

• Nvidia GeForce 400-series and newer (some GeForce 200-series might work - G210, GT220, GT240)
• ATi (AMD) Radeon HD 3000-series (except Radeon HD 3410) and newer
• Intel HD Graphics 2000 and newer

Here's what I did:

  1. Download dgVoodoo 2.53 from here.

  2. Extract it somewhere (e.g. C:\Games\dgVoodoo\).

  3. Copy the "D3DImm.dll" and "DDraw.dll" located in the "MS" folder under the folder you extracted the dgVoodoo 2 archive to (e.g. C:\Games\dgVoodoo\MS\).

  4. Paste the two .dll files in your Machines install directory - must be the same folder as "machines.exe" (e.g. C:\Games\Machines\).

  5. Run Machines.

  6. (a). If the image is too bright, washed out, etc. or you want to try forcing some extra graphical settings (e.g. MSAA, Vsync), run "dgVoodooSetup.exe" located in the folder you extracted the dgVoodoo 2 archive to (eg. C:\Games\dgVoodoo\) and try out the various settings.

    (b). If Machines crashes or runs even worse than before, delete the "D3DImm.dll" and "DDraw.dll" files from your Machines install directory to restore it to the original state.

With dgVoodoo 2 installed I could run Machines fairly smoothly (some rough patches, but I get those on Windows 7 as well) at 1920x1080 without graphical issues (at least none I noticed in the time I could test it). :-)

Seemed to work fine without Windows 95 / 98 / XP compatibility mode.
The game crashes on exit on that PC (with or without dgVoodoo 2).

EDIT: some things to try if Machines doesn't run properly with dgVoodoo 2 installed:

  • Install the DirectX End-User Runtimes (June 2010)
  • Make sure Machines is installed in a folder other than "C:\Program Files" or "C:\Program Files (x86)".
  • Run Machines as administrator
  • Run without any compatibility modes applied (aside from run as administrator)
  • If you use MSAA through dgVoodooSetup.exe and get weird graphical issues ('smearing", blurring, flickering), make sure you don't have any transparency multi-/super-sampling forced on Machines through your graphics drivers

Just followed your steps. The game boots up but now it crashes at loading screen with memory access error.

posted in Support read more

Good to hear this project is not completly cancelled. But if you want somebody's support (not only the financial one) you need to start working on it again. No one supports halted projects.

posted in Machines read more

I guess it's pretty common for old games (pre-2005) to have hidden and not-fully implemented stuff.

posted in Blogs read more

I tried three times and I cant access it. Are you sure it's online?

posted in Machines read more

@StonerHate said:

@ren9999 Hey dude! What's up? Awesome!

I've read the post about Machines (possibly) getting put on Steam sometime in the future. Let's hope all the best for that, right? ;)

Also, welcome back. Think I remember you from the previous incarnation of WFW.

Machines on Steam? Never heard about that. Well while I wish it was true it might be another hoax. We gotta be realist.

posted in General Discussion read more

Well thats odd. I checked this website before and I got an error saying this project was blocked or something.

posted in Blogs read more

Thats weird. I got 0x2e4 error code when trying to run Machines Loader.

posted in Machines read more

The SourceForge site for this project is offline so I doubt if the project is still alive.

posted in Blogs read more

Hello. I'm glad I found this forum. I wish I could find this place before it was removed.
I have a question. Do anyone have a link or a working copy of Machines Loader?

posted in Machines read more