Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HLAE should have a proper log file. #331

Closed
Shadoweee77 opened this issue May 25, 2020 · 5 comments
Closed

HLAE should have a proper log file. #331

Shadoweee77 opened this issue May 25, 2020 · 5 comments
Labels
enhancement New feature or request

Comments

@Shadoweee77
Copy link

HLAE should get a proper log file for trouble shooting. At every star up it should log stuff like:

  1. Version of HLAE and Game
  2. Devices connected as they can sometimes cause trouble
  3. Method of recording ( FFMPEG, streams, etc )
  4. Amount and type of errors.
  5. Other stuff like - Was mirv_pgl used etc.
@Shadoweee77 Shadoweee77 added the enhancement New feature or request label May 25, 2020
@dtugend dtugend added this to the dunno milestone May 26, 2020
@dtugend dtugend removed this from the dunno milestone Jun 12, 2020
@cherinyy
Copy link

cherinyy commented Jul 5, 2020

I urgently need this log. I don’t know why CS:GO will not respond as soon as I start recording the stream.
csgo

When I removed FFmpeg, it seemed to work fine.
So it seems to be a problem with FFmpeg, but I don’t know what caused the problem.
ffmpeg

I completely wrote the cfg file according to the reference parameters on the Wiki.
cfg

@dtugend
Copy link
Member

dtugend commented Jul 5, 2020

It can be caused by some Anti-Virus software that blocks or alters stdin / stdout (standard input/output) between HLAE and ffmpeg.exe.

@dtugend
Copy link
Member

dtugend commented Jul 14, 2020

Not a fan of this feature to be honest.
If we do it, it must be off by default and completely optional.

@dtugend dtugend added this to the v3.0 milestone Sep 25, 2020
@dtugend dtugend modified the milestones: v3.0, v3.1 Sep 18, 2021
@dtugend dtugend removed this from the v3.1 milestone Dec 18, 2021
@dtugend dtugend added this to the v3 milestone Oct 9, 2022
@dtugend
Copy link
Member

dtugend commented Feb 19, 2023

@dtugend dtugend removed this from the v3 milestone May 13, 2024
@dtugend
Copy link
Member

dtugend commented May 19, 2024

Hi. Thank you for your suggestion. The implementation of this feature in a reasonable time-frame is currently not realistic for me. After considering that together with issue #896 I am closing this request as not planned for now, since it would block other things I would like to still get done before that. Sorry for the copy pasta.

@dtugend dtugend closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants