So after playing with RACs I've found a bug, and I'd say its kind of a big bug.
The bug is related to the 'Jam Bar' and Overheating.
When you repeatedly tap the weapon group button that the RACs are in, for some reason even though I have not let them fired the bar continuously goes up, not firing a single round and proceeds to Jam the weapon. You can see this in Source 1.
This continues to happen even after the weapon has became unjammed.
The next part of this is that apparently I think the heat from firing the weapon, despite not actually firing, is still there and is not visible on the HUD. This means that the heat will make you over heat and will kill you, despite never doing anything to even cause your heat to increase, even from outside interference. This happened to me in Source 2.
I think to stop this bug while the weapon Jam bar is going up you need to press that weapon group button again and it will stop increasing, but the fact that still exists is shocking,
Source 1: https://i.gyazo.com/...9b70582f105.png
Source 2: https://i.gyazo.com/...6692901162d.png


3 replies to this topic
#1
Posted 19 July 2017 - 10:06 AM
#2
Posted 19 July 2017 - 10:39 AM
yes this is a feature, the Jam bar will go up wail starting to spin up the weapon,
but why? if it didnt people would just run Macros and Avoid the Spin up and have no ill side effects,
this stops that from happening, as you cant just keep the gun spinning and about to fire at all times,
but why? if it didnt people would just run Macros and Avoid the Spin up and have no ill side effects,
this stops that from happening, as you cant just keep the gun spinning and about to fire at all times,
#3
Posted 19 July 2017 - 10:42 AM
Can understand part 1 even though the reasoning is stupid, part 2 though.... what the hell? That needs some serious fixing.
#4
Posted 19 July 2017 - 11:01 AM
Part 1 is working as designed (probably) and is indeed to prevent people from keeping it constantly spinning and effectively avoiding the spin-up time. Especially if you also use macros to not even need to manually handle the job.
Part 2 is definitely a bug of some sort and needs to be dealt with ASAP.
Part 2 is definitely a bug of some sort and needs to be dealt with ASAP.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users