Difference between revisions of "LlAddCameraView"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
:It would have huge performance impacts, to render just one arbitrary view would double cpu, gpu & network requirements; it does not scale. -- [[User:Strife Onizuka|Strife Onizuka]] 04:18, 26 July 2007 (PDT) | :It would have huge performance impacts, to render just one arbitrary view would double cpu, gpu & network requirements; it does not scale. -- [[User:Strife Onizuka|Strife Onizuka]] 04:18, 26 July 2007 (PDT) | ||
:On that I agree. For the client side it could be an option to have it set from preferences (Use mirrors on/off). On the server side it can be optimised a lot. Not scalable? Maybe. (Nynia) | ::On that I agree. For the client side it could be an option to have it set from preferences (Use mirrors on/off). On the server side it can be optimised a lot. Not scalable? Maybe. (Nynia) | ||
Revision as of 00:52, 5 September 2007
This function creates a new camera view inworld or outworld, depending on the function arguments. Outworld - create a window in which you can look the other way, or keep an eye on your home. Inworld - create a square object which will be alligned and attached to another object. This square works like a tv-set, but the image is controlled by the newly created camera. This way it's possible to implement mirrors and reflecting surfaces.
Please comment on this idea. I think it can be implemented fully client side, so performance is not influenced much.
- It would have huge performance impacts, to render just one arbitrary view would double cpu, gpu & network requirements; it does not scale. -- Strife Onizuka 04:18, 26 July 2007 (PDT)
- On that I agree. For the client side it could be an option to have it set from preferences (Use mirrors on/off). On the server side it can be optimised a lot. Not scalable? Maybe. (Nynia)