Printable View
not intuitive...that isn't a metaphor used anywhere in UI to my knowledge. The tabs in the original version where MUCH better.Quote:
Originally Posted by Tetedeiench
Overall, a great product.
You may want to add a little history to explain your startup metaphor. You will find a large part of your relatively young international audience isn't familar with Russian history.
are there any command line switches for OCCTGPU.exe?
-errorcheck -1440x900 -3600 (seconds)
...stuff like that :confused:
love it so far, but linpack and i7 with HT doesn't even load the cores 1%.
Quote:
Originally Posted by ReverendMaynard
Yes, current beta as got a bug with this setup... i'm working on it atm :)
Yes :Quote:
Originally Posted by ThugsRook
-f : Toggle Fullscreen (default : window mode)
-w=X : Screen/window width
-h=X : Screen/window height
-r=X : Refresh Rate
-e : error check
OCCT PT 3.0.0.b17 OUT !
Changelog :
- The OCCT Test is now executed in a separate process (this is done to open the way for the "one core not detected" bugfix).
- The OCCT GUI will now report on which core the error occured in the OCCT Test.
- The files "ThreadX.txt" aren't generated anymore (the previous point removes all need for them).
- The way translations are handled is now brand new and much, much more easy to update for me ;)
- If the Linpack test refuses to start, OCCT will now lower the memory utilisation until a successfull start. You may see a small delay in launching the Linpack test, but it is usually less than a second in the worst case.
- The field showing the test duration is now always updated, depending on the test selected. Try to select "custom" and change the duration, you'll quickly see what i mean.
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
Nice one. Btw when do you think you'll have a non-beta 3.0 version?
I think this will happen this month. I want to improve the GPU:Memtest, and to get all translations done before releasing.Quote:
Originally Posted by kill_a_wat
Do your planned GPU:Memtest improvements include support for ATI?
--Matt
Yes, of course. For that, i need an ATI video card, and this will happen... well... when either i've got enough donations, either when a reseller or AMD or anyone else will send me an ATI card, hopefully dual-GPU so that i can get it done directly in SLI ;)Quote:
Originally Posted by mattkosem
However, this won't be done before quite some time, so expect a 4/5 months delay at least before getting your hands on an ATI version of GPU Memtest.
The Nvidia one will be updated in the next week (hopefully), and it will be a major update.
TY :DQuote:
Originally Posted by Tetedeiench
I've skipped the annoucements of a few release, because they were mostly debugging versions, as i was struggling with linpack and 32 bits systems with more than 2GB of memory.
I've come to repair that mistake ;)
OCCT PT 3.0.0.b22 OUT !
Changelog :
- The OCCT Test now executes as a separate process
- The bug known as "-1 core detected" is gone
- Monitoring/system info engine updated
- Linpack 32 bits test now works with systems with more than 4GB of memory - max mem considered is 1.44GB (universal value)
- The power supply test now works everywhere as well
- GPU:Memtest has been GREATLY updated : 6 thorough tests have been implemented, and they are EXACTLY the same as Memtest86+. One pass is takes much, much longer though (i'd say about 10 minutes). But the efficiency is now much better. Remember, you need a geforce 8 or later cards.
Enjoy !
http://www.ocbase.com/download.php?fileext=beta
Seems RC1 is out now, just went to this (http://www.ocbase.com/download.php?fileext=beta) download link and it's what downloaded :cool:
Yeah,RC1 is out from 23.Jan 2009.
Waiting for Tetedeiench changelog.
For some reason my +5v line monitoring has disappeared....there seems to be no option in the options menu to enable (no +5v line in the drop down menu)...?Quote:
Originally Posted by Tetedeiench
I had the +5v line monitoring in version 2
:clap:Quote:
Originally Posted by stasio
:does a dad dance around the room:
I just released the stable version one hour ago :)
You can find everything on OCCT's website :) www.ocbase.com
I also opened a board - but i expect one message per day - or so :D
Here's OCCT 3.0 changelog, and download links - i don't know if i should create a new thread or not.
Changelog (Since 2.0.1) :
MAJOR FEATURES
- OCCT's main UI has been completly revamped
- Graphs now shows a 2nd line showing the CPU usage / FPS during the test.
- CPU usage is now instantaneous instead of an average since the start of the test
- OCCT now has 5 different tests. The descriptions are at the end of the changelog
USER INTERFACE
- Entirely revamped - now based on tabs, and completly modular
- Now has a small help module - just move your mouse around OCCT's window, you'll see
MONITORING
- The built-in engine has been updated - lots of new hardware are now supported
- Alot of bugs are fixed, included the famous "3 cores out of 4 detected"
GRAPHS
- Graphs now shows a second line showing the CPU usage/FPS during the test
- A legend explains everything
- The test configuration is now entirely present in the graph's subtitles
TESTS DESCRIPTION
CPU:OCCT
- The original, inherited from previous versions of OCCT
- Now Core i7 compatible
- Optimized
CPU:LINPACK
- The very same as IntelBurnTest, based on a test provided by Intel
- It will make your CPU hotter than never !
- 32 and 64 bits support
GPU:3D
- Home-made test written in Direct3d that will make your GPU really hot - this test is similar to ATITool and Furmark (thanks to Furmark and JegX for his support and for the aborted partnership ;) )
- Will make your graphic card real hot - especially the GPU
- Has an error detection mode similar to ATITool
- SLI and Crossfire support (Just enable Fullscreen mode !)
GPU:Memtest
- Again, Home-made test written in CUDA that'll launch a MemTest86 or MemTest86+ like test on your Graphic card memory and report any error found
- Requires a Nvidia Graphic Card, and a GeForce 8 or Higher !
Power Supply
- Dedicated to power supplies - it'll launch GPU:3D and CPU:LINPACK at the same time to load your power supply. BEWARE, THIS TEST IS REALLY DEMANDING !
- WARNING, DO NOT USE THIS TEST WITH NO-NAME POWER SUPPLY, AS A FEW DEATHS HAVE ALREADY BEEN REPORTED !
- This tests demands 30 to 40% more power than crysis on a quad-core system with an SLI graphic system installed...
Enjoy !
EXE : http://www.ocbase.com/download.php?fileext=exe
ZIP : http://www.ocbase.com/download.php?fileext=zip
Phew, tired after all that writing :D
Well done Tetedeiench:clap:
Good job!
Awesome, been waiting for this for a long time !
Thanks a lot for your hard work !
Tetedeiench Thanks a lot for your software. Probably it's the best all-in-one heating package. :D
Just a tiny-tiny request, latest Everest is able to read CPU power consumption from EPU or DES (sensor name is PCPU) and I'd like to see that in a graph among core temperatures.
I can see it in RivaTuner but I'd like a graph in OCCT too.
Attachment 93763
Thanks. :bows:
Good Job m8 , really working nicely
Is there any way to disable that 1-minute monitoring phase that occurs before any test?
I found a bug: using italian language, if I set max temperature to 100 C°, when I close the program and launch it again, max temp reverted to default 80° and frequently the sensors that I chosed are not in the provious position.
P.S. I found the Power Supply test very effective. After less than 10 minutes, it blew up my Tagan 580 W power supply with a couple of "bangs" and a disgusting burnt silicon smell....:)
I found a bug with linpack testing. I have a Core i7 920 and Windows XP x64 SP2, and when I run the linpack test (and also the PSU test), the CPU only gets loaded with 4 threads, not 8. On the normal OCCT CPU test, 8 threads does work when you enable the hyperthreading option. LinX 0.5.6 properly loads all 8 threads on the i7.
Is GPUmemtest to be trusted? I'm getting errors all over the place with my gtx280 which seems to be stable in all the games I play
BureBista > I didn't know about that feature. I only works with a limited numbers of PSU, right ?
003 > For the 1 min period : use the Infinite test ;)
Brama > i'll look into it, as i've got several reports on such bugs. I'm pretty busy at the moment though, so i can't give you an ETA :/
003 > for i7 and Linpack > This is not a bug. Your i7 only has 4 physical cores. Linpack does not support HT at all.
A somehow limited MB models. All ASUS equipped with EPU and all Gigabyte equipped with DES and maybe MSI with DrMOS.Quote:
Originally Posted by Tetedeiench
Something like that.
GPU memtest is buggered, imho. I've run Video Memory Stress Test for several hours w/o a single error in DirectX mode, while OCCT throws out errors all over the place.
How come LinX is able to load all 8 threads 100%? Maybe check with dualist to see how he was able to do that. OCCT is great now, it just needs to be able to load 8 threads on the i7 with linpack and it would be perfect! :yepp:Quote:
Originally Posted by Tetedeiench
Same for me. My Gtx260 throws shows 40,000+ errors.Quote:
Originally Posted by anzial
He's just launching two linpack, i guess. Nothing proves that this is better than launching only one, at the moment ;) I guess i'll implement that feature later on, but really, i don't think that a really good idea ;)Quote:
Originally Posted by 003
Yes, GPU: Memtest isn't reliable at all on GTX260/280 and cards of the same generation. I couldn't test it at all on those cards.Quote:
Originally Posted by icecold316
I guess that's what comes of limited access to test hardware :shrug:
Any changes in beta1?
I'm centralizing betas in my own board - much less hassle for me :D
http://www.ocbase.com/forum/viewtopic.php?f=5&t=19
Thanx
For those with GTX260 and such cards and GPU:Memtest problems : are you using XP or Vista ?
I suspect a problem with Nvidia's implementation in GT200 Vista drivers, as i've got a few GT200 users under XP without problems...
For those who still wonder, this problem seems to be due to a bug in GT200 drivers under Vista, not to a bug in my test ;)Quote:
Originally Posted by Tetedeiench
I'm working on it with Nvidia ;)
GT200 users, if you want to give a shot to GPU:Memtest, it works fine with Windows XP !
OCCT PT 3.0.1.b02 fixes the GPU:Memtest problem encountered by GT200 users under Vista.
More info centralized over there :
http://www.ocbase.com/forum/viewtopic.php?f=5&t=23
As usual, the download link : http://www.ocbase.com/download.php?fileext=beta .
It has been reported as ok with GT200 and vista.
YOU NEED 181.22 OR HIGHER DRIVERS FOR IT TO WORK
Are there any final release versions in sight yet? :D
Tetedeiench, I think nvidia has gimped your GPU test in the 182.05 and 182.06 drivers! With 181.22, the GPU test would get my GTX280 up to 46C+, but now on 182.05 it won't break 34C, the idle temp. FurMark still hits 45C+.
EDIT:
I'm on water of course.
OCCT 3.0.1 final
http://www.ocbase.com/perestroika_en/index.php?Download
Can you tell me more ? (OS especially ? )Quote:
Originally Posted by 003
i'm using a GTX260, XP32, and 182.06 drivers, and GPU:OCCT (from version 3.0.1, which haven't changed a bit since 3.0.0) still runs perfectly fine and reaches about the same temp than furmark ...
Perhaps you left the Error check mode enabled, which load the GPU much less, which is, for now on, normal (unfortunatly).
I came here to announced it :DQuote:
Originally Posted by xaver
It especially fixes the GTX260/Vista problem, which was due to a CUDA limitation under vista which i can't yet explain and thus label as a bug.
Be sure to use 181.22 drivers, at least.
my 8800gts 640mb fail the gpu memtest in the pass 2 .... it always doesn't detect errors in pass 1, but can't complete pass 2, I tried to manually change it to only make 1 pass, and it passes, I make the test again and again but just manually, I did it 5 times and it doesn't show any errors.
games are working fine.
I'm using 182.06
I think you're right, now that I have error check disabled, it seems to be working normally again, with one small quirk. It is reporting a lower GPU temperature than EVGA Precision 1.4 by about 6 degrees. I don't remember this problem on the 181.22 drivers, but I may just have a bad memory. I'm using XP x64 SP2.Quote:
Originally Posted by Tetedeiench
I recently discovered that G80 aren't compatible with Cuda 2.0. You need G84 or better cards. Sigh.Quote:
Originally Posted by phsinc1
This is seriously starting to hinder the GPU:MEMTEST usefulness for me, and i'm looking into CUDA alternatives... i may have fallen onto something though. Stay tuned.
I'm using version 3.0 and I ran the PSU test and my computer powers off within 5 seconds of testing. Does this mean I have an insuffient powersupply or the PSU is crapping out on me. I should say that my computer powers off after 4 mins of playing crysis. I absolutely have no issues with temperatures on my motherboard, CPU and video cards.
Current specs
PC power and cooling 1000W
e8400 @ 4.2
4 gigs of ram OCZ
Striker II extreme
285 gtx in sli
Three weeks ago released another version:
OCCT 3.0.1a.b01
Hey guys..
I have been using OCCT to stress my CPU, but having issues with it on the GPU.
Setup:
AMD Phenom II 940 BE
Silverstone Zeus
Gigabye 790GX mobo
(2) AMD 4870 (CF)
Windows Vista 32.
I can run the CPU just fine, but I can't do GPU.
The program complains that I'm not running Direct X 9, and something about Cuda.
Since I'm running Vista, I have DirectX 10, and Cuda shouldn't matter since I am on AMD / ATI Gpu.
Any suggestions?
- Ton
PS - dude.. i love the logging feature!! Graphs and CSV.. it is awesome.
PSS - Just installed 3.0.1ab01, and sitll have the issue.
OCCT needs an updated DirectX9 to be able to properly run. Vista comes with DirectX 10, and only 10. If you update DirectX10, you only update DirectX10, and not 9.
Go to the microsoft website, and update DirectX. Easiest way is to go to google, and search for "dxwebsetup.exe".
This should be the best way, and has a validation required :
http://www.microsoft.com/downloads/d...displaylang=en
If you don't want the validation, you can always get the redist version, but it is a bit more cumbersome (download the whole thing, extract the directory manually, go there, and launch the setup file) :
http://www.microsoft.com/downloads/d...8-9f20f1244a8e
Stasio - thanks for the update. I will give it a shot later tonight.
- Ton
OCCT 3.0.2.b02
* CPU:Linpack now supports Hyperthreading. Just make sure the HT checkbox is checked.
* The "Hyperthreading as dual-core" checkbox as been renamed as "Hyperthreading". Simpler, and much easier to understand.
* The Hyperthreading Checkbox is now checked by default for the CPU:OCCT and CPU:Linpack tests if your CPU supports HT. It will only be so on the first run, of course. If you uncheck it, OCCT will remember it.
This program is an awesome all in one tool for overclocking. The gpu test heats my gpu to the same temperature as furmark. The only thing this program would need is a gpu clock/voltage adjustment panel (like EVGA precision). Good job this program rocks!! :up:
Tetedeiench
I have been using your program in varoius versions since jan 2008 and what an awesome job you have done with the development. Love the 3.0.1 version. The test mode under Linpak and OCCT is greyed out whenever I first launch (vista 32 bit, even launch as administrator) but becomes available after runing with default setting on the first run. Is this intentional or am I doing something wrong?
Ok, I just had to change the test type to custom ! lol
OCCT 3.1.0.b04
Changelog :
Main (OCCT GUI)
* GPU:OCCT v0.70 has been integrated !
* OCCT now detects and displays the name of your graphic card (only if it supports internal monitoring, i'm relying on CPU-Z to do this detection)
* OCCT now auto-configure the Shader complexity value based on a CSV file named "ShaderComplexity.csv" file that you can edit. First match on the GC name wins. Wildcards are supported. Edit the file, it's pretty easy to understand.
* A compatibility checking engine has been implemented, that improves OCCT's detection of your computer's compatibility with Cuda and D3D tests.
OCCT 3.1.0.b06
# Main screen resolution will be detected when the user clicks on Fullscreen checkbox in GPU:3D and Power Supply tabs.
# SLI/Crossfire detection improved
# Translation files updates
# A sanity check has been added that verifies that the .exe tests are there, all of them. Seems an "of course", but this ensures the integroty of the download, and that the user indeed uncompress the .zip file with the folder intact.
# Help has been added on the Shader Complexity value
# The red square used to display text in the GPU:3D test has been made wider. We thus jumped to GPU:3D v0.71. Minor modification.
OCCT 3.1.0. RC1
Changelog :
* Fixed a bug that still caused the "error on core -1" message on a few systems
I'm having an issue with OCCT not displaying voltages properly on my i7 920/EVGA X58 Micro-ATX setup. It doesn't display correct voltages for Vcore or any of the PSU volatages.
I'm assuming this is a compatibility issue, since I'm running Windows 7 64-bit, but haven't yet had any luck searching for a solution. Wondering if it could be related to the DirectX9 issue mentioned in post #258?
I figure this has been covered elsewhere, but danged if I can find it.
In the OCCT setting you can set which software you want to displaying voltages properly:
Built-in,Everest,MM 5,SpeedFan 4.xx and SysTool 1.0.
Best are Everest(enable in Preferences/External Application) and set in OCCT what you want to display.
Btw,latest OCCT:
http://www.ocbase.com/OpenBeta/OCCTPT3.1.0.zip
Thank you, stasio! Worked like a charm (I knew I was making it too difficult ;) )
Did i mention how much i <3 oCCt? :P
REBUILD!
A little thread necro here, but I have run into a problem with OCCT 3.1.0 and my Gulftown processor. It seems that the program doesn't read the temps on the hex core i7 procs correctly. It will only show 2 temp boxes active, with the other 2 grayed out. And the numbers it's posting are totally bogus, showing around 27 C max. And they don't follow processor loading either. The program itself seem to load all 6 ocres well and also will handles hyperthreading fine too, but the temp monitoring is FUBAR.
Do you plan to update this fine benchmarking tool you have made? I sincerely hope so, since it has been working so well for me until now. I've been using this as my loading and recording program when testing heatsinks, but the broken temp readings kind of messes that up with my new Gulftown.
Have you tried changing the sensor setting to "use alternate" ?Quote:
Originally Posted by muddocktor
No I haven't. Can it use Real temp as the alternate? Because I know that Real Temp works with Gulftown. The only choices I see for different software are Everest, which I don't have and won't pay for, Speedfan, which I have found to give me problems recently, MBM which is older than crap and Systool v.1.0, which I've never messed with before.
OCCT 4.0.0 Beta 2
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b02.zip
OCCT v4 is under heavy, heavy work. It will soon reach the alpha stage, and is a major release.
It will bring notably :
* New interface written in C# 2.0
* Real-time graphs
* Tests handling improved, options simplified
* Alerts (Min/max) will be configurable per sensor, and not only for the CPU temp
* Fan monitoring
Tests themselves will be next on the line of modifications, mainly :
* Port GPU:3D to DirectX10 or 11
* Redo the GPU:Mem test i'm not happy with
* Update CPU:Linpack
http://i5.aijaa.com/b/00599/7748875.png
Propagation of my betas here is still very quick :DQuote:
Originally Posted by stasio
just to mention that this is a very early unstable beta, and you *will* encounter bugs with it, and some features are still missing (updating the tests, for instance, the translations, automatic "built-in" loading... etc).
if you don't flame me for all the bugs, feel free to test it :)
cant wait for this new version.. best stability testing app ever !!!
Thank you soo much :)
I love OCCT, but sensors and temps aren't read correctly on new boards and I had to stop using it :(Quote:
Originally Posted by Tetedeiench
I can't wait, OCCT 2.0.1 is my favorite for older platforms, in combination with 3.1.4 of course :up:
Every update of OCCT improves the monitoring/CPU detection logic, so it should be better with OCCT v4.Quote:
Originally Posted by BeepBeep2
As if it wasn't always better with versions that aren't stabilized or released yet ;)
As i said to stasio, those are early betas and reflect have gone over a year or so of development, despite the looks, it is a very major release. i do suspect that the list of betas will be long this time...
not sure if this is included, and if not i have a request:
i love the charts and data acquisition, but there was no way to use it unless i turn on a test. so can we have a monitoring mode which logs all the numbers but without stressing any component?
OCCT 4.0.0 Beta 3
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b03.zip
OCCT 4.0.0 Beta 4
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b04.zip
is there any improvements on temp monitoring for multi processor systems?, IIRC, the version I was using on my quad quad (probably mid 3, late2..can't remember which one) would only monitor one set of cores
OCCT 4.0.0 Beta 5
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b05.zip
OCCT PT 4.0.0.b05 OUT !
Changelog (in english as people are copy/pasting it from here) :
Graphs are now in a separate window
The graph window is resizeable. if it is in float mode, it is maximizable also.
You will now be asked to include comments in your bug report if you find an error
Linpack doesn't crash in automatic mode
Linpack libraries updated
The CPU time taken for updating the graphs is related to the graph size, be warned !
And a huge load of bugs.
Enjoy !
Source
OCCT 4.0.0 Beta 6
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b06.zip
* GraphTheme file created : please customize it and send it to me... i do hope i'll receive at least some themes...
* Font size is now linked to the window size for monitoring. Up to some extent, of course (i don't want REALLY big fonts displayed).
* Linpack updated - works on AMD CPUs now
* Test statuses revamped - please do careful review of all tests
* Tests are now stored within the exe instead of the bin folder. This will avoid the security warning on Windows XP
* Donations are now possible directly from the main interface, and a popup asks for donations, only at the first launch
OCCT 4.0.0 Beta 7
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b07.zip
Does not crash anymore on some computers (a problem with the video card detection)
The file graphtheme.csv is available in the release
OCCT 4.0.0 Beta 8
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b08.zip
Removed graphic card name detection as it seemed to cause trouble on some computers
Fixed a bug where CPU:OCCT didn't load all the cores. It works fine now.
Improved the help text in the main form. Not fully done though.
Removed the unused file linecolor.csv
hmm Beta 6 through 8 seems to not work for me...OCCT just crashes. :(
Same problem here..till Beta 5 it works great!Quote:
Originally Posted by emoners
JP.
OCCT 4.0.0 Beta 9
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b09.zip
Most of the font are now internal. It isn't true yet for the monitoring form and the graph form. This was left "as is" as the priority bug was important for me. Will be completed on b10. Only important if your computer doesn't have verdana installed.
Priority is now properly set for both main app and cpu:occt test (ldlc4 : rejoice !)
OCCT doesn't crash anymore when Windows's performance counters are not available
HT detection algorithm improved - results ?
cpu:occt now only checks for memory once, instead of twice (should be more than enough)
Known bugs :
plugin configuration like aida not saved. Couldn't fix that in time, sorry.
thanks stasio for the update! :up: beta 9 doesn't crash anymore on loading BUT CPU usage is set to always 0%
OCCT 4.0.0 Beta 10
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b10.exe
First version of the installer. Supports DirectX update and Framework .net 2.0 auto setup. Try it out !
First version of the localized UI (french only). If the OS is in FR, french will be auto loaded.
UI Optimization. Much faster when changing tabs, for instance.
Graphs generated at the end of a test are now complete. Its folder opens up as well (once per session)
New splash screen with progress information (well, a string saying what it is currently doing). ~tmp001.tmp gone.
Known bugs : still the annoying config loss on aida. Could not debug it yet.
OCCT 4.0.0 Beta 11
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b11.exe
Fixed a critical bug where OCCT crashed if you had two sensors sharing the same name.
OCCT 4.0.0 Beta 12
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b12.exe
Second idle period now properly handled
The monitoring form size does not get too low when going below the taskbar
Monitoring style and position is now handled directly by buttons
Aida64 settings (and others) when auto launched now properly stored
Monitoring tables and graph should not overlap, and should be a bit better looking
A lot of small bugfixes
Voltages are all wrong with my P5E motherboard (X38), shows 12V as being 8V, etc
HWMonitor Pro seems to have the same problem where Aida64 doesn't.
Attachment 117592
OCCT 4.0.0 Beta 14
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b14.zip
Lots of bugfixes
SplashScreen now correctly gives focus to the main window
Built-in plugin settings properly stored
Font size detection improved on monitoring window
Fixed minimum size for monitoring window
OCCT 4.0.0 Beta 15
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b15.zip
The horizontal scrollbar doesn't appear in the monitoring options anymore
Minimize to tray function fixed
the options are now correctly reenabled when a test is either done or cancelled
OCCT, my fav oc software been using it for a while. Great proggy guys. I have 3.1 installed, gonna check out the new 4.0 beta u guys realeased.
OCCT 4.0.0 Beta 16
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.b16.zip
OCCT properly handles sensors sharing identical names
OCCT won't crash when trying to delete temps files (occured sometimes)
OCCT 4.0.0 RC1
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.RC1.exe
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.RC1.zip
New monitoring engine with sandybridge support - try it out
Options now properly re-enables when exiting a test
Monitoring is now on the right-hand side by default
Graph name ending with 0 fixed (e.g. core #0 )
Removed the zip button from now (wanting to improve that part with mail)
minor bugfixes
OCCT 4.0.0 RC2
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.RC2.exe
http://www.ocbase.com/OpenBeta/OCCTPT4.0.0.RC2.zip
Monitoring window position should now be properly saved
Monitoring window won't be set to left when opening/closing the options now
The CPU frequency is updated every second in the main GUI
OCCT 4.0.0 Final
http://www.ocbase.com/download/OCCTPT4.0.0.exe
http://www.ocbase.com/download/OCCTPT4.0.0.zip
Changelog (Since 3.1.0) :
MAIN
Brand new interface with real-time graphs !
Infinite mode is now used as default
In automatic mode, the IDLE periods are fully customizables
GPU:Memtest isn't available in this release (It is scheduled for complete revamp soon)
Settings simplified
Screenshot button (PNG format)
CPU:OCCT
No limit to the number of cores supported
CPU:LINPACK
Updated to support the newest Intel instructions
GPU:3D
Waiting also for complete revamp (already started - will be DirectX10 based (will run on a vanilla seven and vista). I'm studying DirectX11 (waiting for a card that supports it in fact)
MONITORING
Huge update to the monitoring and system information engine (supports Sandy Bridge and Bulldozer)
Fully customizable real-time graphs (look in OCCT's settings)
Minimum and maximum alert values can be set for every sensor !
INSTALLER
Will install .net framework 2.0 if not available
Updates DirectX9 if not up-to-date
TRANSLATIONS
New engine for translating OCCT - XML Based
Older translations had to be dropped - sorry
Instructions on how to translate OCCT will come soon...
I haven't tried it yet, but Great Work anyway!!!!!!!!!!!!!!
omfg thanks for 4.00 FINAL !!!!
"Voltages are all wrong with my P5E motherboard (X38), shows 12V as being 8V, etc"
same here 12V as 9.14v hehe...
OCCT 4.1.0 Beta 1
http://www.ocbase.com/OpenBeta/OCCTPT4.1.0.b01.zip
First early release of GPU:3D DirectX10
Complete rewrite, faster algorithm, much better error checking (should be).
Error check mode is restricted, FOR NOW, to 512x512 windowed
While you can specify a refresh rate, DX10 doesn't really allow me to use it - will be disabled later
Monitoring options will come later
GPu/3D tab still requires DX9 to be installed to be enabled (i didn't implement DX10 detection algorithm yet).
OCCT 4.1.0 Beta 2
http://www.ocbase.com/OpenBeta/OCCTPT4.1.0.b02.zip
GPU:3D DX10 updated - does not crashes on AMD GPUs when detecting errors
Monitoring implemented
Fully integrated with the GUI
Added polish translation