@model directive

[Vbitz]

with this there is a problem, does it look phys or else it will collide with the world some how

[-HP-]

Yes!
There isn't much to say. It's awesome.

[TomyLobo]

with this there is a problem, does it look phys or else it will collide with the world some how

come again?

[Lyinginbedmon]

I think he's asking if the @model directive also changes the physics info of the chip, like if you turn it into a wheel and it rolls down the hill or such.

[Vbitz]

correct, will the code load the new phys into the chip when it is uploaded, also will there be a problem with big props like the big phx building and the combine citadel, will they collide with the world funny

[TomyLobo]

physics and appearance always correspond.
I used no dirty tricks that's break that.
It should behave like prop_physics

[Vbitz]

if i re upload with a new @model will it change instantly. also can we disable the outline if it is there

[TomyLobo]

wire_drawoutline 0

[Tolyzor]

Inb4 necroposter, but out of interest why is @model not included in the e2 header like the similarly optional @trigger line is?

[OmicroN]

Inb4 necroposter, but out of interest why is @model not included in the e2 header like the similarly optional @trigger line is?

Please keep in mind that the post you've replied to is very very old.

As for your response, @model is available in the header, it's just not standard...

@name I have a custom model
@model models/jaanus/wiretool/wiretool_waypoint.mdl