search

foxglove / community

This repo hosts our org-wide discussion board
0 stars 0 forks source link

Bring back the car model #199

Closed jhurliman closed 1 year ago

jhurliman commented 2 years ago

Requiring external hosting of mesh markers is burdensome. It would be nice to bring back the embedded autonomous vehicle glTF, and allow referencing it with a special URL such as foxglove://car.

amacneil commented 2 years ago

Maybe we offer a few options in a dropdown or something?

Although, do people actually want built in models that are not their robot? I can't think of who would want this (besides us developing FG).

Sent via Superhuman ( @.*** )

On Fri, Jan 07, 2022 at 2:08 PM, John Hurliman < @.*** > wrote:

Requiring external hosting of mesh markers is burdensome. It would be nice to bring back the embedded autonomous vehicle glTF, and allow referencing it with a special URL such as foxglove://car.

— Reply to this email directly, view it on GitHub ( https://github.com/foxglove/community/issues/199 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAE3VZ7XNTG3K7HO6GG4DPTUU5P7RANCNFSM5LPXYR3Q ). Triage notifications on the go with GitHub Mobile for iOS ( https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 ) or Android ( https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub ). You are receiving this because you are subscribed to this thread. Message ID: <foxglove/studio/issues/2613 @ github. com>

jhurliman commented 2 years ago

@amacneil I was thinking this would be for mesh markers, although it could be used for PoseStamped as well with a dropdown in the UI.

do people actually want built-in models that are not their robot

We already supply a built-in model that is not their robot. It's a low poly cylinder / arrow thing. This request is to expand support beyond our single model to at least one more.

amacneil commented 2 years ago

Still don't understand who this would be useful for. Pretty big difference between supporting generic shapes and a "Chevvy Bolt" model.

jhurliman commented 2 years ago

@amacneil deeproute.ai

image

You can see in their promo video they use a generic car model that does not appear to be an accurate model of a fully rigged self-driving car. They thought a generic car model made for better data visualization than a purple cylinder driving down the road. To get to a car model in Studio, you can:

  1. Acquire a 3D model of your vehicle, often derived from a CAD model or another very high poly source
  2. Hire an artist to create a low poly rendition of this model
  3. Convert the model to glTF format, ensuring you set the correct up axis and scale, the file size is reasonable, and no unsupported glTF extensions are enabled
  4. Upload this model to a publicly accessible web server and configure the correct CORS headers. Alternatively, if you want to keep your model private you need to run a private web server hosting this file
  5. Point your mesh_resource at this public or private URL

With an embedded car model, you could get to the same visual fidelity of the deeproute.ai promo video by:

  1. Point your mesh_resource at foxglove://car
rgov commented 2 years ago

What about making it easy to select Ignition Fuel models? If you can support loading rendering SDF / .obj files that is.

https://app.ignitionrobotics.org/OpenRobotics/fuel/models/Hatchback%20red

defunctzombie commented 2 years ago

If we have some notion of an asset manager within the app we could allow adding datasets like the above referenced model dataset.