Warzone 2100 Forums

vexed wrote:Also, everything still must work @ 640x480, that is the smallest resolution we support.

... and with my current code changes 640x480 and 800x600 wouldnt be supported: Thus I cannot send any commits at the moment.

While the maximized menus look fine... maximized_menus.png ... there is a problem with the position with the design menu. design_menu.png I had to adjust the position of the design elements (right part of design editor) so that they are visible at all. #define RADTLX (OBJ_BACKX + OBJ_BACKWIDTH + BAS...

The right part of the unit editor seems to be invisible (more probably: positioned outside the screen) when applying the patch. So I need to do some research on that, before finally comitting the patch.

Very nice! Probably worth committing? I tried a pull request, but it does not work, because I changed the code in 3.1.1 tag and when I commit to the current master there are lots of commits. pull_request2.png If I do more changes to the game I will switch to the master version, so that I can contri...

In order to compile the RELEASE version of Warzone 3.1.1 I had to compile some libraries by myself: libogg_static.lib libvorbisfile_static.lib libvorbis_static.lib To compile them just open the visual studio 2010 solution files contained in libogg-1.3.1.zip and libvorbis-1.3.4.zip (to be downloaded ...

Now I also maximized the horizontal menu: Necessary code changes:

Sorry, I cannot help you with the distorsion effect. The 3d distorsion has nothing to do with the user interface overlay. So please stick to topic. If you want to further elaborate on the distorsion, you should do this in the thread you linked yourself.

Maximized the menu height to see much more research/structure items at once. What do you think?

This is why I said to compile all the libs yourself, and don't go for the pre-packaged ones. I did not compile any lib by myself and it works well. (Just as information for people with the same system configuration like me) Summarized these are my sources to successfully compile Warzone 3.1.1 DEBUG...

Browsing the net I found many people having problems with the precompiled glew win64bit binaries. Thus I switched to the Win32 binaries now. They seem to work. It finally generated the Warzone2100-Dbg.exe in this folder D:\wz2100-src\repo\data To actually play the game I had to copy to this folder a...

Also, it might help to post full build logs, not just the error part. Sorry, I just did not want to spam you. I though I better focus on what I though is relevant. But here we go with the full log: 1>------ Rebuild All started: Project: exceptionhandler, Configuration: Debug Win32 ------ 2>------ R...

Thanks again for your help :) //edit: please scroll down to the last CODE box of this post. the other informations are already out dated. i keep them here for interested other users having similiar problems. I installed github, forked the wz2100 project to my github account and then cloned the wz210...

Thanks for your help, vexed :) I installed GLEW and missing GL files now as well as the windows SDK. While the GLEW and GL errors disappeared, a "windows.h" related error is still visible (see copy of errors list at the end of this post). The "windows.h" related error lines refer...

Hey together, since I want to develop visual research path system, I need to get Warzone compiled. But I encounter several errors. I'd appriciate your help. My settings: Windows 7 64 bit Visual Studio Express 2012 Warzone source Tag 3.1.1 (from https://github.com/Warzone2100/warzone2100/tree/3.1.1) ...

The only way is fill the map with gravel or snow and use cliff brush, and then fill the rest with grass. Thank you very much for your fast and helpful answer :-) The solution works fine. (I noticed that there are some cliff issues discussed, but I thought its only about the graphical representation...