Comments - hav00k

FATAL ERROR

[error]Expression : The application has made an erroneous API call...
[error]Function : CHW::UpdateViews
[error]File : ..\xrRenderDX10\dx10HW.cpp
[error]Line : 629
[error]Description : R

This error has been plaguing me for days. After finding a spot on the map that reliably reproduces the above crash (looking at a certain wall in Cordon), I used a method of deduction to narrow it down to the "Steep Parallax" setting.

Try turning off the "Steep parallax" option in the Video/Advanced menu, or run the following command in the console (game restart required):

r2_steep_parallax off

I have no idea why this happens. Maybe it's the steep parallax mapping broken, or maybe it needs some tweaking (I have not tested different values for the r2_steep_parallax_* settings).
Note: I am using an AMD card, whether this is relevant or not.

If you have an AMD GPU, try revert back to Radeon 17.2.1, see my post below.

Try revert back to Radeon 17.2.1, see my post below.

Expression : The application has made an erroneous API call that it had enough information to avoid. This error is intended to denote that the application should be altered to avoid the error. Use of the debug version of the DXGI.DLL will provide run-time debug output with further information.
Function : CHW::UpdateViews
File : ..\xrRenderDX10\dx10HW.cpp
Line : 614

To those having this problem on AMD graphics cards: Revert back to Driver Version 17.2.1. I'm not really sure what's the problem with the newer drivers (including the latest 17.5.2 as of now) but my game was crashing terribly with the above exception until I reverted back.

To Dez0wave: I was standing in the middle of the stalker camp in Cordon, and game crashes as soon as it starts to "Synchronizing game data...". I played around with the rs_vis_distance option and managed to make it work by lowering it to a value of 0.8. But as soon as I start moving out of the camp in the direction of the well there, game crashes again. So I figured it's something that crashes the game when it reaches the rendering horizon. Again, it could be a driver issue, or could be something else...

AMD HD7870, renderer_r4
PS: renderer_r2 works fine.

Hi Tartos. If I am correct, this is due to the "Particles Distance" option. Try increasing it a bit.
I used to have the same problem - imagine my amusement when i ran into "invisible" poltergeists :)

PS: If this doesn't help, enter this into the console:
r2_particle_distance 500