game crashes 80% of the time

June 25, 2009 4:44 PM from

this sucks. My drivers are updated, I'm running a 4850, 4g RAM and a quadcore at 2.55 Ghz. This has never happened in previous builds

see below. If you need the full version let me know:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x76ee2f55
attempted to read memory at 0x0000000d

Program : C:\Program Files (x86)\Stardock Games\Demigod\bin\Demigod.exe
Cmd line arguments :

Callstack:
WahReferenceContextByHandle + 5 bytes ((Unknown)(0) + 0 bytes)

Reactor version: 1.00.56
Demigod version MAIN.1.10.0146
Last 100 lines of log...

A full record of the log is stored in the Demigodlog.txt file

info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request

4,606 views 10 replies

Reply #1 June 25, 2009 4:46 PM from

Demigod Forums Top

Did it create a .dmp file in My Documents\My Games\Gas Powered Games\Demigod? If so, please send that file and this log to [email protected] so they can pass it to the devs.

Reply #2 June 25, 2009 9:01 PM from

Demigod Forums Top

it did, I'll send it now, thanks

Curtains - Customize Windows with additional styles

Reply #3 June 26, 2009 2:03 PM from

Demigod Forums Top

Same here. Crashed yesterday, i've sent the dmp file. Today, again. Never had this problem before. It's only since the 1.1 patch.

Reply #4 June 26, 2009 11:58 PM from

Demigod Forums Top

I too crashed

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x772cef59
attempted to write memory at 0x8bc44d93

Program : C:\Program Files (x86)\Stardock Games\Demigod\bin\Demigod.exe
Cmd line arguments :

Callstack:
RtlLeaveCriticalSection + 9 bytes ((Unknown)(0) + 0 bytes)

Reactor version: 1.00.56
Demigod version MAIN.1.10.0146
Last 100 lines of log...

A full record of the log is stored in the Demigodlog.txt file

info:   SelectionMeshSizeY=4,
info:   SelectionMeshSizeZ=4,
info:   SelectionMeshUseTopAmount=0,
info:   SelectionSizeX=5,
info:   SelectionSizeY=1,
info:   SelectionSizeZ=1,
info:   SelectionThickness=0,
info:   SelectionYOffset=0.5,
info:   Shop=__blueprints.ugbshop08.Shop,
info:   SizeX=4,
info:   SizeY=4,
info:   SizeZ=4,
info:   Source="/units/ug/b/ugbshop08/ugbshop08_unit.bp",
info:   Steering=__blueprints.ugbshop08.Steering,
info:   StrategicIconName="",
info:   Weapon=__blueprints.ugbshop08.Weapon
info: }
debug: Loading module '\000/lua/ui/game/zoomslider.lua\000'
debug: Loading module '\000/projectiles/healingstatueeffect01/healingstatueeffect01_script.lua\000'
debug: Loading module '\000/lua/sim/projectile.lua\000'
debug: Loading module '\000/lua/formations.lua\000'
debug: Loading module '\000/lua/formations.lua\000'
info: If we are trying to attack the same location, ignore the new request
debug: Loading module '\000/lua/sim/tasks/seedbuild.lua\000'
debug: Loading module '\000/lua/common/validatebuild.lua\000'
info: If we are trying to attack our current target, ignore the new request
debug: Loading module '\000/lua/usermusic.lua\000'
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
debug: Loading module '\000/projectiles/bolt01/bolt01_script.lua\000'
debug: Loading module '\000/projectiles/spellslow01/spellslow01_script.lua\000'
debug: Loading module '\000/projectiles/fireball01/fireball01_script.lua\000'
debug: Loading module '\000/projectiles/arrow02/arrow02_script.lua\000'
debug: Loading module '\000/projectiles/fireball03/fireball03_script.lua\000'
debug: Loading module '\000/lua/user/abilitycommand.lua\000'
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
debug: Loading module '\000/projectiles/bolt02/bolt02_script.lua\000'
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: Setting audio parameter 'LEVEL' to value '2.000000'
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
debug: Loading module '\000/projectiles/frostball01/frostball01_script.lua\000'
info: If we are trying to attack the same location, ignore the new request
warning: Attempt to buy invalid item
warning: Unit = \0003145728
info: If we are trying to attack the same location, ignore the new request
info: Setting audio parameter 'LEVEL' to value '3.000000'
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: KILL VO : [KillHero_hema01]
debug: Loading module '\000/lua/simcallbacks.lua\000'
debug: Loading module '\000/lua/sim/simresourceviewer.lua\000'
debug: Loading module '\000/lua/simping.lua\000'
info: If we are trying to attack the same location, ignore the new request
debug: Loading module '\000/lua/user/powerupaction.lua\000'
debug: Loading module '\000/lua/sim/tasks/poweruppickuptask.lua\000'
info: If we are trying to attack the same location, ignore the new request
info: Sim crashed hard in DoSimBeat(): ...\demigod\dgdata.zip\lua\ui\game\hud_msgs_failure.lua(20): attempt to call method `SetText' (a nil value)
      stack traceback:
      ...\demigod\dgdata.zip\lua\ui\game\hud_msgs_failure.lua(20): in function <...\demigod\dgdata.zip\lua\ui\game\hud_msgs_failure.lua:19>
      ...ames\demigod\dgdata.zip\lua\common\validateskill.lua(21): in function <...ames\demigod\dgdata.zip\lua\common\validateskill.lua:17>
      ...\stardock games\demigod\dgdata.zip\lua\sim\skill.lua(118): in function <...\stardock games\demigod\dgdata.zip\lua\sim\skill.lua:116>

Reply #5 June 27, 2009 3:30 AM from

Demigod Forums Top

i´m getting unhandled exception every game now. even in singleplayer!!

here is a log from a singleplayer game:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x006ed6d4
    attempted to read memory at 0x000000d0

Program : D:\Demigod\bin\Demigod.exe
Cmd line arguments :

Callstack:
    Unknown symbol (address 0x006ed6d4)

Reactor version: 1.00.56
Demigod version MAIN.1.10.0146
Last 100 lines of log...

A full record of the log is stored in the Demigodlog.txt file

debug: Loading module '\000/lua/sim/ai/heroes/actions/useachievementitemsactions.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/actions/useitemsactions.lua\000'
debug: Loading module '\000/units/heroes/hema01/hema01_aiactions.lua\000'
debug: Loading module '\000/units/heroes/hepa01/hepa01_aiactions.lua\000'
debug: Loading module '\000/units/heroes/hgsa01/hgsa01_aiactions.lua\000'
debug: Loading module '\000/units/heroes/hoak/hoak_aiactions.lua\000'
debug: Loading module '\000/units/heroes/hqueen/hqueen_aiactions.lua\000'
debug: Loading module '\000/units/heroes/hrook/hrook_aiactions.lua\000'
debug: Loading module '\000/units/heroes/hsedna/hsedna_aiactions.lua\000'
debug: Loading module '\000/units/heroes/hvampire/hvampire_aiactions.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/sensors/buffsensors.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/sensors/ctfsensors.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/sensors/distancesensors.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/sensors/goapsystemsensors.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/sensors/nearbysensors.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/sensors/unitstatussensors.lua\000'
debug: Loading module '\000/lua/sim/ai/heroes/sensors/warstatussensors.lua\000'
debug: Loading module '\000/units/heroes/hsedna/hsedna_aisensors.lua\000'
debug: Loading module '\000/units/heroes/hema01/hema01_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hepa01/hepa01_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hgsa01/hgsa01_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hoak/hoak_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hoculus/hoculus_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hqueen/hqueen_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hrook/hrook_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hsedna/hsedna_aiblueprint.lua\000'
debug: Loading module '\000/units/heroes/hvampire/hvampire_aiblueprint.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/goals/basicgoals.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/actions/capturepointactions.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/actions/ctfflagactions.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/actions/laneactions.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/actions/strongholdactions.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/actions/structuredefensefortactions.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/capturepointsensors.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/ctfsensors.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/herostatussensors.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/lanesensors.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/strongholdsensors.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/structuredefensefortsensors.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/structuresensors.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/sensors/warstatussensors.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/assassinate.lua\000'
debug: Loading module '\000/lua/sim/ai/squad.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/attackstronghold.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/attackstructuredefensefort.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/capturepoint.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/ctfcapture.lua\000'
debug: Loading module '\000/lua/sim/carryableflag.lua\000'
debug: Loading module '\000/lua/sim/forgeunit.lua\000'
debug: Loading module '\000/lua/sim/unit.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/ctfdefend.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/defendflag.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/defendstronghold.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/defendstructuredefensefort.lua\000'
debug: Loading module '\000/lua/sim/ai/squads/pushlane.lua\000'
debug: Loading module '\000/lua/sim/stattracking.lua\000'
debug: Loading module '\000/lua/sim/achievements.lua\000'
debug: Loading module '\000/lua/scenarioenvironment.lua\000'
info: Loading save file: \000/maps/MAP10/MAP10_save.lua
info: Loading script file: \000/maps/MAP10/MAP10_script.lua
debug: Loading module '\000/lua/sim/conquest.lua\000'
debug: Loading module '\000/lua/sim/victory.lua\000'
debug: Loading module '\000/lua/common/preload.lua\000'
debug: Loading module '\000/lua/sim/simcamera.lua\000'
debug: Loading module '\000/lua/system/singleevent.lua\000'
debug: Loading module '\000/lua/gamecolors.lua\000'
debug: Loading module '\000/lua/sim/conquestglobals.lua\000'
warning: Setting pathfinder depth to - 6000
debug: Loading module '\000/lua/aibrain.lua\000'
debug: Loading module '\000/lua/sim/ai/brainplanner.lua\000'
debug: Loading module '\000/lua/sim/ai/herogoap.lua\000'
debug: Loading module '\000/lua/sim/skill.lua\000'
debug: Loading module '\000/lua/common/validateskill.lua\000'
debug: Loading module '\000/lua/sim/ai/heroaiaction.lua\000'
debug: Loading module '\000/lua/sim/ai/heroaigoal.lua\000'
debug: Loading module '\000/lua/sim/ai/heroaisensor.lua\000'
debug: Loading module '\000/lua/sim/ai/heroaiworldstate.lua\000'
debug: Loading module '\000/lua/sim/ai/strategicgoap.lua\000'
debug: Loading module '\000/lua/sim/ai/strategicaction.lua\000'
debug: Loading module '\000/lua/sim/ai/strategicgoal.lua\000'
debug: Loading module '\000/lua/sim/ai/strategicsensor.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/laneasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategicasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/flagasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/strongholdasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/enemyasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/herobrainasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/friendlyasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/teambrainasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/structuredefensefortasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategic/assets/ctfflagasset.lua\000'
debug: Loading module '\000/lua/sim/ai/strategicworldstate.lua\000'
debug: Loading module '\000/lua/sim/structureunit.lua\000'
debug: Loading module '\000/lua/sim/characterunit.lua\000'
debug: Loading module '\000/lua/sim/character.lua\000'
debug: Loading module '\000/lua/factions.lua\000'
debug: Loading module '\000/lua/sim/herounit.lua\000'
debug: Loading module '\000/lua/sim/inventory.lua\000'
debug: Loading module '\000/lua/common/heroutil.lua\000'
info: Sim::Create() crashed: attempt to get as string a nil value
      stack traceback:

Reply #6 June 27, 2009 1:10 PM from

Demigod Forums Top

Please see below and start doing so if you have not already. The more info they have, the better our chances of seeing this fixed. The logs go a long way in identifying the reasons for crashes.

I'm going to start creating posts for my crashes. Someone posted this list before, but please do the same if you are having crash issues.

1. Identify whether any problem you are having is considered a connectivity problem or "other"

2. If it is a connectivity problem: create a thread in the "Demigod Connectivity Help" forum: http://forums.demigodthegame.com/forum/559

3. If it is something else, create a thread in the "Demigod Problem Reports" forum: http://forums.demigodthegame.com/forum/549

4. If you really want to help: go to your My Documents->My Games->Gas Powered Games->Demigod folder, zip your ImpulseReactor.log, DemigodLog.txt, CVPMultiplayerEngine_XXX.csv and MiniDump.dmp files, and email them to [email protected]. Make sure you mention the thread title in your email. Even more helpful would be to provide a link back to your thread in the email.

5. If you really want to help: describe everything about the problem, no matter how trivial it seems, in the thread and the email

Reply #7 June 27, 2009 5:02 PM from

Demigod Forums Top

AHHRGH!!

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x022d26d5
attempted to read memory at 0x00000001

Program : D:\Program Files\Stardock Games\Demigod\bin\Demigod.exe
Cmd line arguments :

Callstack:
Unknown symbol (address 0x022d26d5)

Reactor version: 1.00.56
Demigod version MAIN.1.10.0146
Last 100 lines of log...

A full record of the log is stored in the Demigodlog.txt file

info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: Can't use \000HQueenBrambleShield03
info: If we are trying to guard ourselves, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack the same location, ignore the new request
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
info: If we are trying to attack our current target, ignore the new request
warning: *ACHIEVEMENT WARNING: No tracking of goalIndex = goal1 - achievement = hoak17
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack the same location, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request
info: If we are trying to attack our current target, ignore the new request

Reply #8 June 27, 2009 7:13 PM from

Demigod Forums Top

so I can confirm that this is not a result of too many APM, as claimed in another crash post. I know this because I just abort crashed in the start game lobby oO

The host had opened the all slots and people were joining and leaving very very quickly

Last few lines of Impulse log:

[06-27-2009 17:04:17 513] Message received by CVPMultiplayerEngine: MP_MSG_NAT_PLAYER_ID_PONG from 83.78.58.44:6112 GUID: 603447895.4009552371.3739139500.3725026922
[06-27-2009 17:04:17 513] Processing MP_MSG_NAT_PLAYER_ID_PONG (PlayerID=11146, TitleID=444, GameID=682973, OtherPlayerID=67358
[06-27-2009 17:04:17 513] Processing MP_MSG_NAT_PLAYER_ID_PONG - we ARE connected to player 67358 (their status 1597995957, our status 55102904)
[06-27-2009 17:04:17 513] Sending MP_MSG_NAT_PLAYER_ID_COMPLETE to player 67358 and to us (status 2)
[06-27-2009 17:04:17 513] UpdateDatabaseRecord with row ID 11146 and priority 0
[06-27-2009 17:04:17 545] Message received by CVPMultiplayerEngine: MP_MSG_NAT_PLAYER_ID_COMPLETE from 192.168.2.2:6112 GUID: 4294967295.4294967295.4294967295.4294967295
[06-27-2009 17:04:17 546] Processing MP_MSG_NAT_PLAYER_ID_COMPLETE (PlayerID=11146, TitleID=444, GameID=682973, OtherPlayerID=67358
[06-27-2009 17:04:17 549] Processing MP_MSG_NAT_PLAYER_ID_COMPLETE - sending MP_MSG_NAT_COMPLETE to ourself
[06-27-2009 17:04:17 579] Message received by CVPMultiplayerEngine: MP_MSG_NAT_COMPLETE from 192.168.2.2:6112 GUID: 4294967295.4294967295.4294967295.4294967295
[06-27-2009 17:04:17 579] Server says that NAT is complete.
[06-27-2009 17:04:17 579] Player ID=67358 My Player ID=11146
[06-27-2009 17:04:17 579] Num players: 1
[06-27-2009 17:04:17 579] Player ID in list: 11146
[06-27-2009 17:04:17 579] IsConnected
[06-27-2009 17:04:17 579] NAT COMPLETE: Sender is not me.
[06-27-2009 17:04:17 579] NAT COMPLETE: connection is valid.
[06-27-2009 17:04:17 579] NAT COMPLETE: already connected: 0 bIsConnected: 1
[06-27-2009 17:04:17 580] NewLobby Code!
[06-27-2009 17:04:17 580] We are now fully connected
[06-27-2009 17:04:17 580] Proxying-Via-Peer: (REGISTERING CONNECTED PLAYER) Registering player # 67358 at 83.78.58.44:6112 (At index 8)
[06-27-2009 17:04:17 580] Calling NotifyOtherPlayersOfNewConnection for Player 67358 at 83.78.58.44:6112
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 27670 regarding us being connected to player 67358
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67358 regarding us being connected to player 27670
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 52852 regarding us being connected to player 67358
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67358 regarding us being connected to player 52852
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 66088 regarding us being connected to player 67358
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67358 regarding us being connected to player 66088
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 53168 regarding us being connected to player 67358
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67358 regarding us being connected to player 53168
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 65339 regarding us being connected to player 67358
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67358 regarding us being connected to player 65339
[06-27-2009 17:04:17 581] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67744 regarding us being connected to player 67358
[06-27-2009 17:04:17 582] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67358 regarding us being connected to player 67744
[06-27-2009 17:04:17 582] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 49176 regarding us being connected to player 67358
[06-27-2009 17:04:17 582] Proxying-Via-Peer: Sending MP_MSG_OTHER_PLAYERS_CONNECTED to player 67358 regarding us being connected to player 49176
[06-27-2009 17:04:17 584] OnNATSuccess called
[06-27-2009 17:04:17 584] Now fully connected - 'NAT SUCCESS!' (CONNECTION ACTIVITY)
[06-27-2009 17:04:17 584] OnNATSuccess - adding new process
[06-27-2009 17:04:17 584] ShutdownPingResponseTimeoutProcesses: 0 processes
[06-27-2009 17:04:17 584] UpdateDatabaseRecord with row ID 11146 and priority 0
[06-27-2009 17:04:17 615] COnNatSuccessProcess::OnUpdate

ANd last few lines of Demigodlog:

info: LOBBY: Refreshing Available Games List from Impulse.
info: You are not logged in.
debug: Loading module '\000/lua/ui/menus/main/main.lua\000'
debug: Loading module '\000/lua/ui/menus/menubuttonframe.lua\000'
warning: Screen has no bindings: \000main
debug: Loading module '\000/lua/ui/menus/mpchoosefaction/mpchoosefaction.lua\000'
debug: Loading module '\000/lua/ui/menus/mpinstantactionheroselect/mpinstantactionheroselect.lua\000'
warning: Error opening movie
warning: Screen has no bindings: \000mpinstantactionheroselect
debug: Loading module '\000/lua/ui/menus/mplogin/mplogin.lua\000'
debug: Loading module '\000/lua/ui/controls/combo.lua\000'
info: *DEBUG: OnHide: \000false
info: *DEBUG: OnHide: \000true
debug: Loading module '\000/lua/ui/menus/mpstandings/mpstandings.lua\000'
debug: Loading module '\000/lua/ui/menus/mpsub/mpsub.lua\000'
info: *DEBUG: OnHide: \000false
info: *DEBUG: OnHide: \000true
debug: Loading module '\000/lua/ui/menus/mptournamentcomplete/mptournamentcomplete.lua\000'
debug: Loading module '\000/lua/ui/menus/mptournamentheroselect/mptournamentheroselect.lua\000'
warning: Error opening movie
debug: Loading module '\000/lua/ui/menus/options/options.lua\000'
debug: Loading module '\000/lua/maui/slider.lua\000'
debug: Loading module '\000/lua/options/module_keybinds.lua\000'
debug: Loading module '\000/lua/keymap/userbindablecommands.lua\000'
debug: Loading module '\000/lua/keymap/properkeynames.lua\000'
debug: Loading module '\000/lua/ui/menus/profile/profile.lua\000'
debug: Loading module '\000/lua/ui/menus/replays/replays.lua\000'
debug: Loading module '\000/lua/ui/menus/spstandings/spstandings.lua\000'
debug: Loading module '\000/lua/ui/menus/spsub/spsub.lua\000'
info: *DEBUG: OnHide: \000false
info: *DEBUG: OnHide: \000true
debug: Loading module '\000/lua/ui/menus/sptournamentcomplete/sptournamentcomplete.lua\000'
debug: Loading module '\000/lua/ui/menus/sptournamentcontinue/sptournamentcontinue.lua\000'
debug: Loading module '\000/lua/ui/menus/sptournamentnew/sptournamentnew.lua\000'
warning: Error opening movie
debug: Loading module '\000/lua/ui/menus/sptournamentsub/sptournamentsub.lua\000'
info: *DEBUG: OnHide: \000false
info: *DEBUG: OnHide: \000true
info: MUSIC : Activating cue [Main_Menu]

Reply #9 July 2, 2009 10:32 PM from

Demigod Forums Top

well whatever you guys did to the servers really solves some issues on my side - namely, it keeps me from attempting to play at all

This is because I know the result will be (in order of appearance)

1. a crash on Demigod client initiation

2. a crash of Impulse *and* Demigod

3. a crash in game selection lobby

4. a crash in game lobby after joining

5. a crash while playing

6. a crash immediately upon finishing the game

7. complete and persistent inability to re-login after crash, as apparently my password and/or login are incorrect. This has always indicated server lag in the past, but today I had the privilege of attempting this over the space of an hour twice, and the attempts were seperated by 10 hours - now that's some hefty lag :D

So I'm gonna take the 4th of July weekend and drive around the state, maybe when I come back all of this will be resolved. Good luck with that, and have a great weekend

$\o/$

Reply #10 July 3, 2009 1:51 AM from

Demigod Forums Top

Ke5trl - if you haven't already tried a reinstall, please do so. My crashes were on and off... I've been playing for a few days now without issue. If you are annoyed and want to go to the extreme, uninstall, delete any remaining directories from the game, and then reinstall.

I have been sending my crash logs, etc, anytime I have an issue now.

Welcome Guest! Please take the time to register with us.

Richer content, access to many features that are disabled for guests like commenting and posting on the forums.
Access to a great community, with a massive database of many, many areas of interest.
Access to contests & subscription offers like exclusive emails.
It's simple, and FREE!