If you call a function that initializes CUDA from an app written in java when you install a recently released version of the NVIDIA driver (378.49) (other versions may also be included) (cuInit, Stack cookie instrumentation code detected a stack-based buffer overrun.) There is a bug that crashes.
This is not a bug in Ocam and applies to all apps that use CUDA.
Please install the latest version of 378.66 or higher.
About
This is a blog to share a variety of tips and news associated with OhSoft.
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.