[Sho0ter]

What is faster/better?
pev/set_pev (Fakemeta) or entity_get/entity_set (Engine)?

[xPaw]

entity_* should be very slightly faster, because it's like entity_get_[string,int,float] ...

[abdul-rehman]

But this type of optimization sounds trivial.

[aaarnas]

Just use, what is easier for you. It's 0.001 difference.

Use that module, witch's native is most efficient.

[Sho0ter]

Originally Posted by aaarnas Just use, what is easier for you.

I'm like Fakemeta ;)
Thanks for replies.

[Hunter-Digital]

Still, you should understand that if a engine native cand do it from one call and fakemeta can do it with 2+ calls, it's better to use the engine native, even if you use fakemeta stuff everywhere.

For example, fm_* stocks from fakemeta utils does the same thing only slower than their engine counterparts, so it's better just to use engine for them.

[Sho0ter]

Originally Posted by Hunter-Digital Still, you should understand that if a engine native cand do it from one call and fakemeta can do it with 2+ calls, it's better to use the engine native, even if you use fakemeta stuff everywhere. For example, fm_* stocks from fakemeta utils does the same thing only slower than their engine counterparts, so it's better just to use engine for them.

I know that and asked about the specific functions.

[fysiks]

I would say that if you don't have the more efficient method memorized then just get it working then and can optimize later on such a trivial situation.

[xPaw]

Originally Posted by fysiks I would say that if you don't have the more efficient method memorized then just get it working then and can optimize later on such a trivial situation.

It's easier to write such trivial things from beginning. It's not really worth changing [set_]pev to entity_[g/s]et at later stages...

[fysiks]

Originally Posted by xPaw Originally Posted by fysiks I would say that if you don't have the more efficient method memorized then just get it working then and can optimize later on such a trivial situation. It's easier to write such trivial things from beginning. It's not really worth changing [set_]pev to entity_[g/s]et at later stages...

See bold text.

I like to have something working so that I can debug other things that are more important so I use what I know works then can choose to either optimize or not depending on my knowledge and relavence.