Welcome, Guest.
Username: Password: Remember me

TOPIC: For which log errors to watch out?

For which log errors to watch out? 7 months 4 weeks ago #1

I don't remember which game was involved, but ReShade 4.2.1 logging of errors for that game was non-stop. The effects worked fine (or so it seemed), but can error logging itself or specific logged errors cause performance drops or some other issues? Are there some to watch out for?
The administrator has disabled public write access.

For which log errors to watch out? 7 months 4 weeks ago #2

Normally, the current (all) version is assume works well.
If you have any problems, need detail information and log.
We can not solve what you happened with no information.
Last Edit: 7 months 4 weeks ago by seri14.
The administrator has disabled public write access.

For which log errors to watch out? 7 months 4 weeks ago #3

The log has been cut down significantly in latest versions and there are no messages that can be logged each frame anymore, hence no possible performance penalties.
Cheers, crosire =)
The administrator has disabled public write access.

For which log errors to watch out? 7 months 3 weeks ago #4

What if the log throws error messages every 0.5s (see this thread)? Would be nice if this behavior could be fixed.

edit: btw, what is the size limit of the log in memory and on disk?
Last Edit: 7 months 3 weeks ago by brussell.
The administrator has disabled public write access.

For which log errors to watch out? 7 months 3 weeks ago #5

crosire wrote:
The log has been cut down significantly in latest versions and there are no messages that can be logged each frame anymore, hence no possible performance penalties.

The log size is whooping 240KB, the game is Batman - Arkham Origins and the error is:
[02576] | ERROR | Failed to create depth stencil replacement resource view! HRESULT is '0x80070057'

The log can be found here - drive.google.com/file/d/1VsKO10_ZrflWTMG...Bm8/view?usp=sharing
The administrator has disabled public write access.

For which log errors to watch out? 7 months 3 weeks ago #6

Yeah, there is some error with depth buffer detection. You can stop the error logging by choosing a non-problematic depth texture format in the dx10/dx11 tab until the issue is fixed.
Last Edit: 7 months 3 weeks ago by brussell.
The administrator has disabled public write access.

For which log errors to watch out? 7 months 3 weeks ago #7

brussell wrote:
Yeah, there is some error with depth buffer detection. You can stop the error logging by choosing a non-problematic depth texture format in the dx10/dx11 tab until the issue is fixed.
.

Where would I choose that? I did try changing DX11 tab options, but it had no effect on the error. Thing is, why is this error even happening when the preset seems to work just fine?
Last Edit: 7 months 3 weeks ago by MonarchX.
The administrator has disabled public write access.