Monitor Tests Forum

Full Version: Custom Resolution Utility (CRU)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814
So AMD or Windows is automatically adding extra refresh rates to some of my resolutions. Is there a way to remove those modes?

Like I added 1366x1024@60hz with CRU, but then when I look at the resolution in games or display settings, I see that 85hz is also available. If I select 85hz, my display will scale to the next highest resolution which has a 85hz mode in CRU (in my case, 1440x1080@85hz) so I get a blurry picture. To compound this problem, some games always select my highest available framerate, so I both a blurry picture and a framerate I don't want.

EDIT: I realized that it's only the refresh rate in the first slot in "detailed settings", and subsequently is labeled the recommended resolution, that gets applied to all other lower resolutions. In my case it is 1440x1080@85hz so everything lower than that gets an 85hz mode (and are actually just upscaled to 1440x1080 if there isn't an explicit 85hz mode for the resolution in CRU). Anybody know of way to stop that from happening?
I am using this program for years and it has been working great until recently. I think after some nvidia/or windows driver update I got the following issue:
If I start windows I see my custom resolution (90hz) wich I setup in cru on the nvidia panel.
However if I go to my monitor properties I only see 59+60 hz.
If I do the driver restart.exe then suddenly the refreshrate is also there on my monitor properties.
It's like the monitor readout is wrong when i boot windows. If I take a look at the supported res my custom ones isn't there. When i use the restart driver it does appear as well.

I use 2 gtx780- in sli (no sli same issue) with the nvidia patch (not full one but i did tried that)
Windows 10 x64
overlord oc monitor using generic pnp monitor in win10.

I tried removing the cru setting/nvidia drivers/ (with ddu) and reinstalled it all from 0.
Still same issue.

Yes I can restart the driver automatic after every reboot but then I have to reset my oc setting on the gpu's like voltage and stuff.

Really odd problem but maybe someone has an idea how to solve this or how to fool windows to read it correctly after each reboot without needing to using the restartx64.exe

Thanks
(06-15-2016 07:36 PM)Axejess Wrote: [ -> ]I am using this program for years and it has been working great until recently. I think after some nvidia/or windows driver update I got the following issue:
If I start windows I see my custom resolution (90hz) wich I setup in cru on the nvidia panel.
However if I go to my monitor properties I only see 59+60 hz.
If I do the driver restart.exe then suddenly the refreshrate is also there on my monitor properties.
It's like the monitor readout is wrong when i boot windows. If I take a look at the supported res my custom ones isn't there. When i use the restart driver it does appear as well.
Did you make sure to choose "Custom extension block"? Don't use "No extension block" because what you described is exactly what happens because of an NVIDIA driver bug if GeForce Experience is installed.
(06-16-2016 03:38 PM)ToastyX Wrote: [ -> ]Did you make sure to choose "Custom extension block"? Don't use "No extension block" because what you described is exactly what happens because of an NVIDIA driver bug if GeForce Experience is installed.

Yeah i did choose custom extensions block. If i don't I also wont see the new hz setting in nvc. But even when my monitor pnp says 59-60 I do see my own setting in nvc. I haven't added a extra custom setting in nvc.

And no it isn't GeForce Experience what's causing the problem.
Uninstalled it. Resetted the settings. Problem still there after reboot (only 59-60hz) nvc i do see my custom 90hz. When I use the restartx64.exe it shows on the monitor properties.

Also tried deleting samsung magician. disabled all start-up items. Gone back to a windows restore point from 3 weeks ago.

I am missing something but what.
For now I created a scheduled task that runs restartx64.exe after a logon after 5sec wait. And 5 sec later it runs my oc gpu program so I don't forget to reset my own voltage.

Edit reinstalled windows and all programs. Now it's working. So it seems there was something wrong on my old windows install.
(06-14-2016 10:52 PM)CRTFTW Wrote: [ -> ]So AMD or Windows is automatically adding extra refresh rates to some of my resolutions. Is there a way to remove those modes?

Like I added 1366x1024@60hz with CRU, but then when I look at the resolution in games or display settings, I see that 85hz is also available. If I select 85hz, my display will scale to the next highest resolution which has a 85hz mode in CRU (in my case, 1440x1080@85hz) so I get a blurry picture. To compound this problem, some games always select my highest available framerate, so I both a blurry picture and a framerate I don't want.

EDIT: I realized that it's only the refresh rate in the first slot in "detailed settings", and subsequently is labeled the recommended resolution, that gets applied to all other lower resolutions. In my case it is 1440x1080@85hz so everything lower than that gets an 85hz mode (and are actually just upscaled to 1440x1080 if there isn't an explicit 85hz mode for the resolution in CRU). Anybody know of way to stop that from happening?
The driver automatically propagates higher refresh rates down to lower resolutions as scaled resolutions. I don't know if there's a way to stop that. It should be doing that for all resolutions, not just the first detailed resolution. If it's only affecting the first detailed resolution, you should be able to set the lowest refresh rate as the first detailed resolution to avoid that.
(06-13-2016 02:39 AM)drummer4christ81 Wrote: [ -> ]When I set my Laptop from 1600 x 1200 (6:10) to 1600 x 1080 (6:9) my screen looks like this.

https://www.dropbox.com/s/tuvpa6t8op9b16...n.jpg?dl=0

What am I doing wrong?
Laptop displays don't have scalers, so they can only handle the native resolution. You have to enable GPU scaling for lower resolutions to work properly.
(06-05-2016 09:38 AM)ashlar Wrote: [ -> ]I'm afraid I don't understand. In Windows, with regular drivers, I have both 23 and 24 in the list. And they both exist independently. madVR is capable of selecting one or the other. At least, this is how I remember it before installing and using CRU. Am I remembering wrong?
23 Hz and 24 Hz are supposed to be aliases, not separate refresh rates: https://support.microsoft.com/en-us/kb/2006076

You might be able to create separate refresh rates using the NVIDIA control panel, but not with CRU. You can use CRU to remove the original refresh rates so they don't interfere with the custom ones.
(06-05-2016 10:55 AM)hannes69 Wrote: [ -> ]
Quote:Windows doesn't have a way to list both.
No.
I have AMD Crimson driver 16.5.3 which has the ability to create custom resolutions. In the category "base mode" I have to enter horizontal/vertical resolution, refresh rate, interlaced/progressiv and timing standard. In the category detailed timings I can enter the porches.
The interesting thing is: You can enter what you want at "refresh rate" and this naming is then taken by Windows.
I can e.g. create 2 custom resolutions 47.952Hz and 48.000Hz (in my setup they are actually a little bit smaller so the 48.000Hz becomes a 47.999xxxxHz refresh rate) and call them "47" and "48". In Windows they appear now with these names in the listing of supported resolutions. There´s no plausibility check, if I want, I can call them "46" and "41".
That's using a driver-specific method. CRU uses EDID overrides, so it doesn't have control over that. 47.952 Hz will round up to 48 Hz, and Windows doesn't have a way to list two 48 Hz refresh rates.
(06-16-2016 03:57 PM)ToastyX Wrote: [ -> ]
(06-14-2016 10:52 PM)CRTFTW Wrote: [ -> ]snip
The driver automatically propagates higher refresh rates down to lower resolutions as scaled resolutions. I don't know if there's a way to stop that. It should be doing that for all resolutions, not just the first detailed resolution. If it's only affecting the first detailed resolution, you should be able to set the lowest refresh rate as the first detailed resolution to avoid that.

Yep, that's basically what's going on. I ended up just setting my custom 1024x768@125 mode as the first detailed resolution, and now all my higher resolutions are fine.

Thanks again man, as one of the last CRT holdouts, your tool has made my experience a lot better. Like I'm pretty sure I'm the only person on planet earth playing Street Fighter 5 at 2176x1224, and it looks gorgeous!
First of all thanks for the great tool ToastyX!

I have a question, sry if it was already asked in this 212 pages slong thread, if so just link me the answer Big Grin

My question is regarding the timing:
With the "native" timing I can reach max 66Hz@1080p@163.35Mhz (I dont want to patch the GPU drivers yet).
With the "standard" timing I can go up to 71Hz@1080p@164.96Mhz.
So what are the pros and cons of these timings and what are they there for?
Is there a disadvantage using the "standard" timing which woudl allow me to go up to 71Hz without patching the driver?

I also read somwhere when using the Nvidia control center I don't need to patch driver because it automaticly overlocks the pixel clock?

Edit: Something else just caught my eye.
In the Nvidia control panel it doesn't say HDMI anymore but DVI.
Is this normal?


Regards Magicool
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814
Reference URL's