Crash Offsets
-
Here’s a new plugin for the content 124bd problem. This one only logs on a bad address (also eliminating the crash), so you should have no problem on a running server. It will generate EXE\EngBase-0124BD-bad.txt, logging the values of the previous call.
-
:Reviving stale thread…
Seeing the same 0x47bc4 error in content.dll. What’s interesting me is the idea that it’s related to NPC chatter. I can hear the NPCs chattering to each other, and when I ‘hail’ them. They seem to know who they are but most do not seem to know where they are going or where they’re from.
Every now and again I’ll get the ‘this is patrol white-1, we’re out of the tau-31 system’ or something like that, but in most cases the chatter just dead ends after the we’re out of the/ and no system or base is indicated.
Where would that info be added to the NPCs characteristics? It seems to be related to the added NPCs in the system (Order and DSE in Omicron Minor) and not elsewhere in the universe.
Also, most times you hail an NPC you get the identifier and the destination or origin points. If you want more you have to keep ‘hailing’ them. Usually within a couple hails they start getting rude, but they don’t talk to you without you hitting the hail button.
In some cases I’m experiencing a chatterbox. I’ll hail once and the response will be something like:
idenifier, (chokes just before stating origin)
then an additional choked message will also be played. Most I’ve had were three statements with one press of the hail button, all choked. -
Assuming these are new bases and systems?
-
robocop wrote:
Where would that info be added to the NPCs characteristics? It seems to be related to the added NPCs in the system (Order and DSE in Omicron Minor) and not elsewhere in the universe.Looking at the decoded wav files, only system St01 has a refer line, and there are no St base lines at all.
-
DwnUndr wrote:
Assuming these are new bases and systems?Good God Almighty…
-
I might’ve isolated that content.dll error ( 0x47bc4 ) to a bad encounter. Specifically, I had neglected to add a formation to the factionprop of the faction spawning added armored transport spawns. Once I added the formation to the factionprop, the content error has not reappeared
-
I have strange crashes at content.dll 0005ccd4 sometimes when docking to tradelane.
Anyone experienced this?
-
Getting a strange ctd at offset 0000109c in engclass.dll
engclass is ver 2.0 for multicruise
ctd is reproduce-able by either scanning npcs/players in space or opening the personal cargo window on the hud.
only seems to affect capships. currently testing the rh_cruiser and battleship (you have to love turret zoom for this) tested the engine on an eagle and it worked fine
-
adoxa wrote:
Looks to be a missing/mistyped formation.Maybe. I have changed TTX of vanilla ships, have made pilotable Lifter and Repair ship from vanilla, have added some new ships. And all
SDK - yours, JFLP ))
FLScan 1.3 says 0 errorsMystic…
-
@Helloween: It really looks like it wants a formation - it’s the function to test if the position is for NPC or player. It’s crashing because it can’t read the position data (if you look at the report, ECX should be 0). It appears neither FLScan nor FLEC pick up this error. Here’s a perl script to test it (run it in DATA\MISSIONS).
open(FORMATIONS, 'formations.ini') || die('no formations.ini'); while (<formations>) { if (/^nickname = (.*)/) { $formations{$1} = 1; } } close(FORMATIONS); open(PROPS, 'faction_prop.ini') || die('no faction_prop.ini'); while (<props>) { ++$line; if (/^formation = .*?, (.*)/) { if (!$formations{$1}) { print "Missing formation '$1' at line $line.\n"; } } }</props></formations> -
Thx Adoxa! Now i know where to dig )
-
adoxa wrote:
Here’s a new plugin for the content 124bd problem. This one only logs on a bad address (also eliminating the crash), so you should have no problem on a running server. It will generate EXE\EngBase-0124BD-bad.txt, logging the values of the previous call.2011-06-30 02:29:37.481: Common.0630E681
Bad address = CDCDCDCD
Previous call:
cmp -> equipment\models\weapons\ku_hornet_launcher.cmp
part -> k_hornetlauncher_base_lod1020829120522.3db2011-06-30 02:45:49.832: Common.0630E681
Bad address = CDCDCDCD
Previous call:
part -> equipment\models\torpedoes\ge_torpedo.3db2011-06-30 21:56:49.318: Common.0630E681
Bad address = CDCDCDCD
Previous call:
cmp -> equipment\models\turret\li_turret03.cmp
part -> base021119202809.3db2011-07-01 21:59:10.152: Common.0630E681
Bad address = CDCDCDCD
Previous call:
cmp -> equipment\models\weapons\ku_hornet_launcher.cmp
part -> k_hornetlauncher_base_lod1020829120522.3db2011-07-02 01:51:27.616: Common.0630E681
Bad address = CDCDCDCD
Previous call:
cmp -> equipment\models\turret\ku_turret04.cmp
part -> base021119202046.3dbGot crashes - where to dig?
-
adoxa wrote:
Wasn’t this resolved to the lack of hardpoints (hpid) in the sur?I dunno about it, aby prooflink?
-
I get Crash at Fault offset: 0x00021117 in Common.DLL
it is appeared here:
.text:06281105 loc_6281105: ; CODE XREF: DamageList::operator=(DamageList const &)+91j .text:06281105 mov [eax+4], edi .text:06281108 mov [esi+4], eax .text:0628110B mov edx, [eax+4] .text:0628110E mov [edx], eax .text:06281110 add eax, 8 .text:06281113 test eax, eax .text:06281115 jz short loc_6281128 .text:06281117 mov ecx, [ebx+8] ; <-here .text:0628111A mov [eax], ecx .text:0628111C mov edx, [ebx+0Ch] .text:0628111F mov [eax+4], edx .text:06281122 mov ecx, [ebx+10h] .text:06281125 mov [eax+8], ecxWhats wrong may be?
