Posted in: Uncategorized
Posted 2011-04-06 at 22:36 by Rudd
Hi all, thought I'd let you know about what I've been working on aside from helping community mappers and messing with maps currently in the build.
Burning Sands unfortunately had alot of issues that didn't crop up during testing, however thanks to both friends and fellow gamers I've had a large number of reports identifying the problems.
Burning Sands suffered from:
[B]Memory CTDs[/B]
Why?
- Too many lightmap files
- Too many textures/texture pallets being loaded for objects
[URL="https://www.realitymod.com/forum/f354-community-maps/49073-mapper-info-static-objects-should-not-used-your-maps.html"]- Problem statics[/URL]
[B]Performance issues especially in the city[/B]
Why?
- Too may enterable buildings or high poly buildings close together
- Memory taken up in loading the map in the first place
Other bugs e.g. Combat areas in layer 64 had become messed up.
I'm confident this is all fixed and will be released with the next release, which will be done when its done. :D
[url=http://www.xfire.com/profile/trekkyaaron/screenshots/?view#112686022][img]http://screenshot.xfire.com/s/112686022-1.jpg[/img][/url]
[url=http://www.xfire.com/profile/trekkyaaron/screenshots/?view#112686046][img]http://screenshot.xfire.com/s/112686046-1.jpg[/img][/url]
She's still big and pretty despite my optimisations.
Heres a list of some the changes
Removed pavements (that was about 2000 objects, all had been lightmapped, so thats over 2000 textures not loaded, huzzah!)
Removed problem statics e.g. iraqi low apartments.
Optimised Lightmaps in both resolution and in selection of objects (was [B]55 [/B]atlases, now only 15!
Optimised terrain Lightmaps by decreasing resolution of FINAL LMs to 50% (note this achieves better quality and avoids offsetting colormaps than simply LMing on medium)
Replaced alot of enterable buildings with non-enterables/more optimised versions. This might sound bad to some people, but honestly I think spreading out the enterables will be good for both performance and gameplay. (muttrah being a prime example of this)
Removed a good number of destructable objects
created several more open spaces in the city (both for gamplay and FPS)
Removed alot of rocks (LOD issues)
Removed alot of mid east village statics
Lowered VD by 50m
These changes mean that alot more RAM is freed up during loading than before and also the FPS will be higher since theres fewer polys to render in the city, without sacrificing gameplay.
Also, for those of you who played the last public beta test - I've fixed the CTD on low terrain bug :) HUZZAH!
Gamplay changes
Asset and balance tweaks
Now all assets spawn in main base even at the start, exception is two MEC vehicles in the military base. This will prevent confusion.
AASv4 implemented
For you budding young mappers out there, remember all because it runs at 100FPS on your computer on local doesn't mean it'll behave like that on a public server. Optimisation is key!
Never use 3 objects where one will do, never use 3 kinds of objects when one kind will do.
Space out your enterables
Be selective with your lightmaps
I hope you enjoyed this humble blog, and I hope it reaffirms your belief that optimisation and fixing problems is at the fore of our minds.
Live Long and Prosper
Burning Sands unfortunately had alot of issues that didn't crop up during testing, however thanks to both friends and fellow gamers I've had a large number of reports identifying the problems.
Burning Sands suffered from:
[B]Memory CTDs[/B]
Why?
- Too many lightmap files
- Too many textures/texture pallets being loaded for objects
[URL="https://www.realitymod.com/forum/f354-community-maps/49073-mapper-info-static-objects-should-not-used-your-maps.html"]- Problem statics[/URL]
[B]Performance issues especially in the city[/B]
Why?
- Too may enterable buildings or high poly buildings close together
- Memory taken up in loading the map in the first place
Other bugs e.g. Combat areas in layer 64 had become messed up.
I'm confident this is all fixed and will be released with the next release, which will be done when its done. :D
[url=http://www.xfire.com/profile/trekkyaaron/screenshots/?view#112686022][img]http://screenshot.xfire.com/s/112686022-1.jpg[/img][/url]
[url=http://www.xfire.com/profile/trekkyaaron/screenshots/?view#112686046][img]http://screenshot.xfire.com/s/112686046-1.jpg[/img][/url]
She's still big and pretty despite my optimisations.
Heres a list of some the changes
Removed pavements (that was about 2000 objects, all had been lightmapped, so thats over 2000 textures not loaded, huzzah!)
Removed problem statics e.g. iraqi low apartments.
Optimised Lightmaps in both resolution and in selection of objects (was [B]55 [/B]atlases, now only 15!
Optimised terrain Lightmaps by decreasing resolution of FINAL LMs to 50% (note this achieves better quality and avoids offsetting colormaps than simply LMing on medium)
Replaced alot of enterable buildings with non-enterables/more optimised versions. This might sound bad to some people, but honestly I think spreading out the enterables will be good for both performance and gameplay. (muttrah being a prime example of this)
Removed a good number of destructable objects
created several more open spaces in the city (both for gamplay and FPS)
Removed alot of rocks (LOD issues)
Removed alot of mid east village statics
Lowered VD by 50m
These changes mean that alot more RAM is freed up during loading than before and also the FPS will be higher since theres fewer polys to render in the city, without sacrificing gameplay.
Also, for those of you who played the last public beta test - I've fixed the CTD on low terrain bug :) HUZZAH!
Gamplay changes
Asset and balance tweaks
Now all assets spawn in main base even at the start, exception is two MEC vehicles in the military base. This will prevent confusion.
AASv4 implemented
For you budding young mappers out there, remember all because it runs at 100FPS on your computer on local doesn't mean it'll behave like that on a public server. Optimisation is key!
Never use 3 objects where one will do, never use 3 kinds of objects when one kind will do.
Space out your enterables
Be selective with your lightmaps
I hope you enjoyed this humble blog, and I hope it reaffirms your belief that optimisation and fixing problems is at the fore of our minds.
Live Long and Prosper
Updated 2011-04-06 at 23:35 by Rudd
« Previous Entry
|
Main
-
Posted 2011-04-07 at 13:38 by Redamare -
did you just imply that crashing on load didnt crop up in testing?
cuz thats a pretty hard thing to skip.
anyway i like the map it doesnt get boringPosted 2011-04-07 at 16:47 by karambaitos -
Nice, maby I can get more that 10 FPS in the city now
Posted 2011-04-07 at 22:27 by Gozjh -
thanks rudd keep it up!
Posted 2011-04-08 at 01:49 by Absolute Killer -
First time I saw Burining Sands i thought it will be the next Kashan esert with a Muttrah city inside... Now it's playble!!!!!!!!!!!!!!
Posted 2011-04-08 at 05:21 by Nakata -
Posted 2011-04-08 at 07:23 by Dr Rank -
Posted 2011-04-08 at 19:29 by AnimalMother. -
Posted 2011-04-10 at 05:41 by echo -
Quote:
its pretty hard to get the balance right on that point, However look on google earth for a town called arar in an area called al muthana Saudi arabia, that was my first inspiration.
the sidewalks themselves are pretty good, they waste some UV space but otherwise are not heavy models. The problem is that I used them everwhere, 3000 sidewalks aren the problem, 3000 lightmap files are. The pavements also Zfought quite a bit so its not hugely bad.
Basically, the sidewalks are fine, just don't use them everywhere, or use them in places where they won't require lightmapping.Posted 2011-04-10 at 17:36 by Rudd