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

Bevy Plugin #305

Open
itsezc opened this issue Jul 16, 2024 · 8 comments
Open

Bevy Plugin #305

itsezc opened this issue Jul 16, 2024 · 8 comments
Labels
feature-request Request for a new feature

Comments

@itsezc
Copy link

itsezc commented Jul 16, 2024

Using Maplibre to create Maps in Bevy is very difficult / verbose and requires alot of hacking. Since Maplibre uses similar rendering to Bevy, and there is scope for including "Map rendering" as part of games, it would be nice to have a bevy-maplibre plugin, that is officially maintained by MapLibre.

@itsezc itsezc added the feature-request Request for a new feature label Jul 16, 2024
@nyurik
Copy link
Member

nyurik commented Jul 16, 2024

See #75

@wipfli
Copy link

wipfli commented Jul 17, 2024

@itsezc MapLibre RS does not have all the features of MapLibre GL JS / MapLibre Native. It is more of an experiment to see what new technologies can be used for a next-generation map renderer. So if you want to make maps in Bevy with MapLibre Native, probably it is best to open a feature request issue in MapLibre Native...

@maxammann
Copy link
Collaborator

maxammann commented Jul 17, 2024

Leaving this open as I have not yet thought creating a plugin for bevy (the other way around).

I think it should be fairly easy to do. Maybe maplibre-rs could establish itself as an in-game map viewer?

Anyone knows whether maps are typically generated or designed? My feel is that they are mostly designed and typically raster maps.

@nyurik
Copy link
Member

nyurik commented Jul 17, 2024

I think a different path (for now) would get us much more -- maplibre/maplibre-native#1057

@itsezc
Copy link
Author

itsezc commented Jul 18, 2024

Leaving this open as I have not yet thought creating a plugin for bevy (the other way around).

I think it should be fairly easy to do. Maybe maplibre-rs could establish itself as an in-game map viewer?

Anyone knows whether maps are typically generated or designed? My feel is that they are mostly designed and typically raster maps.

maplibre-bevy makes sense, the scope of the issue is to use it for two purposes: rendering in game maps but also creating map heavy games think Risk, Travel Simulators etc. with the help of the Bevy ecosystem.

@maxammann
Copy link
Collaborator

I think a different path (for now) would get us much more -- maplibre/maplibre-native#1057

I think this is less a question of programming language but more of tool stack/platform. For bevy support you basically need to support WebGPU or the bevy WebGPU layer. To make it available in a GTK app you need to support the surfaces and input handling of GTK.

Input is generally a big thing to overcome after rendering.

TLDR: it is quite complex and every use case needs a tailored implementation.

@maxammann
Copy link
Collaborator

Leaving this open as I have not yet thought creating a plugin for bevy (the other way around).

I think it should be fairly easy to do. Maybe maplibre-rs could establish itself as an in-game map viewer?

Anyone knows whether maps are typically generated or designed? My feel is that they are mostly designed and typically raster maps.

maplibre-bevy makes sense, the scope of the issue is to use it for two purposes: rendering in game maps but also creating map heavy games think Risk, Travel Simulators etc. with the help of the Bevy ecosystem.

As maplibre-rs is niche the market of in-game maps looks interesting!

@maxammann
Copy link
Collaborator

This is closely related to #112 which is concerned about making maplibre-rs more reusable in other rendering engines

@maxammann maxammann added this to the Far far future milestone Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for a new feature
Projects
None yet
Development

No branches or pull requests

4 participants