Grimrock

Of course this isn't a big deal since animation export doesn't support bone animations yet anyway. I'm glad you mentioned that because I was trying to export a rigged animation & getting terrible errors and was about to ask for help. Hopefully, bitcpy returns and adds this feature but if not I ...

I'd be happy to try to correct it but for me the lighting is ok on the models as you see in this pic:
(I'm running Win 7 if that matters)

You need to triangulate all the faces. You will notice after that error that bitcpy's script selects/highlights the n-gons that need to be triangulated.

In edit mode with those faces selected (or all faces), do Mesh -> Faces -> Triangulate Faces.

I am guessing 4th value in color vec is for alpha AKA transparency.

Thorham wrote:Why did they even bother to put that in there?

AFAIK MersenneTwister should produce a more random random number than math.random() does, i.e. closer to being truly random.

Oh yeah, you're right, I did make one, here's how you do it, very easy: defineObject{ name = "swamp_ground", baseObject = "forest_ground_01", components = { { class = "Model", model = "assets/models/env/forest_ground_01.fbx", materialOverrides = { forest_groun...

swamp_ground tile = swamp_ground object
swamp_ground2 tile = swamp_ground object + swamp_grass_01 object

They're right there in the editor, I just placed them on the map, don't understand your dilemma.

I made an entry for MersenneTwister: MersenneTwister.create(seed) Returns an instance of MersenneTwister required to generate random numbers. Seed is a number. e.g. local random = MersenneTwister.create(Time.systemTime()) MersenneTwister.random() Generates a random real number between 0 and 1. e.g. ...

I agree, this feature seems bizarre to me and would be terrific if it could be disabled.

It does look good but I put down 6 of these tiles and lost 10fps so uuuhh I'd go easy on them.