Jump to content

Nalates Urriah

Advisor
  • Posts

    8,850
  • Joined

  • Last visited

Everything posted by Nalates Urriah

  1. I'm not overly knowledgable about mesh but... If I understand correctly, the bounding box for mesh is the physics layer. Make your bounding box as the Collada physics shape.
  2. You do not need to file a new JIRA. HOWEVER, do check that the one you filed is still open. If it is not, update the information and reopen it. Publish the JIRA number in the forum with a good title so people with the same problem can add to the JIRA comments. Publish the number in the Merchant's/Commerce group in-world. Do that every couple of days for a week or so. You want everyone to know about it, so if they have the same problem they can add to the comments. Also on the JIRA click WATCH. It makes no, or little, difference if you click VOTE. Make sure to add new viewer and server version numbers. Make sure you have a step-by-step for how to create the problem. If the Lindens cannot repeat it, they can't fix it.
  3. I disagree with Lindal that the connection is the bottleneck. Once an area has rezzed and your download rate drops the connection has little affect on FPS. You can watch the process in Viewer Stats (Ctrl-Shift-1). How the two systems share your internet connection may have an affect on rez speed, but not much more. Look through Graphics Tweaking for Second Life. You may find some information that will help you improve your viewers' performance. When you ask a tech question include information about your computer and viewer. Get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. This let's us see your driver versions and other details of your system. Don't be surprised that similar systems have different performance stats. The SL viewers are affected by numerious things in Windows. Even minor settings changes can affect performance. Having one viewer with 128m draw distance verse 192m draw distance can make a difference. When trying to compare viewers Inara and I often fly up to 2,000m to see what the FPS will peak at. That gives a good test that is mostly independent of the stuff around you. Even the direction an avatar is facing can have a significant affect on FPS. At high altitude direction is less of an issue. You can use three free programs to check your systems to see what they are doing; CPU-Z, GPU-Z, and System Explorer. GPU-Z will show the graphics load placed on the video card GPU. System Explorer will show you what each CPU core is doing and whether your system is paging data to the hard disk, page faults.
  4. You haven't given us much to go on. When you ask a tech question include information about your computer and viewer. If the viewer will at least show the login screen, get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. Saying you are using the 'latest' SL viewer doesn't mean much to anyone. The versions change pretty fast. Use the actual version and build number. from HELP->ABOUT... Since you are crashing after login it is probably a graphics thing. Before logging in go into preferences and in the graphics settings set LOW. See if that lets you into SL without a crash. If so, it is a graphics issue. Since you did not post your video driver version we can't tell if that is a likely problem.
  5. Get GPU-Z (free program) and make sure the video card is being used. Laptops tend to turn the video card off to save power. Often one has to create a special setup in the video card's control panel to get it running with SL. ATI has not put as much effort into OpenGL as nVidia has. So, shadows are a bit of problem with Radeon cards. You are going to have to experiement with graphics settings to find out what works. Try turning varous Hardware features on and off via the Hardware button in Preferences->Graphics. You may want to suggest the Development Viewer. It has the newest render code. It may work better. Since you have updated the driver that should be ok. But, search this forum to see if you can find posts on the video card model and version number. You may want to try some third party viewers. Niran's Viewer has lots of enhancements for photographers. The user interface is non-standard (see Nirans). Exodus is another good viewer. Firestorm is a very good general purpose power users viewer. They have lots of support people. Ask in their group and see what they have to say about the video card. The render engine made by the Lab is changing right now. It SHOULD work better. When you hit a problem document it well and file a JIRA bug report.
  6. You should be able to select the item in inventory and delete it. But, you may want to wait. To report it, file a JIRA report. You will need all the information you can get about the item. File it as a Security Issue. You can right click the item in inventory and select properties. Read the instructions for how to file a JIRA before you try to file it.
  7. If you want something fixed you need to file a JIRA Bug report. Here we provide user-to-user help. Few Lindens read the Answers sections and I am certain none of the programmers that can actually fix something read Anwers. They proably do watch the stats and trends. Read the instructions in the JIRA for filing a bug report. The bugs that get fixed are the ones that have a step-by-step proceedure for reproducing the problem. For user-to-user help and a possible fix we need to know more. When you ask a tech question include information about your computer and viewer. Get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. You crashing on taking a photo is an older issue. The Lab has fixed it but in some cases the problem was not from the viewer but from the video card driver. So, nVidia or ATI were the ones that had to fix it. Not all games and certainly not SL use the same feature set in the drivers. So, we may see problems that appear in several games or only a few. It get confusing. If the Lab's people can reproduce the problem they can chase the problem down and fix it or explain to the video card peeps what's wrong. That is the fastest way to a fix in a video crad driver. For you, try updating your video drviers.
  8. There are some great articles by Penny Patton on camera position, scale, and proportion in SL. Camera Position Tips is where I embellished a bit on Panny's tips. Penny's original article is here: Second Life Camera Position Tips. A related article by Penny is here: A Matter of Perspective. I have my spin on the problem and link to several articles in: #SL Crusade for Good Looks. The settings controls are in Debug Settings: CameraOffsetRearView and FocusOffsetRearView. The CameraOff... positions the camera. The FocusOff... sets where the camera is looking. These values change the camera position and look-at-point for the default view, what you see when you press ESC. The view that your viewer uses is controlled by a bottom(?) menu/button, VIEW. You can select front, rear, or side. There are Debug Settings to control each view. If you read the articles, you'll find there is a bit of move in SL to get more realistically proportioned avatars in SL. If one uses the basic viewer settings then avatars tend to be 6-foot tall and taller. There are lots of advantages to having realistically sized avatars. It even helps the giant avatars look bigger for those that like giants. Note: A Clean Install is a bit drastic for resetting your settings. I think it is much quicker and safer to rename or delete the viewer's settings.xml file and let the viewer create a new file using all the viewer defaults, which are based on your graphics card. The file is in C:\Users\[win_login_id]\AppData\Roaming\SecondLife\user_settings\settings-[viewer_name_version].xml
  9. I'm not sure where some of the suggestions came from unless you have been posting in other threads... You convinenced there is not a connection problem on your end. Now you need to check that there is not a problem on the SL server side. All the detail steps for testing a connection are here: Troubleshoot Your #SL Connection. The TL;DR check is to look in the Viewer Stats for Physics FPS and TIme Dilation. They should be 45 and 1.0. Below 30 and 0.8 and you can expect some slowing. A TRACERT will show if it is something between you and SL that is a problem. To really know what the problem might be there is a load of stuff to check. So, when you ask a tech question include information about your computer and viewer. Get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. We can then tell if it is a driver issue or a hardware problem. You can read through Graphics Tweaking for Second Life to see what settings may be a problem for you. You can get GPU-Z (free) to see if your video card is carrying part of the load. You can get SpeedFans (free) to see if the CPU or GPU is overheating and throttling back. System Explorer (free) will show you if load is spreading out between the 4 cores. It will also show you if the system is page faulting, writing memory to disk, which can happen if memory is being tied up by something else that is running. Beyond these things, and these too actually, I'm guessing. I hope these clues get you started toward finding a solution.
  10. I describe the fixes for the same problem a bit differently and explain how to avoid the problem. If the Firestorm instuction don't resolve it check: Second Life Wearing All Inventory
  11. There are no recent changes that move avatar baking to the server side. That is a future improvment the Lab annouced it is working on. Depending on the region and the SIM it is in, HTTP on or off may be faster. HTTP will generally be faster and more reliable as it uses TCP with error correction. With HTTP off the viewer falls back to UDP, which has no error correction. Because it is so region dependent one cannot say on or off is better. It depends... The CPU's in an HD Graphics system must calulate most of the 3D models and handle texture decompression. With a graphics card both of those tasks can be handed off to the GPU. Without a GPU the CPU's are going to bottleneck. For more info on graphics tweaking see: Graphics Tweaking for Second Life
  12. I don't know an easy way. Blender has Alt-S scaling that is a big help. It scales in the direction of the vertex's normal. See Alt-S Scaling in Blender 2.6
  13. I suggest you write a step-by-step discription of how to experience the problem. Provide a location. Provide server versions. File it as a JIRA.
  14. Check out my Second Life Mesh Clothes Blender 2.6 Setup 2012 Tutorial. I hope it clears up some of the confusion around how Blender is used and upgraded as well as used for clothes making. Using an Archive install is a huge advanatage and will get you around many problems.
  15. Nalates Urriah

    .

    You aren't doing anything wrong. This link is to an older post but it will show you what others were getting: How Fast is Your Viewer? - Second Life. When you ask a tech question include information about your computer and viewer. Get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. If you want to get into tweaking your computer for performance there is lots to learn. Read: Graphics Tweaking for Second Life. Also, check out: How to improve Viewer performance - Second Life and Understanding the Maximum Bandwidth Option in the Second Life™ Viewer. If you want to reset all your settings to the default, rename or delete the settings.xml file. It is in: C:\Users\[win_login_id]\AppData\Roaming\SecondLife\user_settings\ You will get different performance with different viewers. Also different brands of computers will perform differently on different hardware. People with hardware nearly identical to mine get faster and slower performance. Performance can change from version to version of the same viewer.
  16. This is likely a Windows/nVidia setting problem. The viewer will render a square square and a sphere round regardless of what size or ratio your viewer windows is. If the Windows aspect is not matched to the physical monitor you'll get the distortion you are seeing. Look in the monitor's specs to find the native screen resolution and frequency. Set your Windows settings to match those. If the Windows panel is not detecting the same numbers, you'll need to get a driver for the screen... actually its more of a settings file than a driver. The driver/file is usually on an included CD. If not it can be downloaded from the manufacture.
  17. Also search in-world for FREE. Visit places like Free Dove. These freebie places will have new user 30 day offers. You can get some expensive hair for free. Also visit hair stores and look around. Many have a free to new users offers in their store. Ask people you meet in-world. Everyone has their favorite hair shops. The can give you Land Marks to the stores... click, poof, and you are there. You can also mix and match from Inventory's Library folder. There are a number of avatars in the Library.
  18. Use Viewer Stats to get an idea of whether it is you, the region, or connection (Ctrl-Shift-1). Your connection quality will be shown by Ping and Lost Packets. 250ms and 2%, respectively, are an arbitrary upper limit. I notice degradation when I see those values exceeded. FPS is the indicator for how you computer and video card are preferming. Physics and SIM FPS are locked together now. They give you an idea of how the sim running the region is preferming. Time Dilation tells you if the region is overloading trying to process scripts. PFPS should be 45 for full speed. Between 35 and 45 you probably won't notice much change. Time Dilation below 0.8 means things in the region will show some slowing.
  19. With Firestom try a clean install. Clean Install. Firestorm 4.1.1 is currently the most stable viewer being used with SL. When you ask a tech question include information about your computer and viewer. If the viewer will at least show the login screen, get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. Without knowing which version of Viewer 2 you are coming from we are futher restricted. Since the viewer is logging in and running for a bit, clear the cache too. That is a last resort type of step and one should seldom clear the cache. Navigate to the cache. Windows Vista/7: C:\Users\<win_login_id>\AppData\Local\SecondLife Mac: ~/Library/Caches/SecondLife Linux: ? Delete the contents of the SecondLife folder. All of it. Try resetting the viewer settings to their default values. Navigate to the user settings for the viewer. Win7/Vista: C:\Users\<win_login_id>\AppData\Roaming\SecondLife\user_settings Mac OSX: Users/Username/Library/Application Support/SecondLife/ Find the file: settings.xml and rename or delete it. If the viewer will show the login screen, open Preferences (Ctrl-P) and set the Preferences->Graphics to LOW. Then try logging in. Check to see if you have the latest video driver. From time to time the latest driver is not the best and one must roll back one or two versions for things to work. Search the forum for your video card and driver version to see if others are having a similar problem. Before tearing your computer apart, try installing the latest Development Viewer. This is a pre-beta version of Linden Lab’s viewer. SL Dev Viewer DL. I am assuming you have already manually cleared the cache. If you still crash, look in the Second Life log file: C:\Users\[win login_ID]\AppData\Roaming\SecondLife\logs. Start from the end of the file and work your way toward the beginning. You are looking for errors. That text may give you a clue to the problem.
  20. Be sure to watch the Events Section of this forum. Contact the people promoting those events and ask how you can participate. The Destination Guide has an Events section too. You can find names to run down the promotors of those events. Look through Designing SL. Lots of fairs are announced there. The blog iHeart SL is another good source of events. You can use in-world search to find hunts, just search on hunts. Contact those promotors. You didn't tell us what 'type of product' you wanted to promote, so we can't be specific.
  21. You are going to have to model and weight it to work as you want. There are limits to how well that works. Nothing in SL will do cloth or consider collions of the mesh clothes we wear. The deformer is going to help with getting clothes to fit. It is not going to help with collisions or movement. So, what you see now is still what we are going to have after the Deformer is working. In Blender you will find Cloth Simulation has a collision process. There is no such process in SL. In the Creartors Continent Improvement Informal User Group we are talking about how to add cloth sim to SL.
  22. It is not uncommon to have problems getting into ADITI. The Last Location is often the problem. Some times it lets you in and if the Last Location is down, it sends you to a different region. Other times it just doesn't let you in. Try entering a region name. Morris, PathTest1, PathTest2, PathTest3, or PathTest4. If you make it in, check the map and get some other region names.
  23. The best information you can provide for tech troubleshooting comes from the info from the viewer's Help-About... Paste that into your post with your next question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. There are free programs to test your computer's memory. There seems to be a rash of these types of crashes. There are not many and the Lindens say stats have not shown an up tic in the crash stats. But, some of us have noticed more requests for help with the issue here in the forum. The problem with memory tests is one must make a CD or floppy to boot from and run the test from a special minimal operating system. Some computer shops will run a memory test for you in the hope of being able to sell you new memory. There is a bit of a conflict of interest, so trust is an issue. Fortunately memory for older computers is ridiculously cheap. Google your computer model to see what memory type it uses and possibly how to install/upgrade memory. Installing upgrades or replacements of memory is simple enough and pretty much fool proof. It simply plus in. The complexity is in knowing whilch memory sticks to buy and Google will help you there. With laptops the challenge is getting to the memory. Some laptops have to be disassembled to get to the memory. Others only have to have a simple cover removed, in which case the upgrade is easy and little experience is needed. Some people with the problem have tested their computers and believe they are OK. So, don't be overly alarmed that it is a hardware problem. However, do check that possibility. For nVidia you should be on the 301.42 version or 296.10 (I think I got the last one right) version of the video driver. If you have the viewer's Automatic Update turned on, you may want to try installing one version older. If that works, turn off the auto update and run the older version unstil the next viewer release.
  24. Visit the Phoenix-Firestorm Wiki and look for their troubleshooting section. They have a page on the problem.
  25. Ayesha, your tag line " If I know where I am I don't know what I'm doing there." is apt. There is nothing in my post to suggest there are different versions of the server code or Havok running in Magnum. With 3 packages running in RC and one in main, they have lots to be tracking and watching. Having different versions within a single release channel would complicate things even further. I doubt that happened. Do you have any evidence for your insinuation that the Lab is lying? That you are staggered is revealing but not surprising... I mispoke saying Le Tigre. Oskar edited and updated his OP sometime Thursday, I think. Magnum has PF and Le Tigre got Advanced Creative Tools (ACT). Deploys for the week of 2012-07-16 - Second Life RC Magnum This channel will again have the Pathfinding project. Second Life RC LeTigre This is the Creator Tools project with the LSL calls enabled. The Magnum channel will be running PF for the second week now. We are told that Le Tigre was planned to run PF. But a last minute change, which post roll showed up in Delpoys, put the Advanced Creative Tools (ACT) on the Le Tigre channel. I'm unclear on how grangular the Lindens ability to enable/disable LSL functions and other features are. But, the main channel and Le Tigre's ACT can be reconfigured without rerolls. If I remember correctly, the main and Le Tigre channels have the same version but only in Le Tigre are the tools enabled and ONLY in some Le Tigre regions.
×
×
  • Create New...