New useful Control Bits + Client Controls

Well, using a custom client at least. But still awesome! By using 5 existing control bits that didn't have a real purpose in the sims.
http://nexii.ordoimperialis.com/
They are mapped onto R, Q, 1, 2 and 3. As CONTROL_PITCH_POS, CONTROL_PITCH_NEG, CONTROL_FAST_AT, CONTROL_FAST_LEFT and CONTROL_FAST_UP respectively. Named according to the internal names. There is also a menu which can press them handily.

But I'd like to get some early LSL Scripter oriented input towards some of my bigger ideas at work. Specifically my 'Script Collaboration' idea for Client Controls.

What I am doing is trying to implement much more powerful controls for LSL Scripts of what they can do on the users' viewer. Im aiming for purposeful short and sweet ideas to add as components.

The Data transport layer is via the Dale Glass Protocol. Implementation of the Manager is underway right now, so I thought it might be a good idea to start getting attention.

Script Collaboration Ideas so far, ranked in order of approximate time it would take to implement:
- Targets and other basic visual effects (imagine the Beacon)
- Picker, In World or HUD
- Avatars In Sim
- Custom Floater
- Dynamic Textures

I think this list is really too short, what do you think?

ooooooooo! The names for mini map mouse over are very nice.

Very nice job on the viewer. Only quibble I have is I wish alternate viewers used separate caches, folders and settings instead of sharing the official folders.

Oh, I could actually. But I wasn't sure if it was such a good to do really per user experience. I personally like how people can instantly get into it with their previous settings kinda. Maybe if I could find a way to check for an existing secondlife installation and copy the settings over?

Yep I guess that is a valid point. Anyways what am I to want more when you are doing all of the good work for everyone

Thank you for putting the hours into this Nexii and I hope everyone gives it a try. Guarantee they will love what has been done with this one.

hmmmm what to do with new controls (brain starts clicking) this may be fun.

It was more in line intended for weapons, vehicles and other complex-control devices that were previously strangled by the limitation of imagination.

well, since you're wish-listing, I'd really like to see a way to do some inworld object mouseover effects..dunno if this is the type of suggestion you are looking for but hey..you asked lol

Well, that IS the kind of stuff I am looking for, a huge wish list of more mundane things we should have been allowed to do for a really long time. I would then prune this list for purposeful and useful implementations, essentially you have the power of the users' PC at your disposal for processing even! I was thinking more along the lines of utilizing new ways of presenting and using visual information.

For example the 'Target' idea, what I had in mind was pretty much those huge towering red beacons, or perhaps providing other kinds of HUDEffects from the client at disposal to render on a screen of a user.

Another example is perhaps the long awaited method of knowing where a user clicked, much like llDetectedTouchST and the other new functions, but for quering those touches that are not just part of the prim or linked object that was actually clicked, but other objects, even owned by other users.

Imagine having a particle script targetting any object that was clicked by a user.

Or an RTS game where you assess if a Landscape Sculpty was clicked for a Tank to move to...(This is actually the whole point of my introdcuction of the Picker, but its obviously not limited to this, im not ignorant, I want other developers to take advantage)



But yeah, you can be pretty creative in ideas. I'm open to anything and then judge or even innovate on the final list.

Those keys aren't useful for people who keep the chat bar up.

Well, true. But you can change it around if you want, anyone can! It is pretty straightforward, just open up the keys.ini under Vertical Life v1.4/app_settings/

If you could give me a better idea of where to place them as a default configuration that would be great.

The current keyset is meant to be for the current WASD controls. I'm not sure where to place them for for the arrow controls though.

The best place I could think of, is Home End Delete and Page Up/Down. But these are not always to be placed in the same familiar place between keyboards, especially laptops.

I might have 6 more possible control bits available to use as well upcoming...which is making it even trickier...