forums | blogs | polls | tutorials | downloads | rules | help
Home-> forums-> Technical support-> DS2 & BW Technical Support

[Resolved] SE2 and flickmanager.cpp problem

Submitted by sol77 on Thu, 2007-04-26 20:57

I'm getting tons of errors related to flick when I try to start up SE2.
They might not all be flick related, but after error #300 or so I tired of clicking so aborted. Smile

Here are three of the errors though:

Type         : Error
Module       : E:\programs\development\Dungeon Siege II Tool Kit\SiegeEditor2.exe
Location     : 
Fail Count   : 1 (w:0, e:1, x:0)
Exe timestamp: Nov 28 2005 16:13:07

fc_actor.skrit(1945,30) error: 'NISManager': undefined function
fc_actor.skrit(1945,84) error: syntax error
fc_actor.skrit(1950,13) error: 'UIDialogueHandler': undefined function
fc_actor.skrit(1950,66) error: syntax error
fc_actor.skrit(1950,89) error: syntax error
fc_actor.skrit(2066,30) error: 'NISManager': undefined function
fc_actor.skrit(2066,84) error: syntax error
fc_actor.skrit(2071,13) error: 'UIDialogueHandler': undefined function
fc_actor.skrit(2071,75) error: syntax error
fc_actor.skrit(2071,98) error: syntax error
fc_actor.skrit(2206,30) error: 'NISManager': undefined function
fc_actor.skrit(2206,84) error: syntax error
fc_actor.skrit(2211,13) error: 'UIDialogueHandler': undefined function
fc_actor.skrit(2211,66) error: syntax error
fc_actor.skrit(2211,89) error: syntax error

world/global/flick/commands/fc_actor.skrit - 0 fatals, 15 errors, 0 warnings

Type         : Error
Module       : E:\programs\development\Dungeon Siege II Tool Kit\SiegeEditor2.exe
Location     : FlickManager.cpp line 2446 (at c:\depot\ds2\main\code\projects\mohawk\world\)
Fail Count   : 1 (w:0, e:2, x:0)
Exe timestamp: Nov 28 2005 16:13:07

Flick Manager cannot open skrit "world/global/flick/commands/fc_actor" used by command "attack"

Type         : Error
Module       : E:\programs\development\Dungeon Siege II Tool Kit\SiegeEditor2.exe
Location     : FlickManager.cpp line 6570 (at c:\depot\ds2\main\code\projects\mohawk\world\)
Fail Count   : 1 (w:0, e:77, x:0)
Exe timestamp: Nov 28 2005 16:13:07

*** FLICK COMPILER ERROR ***
[a0_tut_beach_magic_lesson_talk_2]:(line 11):
Unrecognized command name "Capture"

I got a log from SE2 but it is in .mdmp format (binary) so can't read it. It seems like SE2, flickmanager, can't find the resources it needs and even though I have removed and reinstalled DS2 it is in the same location as last time so that shouldn't matter.
I checked the windows registry to see if the install paths were wrong, tip from fb, and couldn't find an entry that seemed valid to me. I found one for BW under:
"HKEY_LOCAL_MACHINE\SOFTWARE\2K Games\Dungeon Siege 2 Broken World"

I expected to find something like: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dungeon Siege 2" for DS2,
but instead I found: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay\Applications\Dungeon Siege 2".

Are the registry entries really that different for the game and the expansion?
What information should each key hold, if correct?

Any idea on how to fix this? Reinstall of windows isn't an option.

forums: 
DS2 & BW Technical Support
»
Submitted by Anonymous (not verified) on Thu, 2007-04-26 21:51

i got 2 solutions for ya.

first the weird solution to try.

wipe out your logs first in ds2 mod folder
1. i had this problem one day while running ds2mod.. if one has a bad character as default character and trys to load a map it would freeze up on the screen and not move. so ya may think this is stupid answer, but run ds2mod load in a new character one that aint modded especially. and then after that save and quit.

then reload siegeeditor 2 and see if the errors happen.

if they still happen... backup your bits folder and reinstall DS2toolkit.

anyways my bad character turned out to be an item in inventory i had placed but forgot a ; at end of line so it produced those errors and i found the errors in My Documents\My Games\Dungeon Siege 2 Mod\Logs\dev-errors-xxxxxxxx.log
»
LoneKnight's picture
Submitted by LoneKnight on Thu, 2007-04-26 23:09

Not 100% certain, mate. Try reinstalling it. I haven't worked with Siege Editor 2, so unless someone else offers a more experienced answer, my recommendation is to try and reinstall it. Good luck, Sol.
»
Sharkull's picture
Submitted by Sharkull on Thu, 2007-04-26 23:28

I have the DS2 key you mention, plus one here: HKLM\SOFTWARE\Microsoft\Microsoft Games\DungeonSiege2
There are other keys too (10+) but I think this one is the important one (since it has two values with the install directory listed...).

I assume that you have removed all non-GPG tanks from your DS2 resources folder, and are working with an empty \Bits folder...?

When I started SE2 for the first time it gave me a bunch of errors. I just did the "Ignore All" thing and that did the trick (well, after installing the 2.2 patch that is :oops: ).
»
Submitted by sol77 on Sat, 2007-04-28 09:16

Thanks for the advice guys. I'll try it out, as soon as I get a chance to start up SE2 again, and let you know how it goes.
It does seem like SE2 can't find the path to the resources for DS2 since it appears like I am missing a registry key.

I have no nongpg mods in my resource folders but there is some stuff in my bits folder so might have to empty that.
»
Submitted by sol77 on Sun, 2007-04-29 11:52

I got it to work. I tried cleaning up my bits folder and setting ds2mod to use a default character. Emptying the bits folder had no effect and ds2mod refused to startup. All that happened was that a tmp file started up as an executable..
So I removed the games and the toolkit, did a registry cleanup with an app called CCleaner for everything that had to do with DS2 and DS. Now that I have reinstalled DS2 and patched it the registry key, that Sharkull posted, is there.
After installing the Toolkit SE2 is now working as well.

Thanks again for the help!
»