It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Incoming + Incoming Forcescreate surface for z-buffer failed action not supported(12 posts)(12 posts)
(12 posts)
Pages:
1
This is my favourite topic
Posted February 17, 2014
as title says soon as i launch i get this
currently on win7 64bit
amd radeon 6700
4gb ram
intel quad core
Posted February 18, 2014
avatar
Jamski: as title says soon as i launch i get this
currently on win7 64bit
amd radeon 6700
4gb ram
intel quad core
The solution is to use Catalsyt drivers 13.2 b7 or older. Unfortunately - can't check it, as I have R9 card.
I'm trying dxwnd currently, but with poor results.
Posted February 19, 2014
no worrys thank you anway i removed that driver and put a older 1 on, works perfectly, all other games run fine and still got both monitors running :)
Posted February 19, 2014
avatar
Jamski: no worrys thank you anway i removed that driver and put a older 1 on, works perfectly, all other games run fine and still got both monitors running :)
Glad to hear it. I, with R9, am not so lucky :(
Post edited February 19, 2014 by marek1712
Posted April 27, 2014
The latest 14.4 drivers unfortunately do not solve the problem.

However, I have tried this solution my HD 7870 and it works fine.
Post edited April 27, 2014 by jamyskis
Posted September 20, 2014
i have this problem, too.

But "Incoming Forces" running wonderful, without Problems

Dennis

Edit:
the "atikmdag.dll" to download was a troubleshoot that bring it run's

Hmm... i think it's an good old 3Dfx/Glide Game, NGlide ? :-)
Post edited September 21, 2014 by Dennis50300
Posted December 02, 2014
I got that error in Windows 8.1 and unpacked "atikmdag.dll" as instructed, but now, I get the erro message"Unable to find suitable device" immediatly upon booting up. Anyone else encountered this?
Posted May 22, 2016
OK, so, I just buyed Incoming in the actual promo, downloaded it and have got this error under Widnows 8.1 with an ATI Radeon R7 250 graphic card (look atscreenshot 1).

But I've managed, to run the game with help of DgVoodoo 2.51.

The problem is, the resolution is set to 640x480 px.
Is there any way, to set it to bigger? I tryed to force resolution with dgVoodoo control panel, but no luck so far. Where is the resolution option inside Incoming?
Attachments:
screenshot1.jpg (11 Kb)
Post edited May 22, 2016 by radigram
Posted November 01, 2016
avatar
radigram: OK, so, I just buyed Incoming in the actual promo, downloaded it and have got this error under Widnows 8.1 with an ATI Radeon R7 250 graphic card (look atscreenshot 1).

But I've managed, to run the game with help of DgVoodoo 2.51.

The problem is, the resolution is set to 640x480 px.
Is there any way, to set it to bigger? I tryed to force resolution with dgVoodoo control panel, but no luck so far. Where is the resolution option inside Incoming?
Ok, I can't start the game (newer versions of DXWND has some changes and old way does not work anymore). So any instructions how to use DgVoodoo to launch it?

EDIT: ok, managed to do it myself. I get an error at the start, but game is working
Post edited November 01, 2016 by Bambusek
Posted September 11, 2017
You can Find a possible solution on youtube try searching "Fix CreateSurface for Z-buffer failed for INCOMING on AMD" works on apu AMD A8 6410.
Posted August 30, 2020
Hi. Had Z-buffer problem with Incoming. Now, solution is easy:

dgVoodoo.

This fixed the whole problem.
Posted January 08, 2025
avatar
ajpiiron: Hi. Had Z-buffer problem with Incoming. Now, solution is easy:

dgVoodoo.

This fixed the whole problem.
In case anyone else runs into this issue, I had to use dgVoodoo (DirectX 32bit) AND turn off Windows ME compatibility from the launcher. I'm running Windows 11 on a Radeon 7900 XT and a Ryzen 7 7800X3D, so your mileage may vary...
Pages:
1
This is my favourite topic
Community
Incoming + Incoming Forcescreate surface for z-buffer failed action not supported(12 posts)(12 posts)
(12 posts)