• Advertisement
Sign in to follow this  

OpenGL Graphics code causing electrical noise

This topic is 3516 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi all, I'm having a pretty strange issue here, hopefully somebody could please give me some insight to possible sources of the problem. It's also a hardware glitch (possibly), so I wasn't too sure where to put this. OpenGL made the most sense as that is the graphics API I am using. I have some code that uses OpenGL to render height-fields/terrains. I recently attempted to improve upon it by adding geo-mipmapping. The addition was a success and notable performance increases were achieved. However, I noticed that my video-card was making electrical noise while I was running my demo. For those unfamiliar with this event, the circuitry of the card makes very high pitched squealing noises. Usually electrical noise is indicative of a hardware problem (I have this card under an extended warranty thank goodness!), but this case was a bit different. Allow me to explain. When I am rendering the terrain at maximum quality, either the noise is not present or it is too high-pitched for me to hear. When I lower the overall quality of the terrain, I begin to hear the sound. Strangely enough, it becomes easier to make out with every consecutive shrink in the number of triangles being rendered. Less stress = more noise? This didn't make sense to me. I tested out the card with various DirectX and OpenGL titles including Crysis, Battlefield 2 and QW - Enemy Territory. Nothing. Zip. Nada. All quiet. It seems that it's only my code that causes this. This worries me. In short, what I am asking is, has anybody else had or heard of this issue? What could it be indicative of? I have only one hypothesis to date. I am rendering the terrain with VBOs and the indice sets are stored in one large buffer. As I decrease quality, the indices are pulled from memory higher and higher up from the start of the buffer. This could mean I'm moving from one memory chip to another (couldn't it?), which might mean one of the chips is the little whiner. But why do other games operate fine then? Any help/ideas/insight would be greatly appreciated, I can paste code as necessary. (There's really nothing out of the ordinary about it though...) If it's not likely to be my code or a software issue then I'll just get the card replaced and try again. Many thanks! :) By the way, the card is an 8800GT (512mb) operating with the latest drivers (updated them yesterday, although the problem existed before the update.) EDIT: It occurred to me to test the code on another card (8600 GTS). Silly of me not to think of this sooner. In any case, it doesn't do it on that card. This reduces the odds that it's a software issue, I suppose.

Share this post


Link to post
Share on other sites
Advertisement
I've had the same thing occur, goes away when I v-sync (that or actually fire enough work at my GPU so it isn't going at 1500fps+).

Regards,
ViLiO

Share this post


Link to post
Share on other sites
also stick a pause in your main loop eg 5 msec's so the CPU is not working overtime for nothing

about the problem, it could be the fan (thats one of the first things to go), easily tested by when the machines going + making the noise, stick your finger in lightly apply presure to the top of the fan.

, in past days u could just tighten the screws aka fix it yourself, but nowadays manufacturers are not to happy about this, (due to you less likely to buy a new part if u fix the broken one) thus have made hardware thats more difficult/impossible to repair

Share this post


Link to post
Share on other sites
Quote:
Original post by GarethC
Usually electrical noise is indicative of a hardware problem (I have this card under an extended warranty thank goodness!), but this case was a bit different. Allow me to explain. When I am rendering the terrain at maximum quality, either the noise is not present or it is too high-pitched for me to hear. When I lower the overall quality of the terrain, I begin to hear the sound. Strangely enough, it becomes easier to make out with every consecutive shrink in the number of triangles being rendered. Less stress = more noise? This didn't make sense to me.

Let me begin by saying I experience the exact same symptomps as you with my GeForce 8800GTX 768MB.

I think it's very likely you're seeing the same thing as I am. But it seems like you're misunderstanding the source of the problem. It's not the workload that causes the high-pitched noise, but rather 'high FPS'.

It seems like this card emits that noise whenever it's allowed to render at extremely high rates (1000 fps or higher). I've noticed this happen with my own OpenGL applications, and with many other old games I've tried.

The only solution, it seems, is to limit the frame-rate by using V-Sync. Don't let it run at 1000+ Fps. I'm not sure if it's a big problem, i.e. if it damages the card or not, but I prefer not to try it just in case.

If I had to guess, it's probably some sort of a common nVidia problem affecting some 8xxx series cards and maybe others. I've never gotten this before with my past ATI vide cards - but then again, I've never gotten 1000+ fps with them either. [smile]

Share this post


Link to post
Share on other sites
Probably the power regulator circuits. The high power consumption of GPUs usually require swithing power regulators, that operate at a high oscillation frequency. Under certain varying loads, interferences can occur, and you can hear these through vibrations of the capacitors and/or coils.

If its not so loud to be annoying, this is not really a problem.

Share this post


Link to post
Share on other sites
Oh wow, this explains quite a bit. While at the highest LOD the card manages 500 FPS (without extra scene details), but when I turn the LOD down it does to 1500 then as high as 5000. I had V-sync turned off to test the performance gains (otherwise it clamps out at 60fps).

I'll half to try fixing my draw/update timers so this doesn't happen again.

Geeze, I was about to go out and replace it just this moment. Good thing I checked here first. Thanks for all your help guys/gals, it's much appreciated!

:)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement