I have a question about the texturing on 3D models. I would love to continue to use webODM with my DJI Manifold Jobs, but unfortunately the texturing isn't as good as I was hoping for. Is there any way to make that better? I attached the screenshot, with the cameras on so you can see I have plenty of data. Is this just a open source limitation?
Can you define "good" ? If you mean image sharpness, make sure you are opening the 3D model outside of WebODM, WebODM will compress the texture to display them in the browser (without crashing it)
MeshLab for example
Ah, you are right! So that leads me to a few other things, I mainly use the docker instance on my main server, but I imported that project locally on my computer and when I tried to view it on the WebODM on my PC I get this:
My PC is a i9-1400ks with 64gb ram and a 5070.
The textured model looks amazing in mesh lab, and I understand why it gets compressed, I didn't know that that is what was happening.
Is there a way we can have that view better through the web? maybe more chucked loading and only loading what is visible on screen. From my knowledge The entire textured model loads all at once.
My clients would love to have that full textured model view through the web.
Look at nira.app, it's probably what you need to use
that is what I am looking for, thank you.
Is there a way that WebODM could implement this in the future? I know this is a big task.....
As soon as we get 10 gold sponsors here https://webodm.org/fund, currently we're at zero so we have some ways to go
Dang okay... If I had the money I'd be the first. Thanks for your help! I'll give Nira a try.
I was actually about to open a thread for the same thing with orthos, is this the same issue? whenever i open them outside of webodm they look better. I'd love to share it like drone deploy how it has the full-res thing and have the different points for overall site photos, & panos.
& i assume also the same limitation of money needed for development?
Yeah it’s the same compression.
The ODX engine is still really good, just the viewer compression is a pain point
Can you attach some screenshots showing the orthos comparison in viewer vs. opened outside?
Yes I can later, I am currently away from home atm
webodm
jpg export
webodm looks more... pixelated? here's a more zoomed in comparison as well,
webodm
jpg export
i know obviously so zoomed in they're both pretty bad (400ft agl ortho) but i feel like jpg is obviously better.
i made this to better compare the two. obviously the scaling is a little off, but you can very easily see the difference in how 'rough' the dirt looks on the right side, and how the vehicles look hella pixelated on the right.
I'm going to guess it's nearest neighbor vs. bilinear filtering (or lanczos). The viewer uses nearest neighbor because it's faster and when zoomed in all the way, (should?) look sharper, more accurate. But it's an interesting point, perhaps at higher zoom levels we should consider applying bilinear filtering and switch to nearest neighbor when reaching higher zoom levels
if you zoom in to some details in the dirt, how does it compare? Or is that the screenshot you posted above? (Did you actually zoom-in from the viewer to take that screenshot)?
i zoomed in from the viewer
it's actually not as awful as i thought zoomed in, you can't really see the seam of where i cut the two.
i'd still argue jpg wins (maybe i'm a little biased xD), but i feel like the webodm viewer is acceptable zoomed in.
When I have a moment I'll look into it; it might be an easy fix/improvement. (Tracking with https://github.com/WebODM/WebODM/issues/2006)
seam is between these lines
as always, not bitching at all & i sincerely appreciate all the work you do <3
also sorry to hijack your thread @LIL-Diabeetus
Haha all good.
But don’t you said you had clients ? Maybe your business model and pricing could include a R&D fee that you could use to fund the features you need in open-source (whether it’s WebODM or other OSS)
it should just be included in the rate. profit is R&D money lol
clients hate seeing a whole bunch of fees & shit. they just wanna see the price.
@YanNoun I am working on something to potentially have as a LoD (level of detail) loading for full res textured model views
If it was just a problem of generating LOD... which WebODM already can do! Don't let AI convince you that this is an easy fix :p
Yes true. However I still am building the custom app to run on my server because I don't want to pay for nira.app for my Terra model
@pierotofy what is the the hold back on not being able to view LOD?
share the code on github and we can have a discussion on the challenges
The uncompressed models look so good! the ODM engine is very good, but I now see the browser viewer is the limiting factor. the first image is from the custom frontend for my models, still being processed through ODX. @pierotofy
mind if i DM you regarding your custom frontend?
yeah go for it.
This discussion happened in the WebODM community Discord. Join and ask your own question.
Join View Original ThreadThis page mirrors a public discussion from the WebODM Discord. How to request a removal.