I keep getting this recently. Never happened before. Not sure what's triggering it but I'm almost certain it's when I use secondary fire for anything. Usually shield cells, heat sinks, discovery scanner. I'm not sure what the mining laser command is all about though, that may be related. I've never been using mining lasers or calling on them to be used. I'm not using a voice command at all when this happens to my knowledge. It locks my hardpoints out and burns through whatever is set to the secondary fire group. Any help would be much appreciated thanks.
Announcement
Collapse
No announcement yet.
Release by variable error
Collapse
X
-
could you provide a better screenshot please as it's illegibleThe Singularity profile - One profile to rule them all and at HCS we bound them
You see, TheThingIs, eventually you'll be allright.
-
it seems i cant make the resolution any higher for the upload. the original defo doesn't look that way. will just have to type out the jist here. not sure why the attachments are so low quality.
So a from top to bottom how it appears it would read like this.
orange square: mining lasers active
green: recognized: retract hardpoints
true
true
true
true
true
red square: Release by Variable {hcskb_primaryfire} not set No keys released
this repeats a few times
green: recognized: engines sevenny five %
orange: mining lasers active
hope this helps and thanks
-
-
Assigning a keyboard press to the primary fire should help on that front1) I reject your reality.... and substitute my own
2) Not to be used when upset... will void warranty
3) Stoke me a clipper i will be back for dinner
4) Never tell Gangrel to do anything... he will probably get it wrong
WARNING! Swedish wall-of-text hits you for bork-bork-bork damage!
Comment
Comment