For which log errors to watch out?

More
1 year 8 months ago #1 by MonarchX
For which log errors to watch out? was created by MonarchX
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?

Please Log in or Create an account to join the conversation.

More
1 year 8 months ago - 1 year 8 months ago #2 by seri14
Replied by seri14 on topic For which log errors to watch out?
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: 1 year 8 months ago by seri14.

Please Log in or Create an account to join the conversation.

More
1 year 8 months ago #3 by crosire
Replied by crosire on topic For which log errors to watch out?
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.

Please Log in or Create an account to join the conversation.

More
1 year 8 months ago - 1 year 8 months ago #4 by brussell
Replied by brussell on topic For which log errors to watch out?
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: 1 year 8 months ago by brussell.

Please Log in or Create an account to join the conversation.

More
1 year 8 months ago #5 by MonarchX
Replied by MonarchX on topic For which log errors to watch out?

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

Please Log in or Create an account to join the conversation.

More
1 year 8 months ago - 1 year 8 months ago #6 by brussell
Replied by brussell on topic For which log errors to watch out?
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: 1 year 8 months ago by brussell.

Please Log in or Create an account to join the conversation.

More
1 year 8 months ago - 1 year 8 months ago #7 by MonarchX
Replied by MonarchX on topic For which log errors to watch out?

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: 1 year 8 months ago by MonarchX.

Please Log in or Create an account to join the conversation.