Using oCam at work or school? A license is required, and it removes all ads, including this window. See the paid version →
The ability to move the recording area while recording with oCam is very useful when you want to flexibly capture a specific part of the screen in real time. Below is a detailed explanation of how to move the recording area during recording.
To change the recording area while recording is in progress, you can use the border of the recording area. Specifically, even after recording has started in oCam, you can click and drag the border of the recording area window with the mouse to move the recording area to the desired position in real time. This feature can be used simply with mouse control and is intuitive to use without any separate shortcut keys or complicated settings.
For example, when recording gameplay, if a specific part of the screen moves or changes, such as a character's position or a certain UI element, you can drag the border to adjust the recording area in real time and capture the scene you want without missing it. This method is especially useful when recording dynamic content, helping the user respond quickly and continue tracking the necessary screen area.
When moving the recording area, you need to click and drag the border accurately. If you move it too quickly, it may shift to an unintended position, so it is best to control it smoothly and precisely. By using this feature, you can perform more flexible and efficient recording with oCam.
When installing or running oCam, you may see an error message like the one below:
"Access violation at address XXXXX in module 'oCamXXXX.exe'. Write of address 00401000"
This error usually occurs when an anti-cheat program such as GameGuard is running. GameGuard uses system resources exclusively to protect the game, and this can interfere with the installation or execution of oCam. To resolve this issue, follow the steps below:
1. Completely close the game that is currently running. When the game closes, GameGuard will also close.
2. To make sure both the game and GameGuard have fully closed, open Task Manager (Ctrl + Shift + Esc) and check whether any related processes, such as GameGuard processes, are still running. If any remain, end those processes manually.
3. After GameGuard has closed, try installing or running oCam again.
By following the steps above, you can resolve the conflict caused by GameGuard and install or run oCam normally. If the problem continues, restart your computer and try installing oCam again without launching the game.