Re: 3.0-beta 1 is released!
Posted: 27 Oct 2010, 06:52
the game crashed when maroy and i were killing each other, i have two theories, A my computer overall sux, or B the game is still a beta so it will crash...
Maybe provide an option to antialias the minimap and have that OFF by default?cybersphinx wrote:The fixed radar will not be blurred on full zoom steps (one mouse wheel click is ±0.25 zoom steps).hao wrote:One more thing i wanted to discuss here. I'm glad the minimap is fixed now. But i don't like the way it's anti-aliased. I'd prefer inaccurate but crisp and clear not-anti-aliased minimap. At least building and unit dots should be crisp. Probably cliffs and water boundaries also.
Code: Select all
Error occured on Wednesday, October 27, 2010 at 15:30:34.
Program: D:\Games\Warzone 2100 3.0\warzone2100.exe(warzone2100)
Command line: "D:\Games\Warzone 2100 3.0\warzone2100.exe"
Version: Version 3.0-beta1
Distributor: wz2100.net
Compiled on: Oct 25 2010 02:38:00
Compiled by: GCC 4.2.1-sjlj (mingw32-2)
Compiled mode: Release build
Executed on: Wed Oct 27 15:28:58 2010
Pointers: 32bit
Compiled against PhysicsFS version: 1.0.1
Running with PhysicsFS version: 1.0.1
Misc Data:
[15:29:02]OpenGL Vendor : Intel
[15:29:02]OpenGL Renderer : Intel 945GM
[15:29:02]OpenGL Version : 1.4.0 - Build 7.14.10.4906
[15:29:02]Video Mode 1024 x 600 (32 bpp) (fullscreen)
[15:29:05]OpenAL Vendor: Creative Labs Inc.
[15:29:05]OpenAL Version: 1.1
[15:29:05]OpenAL Renderer: Software
[15:29:05]OpenAL Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
[15:29:05]Using language: Systemsprache
[15:30:21]Current Level/map is CAM_1A
D:\Games\Warzone 2100 3.0\warzone2100.exe caused an Access Violation at location 026f3a51 in module C:\WINDOWS\system32\iglicd32.dll Reading from location 04752008.
Log message: info |03:29:02: [screenInitialise] Using VBO extension functions under the core names.
Log message: info |03:29:02: [screenInitialise] OpenGL 2.0 is not supported by your system, using fixed pipeline.
Registers:
eax=04752008 ebx=00000084 ecx=047d87c0 edx=00244018 esi=04752044 edi=02ace440
eip=026f3a51 esp=0022f530 ebp=0022f66c iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210202
Call stack:
026F3A51 C:\WINDOWS\system32\iglicd32.dll:026F3A51
026E0D89 C:\WINDOWS\system32\iglicd32.dll:026E0D89As mentioned elsewhere, the 3.0 version has slightly higher requirements in terms of working OpenGL drivers. You might try upgrading your video driver from the manufacturer's site. Also playing with the display settings like hardware acceleration....I suppose, it's the drivers again, BUT 2.3 didn't work while in beta stage and works perfectly since 2.3.0!! I got hope!
Unfotunately there's no update available! Weather at the Asus site nor at Intel. The log says, it uses the fixed pipeline instead of OGL2. This is okay and I get into the game with a "playable" frame rate (20-25 @ 1024x600), but it crashes something around 3 to 20 seconds after it finished loading without touching anything. But as I said before: It was the same with the 2.3 betas before 2.3.0.stiv wrote:As mentioned elsewhere, the 3.0 version has slightly higher requirements in terms of working OpenGL drivers. You might try upgrading your video driver from the manufacturer's site. Also playing with the display settings like hardware acceleration....I suppose, it's the drivers again, BUT 2.3 didn't work while in beta stage and works perfectly since 2.3.0!! I got hope!
They are slightly outside the range of the MG tower.R Hannay wrote:As you can see in the attachment, the mg towers are not firing when they should be
Huh, that's strange by me too.R Hannay wrote:AlsoAs you can see in the attachment, the mg towers are not firing when they should be..
![]()
I also cannot fire with my units from behind my structures, maybe this is a bug as well?![]()
![]()