OCCT Perestroika - 3.0.0.b04 released ! Stable : 2.0.1

[Tetedeiench]

Hi

What does the error 'debordement de pile' mean? Got it after 18h of OCCT RAM (Larger) on 3 beta 10 on system below.

Thanks
Andy

That's an internal error of OCCT. it can mean your system isn't stable, as well as being a bug of OCCT.

I'll try to reproduce it, however i don't have a quad-core system :/

Oh, and i apologize for the logn reply delay, i knew i forgot something.

[powellandy]

That's an internal error of OCCT. it can mean your system isn't stable, as well as being a bug of OCCT.

I'll try to reproduce it, however i don't have a quad-core system :/

Oh, and i apologize for the logn reply delay, i knew i forgot something.

Anything I can do to help?

Andy

[stasio]

The temp monitoring from OCCT is as good as HWmonitor, which is integrated into OCCT

Voltage +12V(-12;-5) wrong and GPU temp missing.
HWmonitor 1.12 has several issues to be fix
Btw,
When loading OCCT PT 3.0.0.b13 in WINDOWS 7,receive notes:
-Your DirectX9 isn't up to date.OCCT GPU and Power supply tests will be disabled.
-Your graphic card doesn't support CUDA.You need Geforce 8 or higher.GPU memtest will be disabled.

[powellandy]

Possible bug reports

- How is OCCT 3b12 supposed to behave on clean vista x64 sp1 install. Says dx9 not installed and no GPU tests - is this normal - should I install dx9?

- How is linpack OCCT 3b12 supposed to behave on Hyperthreading Intel P4 630 (Prescott). System info says 1 core and running linpack test shows 100% CPU usage in OCCT but only 50% in Process Explorer. Using CPU OCCT test with hyperthreading box ticked gives 100% usage in both. Should linpack stress both 'cores'?

Andy

[Tetedeiench]

Possible bug reports

- How is OCCT 3b12 supposed to behave on clean vista x64 sp1 install. Says dx9 not installed and no GPU tests - is this normal - should I install dx9?

- How is linpack OCCT 3b12 supposed to behave on Hyperthreading Intel P4 630 (Prescott). System info says 1 core and running linpack test shows 100% CPU usage in OCCT but only 50% in Process Explorer. Using CPU OCCT test with hyperthreading box ticked gives 100% usage in both. Should linpack stress both 'cores'?

Andy

Those are not issues, but they need explanations

* You have to update DirectX9 even on vista (it is DirectX10, but it does have everything for DirectX9 too). That's why OCCT is complaining

* That's hyperthreading I'll try to keep the explanation short & understandable. Hyperthreading causes your OS to see twice the real amount of real cores on your system (for instance, if you've got 2 cores, Windows will see 4). However, you can view those 4 cores as "2 are real, 2 are "benefits only" from HT". So if you load the 2 real cores, and the 2 others are IDLE, you'll see, In the task manager, 50% workload. In reality, you'll have both of your physical cores loaded, and no benefit from HT taken. Those 50% means "95% of the real horse power of your CPU", to keep it short.

OCCT CPU test has 2 different behaviours :
* Without HT as DC, it will launch one test per physical core (i.e. "real" core). Thus you'll see 50% load, even if 95 or so% of your CPU is busy.
* With HT as DC checked (by default, as it proved more efficient on HT CPUs), OCCT will launch one test per core, physical or logical (i.e. real and "fake" cores). You'll see 100% workload in the task manager.

The linpack test has only one mode : 1 test per real core. Thus the 50% in the task manager.

The hard part is understanding that only half of your cores in the task manager are "real", and that the others represent the benefits from HT.

[Tetedeiench]

OCCT PT 3.0.0.b13 OUT !

Changelog :

• OCCT CPU Test fixed : Now the mode "large data set" works on core i7s
• A message now warns you to use fullscreen mode when you're using SLI/Crossfire. I'm currently working on the profile part in Nvidia's SLI (you do need one). Crossfire should be already supported flawlessly.
• Fullscreen mode is checked by default if you're using SLI/Crossfire, even in Auto mode
• Going back to "Auto" mode doesn't make you switch back to 500x500 anymore. 1024x768 is instead used, as intended.
• The Linpack test is now working again with 32 bits OS with more than 2GB of memory installed.

Enjoy !

http://www.ocbase.com/download.php?fileext=beta

Can someone with a crossfire confirm me that everything is well in Fullscreen mode with the GPU 3D test, even in error check mode ? Thanks !

[kiwi]

Tetedeiench,

What are ci7-1, ci7-2, ... versions? Are they specifically made for core i7?

[Brama]

I see that italian translation is incomplete.
If you need an help, I am available.

[Tetedeiench]

Tetedeiench,

What are ci7-1, ci7-2, ... versions? Are they specifically made for core i7?

They were debugging versions for the CPU OCCT problem. I'm currently deleting them

[Tetedeiench]

I see that italian translation is incomplete.
If you need an help, I am available.

That would be great I'm not done yet, but there will be alot of translation changes soon

[Tetedeiench]

There was an error in b13, i forgot to remove a debug message. It has been fixed and reuploaded

[Tetedeiench]

OCCT PT 3.0.0.b14 OUT !

Changelog :

• The linpack test now works with 32 bits OS with more than 2GB of Memory
• OCCT's way of remembering window position as been changed for some people for which it didn't worked

Enjoy !

http://www.ocbase.com/download.php?fileext=beta

[powellandy]

Those are not issues, but they need explanations

* You have to update DirectX9 even on vista (it is DirectX10, but it does have everything for DirectX9 too). That's why OCCT is complaining

* That's hyperthreading I'll try to keep the explanation short & understandable. Hyperthreading causes your OS to see twice the real amount of real cores on your system (for instance, if you've got 2 cores, Windows will see 4). However, you can view those 4 cores as "2 are real, 2 are "benefits only" from HT". So if you load the 2 real cores, and the 2 others are IDLE, you'll see, In the task manager, 50% workload. In reality, you'll have both of your physical cores loaded, and no benefit from HT taken. Those 50% means "95% of the real horse power of your CPU", to keep it short.

OCCT CPU test has 2 different behaviours :
* Without HT as DC, it will launch one test per physical core (i.e. "real" core). Thus you'll see 50% load, even if 95 or so% of your CPU is busy.
* With HT as DC checked (by default, as it proved more efficient on HT CPUs), OCCT will launch one test per core, physical or logical (i.e. real and "fake" cores). You'll see 100% workload in the task manager.

The linpack test has only one mode : 1 test per real core. Thus the 50% in the task manager.

The hard part is understanding that only half of your cores in the task manager are "real", and that the others represent the benefits from HT.

Thanks for this. I know what hyperthreading is... Just wanted to ensure it was working the way it should.... which it is! Thanks

Cheers
Andy

[Ket]

OCCT PT 3.0.0.b13 OUT !

Changelog :

• OCCT CPU Test fixed : Now the mode "large data set" works on core i7s
• A message now warns you to use fullscreen mode when you're using SLI/Crossfire. I'm currently working on the profile part in Nvidia's SLI (you do need one). Crossfire should be already supported flawlessly.
• Fullscreen mode is checked by default if you're using SLI/Crossfire, even in Auto mode
• Going back to "Auto" mode doesn't make you switch back to 500x500 anymore. 1024x768 is instead used, as intended.
• The Linpack test is now working again with 32 bits OS with more than 2GB of memory installed.

Enjoy !

http://www.ocbase.com/download.php?fileext=beta

Can someone with a crossfire confirm me that everything is well in Fullscreen mode with the GPU 3D test, even in error check mode ? Thanks !

I can probably check that tomorrow at some point for you, stability testing a different system atm.

[Brama]

That would be great I'm not done yet, but there will be alot of translation changes soon

I confirm I am available for translation of OCCT 3 from english to italian.
If you need my help, let me know here or by a PM.

[Tetedeiench]

d'oh -- you should remind those of use that usually use Infinite. And, why?

In error checking mode here, I get 15fps and no movement of the pattern -- but GPU temp goes up like it's under load.
Without error checking, I get 75 fps and the pattern moves nicely.

Same thing in full screen except it's 12.5 & 84 fps. And, why do you use a low res screen? 640x480!

(Video card in sig. -- eVGA 7900 GT KO RoHS, Zalman VP900CU Cooling, mild OC to 645 MHz)

Edit: Also -- a feature request. I usually run LinPak for a certain number of tests, not for a fixed amount of time. Can you include that option?
And, if I run 90% of memory it won't run (no cpu load). I'm assuming that you're not setting memory correctly for 32 bit XP with 4G of memory (IMU, less is usable because of reserved space for memory mapped PCI cards).

I've got so much to read and answer, sorry about the long reply delay

Error checking mode : this behaviour is normal. OCCT GPU checks the 3d output by comparing to a reference frame that was recorded a while ago. Thus, i disable all movement to be sure i've got the same rendering for each frame.

More, CPUs aren't capable of checking alot of frame per seconds. To prevent the CPU from dropping frames because the pile is full, i limit the fps to 15, which is already not bad. And for that, i augment the complexity of the scene. That's what you see at the beginning. It may happen if the pile is full : OCCT will then augment the complexity to avoid dropping frames (and thus, not cheking the results).

What do you mean by low-res screen ? You can configure it in OCCT's UI

As for the linpack "run a fixed # of loops", yes, it is planned. I don't think it'll be done for 3.0.0 (i want to stop implementing features to be able to release a stable version), but in 3.0.1, i'll definitly think about it, as well as, in this case, outputting the GFlops value calculated by linpack.

[Tetedeiench]

I confirm I am available for translation of OCCT 3 from english to italian.
If you need my help, let me know here or by a PM.

Sorry to ask you, but can you send me your email by PM or to iench 'attttt' ocbase 'dot' com ? I'm usually communicating by email with people doing translations

Thanks

[Tetedeiench]

OCCT PT 3.0.0.b15 OUT !

Changelog :

• News version of Linpack test : can someone checdk with XP 32 bits with more than 2GB of memory ?
• The Linpack test isn't limited to 2GB of memory on 64 bits systems. It was successfully tested on a 16GB memory computer - it takes about 13s to allocate all that memory
• The tab order is now correct in the option window
• SLI detection fixed : it should now work and enable fullscreen by default in GPU and Power Supply tests
• The warnings about SLI and Powersupply test now shows correctly (i.e. only once).
• Fixed several errors (invisible for you all) preparing for the translation process

Enjoy !

http://www.ocbase.com/download.php?fileext=beta

[emoners]

@Tetedeiench: thanks for the update!

[Tetedeiench]

OCCT PT 3.0.0.b16 OUT !

Changelog :

• The linpack test is now working again with XP32 with more than 2GB of memory
• the TAB key now works everywhere, and the order has been fixed
• The Temperature line is drawed in front of the CPU Usage line, in the graphs. This leads to better lisibility of the graphs.

Enjoy !

http://www.ocbase.com/download.php?fileext=beta

[shazza]

Just started playing with OCCT ... really like it. I have two questions, pertaining to the first system in my sig:


1) For some reasons, it's not showing the 5V reading for the Power Supply ... it shows disabled, and there is no 5V setting showing up when I do the drop down menu. It does show ... and looks okay with PC Probe II (I read earlier that it's best to remove this app ... haven't done that yet). Also, I pass the PSU test fine.


2) When I run the GPU MEM test, it passes - but shows a large number of errors. I think I also read that this may not work for ATI GPUs ... is that still the case?

[Brama]

2) When I run the GPU MEM test, it passes - but shows a large number of errors. I think I also read that this may not work for ATI GPUs ... is that still the case?

It happens to me too, with an ATI X1900 and Catalyst 0812.
No errors with my second PC with a Nvidia 8800 GTS 512.

[powellandy]

Just started playing with OCCT ... really like it. I have two questions, pertaining to the first system in my sig:


1) For some reasons, it's not showing the 5V reading for the Power Supply ... it shows disabled, and there is no 5V setting showing up when I do the drop down menu. It does show ... and looks okay with PC Probe II (I read earlier that it's best to remove this app ... haven't done that yet). Also, I pass the PSU test fine.

This is a problem with the CPU-Z hardware detection routine used. I have the same thing (with an Asus Maxiumus 2 Formula). I PM'd the chap at canard PC who writes it and he said he was looking into it....

Cheers,
Andy

[shazza]

Thanks, Brama and Andy ... good to know it's not just me. I googled for the 5V issue, but couldn't find much.

Since it passes all tests, and everything seems very stable, guess I'll keep on going.

[Tetedeiench]

Just started playing with OCCT ... really like it. I have two questions, pertaining to the first system in my sig:


1) For some reasons, it's not showing the 5V reading for the Power Supply ... it shows disabled, and there is no 5V setting showing up when I do the drop down menu. It does show ... and looks okay with PC Probe II (I read earlier that it's best to remove this app ... haven't done that yet). Also, I pass the PSU test fine.


2) When I run the GPU MEM test, it passes - but shows a large number of errors. I think I also read that this may not work for ATI GPUs ... is that still the case?

1) Somebody else already answered this I can't do a thing about it unfortunatly.

2) GPU memtest will always work - but reports the number of errors found. I'm not happy with the current state of this test, and it will be revamped soon. Right now, don't put too much trust in it