Josh

The reality is that we have to switch to C++11 if we want to use updated libraries and that our C++11 feature set will be limited because people (including me) will still compile on GCC 4.6/VS 2010.

This page lists all recent changes.

It might be helpful to know Alt+Enter switches to windowed mode.

Done in r15282.

The GUI scripting reference might be helpful. The only feasible way to do a graph with the current system would be by using the <repeat> element with some size manipulations similar to what options.js does during initialization. That said; at best the graph drawing code would be a mess. The best solution would be a C++ extension, but if you aren't familiar with C++ this might work in the mean time.

There was some testing awhile ago, and if I remember correctly, the improvements by optimizing the build flags were within the margin of error.

It would be nice to see if we could make the shaders behave properly (there might be other similar chips with the same issues).

I think big screenshot has been fixed now. The errors from your log are: ERROR: Failed to link program 'shaders/glsl/terrain_common.vs'+'shaders/glsl/terrain_common.fs': Fragment shader(s) failed to link, vertex shader(s) linked.ERROR: Failed to link program 'shaders/glsl/terrain_common.vs'+'shaders/glsl/terrain_common.fs': Fragment shader(s) failed to link, vertex shader(s) linked.ERROR: Failed to link program 'shaders/glsl/terrain_common.vs'+'shaders/glsl/terrain_common.fs': Fragment shader(s) failed to link, vertex shader(s) linked.ERROR: Failed to link program 'shaders/glsl/model_common.vs'+'shaders/glsl/model_common.fs': Fragment shader(s) failed to link, vertex shader(s) linked. Fragment Shader not supported by HWERROR: Failed to link program 'shaders/glsl/model_common.vs'+'shaders/glsl/model_common.fs': Fragment shader(s) failed to link, vertex shader(s) linked. Fragment Shader not supported by HWERROR: Failed to compile vertex program 'shaders/arb/overlayline.vp' (line 1):ERROR: Failed to compile vertex program 'shaders/arb/overlayline.vp' (line 1):ERROR: JavaScript error: (eval) line 1 ReferenceError: help is not defined @(eval):1ERROR: JavaScript error: (eval) line 1 ReferenceError: ss is not defined @(eval):1ERROR: Failed to link program 'shaders/glsl/model_common.vs'+'shaders/glsl/model_common.fs': Fragment shader(s) failed to link, vertex shader(s) linked. Fragment Shader not supported by HWERROR: Failed to link program 'shaders/glsl/model_common.vs'+'shaders/glsl/model_common.fs': Fragment shader(s) failed to link, vertex shader(s) linked. Fragment Shader not supported by HWIt looks like a hardware issue, and according to Wikipedia (first paragraph in the linked section) your graphics card doesn't support hardware vertex processing. Maybe what you are seeing is artifacts of doing the vertex processing on the CPU? It would be nice if someone else who is more familiar with the renderer could jump in.

All the art assets in SVN are available licensed under CC-BY-CA 3.0.

Whoa, whoa, whoa, lets not even go there. There is no way we are going to dump our open-source pyrogenesis engine with 10+ years of development behind it for an expensive proprietary system.

I was heavily involved in the lobby, but I'm not exactly volunteering to make a mod manager (my hands are quite full at the moment). As far as functionality goes, I would suggest starting with a simple offline in-game mod enabler/disabler before going into more complex use cases (online functionality is a lot more complex than you may think). Again though, starting with a clear design is a big part of making great software.

If you'd like a mod manager implemented, some design mockups and functionality guidelines would be a good start.

Stanford has some really good introductory programming lectures on youtube that I'd recommend watching. They use Java, but the techniques are applicable to almost any language.

I've added support for using the scrollwheel in SVN. Personally, I agree with FeXoR on the civilization selection issue and I think that a good contextual help system would work better over a dedicated page. But I think this discussion is on the brink of descending to a heated argument which is silly because: The GUI department doesn't have the resources to implement major features any time soon.This is a trivial issue. Come on, 28 posts on this alone. Really?As for Pureon's new mockups: I really like them, but the yellow buttons distastefully remind me of our first GUI version.

Currently the dropdowns are entirely made up of placeholder sprites. They'll look much better once pureon creates a style for them.

I can't seem to edit it either. HenryJia: Could you please drop by #0ad-dev on quakenet to debug your issue? Trying to sort this out over the forums doesn't work so well. Here's a preconfigured link to the online IRC client.

I found Google translate did a slightly better job translating from Russian: English: To reply to you comment on game lag, we are aware that the game can slow down significantly in large battles and are working to make it faster. Russian (via Google Translate): Чтобы ответить вам комментировать игру лагом, мы понимаем, что игра может существенно замедлится в крупных сражениях и работаем, чтобы сделать это быстрее.

I would be amazing if we could get this working, it's been something we have been wanting far too long now. As far as how to handle failed tests, maybe we could just run it on the main branch and revert failing commits? (That might be a better use case for git though)

I like the sound, it brings to mind the sound of a metal gate being locked. Could you perhaps try another variation adding a more "woody" sound (for the lack of a better word). Perhaps some sort of thunk of a metal lock hitting wood? (I don't make any of the game's sounds so it's just a suggestion)

It's really good! It is not actually that old, it refers to "today" as 2013.

I think Linux Mint is similar enough to Ubuntu that you should be able to just use the Ubuntu installation instructions on trac. You can use Alt+Enter to switch between windowed mode and full screen. If you don't suppress the warning and just click continue, does it keep popping back up? Also, it would be nice to know how you installed 0AD (package manager or compiled from source).

At this point 0AD should "run" on just about any computer. But, I put run in quotes because on anything older than a few years, 0 A.D. would be painfully slow. Edit: I looked up the specs on your laptop... and I have a nearly identical laptop (Shipped with Win 98 I think) with only a few different perprentials (floppy drive in a laptop FTW!), faster clock speeds (Overclocking!), and more RAM (Salvage!). 0 A.D. barely managed to start on it. I would really recommend getting a new laptop, I think ~3 year old laptops off ebay or craigslist go for pretty cheap.

Is the error constantly repeating? In the last month or so I changed the selection system to use SpatialSubdivison and I think there were some issues at one point where the query would be larger then the map size when using the dev overlay which got the SpatialSubdivison angry.

All usernames are actually lowercase on the backend, the lobby just automatically displays using the casing you typed in on the login screen. For example, if I registered with the username "Josh", I could login using "josh", "jOsH", or even "JOSH". And as the nick system is obfuscated in SVN, you should have much less reason to worry in the next release.

I think you might be a little confused here, most of the dev team actually uses Linux and compiles 0 A.D. with a completely open source toolchain. See BuildInstructions#Linux. (as a side note towards some of your quotes, we don't use Visual Studio's UI development stuff at all)