null object error

banger · Sep 30, 2009

hi piddy,

seem to be getting an new error on 8.0.0.x to 8.03 not try yet. xpacker mainly.

Steps.
1) created a building layout from google earth.extruded it to hieght, quickly painted it (for test) and saved it has a Dae file. google sketchup 7.1 i have.
2) started xpacker.
3) imported objected , before it finshed the exception error came up.
4) picture include. no need to send you bin file has it just using the default xpacks textures.

banger · Oct 2, 2009

any idea's

Eric Tozer · Oct 2, 2009

I've had a few of these in xpacker but usually it's because I'm doing something a bit backwards.
Usually I can just hit continue & everything is fine.
I can never really pin point exactly what causes it.

banger · Oct 2, 2009

i never get to continue thou, xpacker just sits there, the object is listed but never visable. try the object in simed same result, object & texture listed. but not visable?

all thought i do seem to be getting alot of materials, i haven't used in sketchup.it seems to be that sketcup saves all the materials in that scene including background colours.fog,line colours.?

ed

Eric Tozer · Oct 2, 2009

Can you email me the dae & any associated files banger & I will check it in Max.

banger · Oct 2, 2009

sent email.

Eric Tozer · Oct 3, 2009

The good news is it's not a BTB problem.

The Bad news is that it's just a poorly constructed object with numerous faults.

Textures are not power of 2.
Some textures are missing.
There are irrelevant objects in the file. (probably a hangover from Sketchup export.)
And the object is just poorly constructed.
See how all the polys are draggged to the corners making very long thin triangles.

Unfortunately you will get this kind of thing using sketchup objects.
They aren't created with gaming (or BTB) in mind.