Option not to move the camera...

when selecting "Edit" from the pie menu.

I usually spend a few seconds before I edit an object finding exactly the right angle and range for me to make the change(s) I'm planning on making (partially because I keep forgetting about this annoying "feature", but mostly because I was looking at the object in the first place to figure out what needed changing.)

Then I right-click and edit, and viola, the camera's in a different room of the house, staring at the floor/wall/ceiling. It does, of course, do this even if I don't bother to set up a viewing angle first.

I realize some people may actually like the way it works now, which I why I suggest making it an option somewhere. Just please let me turn it off!

heh good idea grim, we keep harassing them about it and it will get in. i think that there is a call in at the moment that allows you to lock the camera in place, but i will have to get on and check. jake do you remember the call?

LSL defines an undocumented call named llTakeCamera, but it currently is unimplemented. It would let a script take control of the camera, which probably isn't what Grim is asking for.

Grim, try using ctrl-3 to open the edit tool. You can move your camera into the desired position, hit ctrl-3, and then click on the object. This should put you in edit mode without moving your camera.

heh if we could take control of the camera, we could definately lock it in place so it becomes a highly valuable scripted tool, hooray!!!!!

llTakeCamera would be great! I second/third the movement!

Here is a bug: If an object takes all movement controls and does not pass them on to the AV, using the movement calls will not move the AV. That is not the bug. The bug is that no matter what you do with the camera, as soon as you press one of those movement keys (that is not being passed on to the AV) the camera *still* resets to default position as if you were moving. Very annoying.

There is a way around that Grim...don't use the pie menu while building, ever, it's evil (unless you want to rate or pay someone while building...but that's different).

A lot of people seem to not know that the top 5 icons in the object window can be accessed by hitting CTL 1 - 5.

So for example...say you hit ALT to get your mag glass up, then start viewing all around your house, say you go up two floors from where you are actually standing, and you are eyeballing an object. If you want to edit that object, you might be tempted to right click and go to focus...that will make your camera reset.

Nay nay!

Instead, just hit CTL 3. This will bring the object window up in edit mode and not reset your camera. Then just click your object and do your thing. To switch objects, don't lose focus...just click on the other object.

Goes for creating too. Hit CTL 4 and you'll be ready to click 'n create without resetting the camera or using that slow-me-down pie menu.

Using this technique, I often work on objects so far away and for so long that I forget where I'm actually standing. The only time you should ever have to move when building is if your object is out of range. I teach that at all my building 101s...I recommend it be added to the standard 101 content for all instructors.

So...
Fast Focus/Move/Edit...CTL 3 (I never, ever use the Focus icon, or the Move icon, since being in edit mode focuses and allows you to move the object).

Fast Create...CTL 4, your magic wand will be up and you'll be ready to create. When you do create the object, you'll be focused on it. Just hit CTL 3 while focused and bam you're ready to edit, no camera blues.

I believe this simple little trick makes you a better builder...you maintain consistent views over long periods of time, speeds you up, and factors out a lot of frustration.

Good luck.

Bump this, because two threads are better than one

And I'll chim in yet again about a lack of any way to leave edit mode without your camera snapping back to over-the-shoulder. I hate that.

If I want my camera to reset, I'll hit friggin' ESC, right?

What concerns me is that there has never been any feedback from the Lindens whatsoever on this issue (apparently) over its whole history since launch.

Given the number of people affected, that strikes me as .... odd.

I'd volunteer to fix this for them for free, if it were to do any good. That seems unlikely though.

Calling all Lindens, calling all Lindens!!!

Beep beep!!!

Agreed. This issue has been around for over a year.

I don't know much about the code to SL, but algorithmatically, it would seem to be just a flag variable that is used to skip over a bit of code in a few places. I really can't see why such a highly-in-demand change has been ignored completely for so long.