Sound created by DirectX SDK.

A place for Ogre users to discuss non-Ogre subjects with friends from the community.
User avatar
insider
Orc
Posts: 462
Joined: Thu Sep 15, 2011 12:50 pm
x 31

Sound created by DirectX SDK.

Post by insider »

No I am not talking about DirectSound :lol:

My Graphics card makes a hiss every time I program using the DirectX SDK, It makes a hiss when I draw a mere triangle or when I do shader programming as well.
What is the reason, I am sure it is not the card I have had a 9600GT in the past and my present card is a GTX560Ti but the hiss is persistent.

What does it indicate, is it harmful to the card or am I doing something wrong, what could possibly go wrong in drawing a triangle on the screen :shock:
User avatar
Kojack
OGRE Moderator
OGRE Moderator
Posts: 7157
Joined: Sun Jan 25, 2004 7:35 am
Location: Brisbane, Australia
x 535

Re: Sound created by DirectX SDK.

Post by Kojack »

It's capacitor whine or coil whine.
A lot of gfx cards get it. Usually it happens more at high framerate, so drawing a triangle will probably do it because you've got massive framerate. You will probably hear it whenever a game is rendering a simple screen (like menus) without vsync on.
User avatar
insider
Orc
Posts: 462
Joined: Thu Sep 15, 2011 12:50 pm
x 31

Re: Sound created by DirectX SDK.

Post by insider »

Kojack wrote:It's capacitor whine or coil whine.
A lot of gfx cards get it. Usually it happens more at high framerate, so drawing a triangle will probably do it because you've got massive framerate. You will probably hear it whenever a game is rendering a simple screen (like menus) without vsync on.
Well that explains it, thanks Kojack :D
User avatar
insider
Orc
Posts: 462
Joined: Thu Sep 15, 2011 12:50 pm
x 31

Re: Sound created by DirectX SDK.

Post by insider »

insider wrote:
Kojack wrote:It's capacitor whine or coil whine.
A lot of gfx cards get it. Usually it happens more at high framerate, so drawing a triangle will probably do it because you've got massive framerate. You will probably hear it whenever a game is rendering a simple screen (like menus) without vsync on.
Well that explains it, thanks Kojack :D
I found that we have to use D3DPRESENT_INTERVAL_ONE instead of D3DPRESENT_INTERVAL_IMMEDIATE in the d3dpp.PresentationInterval while filling the D3DPRESENT_PARAMETERS d3dpp to turn Vsync ON.
Is this correct, My GPU usage with INTERVAL_IMMEDIATE is 40% and with INTERVAL_ONE is 18%, so I am assuming it should be correct.

Any input would be great.