Floatplane Pilot
  • Content count

  • Joined

  • Last visited


  • check
    Agree 9
  • info_outline
    Informative 5
  • tag_faces
    Funny 44
  • thumb_up
    Thumbs Up 17
  • thumb_up
    Likes (Old) 77


This user doesn't have any awards

About Cooly568

  • Title


  • CPU
    Intel i7 4790K
  • Motherboard
    ASU Smaximus VI Impact
  • RAM
    Corsair Vengeance LP 16GB Blue
  • GPU
    ASUS STRIX 970 (painted white with blue backplate)
  • Case
    Rosewill Neutron
  • Storage
    256GB Kingston SSD - 2x Seagate 1TB RAID 1
  • PSU
    EVGA SuperNova NEX 750 Gold
  • Display(s)
    AOC Q2963PM
  • Cooling
    Noctua D15
  • Keyboard
    Razer Deathstalker
  • Mouse
    Logitech G502 Proteus Core Tunable Gaming Mouse
  • Operating System
    Windows 10 Home

Profile Information

  • Gender
  • Biography
    An idiot.

Contact Methods

Recent Profile Visitors

436 profile views
  1. I've actually switched cables before, although I'll switch back and see if it performs different. Both cables I can use and have used are known good and are High Speed cables. Thought the only standards for cables were Normal and High Speed. The GPU is a GTX 960, and the TV is a Vizio D58u-3. Both support HDMI 2.0. I just have it set to 3840 x 2160 at 60 hertz, it just automatically sets itself to 59 or 30, despite 60 still being a valid option.
  2. Hiya, so I've been having an issue ever since I moved over to an HDMI 2.0 only setup. Whenever I would go into a game that forced the system to full screen, and quit the game, Windows would set the display mode to either 30 hertz or 59 hertz, both which essentially look like 30 hertz on my TV that I have it plugged into. 1080P never has this issue, but I always run the system at 4K, except for some games where I drop the resolution, and if I quit the game, Windows does it's defaulting down business. It can be fixed easily if I go into advanced display properties in Windows and set it to 30 hertz, and then 60 hertz, which is odd, since it defaults to 59 hertz, but that ends up looking like 30. Changing it to 60 when it's at 59 does nothing, I have to go from 59 to 30 to 60. Also, the nVidia control panel disappeared for no reason, no driver updates have happened since it showed up before. Before it disappeared, I set nVidia control panel to 60 hertz, but it still does this.
  3. I'll, tell you what it comes down to. I was being dumb. The TV was in RGB mode instead of YCBCR mode. Although, when I unplugged and replugged the cable, the two modes looked different, however when I restarted the system and switched between the two modes, nothing changed, odd. Edit 1: Got it working great. Setting limited range with YCBCR mode on the TV makes it look not oversaturated with like Full on RGB, but still with dark blacks. Thanks for the help!
  4. It's a Vizio D58u-D3. The weird thing is that it looks far better on Full mode, when running off of displayport, I was able to choose between the two, and full looked far better to my eyes, so it must of been working.
  5. I'm on YCbCr420. I have Full hacked on with a registry change right now, but if I change any resolution, it sets back to limited. And, well, there's no RGB mode. Only YCbCr420. Anyway to get the GPU to not pick up the fact that it's a TV? I was running Full on Displayport before, adapting to HDMI 2.0, I may look into doing that again.
  6. Hiya, so in the nVidia Control Panel, there's an option to allow RGB values to run from 0-255 instead of 16-233. I'm on HDMI, however, on HDMI, it is turned to limited by default. I've read around that some people turn it to full by setting it off of the limited default, however, when I go to Output Dynamic Range and drop it down, the only possible option to click is limited, full is nowhere in sight. Using a registry hack I was able to get it set to full temporarily, but it stopped working after a reboot. I'm on the latest driver for the GTX 960 on a 4K television that is capable of running full, when I was using a Displayport to HDMI adapter, the mode was allowed to be selected, and ran fine. The option now is not grayed out, as it doesn't exist. Thoughts? Edit 1: Oddly after plugging in the cable to a different input on the TV, specifically one of the 1.4 ports, the option appeared. Plugging back into the HDMI 2.0 port allowed the dynamic range option to appear. Odd. However it was locked to 30Hz. After changing HDMI cable, it defaulted to 60Hz and Limited.
  7. I was looking for drive bays for my server before I stumbled over onto to find a discussion on silencing vibrating hard drives, and openly exclaimed "WHAT THE FUCK FREENAS." how did you know i was a brony freenas? are you buying my web history
  8. Has LTT, CSF, or TQ ever seen a dislike ratio higher than 1:2? Honestly though, the video is nothing off the beaten path, the title just threw people off, and almost made me think it was a press release or something.
  9. Really just as low cost as possible without being a massive rear projection TV that weighs as much as an average hippo. And I'll take a look at this one, thanks!
  10. It seems like all I hear from the massive TV corporations nowadays is, HDR, and, 4K. But I'm a person who's fine without any of that. The TV in my living room is a partially broken 43" Vizio TV, broken because it has a line of dead pixels and a response time longer than the ice age, and I kind have been in the market for something better. I'm looking for a 60+ inch 1080P TV, with acceptable response times for gaming. On the cheaper side. Any ideas?
  11. Hiya. So I have some WI-FI passwords on a Mac OSX device I need to get at, because, I can't remember them, but they are protected as I am not the admin on my device. Terminal commands that find the password either require admin access to get into the sudo commands, or try to call Keychain Access, which requires an admin account. So, any way to do it?
  12. I couldn't give a toss.
  13. Eh, I'm just mostly interested. If I had to choose a price range of what I was willing to spend in the future, I'd say no more than 100$. Or is that too little.