-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
editor: multiple fixes & improvements related to LODs #556
base: master
Are you sure you want to change the base?
editor: multiple fixes & improvements related to LODs #556
Conversation
Tested! |
I don't think that useLODs should be a good idea to be true as default, since most players are not aware of what LODs do in the first place. |
The LOD object model only loads when the object becomes far away, replacing the normal object (or so it should). I doubt it's bad in terms of performance... I know me and many MTA players have always hated seeing objects disappear at a low distance, due to the lack of LOD loaded because the script only did createObject once without assigning any LOD... It's especially frustrating and immersion-breaking in the map editor while you're mapping to see these objects disappear. |
addEventHandler("onResourceStart", resourceRoot, onResourceStartOrStop, false) | ||
addEventHandler("onResourceStop", resourceRoot, onResourceStartOrStop, false) | ||
|
||
-- MTA LOD Table [object] = [lodmodel]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs one more closing ] at the end, two to close the multi-line string and one to encapsulate 'lodmodel' in the final file
-- MTA LOD Table [object] = [lodmodel]]]
Actually, keep this on hold. |
Status: draft as I think of better alternative solution to LOD model ID fetching for object models