create_object and init_object

[james227uk]

Hi,

 

I was just wondering what the difference between init_object and create_object was.

 

Is there even a difference?

 

 

 

James227uk

[Seemann]

The only difference is that 0107 additionally calls CEntity::getDistanceFromCentreOfMassToBaseOfModel()

 

So, I guess it's somehow related to the way the model is spawned. Probably if a part of the model is within another solid object (ground) the game changes its spawn location or not.

[james227uk]

Thanks for that, It appears then, that init_object is the opcode i need.

[Deji]

In my experience, I found "init_object" never needs the model to be loaded before use... It loads automatically as you get close to its area. It fades into view when the player is close enough, so doesn't exist when the player is elsewhere, which saves game memory.

 

Its collision seems to always exist, though... Causing that annoyance of "aghh, I can't see it but I can crash into it"... Hmmm..

[james227uk]

I've been using create_object quite considerably, and haven't loaded the model. No crashes as of yet

[spaceeinstein]

Both opcodes are nearly identical in every way. Seeing the one difference between the two opcodes is most noticeable when spawning the "electric gate." One opcode places the gate higher than the other (forgot which one). Here are the native functions in IV that I think are equivalent to the opcodes:

CREATE_OBJECT

CREATE_OBJECT_NO_OFFSET

[Deji]

Nice... I'll add that to Opcode Database 2.0

[james227uk]

Both opcodes are nearly identical in every way. Seeing the one difference between the two opcodes is most noticeable when spawning the "electric gate." One opcode places the gate higher than the other (forgot which one). Here are the native functions in IV that I think are equivalent to the opcodes:

CREATE_OBJECT

CREATE_OBJECT_NO_OFFSET

It seemed to me that create_object is the one that spawns higher than the other