Guild of Writers

For the last few days my age has been going remarkably well, and of course it couldn't last forever. Yesterday I added a new room, worked out all the texture, and Z-fighting problems, until it was perfect. (or, as perfect as it can be without lightmapping)
It exported perfectly, and had no lag.

Today however, I lightmapped the room. I usually use a synopsis of the steps of lightmapping, that I wrote to make sure I don't do anything wrong, but today I couldn't find it, and lightmapped from memory. The exporting worked awesome, and it seemed to have all worked fine... until I tried to link to it. It showed the loading bar, and seemed to be loading the age, just as it always has, but then it just quits. No error message or anything, URU just quits completely! I thought it might have been Shadbuf, so I unchecked it on the objects in the room, but it still did the same thing when I tried linking! Anyone know what my problem might be? Can Lightmaps cause crashing, if not done right?

Lightmaps don't use the same settings that they used to. In the MAP TO settings, in blender, the amb button must be selected now. But this shouldn't cause URU To crash. But thats needed now for lightmaps to work properly. So Try that.

really? I lightmapped the previous rooms succesfully without hilighting it, and I didn't get a new version of PyPRP between then, and now...

I know animations cause a crash like that if the actor button is not activated in the logic properties panel.

Is there any animation embedded in your lightmaps.

Just an idea I am probably not the best person to be giving advice....

No Animations... However, I did look in the logic panels, and discovered that all the lamps in the age have "actor" selected in the logic panel, but when I create a new lamp, it doesn't have "Actor" selected. What would cause it to select itself? Is it supposed to be be selected? Could that be the problem?

The actor button is what gives an object its coordinate interface. This is why objects like sprites, objects with animations, and objects that are clickable need to have the button pressed. In order for them to move, or interact with the player Plasma needs to know where the object is in relation to the world itself. This would not cause it to crash.

Argh! there doesn't seem to be anything wrong with it! Would anyone be willing to take a look at the blendfile, and see what they find (I'll PM it to you)

Have you remembered to turn of ShadowBuf on each new material you create? Rememeber, it's set ON by default. Just one being on won't cause Uru to crash, but having many of them on will.

Well, the first time I exported it, Shadbuff was on for a bunch of objects, but even after I turned shadbuf off, and re-exported, I got the same error...

Well, I've tried everything, and just can't figure it out... could someone take a look at the file and see if you can find the problem? Thx