Anonymous | Login | Signup for a new account | 2021-04-16 04:30 PDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap | Summary | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||
0008853 | opensim | [REGION] OpenSim Core | public | 2021-01-12 05:17 | 2021-01-12 08:33 | |||||
Reporter | Abaddon | |||||||||
Assigned To | ||||||||||
Priority | normal | Severity | minor | Reproducibility | always | |||||
Status | new | Resolution | open | |||||||
Platform | Any | Operating System | Any | Operating System Version | Any | |||||
Product Version | ||||||||||
Target Version | Fixed in Version | |||||||||
Summary | 0008853: This is about a previous problem with "do not try to pass touch events to root prim if it does not have them" | |||||||||
Description | Right clicking has been fixed and now it is all well, however when TPing from one region to the next one the "magic rose" right click fire up issue still happens and fires up by itself this time right after the avatar's arrival to any region without running the script, but this time there is no mouse event | |||||||||
Steps To Reproduce | Just wear the rose, fire it up once in local and then TP to any region | |||||||||
Additional Information | PS: It would be really nice, if possible, to somehow trap the mouse right click event for quite a few reasons, for example expose in local cloth derendering :) | |||||||||
Tags | No tags attached. | |||||||||
Git Revision or version number | Latest Dev 0.92 | |||||||||
Run Mode | Standalone (Multiple Regions) | |||||||||
Physics Engine | BulletSim | |||||||||
Script Engine | XEngine, YEngine | |||||||||
Environment | Unknown | |||||||||
Mono Version | None | |||||||||
Viewer | ||||||||||
Attached Files | ||||||||||
![]() |
|
(0037505) UbitUmarov (administrator) 2021-01-12 05:19 edited on: 2021-01-12 05:20 |
the magic rose issue is not really a touch issue. A issue on touch was just found checking it issue is some odd particles control thing... |
(0037506) UbitUmarov (administrator) 2021-01-12 06:10 |
looking to sl wiki kind explains the issue a particle system is reactivate as soon it comes into viewer or some prim parameter is changed "When using particle systems that have a non-zero emitter age (PSYS_SRC_MAX_AGE) setting, you may notice that the particle system may restart without any scripted trigger going off. This is due to a bug which causes the emitter to "reset" when any of the prim properties are updated or otherwise sent to the viewer. As a result, you may have to use a timer or a forced sleep and then clear the particle system once the age has expired. Debbie Trilling has posted a work-around here: http://forums-archive.secondlife.com/54/fa/260031/1.html#post1996465" [^] |
(0037507) UbitUmarov (administrator) 2021-01-12 07:59 |
added void osParticleSystem(LSL_List rules, LSL_Integer expire); void osLinkParticleSystem(LSL_Integer linknumber, LSL_List rules, LSL_Integer expire); with expire != 1 (ie false) and system maxage == 0, they do as the ll ones but if TRUE and max age is not zero, the particle system will be lazy removed from the prim after that max age time by lazy means next time the sim will try to read the particlesystem to send to anyone. this should avoid the need for any timer. note that on that "magic" script noparticles just sets maxage to 0.1. That is not correct, to remove particles you need to call llParticleSystem([]); |
(0037508) UbitUmarov (administrator) 2021-01-12 08:19 |
removed the expire argument: osParticleSystem(list rules); osLinkParticleSystem(integer linknumber, list rules); will do the lazy expire if maxage != 0 |
(0037509) UbitUmarov (administrator) 2021-01-12 08:21 |
note that until the expire, the same issue still happen. It is a particles system flaw in viewers and protocol |
(0037510) Abaddon (reporter) 2021-01-12 08:33 |
OK will do thank you, I think it is good enough for now and will stop causing trouble. It seems like some people knew this issue and were using it for that reason. It would be a really great idea if you could also somehow distinguish left from right mouse click. |
![]() |
|||
Date Modified | Username | Field | Change |
2021-01-12 05:17 | Abaddon | New Issue | |
2021-01-12 05:19 | UbitUmarov | Note Added: 0037505 | |
2021-01-12 05:20 | UbitUmarov | Note Edited: 0037505 | View Revisions |
2021-01-12 06:10 | UbitUmarov | Note Added: 0037506 | |
2021-01-12 07:59 | UbitUmarov | Note Added: 0037507 | |
2021-01-12 08:19 | UbitUmarov | Note Added: 0037508 | |
2021-01-12 08:21 | UbitUmarov | Note Added: 0037509 | |
2021-01-12 08:33 | Abaddon | Note Added: 0037510 |
Copyright © 2000 - 2012 MantisBT Group |