| 1 | | sbte: frankly, none. The real problem with using a vector without the map is that if you use tons of temporary entities, you get a huge vector for no real reason, which can be seen as a memory "leak". I "solved" that issue on my version of the patch by using pointers and deleting the informations about deleted stuff, so in itself the only memory used is that of the vector (which is really negligible) but you also have to make sure that serialization works (and deserialization too, which is harder as you'd have to initialize null pointers) and that things don't get too ugly when quitting the game/simulation, and restarting it. Basically It's not really nice, and probably not extremely robust, but it's probably the fastest way to do it. |
| | 1 | sbte: frankly, none. The real problem with using a vector without the map is that if you use tons of temporary entities, you get a huge vector for no real reason, which can be seen as a memory "leak". I "solved" that issue on my version of the patch by using pointers and deleting the informations about deleted stuff, so in itself the only memory used is that of the vector (which is, I believe, largely negligible) but you also have to make sure that serialization works (and deserialization too, which is harder as you'd have to initialize null pointers) and that things don't get too ugly when quitting the game/simulation, and restarting it. Basically It's not really nice, and probably not extremely robust, but it's probably the fastest way to do it. |
