Jump to content

Max Game

Member
  • Posts

    17
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About Max Game

  • Birthday Jan 15, 1997

Contact Methods

  • Steam
    http://steamcommunity.com/profiles/76561198039499788/

Profile Information

  • Gender
    Male
  • Location
    Sweden
  • Interests
    Gaming, video editing, animation.
  • Occupation
    Studying.

System

  • CPU
    Intel Core i7 4770K
  • Motherboard
    Gigabyte GA-Z87X-D3H
  • RAM
    Corsair Vengeance Pro DDR3 1600MHz 8GB
  • GPU
    EVGA GeForce GTX 780 3GB Classified
  • Case
    Cooler Master CM 690 III
  • Storage
    WD Desktop Black 1TB
  • PSU
    Cooler Master V850
  1. I was away for a while but now I've gotten around to doing something. I took out the GPU and the problem doesn't seem to be there anymore. Thoughs? EDIT: Apparently what was causing this issue was EVGA Percision X. When it was off, I stopped getting the glitchy GUI at times. I ran an update on it (Percision X) and now it seems that the problem is fixed.
  2. Yes, I did a completely clean installation of the GPU drivers. I'll take it out and see what happens, then.
  3. It didn't find anything, the problem is still there.
  4. I never physically took out the GPU. I only inactivated the driver and checked again. Should I take it out completely? Running the scan now. EDIT: Scan came up with nothing.
  5. I tried turning off aero before, it didn't help. And yes, the problem has just recently appeared. EDIT: Using integrated graphics doesn't help.
  6. System specs: CPU: Intel Core i7 4770K @ 4GHz RAM: 8GB 1600MHz DDR3 GPU: EVGA GeForce GTX 780 3GB Classified Hello, I have a problem with the GUI in some applications. I'm currently experiencing it in: Microsoft Visual C++ 2010 Express (Almost everywhere) Sony Vegas Pro 12 (Render As - menu) I've just recently noticed this problem, I've run a system restore and I've reinstalled my Graphics Card drivers. The GUI still works, but it is really hard to use it normally. The problem does not show at first, but when attempting to interact with the objects that are affected, it starts showing. I don't know what I can do to fix it so, any help will be much appriciated! Screencaps of the problem in Sony Vegas: Thanks in advance! //Max Game
  7. Can't say these are my favourites, because the content given is all great. But I found these videos especially helpful for me.
  8. Beautiful, makes me want to sleeve my own cables. Keep up the great work.
  9. That's not the point of the video but I can explain it a little myself. Imagine a box which's sides are all 60 pixels long on the left side of your screen, this box's is moving to the right side of the screen at a rate of 60 pixels per second. And since the monitor in this example is a 60Hz monitor running at 60 FPS, the box is moving one pixel each frame. Scaling this down to 30 FPS makes the box move at 2 pixels per second and at 15 FPS it will be moving at 4 pixels per second. (This obviously scales linearly in any direction) Now let's ramp this up using a HUGE monitor with the same pixel ratio (Pixels per cm/inch) disregarding the limits of the hardware. If the box is moving at 3600 pixels per second and the monitor is still at 60 FPS, the box will be moving at 60 pixels per frame. If we double this (7200 pixels per second) it will be moving at 120 pixels per frame. Now we really see when a high framerate makes a difference, when it is moving this fast, there is a clear space between the box's original position and it's new one (60 pixels wide to be exact) This is noticable! This point is very important when explaining this, since it is fluidity that we want in our games. At higher framerates this issue becomes smaller: At 120FPS, there is no longer a space between these two positions, the box moves its own length per frame (60 pixels per frame). And at 7200 fps, the box moves as smooth as possible relative to the monitors's framerate, that being 1 pixel per frame. ATTENTION: A monitor at 7200 FPS is RIDICULOUS! This 'experiment' only exists to prove the point that we can most definately see the difference af different framerates, BUT ONLY WHEN THE OBJECT IN QUESTION IS MOVING VERY FAST ACROSS THE MONITOR! I do hope this is clear enough, because I don't know why I took the time to write all of this. And as I said, this only exists to prove the point that 60fps is not the limit that we can see. Goodnight!
  10. Yeah it was a pain, but I'm not unhappy just because of that.
  11. Maybe a "little". From the start, I was looking after high quality components with good value and found this case and power supply. And from then I suppose I started to like them a little too much. But I'm not dissapointed with what I've got from them...yet...
  12. I actually took those cages out because I wanted better airflow, the only real problem I have with the case is that there is no holes underneath the MOBO for cable routing. Too bad you didn't like it, I think this is an amazing chassi.
  13. That front 200mm is a 'CM Megaflow 200 Blue Led' and yes, it was purchased separately, the stock 200mm fan is placed on the top instead.
  14. [uPDATE] So after a looong while, I've finally got a real CPU cooler. It took a while for me to actually take the pictures, because I was lazy, but here it is. I've also made some slight overclocking to start with and I might go up a little more. So, this post is going to be this way for some time, until I decide to go even further with it. Thanks for checking my build out and please do give me some feedback and/or tips on what I can do later on.
×