vbp 5.7 : visual build pro action spawns child with missing system macros?

[epu]

Hey dudes,

I'm having trouble with spawning a visual build pro instance (chained build). My system environment has 2 variables set, XDK and XEDK, which correspond to the paths to the Xenon and Xbox sdks.

The parent (spawner) project shows that these variables exist in the system macros. The child project shows that these variables do not exist in the system macros.

if I open a cmd.exe instance and type 'set X<enter>' these variables are set.

Is there a known bug with spawned vbp projects where the system macros are truncated? Is there a max length to the number of system macros that can be created?

Thanks for VBP,

-epu