_control87 ( _PC_64, _MCW_PC );
The question is: can I do this only after Direct3D/device creation?
Direct3D vs. doubles
Is it true that Direct3D disables doubles?
I mean I'm almost sure it is so, but it is a problem to me: I'm creating a graphing tool with high precision (its input are latitude/longitude of a point in degrees).
I found that setting precision back to 64 deals with the problem:
You might want to specify D3DCREATE_FPU_PRESERVE when you create your device. This tells D3D to save and restore the FPU state before and after each call into the API.
xyzzy
xyzzy
Check out D3DCREATE_FPU_PRESERVE, a flag used in the CreateDevice() call. Using this is probably a better method than manually changing it back yourself, or so I merely guess.
.NET performance docs say that double is the fastest floating-point type because apparantly processors' FPUs have been 64-bit for a while. Is that true?
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement