October 2, 2017 at 18:43 #20399
Thanks, looks good. One issue with patterns on line like this:
<line src="file:ele_res/p_access-private.svg" symbol-scaling="size" symbol-height="8" symbol-width="8" stroke-width="0.9" />
See screenshots, in mapsforge Cruiser it works well, in GL Cruiser only a black line is visible.
Also zoom levels don’t match.
Developer of Elevate mapstyleOctober 2, 2017 at 19:02 #20403
Thanks for the report Tobias, I’ll check it.
> Also zoom levels don’t match.
Do you mean in screenshots? VTM has continuous scaling, not fixed zoom levels.
But can use the “Tools” > “Go to” to set exact same zoom also in Cruiser GL.October 2, 2017 at 19:20 #20406
It seems to me that scaling of symbols does not work and neither do zoom-max or zoom-min. Neither can I get dashes with rounded ends.October 2, 2017 at 19:36 #20408
– Do you mean some specific rule for symbols?
– Regarding dashes, OpenGL cannot mirror exactly software rendering.
Likewise Mapsforge cannot have the advanced GL theme rules.
Eventually some minor differences will exist!October 2, 2017 at 20:24 #20411
Thanks Emux, with “go to” ZL match. I thought that +/- would snap into exact levels as shown with debug info.
Another thing: switching 3D buildings off results in virtually non existent building borders. BTW, leaving them switched off causes Cruiser to crash on every next start for me.
Round dashes are more than cosmetic differences (compared to different dash length), as lines that e.g. only differ via dotted/square look the same now, so it’s important for theme compatibility to have them.
Developer of Elevate mapstyleOctober 2, 2017 at 21:00 #20414
> I thought that +/- would snap into exact levels as shown with debug info.
It was asked before, probably I’ll have to change buttons behavior!
> switching 3D buildings off results in virtually non existent building borders.
Are the buildings declared with “area” rule and “stroke” (see #213) ?
As explained in #121 in OpenGL the area outlines are hardware dependent. That’s why in VTM themes it’s recommended to use additional line layers, for area borders.
Of course with Mapsforge themes will need to think how to overcome that..
> leaving them switched off causes Cruiser to crash on every next start for me.
I’ll check, though from a quick test cannot reproduce it..
Are there any other app options changed? If uninstall / reinstall Cruiser (to reset options), disable 3D buildings, does it happen?
> Round dashes are more than cosmetic differences
Nothing is impossible, will see what can be done!October 3, 2017 at 09:42 #20418
Yes, all area borders, so it’s a known issue.
I sent fc feedback, just two things necessary with a fresh installation: select latest Elevate.xml, switch 3D buildings off. At next start of Cruiser GL it crashes. With 3D buildings on it doesn’t.
Developer of Elevate mapstyleOctober 3, 2017 at 11:56 #20422
Do you mean some specific rule for symbols?
Turns out this was the maximum zoom render issue you explained above. A search and replace for zoom-min=”18″ solved that.
Using Cruiser GL in Windows, 3D buildings have no sides or tops, only white edges. Are there any relevant instructions for Mapfactor themes?October 3, 2017 at 12:54 #20424
> Using Cruiser GL in Windows, 3D buildings have no sides or tops, only white edges. Are there any relevant instructions for Mapfactor themes?
That should be some issue with the graphics card and OpenGL on Windows.
What graphics card and driver do you have?
Can you create an issue in VTM repository mentioning those details?
You can test the default theme (from map menu), probably with same behavior.
3D buildings should appear the same in VTM and Mapsforge themes.October 3, 2017 at 13:46 #20427
I get the same behaviour from the default theme. The graphics card is an ATI Radeon HD3450 on Windows 10, which appears to be an unsupported OS for it.
The WebGL demo works fine however.October 3, 2017 at 19:34 #20431October 4, 2017 at 20:34 #20464
Something else – lines with stroke-dasharray are rendered/scaled differently than without. See attached screenshots, the brown tracks should have always the same thickness and also the same borders. But at high zoom levels, the dashed ones are much thinner, and at low zoom levels thicker.
Developer of Elevate mapstyle
- You must be logged in to reply to this topic.