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

Obj file support #676

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Obj file support #676

wants to merge 4 commits into from

Conversation

gleblebedev
Copy link
Contributor

.obj file, even if it has "Objects" in it doesn't have information about pivots and everything is in world space. I believe it doesn't make sense to split result into multiple nodes. I think it worth to have .obj support right in the engine.

For example here I opened a 1GB photogrammetry file in the Rbfx Editor:

image

namespace Urho3D
{

bool Model::LoadMDL(Deserializer& source)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not split a class across multiple cpp files. IMO best we do not start doing it :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not? If we support several formats for the Model I would prefer the loader code to be isolated. I can't do it as an external loader without major refactoring because of the code for async loading - the loader would need knowledge of and access to internals of the model. I can squash it into one file. Maybe I can extract obj related code that I took from another project to a dedicated cpp...

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.

None yet

2 participants