Simply...

1. If you use flash, use it sparingly. You can use it, just not a lot.
2. I have 12 bots in one place, no lag
3. Size textures for RLC (512 x 512 or multiples there of) (paint.net is a good program for editing and free)
4. Use jpg not png where possible
5. Optimise your images (https://tinypng.com/ is one good program). It's not the size of the image (I have used really large images), it's whether or not you size them correctly and then optimise.
6. Hit fn F2 on your keyboard and keep your fps up on screen, watch what causes it to drop.

Can't think of any more right now but others will I'm sure.

Good luck and if you need help just ask.

thx yes i know now a bit better but sometimes my photos are not 512 x 512 or 1024 x 1024 - I mean no square ... i work with ps cs6 i can change the the proportions but then dont look good it becomes not shart - as long i hold the proportion auf a pic isthe quality good ... eg my texture - photo is 1024 x 762 I can use it too .. or you mean 1024 x 1024 or the half is better?
thanks so much

Hello Fabian,

I assume, your photos, you've taken have the usual proportions of photos, which are mostly in a relation of 2 to 3 if horizontal or 3 to 2 if vertical. Now let's pretend for a moment, you'd like to use any of the below shown photos, which's original measures were 1536 x 1024 for first and 1024 x 1536 for the second one.





Once you convert any of them into .. let's say ... 512 x 512, they'll for sure look somewhat distorted.

All you have to do to avoid this is do simply some maths. What I usually do is, i reduce them down to ... for example 512 x 512, like shown below.





Now make for example a Sign_01 pro happen, which you scale into the original relation of these photos, means in this case, as example the prop have a scale of 1,5 in X and 1,0 in Y parameter of scale tab ... of course reverse way for second photo.

What you get to see then are the photos as you have taken them, with no distorsion and not much further loss of quality, but they'll be most easy to load for any computer.

Good luck, divingA

Ur question doesn't make much sense. There goes in a lot more then this thinking. The real question here is load on the computer, which is the rendering. This is what affects lag on most computers other then connection.

Now to break it down, and this will be fairly technical. Adding an image, depending on type of caching will cause the image to load up into your ram. Depending on which type of cache, which in utherverse could add the image load 3 times into the ram. Therefore its best to not choose multiple methods of caching within a single property, though thats another story in its intirety. Now adding copying that same prop and same texture should not increase ram usage at all as long as the cache is the same (so a first copied prop set a new type of cache will most likely still load this twice into the ram). Now copying this same prop and this same image a second time will cause this to load no additional ram.

That said, moving your avatar or camera will have to attribute resources from your computer to calculate the new values of what your seeing. While things are in a state of ram, therefor loaded. Having 2 images of the same type on different vectors would cause cpu load. From my expierence there is very little to no use from my gpu for any of these calculaties, that said the final render of the camera is compleetly gpu controlled and henceforth also creates it accordingly.

Adding a new prop with the same image however is a story entirely different as this causes additional ram, this is prolly a leak never fixed by the devs. So in short using the same prop and same texture should not cause additional stress on ram but it will causes additional stres on fps rates and some cpu usage for the calculations.

As I don't really see anyone making places with 10000 the same props on the same spot with the same texture, you have to account for some resource use no matter what. Optimizing your images is far more benificial to prevent lag in location. Highly optimized images on any props, can easily succeeed the 5000 or 10000 props in locations. I have build many places with huge prop counts and even some of the slowest computers (7 ish years old) have been able to visit my places without a problem.

One caviat though, distance is a big factor for the rendering load, and this is also depending on the leaf static properties of props in the property your building at. Therefor not all properties are suitable to build many props at. And with many I mean 3000 or more. Building large places requires understanding and knowledge about decorating. There is many facets you need to master if you want to build really large lag free places.