Occt: what is it and what is it for?

Today we are going to talk about a very simple and quite useful program. Unlike other softwares that we have been seeing these weeks, this program does not focus on a single topic, but it is very easy to use. It was created by the OCBASE group and the application we are talking about is OCCT .

Index of contents

What is OCCT ?

In the right column we have natively a set of information from different computer components.

The bad part is that we will not be able to edit which pieces will make up this first panel. Not surprisingly, we can switch between three different panel views (Components, Graphics and Table), each having different characteristics.

It should be noted that we can edit some of the values ​​shown in this trio of screens. It is quite simple, so we will start by talking about it.

Monitoring tools

We will have three main screens between which to exchange information. The displayed data will be slightly different and in two of the cases we will be able to edit it in a simple way.

Components

The first screen of all you have already seen. In our case, this contains general CPU information, secondary graphics card information, and third, the CPU again .

Everything is pretty well presented and very visual. We have to emphasize that both the labels at the top of the graphs and the legends at their base are very explanatory.

However, as we have already indicated at the beginning, we have no way to change the projected information. Maybe it is a mistake of ours when interacting with the program, but it does not seem the case.

For example, the secondary graphics card is not very relevant information (in case you wonder, it is used to run PhysX) . Also, we have three CPU data at the top (temperature, voltage and consumption) and the frequency at the bottom.

It is a waste of space and it seems to us a mistake not to allow the user to edit it. We think that the information about GTX 660 on the main screen should be a problem when detecting the components of the equipment, but not many users have similar builds.

Graphics

The graphics display is similar, but a little more chaotic.

Here we will see information in 4 separate groups:

• Temperature Voltage Consumption Fans

However, the values ​​you are seeing in this image are the parameters that we have chosen to make it considerably more readable.

On this screen we can edit the values ​​shown in the graphs and they will be highlighted in different colors chosen automatically. In addition, everything we see is in real time, so we can see the evolution of the components, although the time shown is quite short.

The only bad thing is that some visual bugs may appear. As you can see, some points in temperature and voltage are out of place, but it does not matter much.

Table

The last of the panels is separated into 4 different lists. If you look, they are the same ones that appear in the graphics panel and, as you can imagine, it is used to edit the parameters that appear in the graphics.

• In the first column you will see the checks to know which lines are activated. The second indicates the name of the component or sensor The third the name that this parameter will have on the graph AND the following three values ​​are respectively its current value, the minimum and maximum registered (ºC, W, RPM…)

Here you will see a different tab, although the fields do not vary.

To know first hand the values ​​that the CPU , the graph or any other compatible component are taking, we advise you to use this data panel. It is much easier to see and analyze and shows you the data discreetly.

Benchmarking at OCCT

The benchmarks section is something that also takes its space. It's nicely compressed in one of the corners of the main screen, but it will have a fair amount of options.

When OCCT places us in the 'Test Schedule' box, it refers to the time we will be running the program. The three options we have are:

• Endless execution until the process is canceled Test with a limited time Test with a limited time and pauses

The first two tests are very self-explanatory, but the third perhaps not so much.

Pauses refers to the time we will take before and after taking the test. If we put 5-minute tests with 1-minute breaks, the first and last minute the component will rest and the 3 intermediate ones will perform the benchmark.

As well as data, when starting the tests a window will appear urging us to collaborate by donating something to OCCT . It is completely voluntary and if you are not interested you can close the window after 10 seconds of waiting.

Afterwards, they will show us the results indicating if we have had any failure and, below, the configuration that we have selected for the benchmark.

Configuration and benchmarks

Regarding benchmarks, everything important is in the bottom box.

Here we will have the 4 tests available and the different options that we can choose. Of the 4 benchmarks 2 are for the CPU , 1 is for the GPU and the last one is for the power supply.

Most sections are in automatic or in the upper configuration, but we can easily edit it. In the words of the same developers, the best test to detect errors in the CPU is:

• CPU: OCCT Big data set Automatic number of threads Automatic instruction set 1 hour test

According to them, with this we can detect instabilities in the processor, memory and motherboard. They mention that if there are errors they will surely appear in the first five minutes, but a 1 hour test will ensure stability.

For the test set of both the GPU and the power supply, the important thing is that we establish the native resolution of our screen. The rest we can leave in automatic or in its default values.

When starting the test, a screen like the following will open and the program will run for the estimated time.

You can cancel the test by leaving the window or pressing Esc .

Next, we leave you with a screenshot of the OCCT FAQ section. The first recommendation is the one we have shown you above, but two more are also listed.

General configuration

The configuration section of this application is especially brief. We hardly have a chance, so this section will be short.

The only things we have to edit on the main screen are the buttons that change panels and the central button 'Monitoring and System Information' . This last button is vertically in the center of the window and if we press it it hides the entire right column.

The only extra we can add to this equation are the buttons in the upper left corner and we hardly have anything to tell you about.

• The information button displays a window with company information, the license we have and a list of thanks. We are missing information such as the version of the application.The icon with a photo camera takes a screenshot of the current state of the program. The wrench (options) opens a small window and disappointment comes when we can only change two values: the language and the critical temperature. This second option is important, since it limits the tests. If we cross this temperature in any component, the active benchmark ends instantly.

As you see, almost no type of freedom.

Final Words on OCCT

If you want to perform a quick benchmark or just want to test the power of your team, OCCT is your program. However, if you are looking for something more serious where to get data, parameters and more, you will have two options: either go to other software or buy the advanced version of OCCT .

For our part, we believe that this is all we can teach you about this program. Now tell us, what do you think of the OCCT interface? What option would you miss using this software? Share your ideas in the comment box.

OCBASE font