# Weird loadClip behaviour

**URL:** <https://forum.kirupa.com/t/weird-loadclip-behaviour/183488>\
**Category:** Uncategorized\
**Created:** [March 27, 2006, 2:58pm UTC](https://forum.kirupa.com/t/weird-loadclip-behaviour/183488 "2006-03-27T14:58:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xoc](https://avatars.discourse-cdn.com/v4/letter/x/8e7dd6/32.png) [@Xoc](https://forum.kirupa.com/u/Xoc)\
**Post date:** [March 27, 2006, 2:58pm UTC](https://forum.kirupa.com/t/weird-loadclip-behaviour/183488/1 "2006-03-27T14:58:45Z")

</div>

I’ve got a nicely functioning swf that I’m trying to make a preloader for. I’ve opted for the path of having a small preloader swf load the main one. Even though the main.swf works beautifully as a stand alone, there are all kinds of problems with it if I import it into \_root.mcHolder with loadClip.

1. One of the two music tracks doesn’t play anymore.  
[INDENT]The one in the timeline works, but the one loaded with actionscript doesn’t:  
\<AS\>sound = new Sound();  
sound.attachSound(‘soundclip.mp3’);  
sound.play();\</AS\>[/INDENT]2. The v2 scrollpane component falls apart in weird and not so wonderful ways.  
[INDENT]There are multiple instances of the scrollpane, and it has been skinned. When imported, the scrollpane has a green border when clicked, and all but the first instance fail to mask the content being scrolled (so it just runs up the screen).

[/INDENT]I’m at my wits end trying to work out why. I’m starting to think that it must be because Flash is broken, even though I know that there is a 99% chance the errors are mine, I just can’t work out what they could be, or why it works perfectly standalone but not imported.

I don’t think its a problem with loading the swf into the wrong level. I create a holder in the preloader to load the swf into, and the swf does not use absolute identifiers for the levels - everything is a child of the ‘app’ mc created with createEmptyMovieClip(‘app’,1);

Anyone experienced anything like this? Is there a workaround?
