Jump to content
View in the app

A better way to browse. Learn more.

Obsidian Forum Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

Edit: I mean "inaccurate" in the title ;(

 

There is already a post in this forum https://forums.obsidian.net/topic/98617-bug-attack-frequency-on-guns-capped-at-36-sec/

in which the author pointed out that reload time of firearms capped at about 3 seconds.
 
I did some tests in game.
Actually the animation is always played with the same speed. For longer reload time, certain scene will be repeated several times.
The animation is alwasys played smoothly, that means a reload can't end unless certain part of the animation is over.
 
Example: Lets see how a pistol is reloaded in game
 
Fire!
--------------------------------------
Left hand into pocket and grab a club(or sth I don't know its Name), put it into pistol.       (Part A)
Left hand into pocket and grab a club(or sth I don't know its Name), put it into pistol and prepare to do sth to your pistol   (Part B)
Put the club into your pistol then draw it back, repeat several times(I don't know how to discribe it better in english, sorry).  (Part C)
Pull the bolt.   (Part D)
---------------------------------------------------
Fire again.
 
 
Part A and Part D must be played, takes about 3 seconds, that is the shortest real reload time.
Part B and Part C are repeatedly played in loop for several times according to theoretical reload time(displayed in tooltip).
The end of Part D is also the end of reload.
Part is the smallest unit, unable to be split further.
 
So there are 3 cases.
1. A -> D.   shortest reload time, about 3 seconds.
2. A -> B -> C -> B -> C -> ... -> B -> D
3. A -> B -> C -> B -> C -> ... -> B -> C -> D
 
That means the real reload time is not very accurate (frame-level ), it is only roughly sorted(about 1 sec difference between levels, since part B,C lasts about 1 second) according to the theoretical reload time.
Therefore the theoretical reload time displayed in tooltip is quite misleading and it is hard to manage "-recovery" or "+speed" bonuses so that they won't be wasted.
Sadly, it seems not to be very easy to fix.
 
 
Tell me if I'm wrong.

Edited by zczczc1680

Yeah, they give us so little info on how things are supposed to work. Part of me thinks it's because if they tell us how it's supposed to work, they'd actually have to code it to work.

  • 5 weeks later...

Greetings,

 

Thank you for the post! We have this problem logged currently for our devs to look for a fix with animation exploits.

 

Regards,

 

-Caleb

I like big bugs and I cannot lie...

Create an account or sign in to comment

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.