12 réponses à ce sujet

[MightySword]

I'm playing with the toolset a bit and making some mock up area following the tutorial. However when I try to export the area to test, it always freeze up.

- if I "export without dependent resource" it works fine, although it doesn't do anything much since no scripts/objects are exported.

- if I "export with dependent resource" I always freeze. Looking at the log I see that it always freeze when trying to export the file "effect_death_h.nss".


So anyone have any idea what's going on?

Modifié par MightySword, 10 novembre 2009 - 04:03 .

[MightySword]

Just in case it was something I did in my own module. I tried to Export the Demo Module that came with the toolset, it also freezes at "effect_death_h.nss"

[PavelNovotny]

I've been having this happen a lot too. It happens whenever I try to export a module, including the demo module, and it happens whenever I try to compile a script or save a script.



It's very frustrating to have the toolset install and then not be able to really do anything with it because it keeps freezing. :-P

[PavelNovotny]

I should add that the demo module export freezes if you export without dependent resources too at the effect_death_h.nss

[MightySword]

Well after spending the last three hours trying all the things I can think of I'm still stuck with this issue. I'm starting to feel depressed

[Craig Graff]

I'm not seeing this problem myself, but as a work-around you could try to export all the resources you need without dependent resources. There really isn't any reason to export the core resources unless you have made changes to them.

[AnTeevY]

Is there a way to only export the resources I created or changed myself and not all the standard core stuff (which gets exported into the core package override folder which causes bugs in the main campaign) without opening up each and every resource and manually export it?

[headcat]

Do you guys have your System Locale set to something other than English (United States)? It's under the language control panel, the "Language for Non-Unicode programs" part. I had mine set to Japanese as it was needed for another game and I found the exact same problem happened to me when exporting, until I set it back to English(United States) and rebooted and then everything exported fine. This is on Windows 7 64-bit, but I'd think Vista/XP might have the same problem as they have that same system locale setting.



The only other thing I can think of is the locale had nothing to do with it and it was simply the reboot that fixed it, but I'll have to test that further.

[headcat]

Ok, I did some further testing with more locales. Russian appears to work fine, the "export with dependencies" process completes without a hitch. Chinese, however, has the exact same issue that Japanese had, it freezes at effect_death_h.nss during the export process. I'm not sure what's causing this but it seems to be an issue primarily with the east-asian locales. Maybe because of differences in text formatting? I'd test more of them but rebooting every time gets kind of annoying.



Either way, I'd advise you guys to check the locale settings and see if setting it to English or perhaps another european language fixes the problem.

[PavelNovotny]

headcat you're a genius!



I had the language for non-unicode programs set to Japanese and didn't even realize it. Once I changed it to English (United States) the freezing problem went away both during compile and during export.



How did you ever figure that out?



Thanks!

[MightySword]

I don't have time to check now but I figured you're right Headcat, since just like you I have my computer set in Japanese mod to run several program. I'll change it back tonight when I have time. Thank you very much.

Craig Graff wrote...
I'm not seeing this problem myself, but as a work-around you could try to export all the resources you need without dependent resources. There really isn't any reason to export the core resources unless you have made changes to them.

What do you mean? I tried to use the "Export without dependent resource", it works fine but like I said it doesn't do anything. Say If I export an area this way it seems only the map data is export, no placeable or script is exported in said area is exported. Do you mean I have to manually export each resource under the area?

From what I understand I probably only use Export with dependent resource the first time I upload the module, everytime after that I probably only use Export Without Dependent resource. But it's freezing on me the first time it's the problem.

Modifié par MightySword, 10 novembre 2009 - 05:12 .

[headcat]

Glad to hear it worked. I figured it out because when I was first messing around with the toolset, I had no problems with the export and the locale was still set to English. I was messing around with it a day or two later after I had changed the locale and that was the only change I could think of that occurred in the meantime.

I normally use AppLocale for application-specific locale changing but I hadn't redownloaded it since moving to Win7 since I never had problems not using English locale until now. It may be possible to run toolset in English mode with AppLocale and keep the system locale as Japanese so you don't have to reboot back and forth, though I don't know if that will get around the export issue or not, I haven't tried it yet. May have to leave the system in English and use AppLocale for the Japanese programs if it doesn't.

Modifié par headcat, 10 novembre 2009 - 06:18 .

[PavelNovotny]

I posted this info on the Troubleshooting page of the wiki in case anyone else looks there.



Thanks again headcat.