As of late, many users have been reporting recording issues. I believe future recording issues are now caused by the LTC process.
From my little understanding, the LTC process is basically the encoder/capture process which runs side by side with the Plays client. That means the Plays client really has nothing to do with the recording process other than telling the process to start recording the game/application.
Now here's the real problem, the LTC process cannot be easily modified like the Plays client. So I (personally) do not have a way to resolve any recording issues caused by the LTC process.
These LTC process issues vary from computer to computer, I cannot pinpoint if it is a hardware issue or a software related issue.
If you are trying to assist others (or looking into it yourself), create logs and look into 'orbital.log' file. Search for the string 'LTCInterface.js' and see if there are any error messages on that same line. If there is, then it is a LTC process error. Most of these errors are very generic or lacking information.
Some examples of LTC issues/errors:
debug: [LTCInterface.js::Object.get] Communication channel with LTC has not been established. Ignoring call to LTCInterface.<...>
Best of luck folks. Whenever I have a huge time off span, I will create an experimental branch replacing this LTC process with different methods of recording. But as of now, some people will just have to coinflip and see if they can record with Plays or not.
As of late, many users have been reporting recording issues. I believe future recording issues are now caused by the LTC process.
From my little understanding, the LTC process is basically the encoder/capture process which runs side by side with the Plays client. That means the Plays client really has nothing to do with the recording process other than telling the process to start recording the game/application.
Now here's the real problem, the LTC process cannot be easily modified like the Plays client. So I (personally) do not have a way to resolve any recording issues caused by the LTC process.
These LTC process issues vary from computer to computer, I cannot pinpoint if it is a hardware issue or a software related issue.
If you are trying to assist others (or looking into it yourself), create logs and look into 'orbital.log' file. Search for the string 'LTCInterface.js' and see if there are any error messages on that same line. If there is, then it is a LTC process error. Most of these errors are very generic or lacking information.
Some examples of LTC issues/errors:
debug: [LTCInterface.js::Object.get] Communication channel with LTC has not been established. Ignoring call to LTCInterface.<...>error: [LTCInterface.js::_ltcNode2.default.on.code] Recording error code: 40002Best of luck folks. Whenever I have a huge time off span, I will create an experimental branch replacing this LTC process with different methods of recording. But as of now, some people will just have to coinflip and see if they can record with Plays or not.