Package scene error

[shrox]

I get this error message when I try to package a scene.

"Line 785, attempt to access undeclared array tarSplit"

Any ideas on why and how to fix?

[Salv8or]

Never seen thet message before.
Are you trying to package the scene over network or somthing? Any strange caching from some plugin? I have no ideea, but that was the first thing that struck me when I read the topic. Im sure some one else can give a better explenation.

[3DGFXStudios]

In some versions of lightwave it's broken. Try an other version.

[shrox]

9.6 and not through a network. Both the 64 bit version at work and the 32 bit version at home do it. It worked before on another 64 bit system with 9.6.

Such a good idea too.

I also installled WinZip just in case it was dependent on it, but I get the same error.

[Salv8or]

I used it just the other day on win7 64 and lw 9.6 64, and it worked like a charm. Any odd things outside the LW Project path that are used in the scene?
Perhaps something in a directory that are not standard lw paths that packager cant recreate. I dont know, im just tossing ideeas. Hope you figured it out.

Oh.. Its not dependent on winzip. THe only thing package does is collecting all materials to a different folder (or the same) to get correct paths for the entire project.

[Danner]

I can't remember the error I used to get, but I unchecked image sequences and it worked.

[bjornkn]

To circle in on the problem the first I would do was to try with another scene, to see if it may be something inside the current scene that causes it, or something with your setup/version?
I haven't had any problems using it on 9.6x/32.

[Matt]

Looking at the source:

tarSplit = pssplit(target);

The tarSplit array gets it value from the 'psUltraCopy' function passing a value to it.

Problem is, psUltraCopy is used throughout the script for:

Images
.bdd files
.mdd files
.ies files
.pfx files
Radiosity cache files

So, does the script copy _anything_ to the new location? If so, what did it copy successfully? This will narrow down which content item is causing it to fail, then you can look at the paths to those and see which is buggering things up.

You could try saving copies of the scene each removing one of these from content types from it, then test Package Scene to see which one fails, again this should help narrow down which content type (and its path) it causing the issue.

[digitaldoc]

I've had that happen. Saved an incremental scene version and worked fine.