Aller au contenu

Photo

Toolset freezes when compiling script


14 réponses à ce sujet

#1
none0421

none0421
  • Members
  • 10 messages
Hi, all
I am new to this DAO toolset.
With you guys' experience, how long does it take to compile a script?
Last couple days, I was following the tutorial on http://dragonagemodd...player-an-item/

Here's the script I used:

#include "utility_h"
#include "wrappers_h"
#include "events_h"
void main()
{
    event ev   = GetCurrentEvent();
    int nEvent = GetEventType(ev);
    Log_Events("", ev);
    switch (nEvent)
    {
        case EVENT_TYPE_MODULE_LOAD:
        {
            // get the object which contains the player
            object oPlayer = GetHero();

            object oBow = GetObjectByTag("gen_im_wep_mel_dag_ros");
            if (!IsObjectValid(oBow))
                UT_AddItemToInventory(R"gen_im_wep_mel_dag_ros.uti",1);
            break;
        }
        default:
        {
            break;
        }
    }
}

Yet, when I clicked complie, the whole toolset was forzen and not responding for hours.
Has any one encounter this situation before?

Thanks in advance.

Modifié par none0421, 18 mars 2010 - 11:21 .


#2
none0421

none0421
  • Members
  • 10 messages
BTW, when toolset froze, one cpu was fully loaded. But since I could not see the progress of compiling, I did not know whether the compiler was working or not.

#3
DavidSims

DavidSims
  • BioWare Employees
  • 196 messages
It's not a problem of the contents of the script, as that compiles fine for me. Have you changed any of the include files? Or closed the toolset and tried compiling again?

#4
none0421

none0421
  • Members
  • 10 messages
Nope, I haven't touch any core file, just adding this script.

Normally, how long does it take to complie?

#5
Charsen

Charsen
  • Members
  • 2 266 messages
Shouldn't take very long to compile. Enough time to grab a drink and maybe a power snack from the kitchen, tops. If it's taking hours, then something else is wrong... Hard to say without knowing more info though. =/

#6
none0421

none0421
  • Members
  • 10 messages
Well, I got 1.03 patched to DAO, and I am using 1.01 toolset.

I did a little test, it seems Like it froze if I included utility_h



Is there any way to see the compiling progrss ?

#7
none0421

none0421
  • Members
  • 10 messages
Is there any library I should install for Toolset?

#8
Craig Graff

Craig Graff
  • Members
  • 608 messages
utility_h has a lot of includes and will slow down compile time significantly - to see the progress, right click on the script (either in the palette or the tab for the script editor) and select Export without dependent resources.

#9
none0421

none0421
  • Members
  • 10 messages
hmm.... I tried to export it without dependent resources, it froze again.

The log file stopped at this line:



".\\ExportManager.cpp", 2115, "CExportManager::ExportResource Exporter completed successfully for resource: effect_death_h.nss"



Maybe it's the next header file cause me problem?

#10
Craig Graff

Craig Graff
  • Members
  • 608 messages
If so, the next one is likely items_h.

#11
none0421

none0421
  • Members
  • 10 messages
hmmm.....I even restore my database and reconnect Toolset to SQL.

Still not working.

It it because of my C library?

Which C environment do you guys use?

#12
none0421

none0421
  • Members
  • 10 messages
I tried using a blank script:



void main()

{

}



and try export it without dependence resource



I got this error:

Cannot load the AddIns.xml file. Unable to verify



Is this the case for you guys?


#13
none0421

none0421
  • Members
  • 10 messages
Wow....you guys are not gonna believe this.

I test this on my Laptop. It seems like its the windows locale's problem.

After I change it to English(United States), guess what? It compiled.

Need to test this on my desktop.......



But if this is why.......don't know what should I say about WINDOWS OS......

#14
none0421

none0421
  • Members
  • 10 messages
Yup... It IS because Windows Locale.

Speachless........

#15
Thaxor

Thaxor
  • Members
  • 308 messages
Thank you for this. I ran into the exact same problem. Windows Locale (of all things) was locking up the toolset.

Unbelievable.