Jump to content

Carlos Sunbelter

Resident
  • Posts

    35
  • Joined

  • Last visited

Posts posted by Carlos Sunbelter

  1. With so little information it is hard to diagnose.

    1 - Check your connection - wi-fy, modem, router, ...

    2 - Check your account status on secondlife.com

    3 - Perform a clean install of your viewer or try another viewer.

    Hope this helps.

  2. Continue insistindo nos ticketes para o LL, é a forma mais correta.

    O fato de dever para um grupo não deveria impedir de logar, sua conta pode ter sido hackeada por usar algum programa que não o navegador oficial.

    Desinstale os programas estranhos que te indicaram, entre na pagina de secondlife.com e tente recuperar a sua senha.

    Busque mais informacões sobre o grupo e os donos (nomes completos) para colocar nos tickets.

    Tutoriais sobre SL, inclui griefers.

    http://wiki.secondlife.com/wiki/Video_Tutorials/pt

  3. Take a look at this thread.

    http://wiki.phoenixviewer.com/100_cpu

    There are three methods to attack the freezing problem.

    1 - Disable Threaded Optimization (nVidia Only)

    2 - Set Process Affinity

    3 - Anti-Virus

    I applied the 1 and 3.

    I noticed in the task manager that my viewers, all of them, including radegast with the 3d-tab, would get one of the 4 cores of my CPU and take it to 100%. The problem was so serious that if I opened another cpu-bound application at the same time the power consumption would skyrocket and my no-break would shut down.

    I added the cache folders to the exclusion list of the anti-virus (mine is Microsoft Security Essentials), that speed-ed up the cache operations.

    I also applied the solution 1 - To Disable the Threaded Optimization. After that the CPU consumption is leveled among all 4 cores of my CPU.

    To monitor that you can key Ctrl+Alt+Del and activate the Windows Task Manager, set it to show in CPU History, one graph per CPU. Keep an eye on the Processes tab, where you see how much cpu/memory each process uses and the Performance tab, where you see each history core graph.

    My Configuration:

    Motherboard: M3A

    CPU: AMD Phenom 9850 quad-core 2500MHZ

    Memory: 4096MB

    Graphics Card: NVidia - GeForce 8600GT

    Windows7

     

    Follows the article I mentioned above.

    ==========================================================================

    My CPU is Always at 100%

     

    nVidia Related

    NOTE: this issue is specific to Windows.

    There are situations where a CPU will go to 100% usage when a viewer is running. This appears to occur most in computer with nVidia video cards - but not only.

    Another effect that seems to happen with nVidia cards is that the viewer will freeze, seemingly at random, and for varying periods of time. Or it will lock up when you attempt to open profiles or try to search.

    There are two solutions possible.

    Disable Threaded Optimization (nVidia Only)

    • Make sure you are not logged into Phoenix or Firestorm and that it isn't running
    • Bring up the Nvidia Control Panel; under Advanced Settings there is a section called “Manage 3D Settings”.
    • To the right are two tabs, one labeled “Global Settings” and the other labeled “Program Settings”.
    • Under the Program Settings tab, you need to make a profile for Phoenix or Firestorm (which ever you are using). You will need to locate the PhoenixViewer or Firestorm application here; it will be something like: C:\Program Files\Phoenix Viewer\Phoenix.exe or C:\Program Files\Firestorm\Firestorm.exe
    • Once the profile has been created, scroll to the bottom of the list of settings you can change, and find the one titled “Threaded Optimization” and set it to OFF. Hit apply and then OK to exit. (Don't change any other settings unless you know exactly what you're doing.)

    Now try to start Phoenix or Firestorm and see if the situation has improved for you. If for any reason you wish to revert, then quit Phoenix or Firestorm and simply delete the profile - or reenable “Threaded Optimization”.

    Set Process Affinity

    Should the above option not be available to you, or should it not solve the problem, then you can try to set the process affinity to a specific CPU core:

    • Bring up Windows Task Manager with:
      • Windows XP: Ctrl-Alt-Del
      • Windows Vista: Ctrl-Shift-Esc
      • Windows 7: Ctrl-Shift-Esc
    • Click the Processes tab and select Phoenix.exe or Firestorm.exe.
    • Right click Firestorm.exe and select “Set Affinity”.
    • Select only one of the available cores, to begin with.

    You will need to experiment at this point; there is no guide as to which core will work better for you. You may also be able to select more than one.

    Also, the downside of this is that it will have to be done every time you run the viewer.

    Anti-Virus

    There is at least one anti-virus program which will scan every file placed on your computer, even if created by an authorized program. This affects Phoenix, Firestorm (and any viewer really) in that it will scan each and every texture placed in cache, slowing down performance of the viewer significantly, and keeping CPU usage high.

    If you find yourself in this situation, see if you can exclude the viewer cache folder from being scanned. Ideally, you should exclude the entire settings folder as well.

    You can determine the current location of your cache by looking at Preferences → Network & Folders → Disk Cache Location and Sound Cache Location (if this is set).

     

  4. I worked with SL libraries a while ago. This is what I know about copybots, I will only go over the information necessary to enhance protection:

    1 - They can copy any rezzed objects, including attachments of any avatar, but only the structure (prims and textures). They don't copy the contents (It may be copied by other means but I will not tell how).

    2 - The contents of objects can only be copied if they're MOD. NO MOD scripts and contents cannot be copied, including scripts.

    3 - They're very efficient to rez these objects back, but only prims. Mesh is a different story.

    4 - Mesh can be downloaded, but it loses the riggin' information. The mesh object have to be converted to the SL format and rigged again before being uploaded. That's a complicated step that involves other tools than copybots, and involves work and time, what keeps away most copyboters.

    5 - Avatar textures can be copied, as well as the shape. But only the baked textures. The original skins and clothes are not visible to the copybot libraries.

    6 - The only way to get the base textures of skins and shapes (and their UUIDs) is if a copyboter BUYs them, and then download each piece, or to get an avatar naked (piece of cake in some sims) and get the naked baked skins, but only what the avatar is wearing.

    ==============================================

    What I know is a good defense against copybots (for now):

    1 - BUILDS: Use MESH. It is hard to be uploaded again, and I think it is only used in Second Life, the other Sim worlds do not use it (as far as I know). And there are costs involved for uploading mesh. Uploading of builds is free for copybots. If you already have a build using prims, replace one critical piece for mesh. The textures UUIDs are included in the download, but for some reason all copybots I know do not download these textures with a format that preserves the resolution and transparencies and I know this capacity is present in the base code. (Will not tell how to circumvent this).

    2 - SKINS: Give your customers lots of variants on the same skin - make-up, hairs, tatoos, tones. It reduces the value of a copied skin (and for that it have to get the avatar naked). Doesn't work if the copyboter BUYS the skin tough. For your DEMOS, write DEMO all over it, with faded borders to make it difficult to remove.  Include builds using prim/mesh with scripts NOMOD (ex: jewelry) to add no-copy functionality.

    3 - CLOTHES: Same exposed for skins, but I give you one additional advice. It is hard to separate the clothes from the skin of a baked texture, specially if you use transparencies and laces over the avatar skin. Fade the borders of your clothes if it does not affects que result quality of your build. It makes them harder to separate from the skin.

    4 - SCRIPTS - Keep them NO MOD. It's the only object that is really safe with this measure. Scripts are stored in the server and the client only receives them if they're MOD.

    5 - ANIMATIONS - Can be copied, I'll not tell you how. I don't know much about animations, but from what I learned from the libraries, I believe that some parameters that are set during upload-time are lost. If you use non-standard parameters for you animation at this point, the uploaded animation may present problems.

    6 - MESH - Hard to be uploaded again, this keep away most copyboters.

    7 - TATOOS, PHYSICALS, ALPHAS and SOUNDS - whenever possible, paint DEMO on the textures, use DEMO with faded borders. To be honest, I never went deeper in the sound related code, no hints here.

    8 - ADD FUNCTIONALITY WITH SCRIPTS. Since scripts cannot be copied if they're NO MOD, the functionality you add with scripts can only be duplicated with hard work, something that goes by those lazy copyboters. Use an interface script in the root prim and use linked messages to communicate with your core scripts and place them in prims other than the root prim (notecards, animations, and textures), this way you keep these resources out of sight, got it?

    I will only answer technical questions related to protection. No how-to-copyboting stuff.

     

×
×
  • Create New...