DyDo 2.2.2, AI for skirmish games and challenges

[DylanDog]

Last Version: 04 August 2010 - DyDo-AI_2.2.3.wz download.

DyDo is a not-cheating AI ("mod") with multiple personalities and can be used for skirmish, challenges and multi-player games, it cannot be used in campaigns.

DyDo "mod" comes with a modified scavenger AI and with challenges, the maps related to the challenges can be found here.

It can be downloaded also from Warzone2100 SVN. More info about this mod can be found on the DyDo homepage.
Report any bug here.

To play with DyDo follow general instructions on how to use mods.

Enjoy it.

[zydonk]

I've had to go back to v2.1 of DyDo to find one that will work with WZ2.3. Prior to that i had been using an early 2.2 version of WZ with a 1.n version of DyDo, as I couldn't be bothered matching WZ vers with DyDo vers beyond that (no apparent gaming advantage).

I'm stating this for the record: I'm sure DylanDog is aware of the general situation. But I was surprised that the ver of DyDo included with WZ2.3 failed. WarZombie works.

[kringled]

I didn't have any problems starting the included dydo-ai mod, other than the files name changed between 2.3 RC1a and 2.3.0 (It's now dydo-ai.mod.wz).

Keith

[DylanDog]

I've had to go back to v2.1 of DyDo to find one that will work with WZ2.3. Prior to that i had been using an early 2.2 version of WZ with a 1.n version of DyDo, as I couldn't be bothered matching WZ vers with DyDo vers beyond that (no apparent gaming advantage).

There is an issue with the scavenger AI. Try by deactivating scavenger or download the last scavenger AI version form the DyDo website.

[zydonk]

Tried again with DyDo 2.1.2 with scav disabled. Then tried it with the scav ai fix added, again scav mode disabled. Same error message in both cases. Including stderr for your info.

[kringled]

Zydonk, did you just try to load the new dydo-scav at the same time as dydo-2.1.2? What I did, which worked for the same error on my system, was unzip dydo-2.1.2, replace the scavfact.slo/vlo files in it with the new ones from the dydo-scav download, and rezip dydo-2.1.2. For me, it then loads maps without fatal errors. Just disabling scavengers from the map selection screen (or playing on a map without scavengers) doesn't seem to help.

Keith

[DylanDog]

Ok, I have now added on the DyDo webpage DyDo-AI 2.1.2b with the correct version of the scavenger AI.

Sorry for the inconvenience.

[zydonk]

Ok, I have now added on the DyDo webpage DyDo-AI 2.1.2b with the correct version of the scavenger AI.

Sorry for the inconvenience.

That does the trick. Thanks. Saves me from having to do what kringled suggests, but thanks there too in any case.

[sensor]

problems; game be closes and the desk top of computer appears (maps 4c - Rush),dydo-ai_2.1.2b

[Black Project]

Can you upload the .RPT file too?

It will be much easier to discover what's wrong with DyDo AI in the .RPT file

BP

[sensor]

file RPT no searching...
he should to come into being he in case this kind of mistakes ?

[DylanDog]

problems; game be closes and the desk top of computer appears (maps 4c - Rush),dydo-ai_2.1.2b

Difficult to understand what happens. From the stderr.txt file I see an error (#1758) appearing but this is not a crushing one (at least in Windows...do you have Linux? ) and it is neither an error which reduces DyDo strength.

[Black Project]

file RPT no searching...

Do you have checked the following directory to find the file?

"My documents/Warzone 2100 2.3/logs/Warzone2100.RPT" (NOTE: For Windows only, since i don't know which OS you are using, i'm trying to help you and Dylan Dog too )

BP

[sensor]

searching...
system Windows XP 2003 + Service Pack3

[Black Project]

Code: Select all

Error occured on Saturday, May 1, 2010 at 21:53:38.

Program: D:\Gry\Warzone 2100\warzone2100.exe(warzone2100)
Command line: "D:\Gry\Warzone 2100\warzone2100.exe" "--mod" "dydo-ai_2.1.2b.wz" 
Version: Version 2.3.0
Distributor: wz2100.net
Compiled on: Apr 24 2010 12:00:16
Compiled by: GCC 4.4.2
Compiled mode: Release build
Executed on: Sat May 01 21:34:28 2010

Pointers: 32bit

Compiled against PhysicsFS version: 1.0.1
Running with PhysicsFS version: 1.0.1

Misc Data:
[21:34:29]mod: dydo-ai_2.1.2b.wz
[21:34:29]OpenGL Vendor : NVIDIA Corporation
[21:34:29]OpenGL Renderer : GeForce 6600/PCI/SSE2/3DNOW!
[21:34:29]OpenGL Version : 2.1.2
[21:34:29]OpenGL GLSL Version : 1.20 NVIDIA via Cg compiler
[21:34:29]Video Mode 1024 x 768 (32 bpp) (fullscreen)
[21:34:30]OpenAL Vendor: Creative Labs Inc.
[21:34:30]OpenAL Version: 1.1
[21:34:30]OpenAL Renderer: Software
[21:34:30]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
[21:34:30]Using language: Polski
[21:34:43]Current Level/map is Sk-Rush


D:\Gry\Warzone 2100\warzone2100.exe caused an Access Violation at location 0043c99b in module D:\Gry\Warzone 2100\warzone2100.exe Reading from location 000000a8.

Log message: error   |09:44:54: [moveDroidToNoFormation] Bad movement position
Log message: error   |09:44:54: [moveDroidToNoFormation] Assert in Warzone: ../../../src/move.c:443 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:54: [SendDroidMove] SendDroidMove: Invalid move order
Log message: error   |09:44:54: [SendDroidMove] Assert in Warzone: ../../../src/multibot.c:447 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:55: [moveDroidToNoFormation] Bad movement position
Log message: error   |09:44:55: [moveDroidToNoFormation] Assert in Warzone: ../../../src/move.c:443 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:55: [SendDroidMove] SendDroidMove: Invalid move order
Log message: error   |09:44:55: [SendDroidMove] Assert in Warzone: ../../../src/multibot.c:447 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:56: [moveDroidToNoFormation] Bad movement position
Log message: error   |09:44:56: [moveDroidToNoFormation] Assert in Warzone: ../../../src/move.c:443 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:56: [SendDroidMove] SendDroidMove: Invalid move order
Log message: error   |09:44:56: [SendDroidMove] Assert in Warzone: ../../../src/multibot.c:447 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:57: [moveDroidToNoFormation] Bad movement position
Log message: error   |09:44:57: [moveDroidToNoFormation] Assert in Warzone: ../../../src/move.c:443 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:57: [SendDroidMove] SendDroidMove: Invalid move order
Log message: error   |09:44:57: [SendDroidMove] Assert in Warzone: ../../../src/multibot.c:447 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:58: [moveDroidToNoFormation] Bad movement position
Log message: error   |09:44:58: [moveDroidToNoFormation] Assert in Warzone: ../../../src/move.c:443 (x > 0 && y > 0), last script event: 'N/A'
Log message: error   |09:44:58: [SendDroidMove] SendDroidMove: Invalid move order
Log message: error   |09:44:58: [SendDroidMove] Assert in Warzone: ../../../src/multibot.c:447 (x > 0 && y > 0), last script event: 'N/A'

Registers:
eax=00000000 ebx=00000026 ecx=0000003b edx=0000005c esi=0000003b edi=0002ab20
eip=0043c99b esp=0022fa00 ebp=0022fa68 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00210246

Call stack:
0043C99B  D:\Gry\Warzone 2100\warzone2100.exe:0043C99B  droidStartBuild  /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/droid.c:1132
00405D16  D:\Gry\Warzone 2100\warzone2100.exe:00405D16  actionUpdateDroid  /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/action.c:1913
0043D74C  D:\Gry\Warzone 2100\warzone2100.exe:0043D74C  droidUpdate  /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/droid.c:850
0048A34B  D:\Gry\Warzone 2100\warzone2100.exe:0048A34B  gameLoop  /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/loop.c:305
0048CF27  D:\Gry\Warzone 2100\warzone2100.exe:0048CF27  SDL_main  /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/main.c:823
005A8ABE  D:\Gry\Warzone 2100\warzone2100.exe:005A8ABE
005A8B74  D:\Gry\Warzone 2100\warzone2100.exe:005A8B74
005A8529  D:\Gry\Warzone 2100\warzone2100.exe:005A8529
004010A7  D:\Gry\Warzone 2100\warzone2100.exe:004010A7  __mingw_CRTStartup  /home/ron/devel/debian/mingw32-runtime/mingw32-runtime-3.13/build_dir/src/mingw-runtime-3.13-20070825-1/crt1.c:237
00401123  D:\Gry\Warzone 2100\warzone2100.exe:00401123

0043C99B D:\Gry\Warzone 2100\warzone2100.exe:0043C99B droidStartBuild /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/droid.c:1132
00405D16 D:\Gry\Warzone 2100\warzone2100.exe:00405D16 actionUpdateDroid /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/action.c:1913
0043D74C D:\Gry\Warzone 2100\warzone2100.exe:0043D74C droidUpdate /home/admins/wz2.x/2.3.0/win32/build/src/../../../src/droid.c:850

I suspect that the quoted lines refers to a issue with the update of droids and production of these, when DyDo have new body/propulsion/weapon available to make these new droids.

No. I'm not a scripting expert, i'm just trying to discover, IMHO, what's wrong with the AI.

Does someone got a crash too on DyDo 2.1.2b like sensor got one? I'm smelling new DyDo version with new bugfixes.

BP