Warzone 2100 Forums

And now unless I want to play a buggy master build I have to take the extra time away from my game in order to re-apply this hold order every time I move a flak gun around. I just wanted to point out that the master branch is much more stable than 3.2.x at this point. (A huge list of bugs fixed, ma...

Thanks @Prot!

I checked-in a fix to prevent this from happening again.

Defaulting to the highest display scaling available is a complete deviation from prior behavior and also from recommendations on most operating systems. In the future, we could default to high-DPI support that matches the current display . This already works on macOS, but we need to wait on fixes / ...

@Prot: If it's working again, this has the smell of a locale-related issue (and we may currently be relying on a side-effect of Qt initialization). I'd very much like to track down what's going on. What OS are you using, what version, and what is your system locale setting? Can you try running fc86a...

On the matter of multi-threading: The game already uses multi-threading for things like loading games and data, and tasks where it is a benefit - like processing path-finding. For other tasks, I'd encourage you to run a profiler on the game - the latest builds of the `master` branch on GitHub have a...

Check to see if commit 3ac5343a6c39bf86f918ef6e4e916faf80a4ca15 causes this for you, since that's the most recent commit that really affects the code in question.

(Also, are you building from a clean checkout? Because there are some other errors there that are odd...)

What version of Warzone are you running?

3.2.3? One of the nightly builds?

The WzString class in my branch is a lightweight wrapper around std::string & stdlib C++11 functionality (with utility functions) for just this reason. Because std::string does nothing to natively support UTF-8, using std::string methods like `length()` or `size()` or enumerating "character...

I appreciate what you are doing, but your class does not properly handle Unicode, which the WzString class in the branch above already does. I do like your ideas surrounding additional operator+ overloads, so we may roll those ideas into WzString to ease future development. And as we go through olde...

The goal is to produce a largely drop-in replacement for QString for Warzone, not to write a C++ string class with a new API (and not to replicate *all* of QString since Warzone doesn't use or need all of it). We'd be using std::string directly if we weren't intending to: (a) provide an easy drop-in...

If you're testing with a small, resource-constrained system, you should test with a recent build of the `master` branch, which has a number of recent performance enhancements. See: https://github.com/Warzone2100/warzone2100

There's more that I have yet to push to my branch. Those changes will be coming soon. The goal is to move the core over to C++, the C++ stdlib, & reasonable (small, cross-platform, stable, performant, easy to build) libraries. In this first phase, that is being done with minimized changes to the...

This is already in-progress, including a WzString class that replicates all necessary QString functionality with proper Unicode support. It's not yet in master, but it's well under-way.

EDIT: Before you do the below, please grab a copy of the log file mentioned in the screenshot you took. That should explain where it's failing. Try re-running `vcpkg install gettext`, and see if it succeeds this time. If not, you may have to roll-back vcpkg to before this vcpkg commit . At the momen...

Sur3 wrote:I can't compile it for linux because I'm getting lots of physfs deprecated warnings:

Please use the patch here, which should resolve all deprecation warnings but one: https://patch-diff.githubusercontent.co ... /143.patch