[FAQ]Cause: Failed to avio_open (error=-13)  

[FAQ]Cause: Failed to avio_open (error=-13)

 

This error can occur as a false alarm, if Avast software is running. When the error appears, press Allow App, and the error disappears and oCam will continue working any problem.

 

If the pop-up window asking wheter to allow app does not appear

Click the + ALLOW APP button in Menu -> Settings -> Blocked and Allowed Apps and select oCam to add it.

If oCam is added to the list of allowed apps, you will be able to record without any problem.

 

or, you can turn off Ransomware Shield off instead as follows.

Either way should be fine.



Additional tips

[HOWTO]Setting up oCam - Record - Game Tab

Learn about the Game tab settings in the Recording category when you click Tools-Options in the Ocam Menu.


FPS View

- Check whether to display FPS in the upper left corner of the game while in the game recording mode, and it is checked by default.

 

FPS Calculation-Interval (milliseconds)

- Displays the FPS in the game in the set millisecond time unit. FPS is the number of frames in the game drawn per second, and 1000 milliseconds is 1 second, so if a value less than 1000 milliseconds is entered, the predicted FPS value is calculated and output.

In rounding mode, the FPS calculated per second is calculated internally in decimal units. It sets whether to round, round, or round the value in decimal units.

FPS Limit

- In game recording mode, the game's FPS is limited to the specified FPS value.

If the CPU cycle is selected in mode, the CPU will be used continuously to accurately limit the FPS. If the CPU is yielded, the CPU will wait without using the CPU to limit the FPS.

CPU cycle consumption can be limited almost exactly as the FPS entered by the user, and yielding to the CPU is not limited as accurately as the FPS entered by the user. It is.

FPS limit only when recording is limited only while the recording is started by pressing the record button.


Back to top