Skip to content

Reference: Subtle DirectX API call stream differences

Echelon9 edited this page Jul 14, 2014 · 2 revisions

One of the fundamental tasks of Cxbx is to convert a Xbox-targeted DirectX API call stream into a valid Windows-based DirectX API call stream.

As part of the process of debugging individual calls, it is work documenting as reference material the subtle differences in the behaviour of that Windows-based call stream. Particularly, settings which can be tweaked by the developer or end user.

  • Debug vs. Release version of Cxbx (some slight differences in call stream, and memory setup)
  • Hardware accelerated D3D Device or Software Reference D3D Device (via the Cxbx "Settings -> Config Video ..." preferences)
  • DirectX 8 vs. DirectX 9
  • Debug Runtime or Retail Version of DirectX (via the DirectX Control Panel, enabling extra validation)
  • NVIDIA vs. AMD Ati vs. VMware vs. [ ... ] hardware / driver package if hardware accelerated

Order is broadly in the order of those changes most easily set by an end user, through to those which require a development environment.

It is worth keeping in mind that each of these settings can be tweaked independently of others, creating a significant number of combinations. When reporting bugs or issues, please specific which combination of these settings applies at the time of the report.

Clone this wiki locally