Horde3D

Good day, getting this error appear at the start of the engine log:



Any suggestions?

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.

If I remember correctly I had the same warning when I tried the demos on my AMD 780g onboard graphics card. But it was no error that would prevent me from using the engine

Right, this is just a warning and can be ignored. Usually you get it on some low-end ATI cards that do not support 24 bit framebuffer depth attachments. The only issue is that there may be more shadow artifacts since the shadow maps are stored with lower precision.

Thanks for replies - regards to low end, running an ATI HD 4890.

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.

Make sure you have the latest (stable) drivers installed.

_________________
Tristam MacDonald - [swiftcoding]

I have the same problem, but also colored noise all over the screen in Knight sample (using HDR pipeline, with forward pipeline everything is fine). Any ideas how to fix that?

WinXP SP3, ATI Radeon X1950GT, 9.11 drivers.

Bumping for skinning problems, too. I am using ATI X1300 on WinXP Sp3 as well. Although I installed the latest catalyst drivers I got the same warning and errornous triangles when rendering textures. Anyways here are my gfx card stats from the catalyst info program. BTW: ATI has put my gfx card to the discontinued page So there is no later driver version than these.

_________________
philipppixel
8=:(=)D { Save the Giraffes )

ATI still makes drivers for legacy, as they call them, video cards. They are downloaded separately from main drivers. The latest drivers for outdated cards like ours are 10.2, as are the main drivers. Here is the link:

http://support.amd.com/us/gpudownload/w ... ng=English

Sorry for offtop.

Why offtop, I guess any help is appreciated.

Do the problems still exist with the 10.2 drivers and the svn trunk version of Horde?

The 16 bit precision warning should not be related to the problems, however, we recently fixed the depth buffer precision for ATI cards, so this warning will only appear on very old cards now.

No warnings here on 4890 + 10.2 drivers

Thanks Irdis for pointing to the new driver which I installed in new york minute.

I wished it would work like a charm, but actually there is no change in the textured graphics (see phony image where the water tower should look like a big wood tank) nor in the EngineLog, where my warning-of-the-day waited for me


Nevermind thanks for trying

edit:
As a side effect of this driver installation my whole system has acquired some lag. I take this is the part where Microsoft would tell me on the phone: "Didn't windows issued a warning for drivers that didn't accomplish the Microsoft test?" - "yes it did... twice". Now I have to uninstall the new driver again

_________________
philipppixel
8=:(=)D { Save the Giraffes )

Sorry for "upping" the thread, and it may not be the correct thread for this, but the problem I described earlier in this topic still exists. I (finally) updated my ATI x1950 Pro (512mb) to 10.2 drivers (latest drivers for legacy cards), and the problem of the colorized noise all over the screen is still there in knights sample, if you use the HDR pipeline (everything is fine with deferred and forward pipelines). It looks like it is a problem of a shader, because overlays (logo and fps) are displayed and updated correctly above the noise. No errors or warnings in the log, using engine from latest svn (454)...

Here is a snapshot:


P.S This noise usually looks the same, even if you shut down the sample and load it again. It will look different if you switch to fullscreen mode or execute another 3d app and then load knight's sample again...

Any ideas?

Hmm, this can only be some driver issue with the floating point buffers. I have an ATI HD5000 series card at home and no problems.

You could try out GPU PerfStudio. It is quite easy to use, maybe it gives a hint where the corruption is happening. Make sure that "Application Supports Self-Pause" is selected in the PerfStudio settings and pause the knight sample by pressing space two times so that the view does not change any more. In the frame Debugger, you can use the slider to inspect the drawcalls.

I have quickly put together a small "Getting Started" tutorial for GPU PerfStudio. You can find it in the wiki.