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

Triggernometry Kills Audio / Discord Audio #18

Open
Huffman17 opened this issue Dec 22, 2019 · 3 comments
Open

Triggernometry Kills Audio / Discord Audio #18

Huffman17 opened this issue Dec 22, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@Huffman17
Copy link

As of 2 patches ago, triggernometry will cause audio to basically die, game performance runs poorly and requires a client reset, even discord will need to reassign the default audio devices. I have both Triggernometry and Triggernometry discord bot and have tried with the bot disabled.

@paissaheavyindustries
Copy link
Owner

Game patches, Trig patches, and/or ACT patches? Trig hasn't had any sound related changes in quite some time, but ACT did have some.

I would recommend trying without Trig, and then trying to roll back your ACT version to something earlier.

@Huffman17
Copy link
Author

I have it only happens when using triggernometry. I was running TEA yesterday and others have the same issue and stopped using trig

@mizeryschild
Copy link

I am also having this problem. I had to do a clean install of ACT and all of my plugins the other day, and ever since then the triggers coming through causes the audio to die in-game, discord loses its audio (i have to disconnect and reconnect) and the performance in-game is horrible, like single-digit fps. I have to restart the client to get it to work properly. I use cactbot, triggernometry, discord triggers (which was not connected because I was using ACT solo and not with a group), overlay plugin and the ffxiv act plugin. Discord triggers is at the top of my plugins list.

@paissaheavyindustries paissaheavyindustries added the bug Something isn't working label Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants