Lightmapping broken importing package into new project. help please!

ISSUE RESOLVED! See thread for solution.

Hello all. I have a dilemma. I have a scene with light mapping(scene is prefabs from .fbx files)(Unity 3.5 Pro) I export a package of the scene(with dependencies). Unity generates the appropriate package, but when I import the package into a new project the light mapping is broken. I am testing this as I want to add this project for sale on the Asset Store, and need to test for errors.

Any help would be greatly appreciated. See images for problem.

Sincerest Regards,

Gary Haus

Correct:

New project with importing exported package:

Far as I know, moving light maps out of a project they were originally created in has always been a pain. If selling on the asset store, I would bake lightmaps with mental ray, VRay, etc. in a dcc app and avoid the problems altogether, but that’s just me.

Thanks for the info. That is not very cool though…

Regards,

Gary

Wait… Bootcamp and Angrybots have light mapping right? Unity, anyone, please help?

Tried with selecting all in the project and exporting a package that way. The light maps are messed up with that as well.

if you export a package of the scene with the 3.42 version it is the same thing ?

Its all 3.5 now. Going to 3.42 breaks things…

I have no idea how to solve your problem and I hope someone helps you but I just wanted to say that is some great modelling work you have done there.

The unwrapping algorithm changed significantly from 3.4.2 to 3.5. You need to re-import all meshes that use Unity’s secondary UV unwrapping and then bake the lightmaps again. This should solve the package issue.

Ethan,

Thanks. I would have thought that upgrading the project from 3.4 to 3.5 would have done that… My bad for assuming as much. Trying a rebake after re-import now.

Fingers crossed and hope it works :slight_smile:

Cheers,

Gary

Ethan,

That worked. Good to know for future reference!

Regards,

Gary

Nice, mark the thread as solved.