Pavel Kovalenko

BugTrap pdb may be required to debug BugTrap code, but why would you need that?

I've created a new branch [`no_dxsdk`](https://github.com/OpenXRay/xray-16/tree/no_dxsdk) with some fixes for xrCore (dxerr) and xrRender (FVF utilities).

@fedan проблемы с dxerr нет с тех пор, как соответствующий API был [реализован в xrCore](https://github.com/OpenXRay/xray-16/blob/dev/src/xrCore/Debug/dxerr.h).

@Postal86 xrCore does implement [DxErr](https://github.com/OpenXRay/xray-16/blob/dev/src/xrCore/Debug/dxerr.h).

Moving to 64-bit - almost no serious problems. As for multithreading - I have no idea for now. First priority is to fix bugs (lots of them), move original libraries...

@fagoatse Don't think, profile it. As for 'very active Russian project', here are two public SoC repos: 1] https://xp-dev.com/sc/204486/HEAD 2] https://bitbucket.org/stalker/x-ray I nave no plans to mess with old SoC...

- Rendering is always bottleneck in all games I've ever seen. You'r wrong. Stalker has pretty complicated AI but pretty simple r1 renderer that runs so fast that GSC released...

- 4. Renderer is not simple, as it is highly customizable. 'Simple' means 'simple for hardware', that's it.

- At this point cleaning up and organizing things is more important than worrying about threading and such. Exactly. Complicated and long-term modifications will be easier once we have organized...

Also, for profiling: you can use Visual Studio profiler.