You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running on windows 10 1809 with all the latest updates. Fresh install, when selecting an fixed region to record, then pressing the record button, Camstudio pauses, then crashes. If i press record without trying to set a selection or area( or any preset recording option ), it will record.
I tried to run as administrator, no change. Video card is an Nvidia GeForce GT 620.
Didnt see a log file, but might be looking in the wrong place. Be happy to attach it though.
The text was updated successfully, but these errors were encountered:
Update: I rebooted the machine, it still crashes on select region recording option. Oddly enough, i selected a different screen ( as i have three on this computer ) and it actually did start recording that screen. The output however was not correct. The video output was in 264 ( tried avi and mp4 ) and was just a black screen with the mouse floating around and the yellow dot(mouse highlight ). It left a trail as the mouse moved ( so anywhere the mouse was, it left a picture in place of the mouse and yellow dot ). Like permanent mouse trails.
distributorofpain
changed the title
Selecting custom regions causes crash
Selecting Fixed Region causes crash
Jun 13, 2019
@distributorofpain thanks for the bug report. Unfortunately I don't have time to work on bug fixes (help is welcome). I am planning some time in about 4 months to work on camstudio again (not promising anything).
Running on windows 10 1809 with all the latest updates. Fresh install, when selecting an fixed region to record, then pressing the record button, Camstudio pauses, then crashes. If i press record without trying to set a selection or area( or any preset recording option ), it will record.
I tried to run as administrator, no change. Video card is an Nvidia GeForce GT 620.
Didnt see a log file, but might be looking in the wrong place. Be happy to attach it though.
The text was updated successfully, but these errors were encountered: