Fractal Softworks Forum

Please login or register.

Login with username, password and session length

Author Topic: [0.9a RC10]A bug with weapon charge down  (Read 1385 times)

cjy4312

  • Ensign
  • *
  • Posts: 40
    • View Profile
[0.9a RC10]A bug with weapon charge down
« on: April 12, 2019, 11:40:00 PM »

Sorry I'm not good at English. Try use GOOGLE  TRANSLATION:

I made a weapon with:

"interruptibleBurst":true,

"chargedown">0

"burstsize"=4

if burst delay less than 0.05, "chargedown" will be "0" when I stop firing.
« Last Edit: April 12, 2019, 11:48:46 PM by cjy4312 »
Logged

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 24105
    • View Profile
Re: [0.9a RC10]A bug with weapon charge down
« Reply #1 on: April 14, 2019, 10:07:30 AM »

Thank you - confirmed the issue and fixed for the 0.9.1a release.

(Btw, you probably don't want a rate of fire much faster than .05 or so. The slowest the combat engine will go is 30 frames per second - it'll slow down after that, but still go at 30 frames per "second" internally, with each second taking longer - so a weapon that fires really fast can skip shots if the frame rate drops down. So, anything that fires at >30 shots per second is probably not a good idea.)
« Last Edit: April 14, 2019, 10:10:42 AM by Alex »
Logged

cjy4312

  • Ensign
  • *
  • Posts: 40
    • View Profile
Re: [0.9a RC10]A bug with weapon charge down
« Reply #2 on: April 14, 2019, 05:01:10 PM »

(Btw, you probably don't want a rate of fire much faster than .05 or so. The slowest the combat engine will go is 30 frames per second - it'll slow down after that, but still go at 30 frames per "second" internally, with each second taking longer - so a weapon that fires really fast can skip shots if the frame rate drops down. So, anything that fires at >30 shots per second is probably not a good idea.)
thank you, that's helpful ;)
Logged

Alex

  • Administrator
  • Admiral
  • *****
  • Posts: 24105
    • View Profile
Re: [0.9a RC10]A bug with weapon charge down
« Reply #3 on: April 15, 2019, 10:54:30 AM »

(Never mind on fixing this for .1, btw - turns out the fix caused another bug, and I don't quite have the time to really dig into it. Sorry!)
Logged