You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I take this DEM file, set it as elevation, and then attempt to view it in qgis2threejs, I often (but not always) get something that looks like this:
Any ideas on how to troubleshoot? I've seen this happen with many different DEM files. Sometimes uninstalling and reinstalling qgis2threejs helps and sometimes not. I can't reproduce it reliably either; sometimes a file will work flawlessly and sometimes not.
The text was updated successfully, but these errors were encountered:
fsiler
changed the title
inconsistent behavior: "spagetti" render mode
inconsistent behavior: "spaghetti" render mode
Feb 10, 2024
fsiler
changed the title
inconsistent behavior: "spaghetti" render mode
inconsistent behavior: "spaghetti" render mode #bug
Feb 10, 2024
fsiler
changed the title
inconsistent behavior: "spaghetti" render mode #bug
inconsistent behavior: "spaghetti" render mode
Feb 10, 2024
This is a commonly asked question. Probably the CRS (Coordinate Reference System) of your project is a geographic coordinate system, with degrees as the horizontal unit and meters as the vertical unit. Try changing the CRS of your project to a projected coordinate system to ensure consistency in horizontal and vertical units.
Fantastic, I will try that, thank you. Is there any way to detect this condition- perhaps by aspect ratio of the rendered model- and suggest a suitable coordinate system?
If I take this DEM file, set it as elevation, and then attempt to view it in qgis2threejs, I often (but not always) get something that looks like this:
Any ideas on how to troubleshoot? I've seen this happen with many different DEM files. Sometimes uninstalling and reinstalling qgis2threejs helps and sometimes not. I can't reproduce it reliably either; sometimes a file will work flawlessly and sometimes not.
The text was updated successfully, but these errors were encountered: