11 réponses à ce sujet

[3ra]

Cheers. I'm having a rather annoying problem here. I've been trying to solve this for days now, but there seems to be no way doing it! The problem is that when ever i try to render lightmaps, i get;

ImportError; No module named win32com 
File "",line12 in
Traceback (most recent call last):

I do have python installend,  (2.5) x86. Allthough i have a x64 OS, i tried with the x64 version of python, and the problem got kinda worse.

When i try to "Do all local post" i get a fail message, which is something called;

lvlname.lvl - Exporter failed for resource: lvlname.lvl

The funny thing tho, is that if i do "Post to local", it goes trhough with no errors, only that the room i made have no walls in the area.

If someone could help it would be awesome. Also, i dont think i fully understand the relations between areas/levels and how to export things from and to.

PS: I have tried several tutorials, following them step by step (closely and precise) and i get the same errors. ie, it must be software..?

[georage]

Do you have the proper extensions for python?



I suggest uninstalling python entirely, then reinstalling this version, which has the win32 extensions.



http://downloads.act...4-win32-x86.msi

[3ra]

Thanks, i'll try it  

*Lightmaps works correctly now. Thanks again!

Modifié par 3ra, 28 novembre 2009 - 12:52 .

[FalloutBoy]

I am getting this problem as well even though I have installed the link listed above. I created a level in the level editor, made a walkable area and tried to Do All Local Posts.

I: 20:21:45 - Generated the campaign file.
W: 20:21:45 - No starting area specified for campaign.
I: 20:21:45 - PostProcessing
E: 20:21:45 - test100_terrain.lvl - Exporter FAILED for resource: test100_terrain.lvl
W: 20:21:45 - SanityCheck: No lightmap atlases found. Using legacy non-atlased lightmap data instead.
W: 20:21:45 - No lightmap atlas found. Falling back to display legacy lightmaps in editor.
I: 20:21:45 - Starting local export and post...

EDIT: Nevermind, it just fixed itself.

Modifié par FalloutBoy, 28 novembre 2009 - 04:49 .

[indio]

Fallout, what fixed it?



I'm having the same problem, as of 12 hours ago.



Mind you, I've successfully exported several levels already (at least 10) over the past weeks. Yesterday, I get the error you got.



So any ideas on what fixed it?

[indio]

Just reinstalled everything and still have the same problem.



It's a real mystery. I exported a level just yesterday. Now today, no joy.

[indio]

And now it seems, having tested some more, I can post interior levels, but not exterior levels.

Modifié par indio, 28 novembre 2009 - 07:50 .

[FalloutBoy]

From the level editor I tried Do All Export Operations..., which took a while, but ever since I did that, now I can Do Local Posts successfully. This is with an outdoor area.



I also installed the Python link that georage posted but I was still getting the error after that so I can't confirm that is what fixed it.

[indio]

E: 13:43:01 - Local Posts Failed!
S: 13:43:01 - Export Summary, 1 Requested, 0 Success, 0 Skipped, 1 Failed. Please see below for more details.
I: 13:43:01 - Offers.xml file has been updated successfully.
I: 13:43:01 - AddIns.xml file has been updated successfully.
I: 13:43:01 - Generated the campaign file.
I: 13:43:01 - PostProcessing
E: 13:43:01 - 1.lvl - Exporter FAILED for resource: 1.lvl
W: 13:43:01 - SanityCheck: No lightmap atlases found. Using legacy non-atlased lightmap data instead.
W: 13:43:01 - No lightmap atlas found. Falling back to display legacy lightmaps in editor.
I: 13:43:01 - Starting local export and post...

Reinstalled everything, including Python (I'd already installed the one geo linked above).

No joy. When I try to Do All Export Operations, it begins running the light render and sits there, for hours, without doing anything, never getting any further or tackling the remaining jobs.

24 hours ago I posted an exterior level. I was attemtping the water fix and so switched modules to Single Player. Having switched back, can no longer post to local. It's the only change I can think that I've made that would explain the sudden shift from working to not working.

Any help appreciated.

Modifié par indio, 29 novembre 2009 - 02:51 .

[giskard44]

I too have this problem and another issue the solutions to this problem cause.

I have many programs here including blender that i use that need specific versions of python, Uninstalling one to get this to work is there for a BAD option for me and does not appear to fix anything anyway. I tried, it, no difference at all here.

But I would point out that Do All Posts to Local actually only does the following (according to the output text)

I: 16:14:42 - Starting local posts: Visualize/Update Lightmaps, Pathfinding and physics culling, Render Light Probes, Post Trees to Local, Post Layout to Local

Of which only the lighting part seems to fail, the rest is performed normally.

Also it may be that we are supposed to supply the missing DDS lightmap files our selfs, placing them in a specific folder where the editor will find them. All the missing lightmap files appear to be unique names named after my own level.

Here are the errors i get doing the post to local (not do all posts to local).

W: 16:35:07 - Missing lightmap [lmwhlay01_a_1_0.dds].  Continuing.
W: 16:35:06 - Missing lightmap [lmwhlay01_m_1_0.dds].  Continuing.
W: 16:35:06 - Missing lightmap [lmwhlay01_i_1_0.dds].  Continuing.
W: 16:35:06 - Failed to get tree lightmap value for position 41.988010, 109.087257, 10.483345
W: 16:35:06 - Missing lightmap [lmwhlay01_e_1_0.dds].  Continuing.
W: 16:35:05 - Failed to get tree lightmap value for position 24.083021, 108.900108, 5.646111
W: 16:35:05 - Missing lightmap [lmwhlay01_9_1_0.dds].  Continuing.
W: 16:35:05 - Failed to get tree lightmap value for position 105.472992, 77.638443, 20.439819
W: 16:35:05 - Missing lightmap [lmwhlay01_l_1_0.dds].  Continuing.
W: 16:35:05 - Failed to get tree lightmap value for position 84.686508, 90.255264, 22.020174
W: 16:35:05 - Missing lightmap [lmwhlay01_h_1_0.dds].  Continuing.
W: 16:35:04 - Failed to get tree lightmap value for position 32.315327, 75.052689, 4.473457
W: 16:35:04 - Missing lightmap [lmwhlay01_d_1_0.dds].  Continuing.
W: 16:35:04 - Failed to get tree lightmap value for position 15.743073, 71.327385, 3.270639
W: 16:35:04 - Missing lightmap [lmwhlay01_8_1_0.dds].  Continuing.
W: 16:35:04 - Failed to get tree lightmap value for position 105.897980, 52.107445, 15.918498
W: 16:35:04 - Missing lightmap [lmwhlay01_k_1_0.dds].  Continuing.
W: 16:35:03 - Missing lightmap [lmwhlay01_g_1_0.dds].  Continuing.
W: 16:35:03 - Missing lightmap [lmwhlay01_c_1_0.dds].  Continuing.
W: 16:35:03 - Failed to get tree lightmap value for position 31.788113, 53.240112, -4.442327
W: 16:35:03 - Missing lightmap [lmwhlay01_7_1_0.dds].  Continuing.
W: 16:35:02 - Failed to get tree lightmap value for position 113.065819, 28.700138, 7.163338
W: 16:35:02 - Missing lightmap [lmwhlay01_j_1_0.dds].  Continuing.
W: 16:35:02 - Failed to get tree lightmap value for position 67.551727, 18.175726, -4.597809
W: 16:35:02 - Missing lightmap [lmwhlay01_f_1_0.dds].  Continuing.
W: 16:35:02 - Failed to get tree lightmap value for position 46.000000, 18.000000, -1.485352
W: 16:35:02 - Missing lightmap [lmwhlay01_b_1_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 10.857761, 28.240326, 2.223003
W: 16:35:01 - Missing lightmap [lmwhlay01_a_0_0.dds].  Continuing.
W: 16:35:01 - Missing lightmap [lmwhlay01_m_0_0.dds].  Continuing.
W: 16:35:01 - Missing lightmap [lmwhlay01_i_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 41.988010, 109.087257, 10.483345
W: 16:35:01 - Missing lightmap [lmwhlay01_e_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 24.083021, 108.900108, 5.646111
W: 16:35:01 - Missing lightmap [lmwhlay01_9_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 105.472992, 77.638443, 20.439819
W: 16:35:01 - Missing lightmap [lmwhlay01_l_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 84.686508, 90.255264, 22.020174
W: 16:35:01 - Missing lightmap [lmwhlay01_h_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 32.315327, 75.052689, 4.473457
W: 16:35:01 - Missing lightmap [lmwhlay01_d_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 15.743073, 71.327385, 3.270639
W: 16:35:01 - Missing lightmap [lmwhlay01_8_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 105.897980, 52.107445, 15.918498
W: 16:35:01 - Missing lightmap [lmwhlay01_k_0_0.dds].  Continuing.
W: 16:35:01 - Missing lightmap [lmwhlay01_g_0_0.dds].  Continuing.
W: 16:35:01 - Missing lightmap [lmwhlay01_c_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 31.788113, 53.240112, -4.442327
W: 16:35:01 - Missing lightmap [lmwhlay01_7_0_0.dds].  Continuing.
W: 16:35:01 - Failed to get tree lightmap value for position 113.065819, 28.700138, 7.163338
W: 16:35:01 - Missing lightmap [lmwhlay01_j_0_0.dds].  Continuing.
W: 16:35:00 - Failed to get tree lightmap value for position 67.551727, 18.175726, -4.597809
W: 16:35:00 - Missing lightmap [lmwhlay01_f_0_0.dds].  Continuing.
W: 16:35:00 - Failed to get tree lightmap value for position 46.000000, 18.000000, -1.485352
W: 16:35:00 - Missing lightmap [lmwhlay01_b_0_0.dds].  Continuing.
W: 16:35:00 - Failed to get tree lightmap value for position 10.857761, 28.240326, 2.223003
W: 16:34:58 - SanityCheck: No lightmap atlases found. Using legacy non-atlased lightmap data instead.
W: 16:34:58 - No lightmap atlas found. Falling back to display legacy lightmaps in editor.

You can see the names of the files its expecting to find very clearly.
Id take a guess and suggest they expect some sort of greyscale lightmap for shadows and stuff to be in them, meaning each section has a shadow map that tells it what should appear dark and what should appear light. Which basically means tree shadows etc etc.

Thats usually what other games with similar light maps are looking for, probably the same thing here.

The Python script designed to produce them is clearly bugging out for some reason.

Modifié par giskard44, 29 novembre 2009 - 04:41 .

[giskard44]

Update

I uninstalled everything related to python and downloaded the 32 bit version of that active python above and installed that. I was using the 64bit version on Vista 64.

This is the result.

I: 17:13:42 - Successfully submitted lightmap job.
I: 17:13:42 - Submiting jobs to lightmapper took 198 seconds.
I: 17:13:42 - no FESL allocator defined
I: 17:13:42 - Lightmapper script completed successfully.
I: 17:13:42 - Local Posts Succeeded!
S: 17:13:42 - Export Summary, 1 Requested, 1 Success, 0 Skipped, 0 Failed.  Please see below for more details.
I: 17:13:42 - Offers.xml file has been updated successfully.
I: 17:13:42 - AddIns.xml file has been updated successfully.
I: 17:13:42 - Generated the campaign file.

As you can see it worked.

Previously it was reporting a failure to import win32com which tells me it expects to find the 32bit version of python. I have seen other programs such as Xfire and spore failing to work correctly on Vista 64 because they are looking for a 32bit command on a 64bit OS. Usually the 64bit stuff steps in and lets them work anyway but it seems not in this case.

Since installing the 32bit stuff above many of those little errors seem to have disappeared from the log window.

[giskard44]

Now i have the python stuff working, I made some progress.

It appears the lighting has to be set first in the Exportable area properties for an external level and only items you place or edit after setting the lighting actually use the new lighting settings. That means any item on the level prior to the lighting be setup will need moving slightly if you wish it to automatically start using the new lighting you created. Fortunately undoing the move puts the item back in its original location BUT DOES not undo the lighting changes, so you can move an item then Control X to cancel the move and still keep the lighting.

I am keeping notes on my findings on my forum, you can check them by clicking HERE. The above is a direct quote for my forums. I figured it might explain why sunlight appears to be broken sometimes.  The notes from that page are going to be made in to a tutorial eventually so let me know if you have anything to add.

I should also add that the Exportable Area properties has an option to turn off Sun light, the moon counts as a sun at night (waves at sabbath fans lol) so if you turn it off, you lose the moonlight too.

Modifié par giskard44, 29 novembre 2009 - 09:18 .