[Viewer crashing upon uploading an image.]

---

dd Temin wrote:

Hi,

Try opening your viewer as Administrator . (for windows users).  I saw this suggestion posted someplace recently.

It seemed to work for me...the one time i tried it.

Also...My experience has been it only does this on the first download.... After relogging ...the next and all following downloads did not do this again.

I have seen the same issue in OPEN SIM/ OS grid sometimes.

BTW..i use older sl viewer with cool view added.

I dont have or use MS skydrive.

 

---

Just so I can go on the record as saying it, that's a terrible idea. Nothing should have administrative execution permissions unless they absolutely need them. I don't trust any open source software that far, and definitely no non-commerial non-OS products. It's safe 99% of the time, but the one time source checking due diligence fails that means the application can do anything to your machine it wants to.

[Ultra Graphics Settings and Shadows]

Thanks in advance!

Operating System

MS Windows 7 Home Premium 64-bit SP1

CPU

Intel Core i5 @ 2.50GHz 114 °F

Ivy Bridge 22nm Technology

RAM

8.00 GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)

Motherboard

 

Graphics

Generic PnP Monitor (1366x768@60Hz)

NVIDIA GeForce GTX 660M

Intel® HD Graphics 4000

Hard Drives

758GB SAMSUNG SAMSUNG MZMPC064HBDR-000 (SSD)

Seagate ST750LM022 HN-M750MBB (SATA) 114 °F

 

 

 

---

Late to the party, but what has those specs? I don't know what the problem is, but those ram timings are ugly, bottlenecking vs the cpu.

[How can i adjust windows time out limit as it is affecting SL and causing me to crash?]

First, deprecated. Second, I'm ready to say this answer is probably offbase. Here's the reasons:

1. It hasn't been an issue for me until I started using the V3 viewers. I've also yet to update my drivers, going on 6 months of problem free usage until this particular issue. This more than anything leads me to believe it's new code that's the problem, not upgraded drivers.
2.The only exception I see when debugging the process using exodus, where I also see the bug in question, is kd_header_in at memory location [x], which is just some bug in the login screen, and is handled gracefully.
3. I let the failing first-chance exception go, get the unhandled exception and it fails through to llcommon.dll where it blows up. I get 0 significant errors before this.
4. If you log in with all pop-out windows (read: inventory, sim stats, etc) closed, it loads perfectly and reproducably every single time. (Read: This is a potential workaround, on a GTX 460, and a GTX 570)

I'll do some profiling later, but it looks to me like the new window code for non-docked windows (haven't tried opening the dock yet, will later) is blocking the render thread long enough to cause a timeout. This doesn't change if multi-threading is enabled or not.

Summary: try closing all windows save the chat window, which I have in the condensed mode where it's a floating window. I've been able to reliably reproduce both crashes (with windows open) and logins (when windows are closed) using this method.

ALSO. Exodus crew, there's breakpoints in them thar hills. Thanks.

[Mac OS X Snow Leopard]

My experiences playing games under OS X say otherwise. Rather blasé, defensive reply. Then again, I run bootcamp as opposed to parallels, so I suppose that probably accounts for a lot of the conflicts you have that I don't. Driver support has been unquestionably lax since they started disallowing 3rd party drivers under the Mac OSes, there's no questioning that either. I see a ton of difference in game performance between the systems I have running GTX 285s under windows and under OS X, so that's true as well.

I think you answered what you wanted me to say, as opposed to what I actually did.

[Mac OS X Snow Leopard]

Yeah, I don't bother trying to play any games on my Macs while running OS X. Even with similar hardware and the same video hardware, driver support is iffy and the performance just isn't there. As far as I'm concerned, buying a copy of Win 7 is part of the cost of owning a Mac.

[Copying WindLight settings from one viewer to another]

For mac, just look inside the app folder in the same relative path.

[Mouse sensitivity when building]

I usually don't gush, but I've had a certain mouse for awhile that was *made* for building in SL. The miracles, good tiding and hope that the navigator fails to deliver, the Razer naga delivers in spades. Variable dpi higher than you'll ever possibly want to go (I use it on my leg during plane flights @ 65% max sensitivity and a twitch moves across the entire screen) and the ability to dial it down 6 ways to sunday on the fly. On top of this, it's an 18 button mouse, with a 12 button keypad immediately available on your left thumb. I've mapped it to all the v2 build shortcuts, ctrl, shft and alt; I only have to use the keyboard to enter names, and the sensitivity is beyond belief.

Couple it with a low grid setting as recommended previously and it'll be the best mouse you've ever used.

http://store.razerzone.com/store/razerusa/en_US/pd/productID.169418900/parentCategoryID.35208800/categoryId.37466100

[Lag...]

For wired connections: Disconnect all wires concerning your connection, wait 30 seconds then plug them back in again, including the modem and transformer. Wires should snugly fit into ports.

Please note doing this is an incredibly bad idea under normal circumstances and is a last ditch measure. This will default any and all security settings configured within your router, and will open your wireless connectivity to the public in most cases if it is part of said router.

[Does anyone know anything about this graphic card?]

If you tell me the model number, I can tell you everything you ever wanted to know about that laptop/pc. Presario doesn't narrow it down enough unfortunately, there's a few hundred models with that family name.

Sans that, this should tell you if you run it and look under video adapters. http://www.gtopala.com/

Hardware manager *might* tell you, but only if you have the proper drivers installed, or look under the hardware id and crossreference that by device (http://www.pcidatabase.com/)

[How can I get my mac to process quicker?]

The solution I'd recommend is keeping your current macbook, and buying a new pc laptop to play games on. They cost less, and have hardware that's more tailored to the activity. The current line of Apple laptops all have respectable hardware, but obsolete graphic cards. The hardware the 9600M GT is based on is over 2 years old. A modern card would be a GTX 200 series or Mobility Radeon 48/900 series card.

You can get the same specs as a macbook, in a more game-ready form with a better GPU, 4gb of DDR3 and the ability to go up to 8 for 745 USD. If your current macbook works well for you for everything but games, I see no reason to discard it when it serves a purpose.

I know for some it isn't an option, but I'll lay it out side by side for your perusal, right tool for the job sort of thing. Neither is a very 'futureproof' option, but they're both good examples of what is currently available.

http://store.apple.com/us/configure/MC207LL/A?mco=MTM3NDkxOTY

http://www.xoticpc.com/sager-np2098-custom-laptop-built-compal-khlb2-p-2581.html?wconfigure=yes

[How can I get my mac to process quicker?]

Since the suggestions relating to optimizing SL have already been covered thoroughly, I'll tackle the operating system slant. OS X can be a bit quarrelsome with how it treats processes and the apparent lack of transparency, but there are a few things you can do to increase overall system performance, outside of SL:

1. Take a cue from windows users and terminate processes you don't need (but in this case, programs, not system processes):
   • Open Terminal.app, type "ps -A > process.txt" (no quotes). This creates a text file with the list of currently running processes and saves it to your home directory. This step is not entirely necessary, but it makes it easy to sit back and think about what you do and don't need.
   • Find system processes here: http://triviaware.com/macprocess/all
   • From there, you can use the Activity Monitor (utilities -> activity monitor) to terminate any processes that you don't actually need. Please note that most on that list are required for OSX to run. Lots of overhead, but it gives you a base to work from so you can terminate programs that are unnecessary. With any operating system, it's a great idea to become familiar with the processes that routinely run on your system.
   • I've found that asking OSX to do a lot of multitasking is asking for trouble, so when you're running SL, keep it to one or two other applications max. It doesn't matter how well OSX manages memory when your processor has a thread backup.
2. At the risk of being pedantic, I have to say it another way to make sure it comes across: Close programs you aren't using.
   • iTunes, iMail, iCal, iLife, Can Opener, Little Snitch, etc are great applications, but they should all be closed when you're not actually using them. Doing so can make everything else run faster.
3. Follow the instructions found here: http://www.thexlab.com/faqs/performance.html . Some of the key points to pay attention to are:
   • Turning off visual effects
   • Repair permissions
   • Keep your hard drive free of clutter. (Read: Move data that isn't necessary to run the operating system and your applications to a separate drive, dvds, pen drive, tape, whatever you're comfortable with. OSX wants your yummy hard disk space for paging.)
   • Update Prebinding (occasionally)
   • Defragment your hard drives at least monthly (yes, drives *do* fragment under OS X/HFS+)
   • Check your Processor Performance Settings (power management)
   • Keep Fonts to a Minimum (loads of system fonts bog down your system). I recommend using Extensis Suitcase Fusion (2) for your font management. Since OSX keeps an active font registry, you don't have to worry about restarting applications to use fonts.
   • This document also contains some excellent tips on gauging and measuring your system's performance and troubleshooting issues, but they're largely superfluous to this discussion.
4. Disable drive indexing by adding your hard drive to spotlight's privacy list
   • To do this, just open spotlight's preferences, select the privacy tab, then drag the drive to the list.
   • Here's a great (and short) article on using and customizing spotlight: http://www.macworld.com/article/132755/2008/04/spotlight1.html
   • I don't recommend disabling spotlight altogether because there are a lot of things going on in the background that are not immediately apparent (for instance, mail search).
   • If you absolutely must do so, here's how (and a number of reasons not to): http://www.macosxhints.com/article.php?story=20071102215912892

The best thing you can do, however, is get more ram. Simon is absolutely right, you're going to need all the ram and processor power you can get to compensate for the lackluster graphics hardware.