test content
Logo
What is the Arc Client?
Install Arc
Options
VO issue with temporal ambassador and jem'hadar rifle firing bug
lazarus51166
Member Posts: 646 Arc User
Reproduced the following bugs several times on different characters:
VO for garak in temporal ambassador is using the old rugan skyl audio
There appears to be an issue where if you use the secondary firing mode for jem'hadar rifles and try to use the primary firing mode before the barrage finishes completely it'll bug out the option to fire the primary firing mode until you switch to your secondary weapon and back or holster the rifle and take it out again. I had it happen several times today and over the last few days and have been able to deliberately reproduce it several times by doing the following:
1. highlight a target to fire at
2. fire 2 or 3 primary bolt attacks at said enemy
3. fire secondary barrage attack
4. fire the primary bolt attack right before the barrage finishes and it the primary firing option just stops responding to being clicked until using the solution I mentioned
I tested this on both a jem'hadar and a klingon and both had the same issue so i'm assuming it has to be a bug
VO for garak in temporal ambassador is using the old rugan skyl audio
There appears to be an issue where if you use the secondary firing mode for jem'hadar rifles and try to use the primary firing mode before the barrage finishes completely it'll bug out the option to fire the primary firing mode until you switch to your secondary weapon and back or holster the rifle and take it out again. I had it happen several times today and over the last few days and have been able to deliberately reproduce it several times by doing the following:
1. highlight a target to fire at
2. fire 2 or 3 primary bolt attacks at said enemy
3. fire secondary barrage attack
4. fire the primary bolt attack right before the barrage finishes and it the primary firing option just stops responding to being clicked until using the solution I mentioned
I tested this on both a jem'hadar and a klingon and both had the same issue so i'm assuming it has to be a bug
0