vladislavbelov

Probably we'll find an open-source library that converts OpenGL calls into Metal calls. That'd be really helpful for the developing. It also may limit some old versions of Windows, because of no drivers with VK.

I hope we'll find a way to fix the macOS build. Also you always can run older versions

I have macOS (I said it some time ago), but I can't bundle the game, because it has a different framework.

As Stan said, for most lagging moments the rendering doesn't spend much time in comparison with the pathfinder. LOD can be supported on the engine side, but the instancing already has prototype. LOD is best when all models are different/some models are highpoly, Instancing is best when all models are the same. I.e. LOD would be better for buildings like CC or Wonder with many polygons. instancing - for many similar trees. But again quoting Stan, LOD requires an artist work. That's the good idea, reusing may save memory and performance.

I'm here now, I was at vacation I'll try to answer to all messages, sorry for delay.

It could be FreeType too, it just requires some refactoring for the GUI code (we already have a lot of patches for refactorings). I hope we'll try to make a solution for the next release.

As Stan said we support only prerendered fonts. So an additional language requires an additional font textures, like for Chinese languages. Cairo is pretty complex, so it requires a lot of time to replace our GUI rendering. I think it'd be better to use a smaller library, because it'd be much easier and it'd still easy to replace it by Cairo.

+1. Especially from this studio, it seems they discovered design and UX just now.

I'd call it an additional option, because we have some custom things. Brew can be an alternative option in case we remove these custom things.

Could you disable all effects and try again?

If you try to build the game with a different build system, you'd need to know which dependencies are needed. Because it seems, that you didn't install SpiderMonkey. Old != invalid. Also we can't use brew yet, because brew supports well only 10.11+, 10.5–10.10 are supported on a best-effort basis (https://docs.brew.sh/Installation), but we support 10.9+ (for bundles 10.7+). I don't think that the brew can fully replace the script, because we need to use custom compilation options and to patch some libraries anyway.

Did you use official build instructions for macOS: BuildInstructions? Because I don't see build-osx-libs.sh in logs, so that's the problem I think.

I think because of a different version of the gloox library, probably @fcxSanya might know.

It's not so critical as it could be, but it's still UB and should be fixed. But how it may work: How usually (compiler depended) new[]/delete[] work: new[] allocates a block with a needed size + a space for size - a number of objects. delete[] extracts a size from the block and calls a destructor for each object and deallocates the block. But! u8 is a basic type, not an object. So a compiler may replace new[] by new for basic types or use another trick, especially in case all actions are in the same place and the compiler knows a storing object. Also we have own pool and arena for some cases. Not all, i.e. clang-802.0.42 doesn't detect it for basic types (for N5 too), only for objects, even without -O0+. Probably because of the trick above. We had an option for it sometime ago, if I'm not mistaken. It was called --enable-address-sanitizer. It'd good to add a regular (1 per week) build on Jenkins.

I already answered to your post on the habr. But thanks a lot again for helping to find errors. Only few of them are known, and patches are waiting for the end of FF. UPD. I will create tickets for missed bugs, when I'll be at home.

This note doesn't make Javascript nondeterministic. It just means that it depends on an implementation. Because different engines for different types may use different structures behind objects/arrays for more optimal storing. Also this reference suggests to use `for ... of` or `.forEach(...)`, when the order of the iteration is important. But `for ... in` is used for cases, when you just need to change/find a property, without knowing its index (the not fixed order may make it a little bit faster). So Javascript as the language is deterministic.

PBR could make the metal more metallic, but it's more expensive and requires more memory.

Could you attach the exported DAE file? It looks like it doesn't have this point in the right place. You could open your file and any other of the game to compare where attach points are placed.

Skybox is hardcoded, so currently you're not able not change its shape, only textures. But change it to sphere would be good. Also It'd be good to add atmospherics scattering. I have some plans to improve the sky. But the game is RTS, so usually sky isn't really visible, so even a flat sky works.

The same for your resolution, because it uses a power of two, so for you it'd be 1GB too.

When I added these settings I evaluated the high shadow settings on 1080 Ti for 4K monitor, it has 11GB. How many video memory it costs depends on 2 things: settings and a screen resolution. So if you have high settings on 4K monitor, it'd cost at least 4096 * 4096 * 4 * 4 * 4 = 1GB.

You can edit a configuration file, you can find the file for your OS here: https://trac.wildfiregames.com/wiki/GameDataPaths. And add or edit (if present) lines: view.zoom.min = 50.0 view.zoom.max = 200.0 view.zoom.default = 120.0 Cinematics zoom like in SW: Empire at War isn't supported, probably yet. It's not valid for multiplayer, especially rated matches.

I tried, it doesn't work (it does nothing).

Yes, leper suggested few solutions for this. The main idea is to load fonts (.ttf), but not prerendered atlases. Also we need to support system scale (I have a patch for it) to prevent a blurry image. Why there are random lines? Because it's a standard problem for all systems that are simply positioned in DIPs. First of all we need to refactor GUI for it.

As I said before: after refactoring