Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restrict notifyDriverOfPrototypeAndBehaviorProps to 3D nodes #530

Conversation

BrettASwift
Copy link
Contributor

@davideaster @kadst43

David, I tested what nodes this portion of the code was hitting by checking for !node || !node.threeObject and all of the child ids it spit out were not important to the driver, so I added the check for node and threeObject. The result was a total load time improvement of 6 seconds on my lap top (~28s down to ~22s). The scene remains intact and the game is playable. I didn't notice any issue in testing. Is there any obvious issue I am missing here or does this do the trick?

@davideaster
Copy link
Member

Looks good. Virtually all of the threejs driver functions should have an early exit if the node doesn't map to a three.js node.

BrettASwift added a commit that referenced this pull request Jan 25, 2016
…iver-props-performance

Restrict notifyDriverOfPrototypeAndBehaviorProps to 3D nodes
@BrettASwift BrettASwift merged commit 270d238 into branch/mars-game-development Jan 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants