[Mapper Info] Static Objects that should not be used in your maps - Page 2

Rabbit · 2011-07-23, 17:10

I feel like this needs updated, as I'm having crashes suspects are textures , sounds or other data ( non-text ) files but I am not using any of these objects.

Rudd · 2011-07-23, 17:25

you need to confirm its ur objects causing ur crashes, rename the staticobjects.con to something else, or load only the staticobjects to test

staticobjects that are not listed here can still cause crashes, but only usually if you have used too many statics, too many high poly statics or too many different families of statics that load separate texture pallets.

I don't recall any new statics being added to the build that could be causing trouble, so I suggest you bump your map's thread and we'll see if we can help you

Rhino · 2011-07-28, 11:50

Added tent_v2 to the list

Quote:

Originally Posted by [R-DEV]Rhino

tent_v2
objects\staticobjects\pr\military\tent_v2
objects\staticobjects\pr\military\tent_v2_closed

AFsoccer · 2012-04-12, 23:17

~~Added "industry\ind_objects\chimney_01" to the OP.~~

Fixed bug, so object is useable now.

Rhino · 2013-04-25, 04:39

Updated OP with the following info and new oil barrels:

Quote:

Oildrums #2
objects\staticobjects\pr\new_misc\oildrum_white
objects\staticobjects\pr\new_misc\oildrum_yellow

These two oildrums have now been replaced by very similar looking ones but in a lot more colours, including the two colours above. The only real difference is the new oil barrels have much more optimized lightmaps and as such, should be used over these ones.

These new oil barrels can be found in: \objects\staticobjects\pr\common\props\oil_barrels \
Download for the new oil barrels: http://realitymodfiles.com/rhino/sta...5_25-04-13.rar
These files are the property of Project Reality and are only for use in maps that are planned to be used in Project Reality.

Also I've removed townhouse_1 from the OP as this static has had its main critical issues fixed in v1.0 but is still far from perfect so would avoid using it if you can.

Quote:

townhouse_1
\objects\staticobjects\pr\chinese\townhouse_1\

This static has many issues and also has some issues which can lead to exploitation, this static is planned to be fixed up at some point so if you do plan on using it, keep in mind that you will need to re-lightmap it at some point.

Rabbit · 2013-11-21, 16:31

Is there a problem with "shack_v1"? I keep find that static in all my fps drop areas.

Rhino · 2013-11-21, 18:53

Quote:

Originally Posted by Rabbit

Is there a problem with "shack_v1"? I keep find that static in all my fps drop areas.

There are no known issues with it afaik and can't see any massive problems with it looking at it in BFMeshView. Biggest issue I can see is the Lightmap sizes for it are pretty damn large, for lod0 its 256x256, could easily be 128x128 and that the panels on the top are prone to zfighting but since they don't generate a shadow under them they only zfight with a texture of themselves just at a different angle so hard to see.

Rabbit · 2013-11-21, 19:44

Damn, thought I found my lag problem.

Thanks for the quick reply.

Rhino · 2013-11-21, 19:52

Can always try removing it and see what happens but can't see anything. Even uses the vBF2 common textures so unless your not using any other vbf2 statics, shouldn't even have a drain on ram.

Rabbit · 2013-11-22, 02:04

Quote:

Originally Posted by [R-DEV]Rhino

Can always try removing it and see what happens but can't see anything. Even uses the vBF2 common textures so unless your not using any other vbf2 statics, shouldn't even have a drain on ram.

No, texture paths are optimized. Must be something (or a few things) that is causing it.

2011-07-23, 17:10	#11
Rabbit Join Date: Dec 2006 Posts: 7,750 United States of America Location: Ohio Blog Entries: 7	Re: [Mapper Info] Static Objects that should not be used in your maps I feel like this needs updated, as I'm having crashes suspects are textures , sounds or other data ( non-text ) files but I am not using any of these objects.

2011-07-23, 17:25	#12
Rudd Retired PR Developer Join Date: Aug 2007 Posts: 21,157 United Kingdom Location: Brighton Blog Entries: 2	Re: [Mapper Info] Static Objects that should not be used in your maps you need to confirm its ur objects causing ur crashes, rename the staticobjects.con to something else, or load only the staticobjects to test staticobjects that are not listed here can still cause crashes, but only usually if you have used too many statics, too many high poly statics or too many different families of statics that load separate texture pallets. I don't recall any new statics being added to the build that could be causing trouble, so I suggest you bump your map's thread and we'll see if we can help you

2012-04-12, 23:17	#14
AFsoccer Retired PR Developer Join Date: Sep 2007 Posts: 4,280 United States of America Location: Denver, Colorado	Re: [Mapper Info] Static Objects that should not be used in your maps ~~Added "industry\ind_objects\chimney_01" to the OP.~~ Fixed bug, so object is useable now.

	Last edited by AFsoccer; 2012-04-13 at 21:04..

2013-11-21, 16:31	#16
Rabbit Join Date: Dec 2006 Posts: 7,750 United States of America Location: Ohio Blog Entries: 7	Re: [Mapper Info] Static Objects that should not be used in your maps Is there a problem with "shack_v1"? I keep find that static in all my fps drop areas.

2013-11-21, 19:44	#18
Rabbit Join Date: Dec 2006 Posts: 7,750 United States of America Location: Ohio Blog Entries: 7	Re: [Mapper Info] Static Objects that should not be used in your maps Damn, thought I found my lag problem. Thanks for the quick reply.

2013-11-21, 19:52	#19
Rhino Retired PR Developer Join Date: Dec 2005 Posts: 47,448 United Kingdom Location: Somerset - UK Blog Entries: 45	Re: [Mapper Info] Static Objects that should not be used in your maps Can always try removing it and see what happens but can't see anything. Even uses the vBF2 common textures so unless your not using any other vbf2 statics, shouldn't even have a drain on ram.