Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Perhaps something custom in your GPU's rendering/AA settings?
https://www.matrixgames.com/forums/viewtopic.php?f=10230&t=397225&p=5115731&hilit=borders#p5115731
Working with the AA setting in my Nvidia control panel doesn't seem to affect it much.
I've tried several different configurations in the Nvidia Control panel settings related to Anti-aliasing. And while there can be marginal differences, the core issue remains, and it's definitely with the borders/coastlines layer which just refuses to render cleanly at all.
This definitely started after the 64 Bit update.
If ONLY the borders/coastline layer is enabled, they all look perfect, so I feel it's something with the way the different layers interact with this layer that is the issue
While all layers seems to cause this poor rendering, the Day/Night Lighting one seems to affect it the worst, with an apparent circular "shadow" completely removing the borders that are directly center of the camera view.
Personally, I'm thinking this may be related to the hard setting that fades the Borders/coastlines when zooming in, as that does not seem to be enabled with ONLY that layer enabled, as I can cleanly zoom in very close with the borders/coastlines clearly visible
It may have been your post I saw about using 32 bit for my other issues, but from my messing about. (generating and putting in my own files)
Based on your screenshot I presume you're also running at a high resolution? Looking into the difference with 32bit and 64bit it looks like DX11 or w/e is rendering images doesn't handle transparency and the like easily. I've generated my own images and still output is the same.
Looking on my other devices that aren't 4k I can see the same issues but because it's so much smaller it's harder to notice.
4k monitor: https://imgur.com/a/iIXK1my
Smaller Resolution: https://imgur.com/a/KgzlXOk
@Dimitri this is the 32bit I referred to.
It seems to be when layers are webp that they are the most jank - I replaced a layer with google maps and it renders fine. https://imgur.com/a/frCufuQ
I also created my own placenames due to the issue, grabbing them from the stalmen tiles.
and when I edit them myself in gimp you can see where transparency should occur
https://imgur.com/a/d8z4w4j (but in the game there is no transparency https://imgur.com/a/IfbIhCl in the 32 bit version this rendering issue doesn't exist )
This is from the link: https://tiles.stadiamaps.com/tiles/stamen_terrain_labels/{z}/{x}/{y}{r}.png
hopefully this helps finding the issue!
Not sure which one you mean, but in terms of the border lines I meant only to show it was less noticeable at lower resolutions.
I've been messing with the shaders because they are new and seem to involve various references to the interaction of layers and their alpha layers, though I've not dealt with shaders before so still figuring out how to force DX11 blendstate.
Great! can't wait to try it out!