Difference between revisions of "Talk:Disable"
imported>Omzy (Redaction of statement) |
imported>Omzy m |
||
| Line 6: | Line 6: | ||
EDIT | EDIT | ||
I've narrowed my problem down to something excruciatingly simple. I was wrong in assuming Disable was the problem, and now it is clear that Disable does deactivate collision on activators. | I've narrowed my problem down to something excruciatingly simple. I was wrong in assuming Disable was the problem, and now it is clear that Disable does deactivate collision on activators.--[[User:Omzy|Omzy]] 07:04, 2 June 2007 (EDT) | ||
Revision as of 06:04, 2 June 2007
Disable DOES improve performance
Dragoon Wraith TALK 21:37, 26 May 2007 (EDT): I think the line "do not depend on Disable to improve performance" is misleading. It does improve performance, by making one less thing for Oblivion to render. In many cases, the effect on performance of the graphics of an item is much greater than the effect of its script.
I'm having a problem getting the collision of an object to turn off. Is it possible that the Disable command does not disable the collision of an activator? I'm sure I am right that the collision is not turning off since I have an invisible capsule around the player and when it is supposed to be disabled, i am still stuck inside. My code basically puts the capsule there, then disables it a few frames later. There shouldn't be any problem unless there is a problem with Disable. Any thoughts?--Omzy 17:50, 1 June 2007 (EDT)
EDIT I've narrowed my problem down to something excruciatingly simple. I was wrong in assuming Disable was the problem, and now it is clear that Disable does deactivate collision on activators.--Omzy 07:04, 2 June 2007 (EDT)