Analysis of ns2_tram
<div class="IPBDescription">Did you compare your map before ?</div>Nowadays I'm testing and developing my map ns2_thedron. I just wanted to see details about ns2_tram map and it is really awesome. This map may be made to overload the ns2 engine by UWE. And that explains why FPS is low and how this Max's Engine is awesome ! I obtained those numbers by filtering lights, objects only.
There are 1742 lights and this is really really awesome. If you are a 3D designer you should know what more then 5 lights are while rendering in 3D Studio Max or Lightwave, Maya etc. Numbers has also meaning when you compare with yours.
This engine also renders in realtime so this is really perfect. In one of a previous version of tram i see 400-500 lights while commanding which means it renders those 500 lights in realtime. And again I just want to say wooww !
On the otherhand 1742 lights are really big it should be reduced by UWE I think. Think your house how many lights do you have? We have 15 lights. And think factories, so number 1742 is really big here for a map imao.
ns2_tram by UWE (a playable fully detailed map including readyroom)
------------------------------------------------------------------------------------
7684 KB size
116090 total elements
1742 lights
6916 objects
847 entities
ns2_thedron by me (a playable less detailed version including readyroom)
------------------------------------------------------------------------------------
380 KB size (probably will be 1000-2000 when detailed)
7222 total elements
38 lights (I just focused on this and gonna be about 100-200 lights)
205 elements
424 objects
My map is also playable, there are readyroom, 1 base, 3 hives, 9 res nodes. There are light and dark rooms.
Am I do something wrong while selecting those objects? And what about your map stats?
and again WOOOWW ! :) Congrats UWE for the great engine again !
There are 1742 lights and this is really really awesome. If you are a 3D designer you should know what more then 5 lights are while rendering in 3D Studio Max or Lightwave, Maya etc. Numbers has also meaning when you compare with yours.
This engine also renders in realtime so this is really perfect. In one of a previous version of tram i see 400-500 lights while commanding which means it renders those 500 lights in realtime. And again I just want to say wooww !
On the otherhand 1742 lights are really big it should be reduced by UWE I think. Think your house how many lights do you have? We have 15 lights. And think factories, so number 1742 is really big here for a map imao.
ns2_tram by UWE (a playable fully detailed map including readyroom)
------------------------------------------------------------------------------------
7684 KB size
116090 total elements
1742 lights
6916 objects
847 entities
ns2_thedron by me (a playable less detailed version including readyroom)
------------------------------------------------------------------------------------
380 KB size (probably will be 1000-2000 when detailed)
7222 total elements
38 lights (I just focused on this and gonna be about 100-200 lights)
205 elements
424 objects
My map is also playable, there are readyroom, 1 base, 3 hives, 9 res nodes. There are light and dark rooms.
Am I do something wrong while selecting those objects? And what about your map stats?
and again WOOOWW ! :) Congrats UWE for the great engine again !
Comments
Really nice looking, big houses also have probably more than 15 lights :)
I'm already at around 1200 Lights and I still have to do a few corridors, a tech- and a node-room.
I found removing all prop and light shadows then going back and adding shadows at key points on lights and props boosted my frame-rate up substantially.
Until there is a final value of the cost between shadow casting and non-shadow casting lights it is kinda hard to tell in the grand scope of things what these factors will cost overall. And do the numbers include ambient lighting as well?
I have mostly ambient lights and lights at the corners of hallways which looks to the both sides of hall ways.
I didnt do anyting about disabling cast shadows but i will gonna do later.
I think ns2_tram is a limit for us. Normaly map should have less then 500 lights and should be about 2000-4000 KB for a good performance imao..
Radious/range of the light only matters greatly if its going to be a source of any shadows where there are a lot of objects in its path to cast from.
Your map may be great but run poorly, which would let the UWE team have a good use case to optimize for.
Indeed, bouncing lights is faked here though with the use of more lights in an area. Spark doesn't bounce light in realtime does it? Source's precompiled lightmaps are stilll a huge advantage to bouncing lights, less cost to make things look good at the loss of real-time lighting. Spark has is right though if it can do all of the things Source does, but the realtime!