Anonymous | Login | Signup for a new account | 19-04-25 20:08 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 | |
0002151 | SphereServer | executable - windows build | public | 26-03-13 02:00 | 27-03-13 02:56 | |
Reporter | EXTREME | |||||
Assigned To | Ben | |||||
Priority | normal | Severity | minor | Reproducibility | always | |
Status | closed | Resolution | no change required | |||
Platform | OS | Windows | OS Version | Seven 64 | ||
Product Version | 20-09-2009, 0.56b Prerelease | |||||
Target Version | Fixed in Version | |||||
Summary | 0002151: ON=@TIMER Problem | |||||
Description | I have tested a long time ago that the on=@timer is firing every second, so its was giving problems with common things. I recorded 2 videos that shows whats happening... The first one: - using function teste1 made by me, that creates an item and your char will equip it. when equipped, will broadcast 'TESTING' and give timer = 5 to item, and when on=@timer is fired, broadcasts 'TESTED', then the item is removed. with a script running in Injection, I'm measuring the real timer that sphere is using to do the '5 seconds' timer. you can see everything here: https://dl.dropbox.com/u/51370445/Untitled%202.avi [^] the second one: - using the same function (teste2 on bottom) but using timerf instead creating the item and setting timer = 5... it works FINE you can see it here: https://dl.dropbox.com/u/51370445/Untitled%204.avi [^] So, what I think is: something is broke or the on=@timer being fired only every second is very sucks. If you need more informations, just tell me. Thanks! | |||||
Steps To Reproduce | [ITEMDEF I_MEMORY_OI] ID I_MEMORY TYPE T_EQ_SCRIPT ON=@EQUIP SERV.B TESTING TIMER 5 ON=@TIMER SERV.B TESTED REMOVE [FUNCTION TESTE1] SERV.NEWITEM I_MEMORY_OI SRC.EQUIP <NEW> RETURN 1 [FUNCTION TESTE2] SYSMESSAGE TESTING TIMERF 5,SYSMESSAGE TESTED RETURN 1 Injection code: sub teste1() var d while not uo.dead() while not uo.injournal('TESTING') wait(1) wend d = 0 repeat wait(1) d = d + 1 until uo.injournal('TESTED') uo.print(str(d)) uo.deletejournal() wend endsub | |||||
Tags | No tags attached. | |||||
Nightly Version | Not Available | |||||
Experimental Flags | New_Triggers, Item_Strict_Comparison, NewPositionChecks, Script_Profiler, DamageTools | |||||
Option Flags | Command_Sysmsgs, FileCommands, NoHouseMuteSpeech, NoPrefix | |||||
Internal Build Number | ||||||
Attached Files | ||||||
![]() |
|
(0001529) xwerswoodx (reporter) 26-03-13 21:10 |
did you try? CONT.SYSMESSAGE TESTING |
(0001530) EXTREME (reporter) 27-03-13 00:38 |
Nothing will change because the problem is when the trigger is fired... :/ |
(0001531) Ben (manager) 27-03-13 02:56 |
Timers are affected by server process time... there is nothing that can be done for this. Timerf are parsed early in the cycle where as an item timer is process later causing more inconsistencies in the precision. |
![]() |
|||
Date Modified | Username | Field | Change |
26-03-13 02:00 | EXTREME | New Issue | |
26-03-13 21:10 | xwerswoodx | Note Added: 0001529 | |
27-03-13 00:38 | EXTREME | Note Added: 0001530 | |
27-03-13 02:56 | Ben | Note Added: 0001531 | |
27-03-13 02:56 | Ben | Status | new => closed |
27-03-13 02:56 | Ben | Assigned To | => Ben |
27-03-13 02:56 | Ben | Resolution | open => no change required |
Copyright © 2000 - 2010 MantisBT Group |