Difference between revisions of "User talk:Ashileedo"
Jump to navigation
Jump to search
→disable
imported>Mrflippy |
imported>Ashileedo |
||
| Line 64: | Line 64: | ||
::We use disable a lot on environment that is already there (it may start enabled and be disabled later, or some variation of this) - but the art is already loaded in the scene, you just can't always see it right away until there is change of state. We don't use it with placeatme very often, I can't think of any example off hand. Need to be careful if you are allowing player to call objects that aren't loaded already, esp if you are calling actors (npcs or creatures) as they are very expensive. If player is in middle of memory intensive scene, summoning more art could adversely affect framerate. | ::We use disable a lot on environment that is already there (it may start enabled and be disabled later, or some variation of this) - but the art is already loaded in the scene, you just can't always see it right away until there is change of state. We don't use it with placeatme very often, I can't think of any example off hand. Need to be careful if you are allowing player to call objects that aren't loaded already, esp if you are calling actors (npcs or creatures) as they are very expensive. If player is in middle of memory intensive scene, summoning more art could adversely affect framerate. | ||
:::So the real danger is actually the summoning and not the disabling? Or am I misunderstanding? If I summon and disable 50 iron shortswords, will there be 50 disabled instances floating around? [[User:Mrflippy|Mrflippy]] 15:01, 7 April 2006 (EDT) | :::So the real danger is actually the summoning and not the disabling? Or am I misunderstanding? If I summon and disable 50 iron shortswords, will there be 50 disabled instances floating around? [[User:Mrflippy|Mrflippy]] 15:01, 7 April 2006 (EDT) | ||
::::The danger is summong 50 iron swords at the wrong time and running out of memory. However, if you disable something that you've placeatme'd, I believe it gets thrown out -- I don't think right away, but our memory management code will clear it out when you hit your next load (though we'd have to check the code to be absolutely sure its at your NEXT load. But I am sure it does get cleared away eventually and won't linger). But the bigger risk here is if you placeatme something that is too expensive -- especially if player does it over and over and over again consecutively. | |||