| Anonymous | Login | Signup for a new account | 21-06-26 10:28 CEST | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |
| 0002048 | SphereServer | new feature request | public | 05-11-11 09:37 | 22-03-12 02:48 | |
| Reporter | xantier | |||||
| Assigned To | ShiryuX | |||||
| Priority | normal | Severity | feature | Reproducibility | have not tried | |
| Status | closed | Resolution | not fixable | |||
| Platform | OS | OS Version | ||||
| Product Version | ||||||
| Target Version | Fixed in Version | |||||
| Summary | 0002048: TicksPerSec for sphere.ini | |||||
| Description | in order to make OSI accurate calculations, i need to change internal clock, ticks per second. it is 4 ticks (0.25 ms per tick) per second at OSI. 10 at sphereserver. so there is no way to have accurate results especially at spell cast and freeze time. i thought TIMERD function is based on that tick thing (TIMERD=1, 1 tick = 1/(tickpersec) seconds). so this feature may bring useful things. | |||||
| Tags | No tags attached. | |||||
| Nightly Version | Not Available | |||||
| Experimental Flags | None | |||||
| Option Flags | None | |||||
| Internal Build Number | ||||||
| Attached Files | ||||||
Notes |
|
|
(0001300) ShiryuX (developer) 22-03-12 02:48 |
No way. I can't let anyone modify the internal clock of sphere, specially when it's used in many sensitive functions. Saves, cleanup, networking, etc. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 05-11-11 09:37 | xantier | New Issue | |
| 22-03-12 02:48 | ShiryuX | Note Added: 0001300 | |
| 22-03-12 02:48 | ShiryuX | Status | new => closed |
| 22-03-12 02:48 | ShiryuX | Assigned To | => ShiryuX |
| 22-03-12 02:48 | ShiryuX | Resolution | open => not fixable |
| Copyright © 2000 - 2010 MantisBT Group |