-
Notifications
You must be signed in to change notification settings - Fork 26
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
Cruiser not working with default VTM theme #245
Comments
Cruiser VTM doesn't work on 64bit macOS by default, as the VTM libraries are 32bit only at the moment! That is a known issue of cruiser - see issues on this side (vtm library used by cruiser). This is no issue of the code in this repo. You can get it working using 32bit Wine starting the Windows bat file. Or use an old macOS having native 32bit support. |
Sorry, not the most computer savvy but have managed to get custom maps to work.I have managed to get it to all work on my wahoo but not fully satisfied with how certain trails are shown on the map so using cruiser will be essential to testing this. so what your saying is if I run cruiser on a windows pc I will be fine. Or use an old mac, how would I see if its 32 bit? |
I can't comment on anything MacOS related being on Windows. |
When I am on cruiser I dont have a rendering engine setting? |
You can't get the VTM render engine on 64bit macOS. You can try by changing the call in the .sh file, but then you get other errors. When did macOS go 64bit: not exactly sure, was it Catalina? On 10.13 it works fine here. On newer macOS you just can try the Wine workaround. |
Thanks for helping out @masc4ii and @Ebe66! This is a related discussion about using cruiser on macOS: mapsforge/vtm#1004 (comment) and devemux86/cruiser#20 (reply in thread) |
Expected Behavior
When using cruiser we upload the map we want to view, then select the wahoo theme we wish to see the map viewed as from the theme repository from github.
Current Behavior
We in cruiser and selecting the VTM theme I get an error of "Unknown element: style-line"
Steps to Reproduce the Issue
Context
Mac
For boltV2
The text was updated successfully, but these errors were encountered: