3 réponses à ce sujet

[Quilnux]

Hello,

I have a small level that I am trying to export which I'm using to learn the toolset.

I have a platform and 4 walls on each side. I do not have any lights on the lvl. I do a lightmap anyways (which gives warnings but completes as successful) and create the pathfinding.

I save but when I click the export to local I get an error, "Invalid Intermediate Directory". This seems to be the root cause of the compilation failing. I can't figure out for the life of me what this error is. Without knowing what directory it uses for intermediate compiling I don't have a way to check the folder permissions (this is what I am assuming is the problem). Any ideas?

I use Windows Vista/Windows 7 (both fail with same). I am running as administrator. I have tried running each without UAC as well and nothing.

*EDIT* I should add that I am creating a room level, not a terrain lvl.

*EDIT* I included this image of the error: http://cid-ac9f05b10...S/DATSError.jpg

Modifié par Quilnux, 22 novembre 2009 - 01:19 .

[Erenz]

Similiar problem:
When I try to do a local post of my level, so I can use it in my module, I get the following error:
(...)
I: 23:25:49 - /source_addins/gis_module/layouts/gis_hut/gis_hut.arl
I: 23:25:49 - Inputs:
I: 23:25:49 - (win32) copy layout gffs addin gis_module
I: 23:25:49 - Job/Rule:
E: 23:25:49 - Processing failed of the following job.
I: 23:25:49 - Das System kann die angegebene Datei nicht finden.
I: 23:25:49 - C:\\\\>rename "gis_hut.arl" "gis_hut.arl"
I: 23:25:49 - PROCESSOR OUTPUT:
(...)
The line in german ("Das System kann die angegebene Datei nicht finden.") simply translates to "system cannot find the file specified". So it seems it cannot find the levelname.arl file.. OS is Vista64, Admin Account, Toolset running with admin privileges.
Any ideas?

Modifié par Erenz, 21 novembre 2009 - 10:37 .

[Languard]

While I've encountered that error before, it was on a test level that I just abandoned. I never saw it since. I'll see if I can still find that level and take a second look.

[Quilnux]

Languard wrote...

While I've encountered that error before, it was on a test level that I just abandoned. I never saw it since. I'll see if I can still find that level and take a second look.

So your saying that your issue was resolved by just starting over again?

I haven't tried that yet. I'll do that next time I am in the toolset.

Thanks,