Jump to content

Pentasis Adamczyk

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Pentasis Adamczyk

  • Rank
    Advanced Member
  1. I know this thread is almost 3 months old, but I too have experienced this, for a while now. I used to have no problems with SL until last november (2010), then my framerate suddenly dropped after a viewer update (using viewer 2.x). It used to be around 17 (not really high perf. but it was ok) and then it dropped to 3. Nothing changed in hardware or internet connection. Since then I doubled my internet speed and bought a better videocard, but framerate is still 3 of 4 fps with some sudden bursts to 39 (for 1 second). Ping time is ok as is packet loss. I disabled every single program in the
  2. One more thing, I am assuming all these replies get read and I am fed up with Jira's so here's another request: Make it so you can click through the chat text. Being unable to click a HUD when text is shown makes that HUD position useless.
  3. I reverted back to 2.1.1 because of many issues. At first I suspected a server problem but in the end I unequivocally determined it was a viewer problem. I opened a Jira for it (which is a bit of a mess because I thought it was a server problem at first). For now they are asking for crash-logs, but I have no energy or time left to reinstall 2.2.x again to test it and generate logs, this has taken up 2 full days as it is. So if anyone experiences the same problems as described in that Jira, please provide it with info. https://jira.secondlife.com/browse/VWR-23193
  4. This viewer is becoming more and more usable. However, regarding the detachable sidebars: I myself don't care for minimizing windows once they are detached (I fail to see the difference between a minimized titlebar and a tab on the side). What I do hope though, is that it will be possible in future to completely CLOSE a window. Meaning it won't be either minimized or a tab. Some tabs are useless and I would like to remove them from my view completely. Another thing is the sub-tabs (for example friends and groups are part of the same tab) those can still not be split apart. And as such can n
  5. I was going to post a jira for this but I might as wel post it here. To reduce the confusion and clutter this will cause in our friends list. It might perhaps be a good idea to make the entries in our friends list editable. So we can give our friends/contacts custom names (in this list) which we can remember and we do not have to search for them when they change their name. So for example, John35265 has a display name of Mr. Right. I send him a friend request and store him in my list as Jo. Now when he changes his display name to Sad Git, he will still show up in my list as Jo. (think of yo
  6. Kinda makes you wish they had given typewriter manufacturers a course in how to build computers before they introduced them. Seriously though, last time I did anything slightly "professional" in 3d was way back when I just had my Commodore Amiga. I downloaded Blender last week because the last version is finally in beta and its interface is a vast improvement over the last. I have to learn blender from the start as well, but I feel in no way threatend by this. Agreed, your business is far older, more established and better than mine, and I probably stink at creating meshes as well (I couldn'
  7. Blog ate my reply Thank you !!!!!! I have a small question: I was under the impression that one of the things that was tested was the impact on lag, right? Can you tell us a bit about that? Will mesh add to lag, if so how much or not at all?
  8. I have great emotional problems accepting this project. I won't leave SL because of it, since such "threats" are just silly. @Jack: Please answer the following question I have seriously. The Display Names project is about the freedom to express yourselves inworld -- including using the tag above your head. As people live out their Second Lives their needs for the name above their head may change -- perhaps they meet someone and fall in love, or they make a new professional affiliation or decide to roleplay. This is why an important principle behind this change is that Display Names not
  9. I like it. Good clean design. Usable. And hopefully it reflects the new way of working. I love the use of whitespace. Whitespace is good. One point of "advice" if I may? The sections on the left (like "Description" and "Environment") sort of blend into the background. They don't stand out well enough. This could be improved either by using a different font or font color, or by introducing a vertical divider, or something like that. Other than that. Great job! ok, one more remark ;-) Consider moving related and duplicate issues to the right column in a smaller font?
  10. I didn't post about double-clicks so we can talk about it here. I posted it as an example. Let's not dilute this thread any further :-)
  11. Please allow me to give an example. I see in the backlog you are also working on “VWR-20713: Double-click on land to teleport” I am taking this because it is relatively “simple” item to discuss and it involves options ;-) Personally I would rather “auto-pilot” to the spot I double-click instead of teleport. And I know of others who would like that as well. Not only that, but in emerald I sometimes double-clicked by accident and I don't like that either, so we must first define the problem perhaps like so: When a user double-clicks on ground, one of three things can happen: The user telepo
  12. @Q: Ok, so this weekend I read and viewed everything published and related by/to snowstorm over the last few weeks. My perception has changed a bit by this. I genuinly believe now you are trying to change the way you work and you want to involve us as users in the process. I also understand that this is a major change from your previous way of working and a big change like that cannot be made overnight. I hope you acknowledge that as well. Not only is this a big change for you (LL) but also for us as users. My first question to you therefor is: Do you understand that your old way of workin
  13. I agree with most you say, but 2. Go back to 1.23, They are very adament about not doing this, and I suspect this is because the code-base of vwr 2.x has some stuff that is needed in the near future and which is missing from 1.23 and which is probably not easy (if not near impossible) to integrate in 1.23 without spending huge amounts of time and money on it to rewrite it. This is also why (when you read between the lines) they are confident use of TPVs based on 1.x will decline and we will adapt to 2.x. The best course of action would be to rip the code-base and the UI-code of the viewer
  14. Please forgive me if my words sound wrong, english is just not my native language and I often have to settle for other words than I actually want to use, but: I read the backlog. It is a first step, I agree. But by no means does it radiate a sense of "confidence". It is missing a lot of input that has been given and asked for in the past, but much more important: It doesn't show us anything. Please, please, please. Tell and show us BEFORE you make a desicion and start coding. Show us how the changes in the UI will look and work so we can give you constructive input instead of having to comp
  15. Some have explained much better than I could what the problem is Q. Basically users feel ignored. They have been talking and giving feedback for years. In fact they are showing you what they want through TPVs. If you (and LL) want to take one BIG step towards gaining trust, continuity and respect I would suggest you do the following: 1) Download all TPVs and make a list of the features they have. 2) Extract all viewer related jiras. 3) Make from this a list on which everything from the above is mentioned (save the impossible ones). 4) Let users vote for each feature to prioritize the list
  • Create New...