Wolfire Games Forums

In the arena sometimes the AI manages to choke someone to death before the fight started. They should be disqualified. I also have seen someone "getting choked" by nobody in the second round in the arena and then dying. Should make sure everything is really reset before starting the round....

I really don't know anything about the windows executable so I can only say that opening the main overgrowth.exe or whatever with a hexeditor and search&replace might work but I really don't know. Don't try with text editors like notepad or so, because there's a good chance they'll try to do som...

Jeff some of us or most are having this error: 0(1): error C0118: macros prefixed with 'GL_' are reserved How to fix it? I've tried downloading the alpha manually and verify on steam and nothing works. I'm on Windows 7-64bit The problem is that you have a driver with a glsl compiler that works acco...

The steam version is now playable on gallium drivers if you replace GL_ARB_sample_shading_available both in the binary and in the shaders with sed -i "s/GL_ARB_sample_shading_available/XX_ARB_sample_shading_available/g" Overgrowth.bin.x86 for i in Data/GLSL/*; do sed -i "s/GL_ARB_samp...

#define GL_ARB_sample_shading_available Ok, so I ran grep on the whole overgrowth thing and this string only appears in some checks in some shaders in Data/GLSL/ and in Overgrowth.bin.x86. So patching the binary and the shaders with sed works: sed -i "s/GL_ARB_sample_shading_available/XX_ARB_s...

Well, I tried the steam version and overgrowth tries to make the glsl compiler compile a shader that contains #define GL_ARB_sample_shading_available But the GLSL 1.30 specification says All macro names prefixed with “GL_” (“GL” followed by a single underscore) are also reserved. Am I crazy or shoul...

I am trying to run the version from steam with mesa drivers and I am very confused. I get the error "Macro names starting with "GL_" are reserved." when trying to start a map. So I ran it with MESA_GLSL=dump $HOME/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh ./Overgrowth.b...

On Linux I still needed to add #version 120 to the shaders for intel graphics. I did that this way: http://forums.wolfire.com/viewtopic.php?f=13&t=6868&start=555#p163159 Then it seems to work fine. But "Gladiator" segfaults on start: ***************** Calculating detail textures Fi...

You people are having two problems. 1. The installer per default extracts files to /tmp. I don't know by heart how much it uses but it's definitely much more than 2 GB. To be sure, if you have less than 10 GB free in /tmp, use --target=/some/directory for the installer and be careful, it will delete...

Windlord wrote:There used to be a bug tracking system. Trac, I believe.

Unfortunately it was not used enough.

But what would have been the harm in keeping it running then?

On linux I'm still getting Removed 5148 degenerate triangles. *** glibc detected *** ./overgrowth.bin.x86_64: free(): invalid next size (normal): 0x00007f461461bc60 *** ======= Backtrace: ========= /lib/libc.so.6(+0x784b6)[0x7f46794594b6] ./overgrowth.bin.x86_64[0x42051e] ./overgrowth.bin.x86_64[0x4...

- Fixed major Linux crash bug (Edward Rudd) 1. Yay, segfault with boost resolved. 2. *** glibc detected *** /home/chris/games/Overgrowth/overgrowth.bin.x86_64: free(): invalid next size (normal): 0x00007fff8ce93110 *** Backtrace: #0 0x00007ffff118cfa5 in raise () from /lib/libc.so.6 #1 0x00007ffff1...

So it's at least three different: 0x0000000000449640 in std::vector<int, std::allocator<int> >::push_back(int const&) () 0x000000000092986f in btQuantizedBvh::setInternalNodeAabbMin(int, btVector3 const&) () 0x0000000000af53d3 in asIScriptFunction::asIScriptFunction() () (http://forums.wolfi...

I too got a segfault and reported it for the last alpha. You can view a backtrace to see if it segfault is happening in a similar way. So instead of only having "it crashes for me too" we could see if it is only one problem or several. :) gdb ./overgrowth.bin.x86_64 ... (the debugger start...

Mhm, shaders don't compile but that is almost surely not your fault but the radeon driver's. Fragment shader failed to compile with the following errors: ERROR: 0:99 error(#110) Invalid Directive include ERROR: error(#273) 1 compilation errors. No code generated When you write not supported by Wolfi...