For got to post the crash text:

Exception: Access Violation (code 0xc0000005) at address 0045DF3C in thread 15A8
Module: WorldOfGoo.exe
Logical Address: 0001:0005CF3C

01408F70 0045DF3C 0001:0005CF3C WorldOfGoo.exe
Params: 00000000 00000000 0140A410 00000001

StackWalk failed (error 299)

EAX:00000000 EBX:0C22BA18 ECX:0012F900 EDX:004BE5D0 ESI:0C21F697 EDI:005D253B
EIP:0045DF3C ESP:0012F820 EBP:01408F70
CS:001B SS:0023 DS:0023 ES:0023 FS:003B GS:0000
Flags:00010216

Windows Ver: NT 6.0 Build 6000
DDraw Ver: 6.0.6000.16386
DSound Ver: 6.0.6000.16386

Product: Product
Version:
Time Loaded: 00:00:29
Fullscreen: No
Primary ThreadId: 15A8

Hey Joris...
The crash text is ALWAYS pretty much useless.... and there's loads of little things that can make WoG crash...
1) When does WoG crash?
2) If you can produce a goomod, upload it to an external site (mediafire, rapidshare.. or whatever).. I'll dl and take a look.

I'm interested because I'm trying to find all the ways you can crash WoG, so I can get WoG Editor to recognise them, and warn / fix them.

I start the level,the title screen appears and then it crashes.

Addin: http://www.mediafire.com/?hzcyit21t22

Wow... that was a toughy to find!
It's a new one on me... so thanks for posting about it!
It shows a "weakness" in the coding of WoG (IMO)

The problem is...
The level has a Strand which links goo11 to goo12 (Anchor to Water)
But the Strand Entry appears in the list (and the file) before the "BallInstance" entry for goo11
Looks like WoG crashes if it finds a Strand before it finds one of the balls it connects.

Solution...
Delete the Strand goo11 -> goo12 (Easiest if you select it in the tree list)
Then add it again.

Adding it again, adds it at the bottom of the list (end of the file) so the goo is now before the Strand... so no crash!

Please confirm that fixes it for you!

I'll see if I can get WoG Editor to spot that, and warn / fix it before you try to play.

Also.. a couple of tips.
i) Always set the depth of your background image to less than 0 (even if it's only -1) That way you can see the strands.
ii) You'll need to change the Scene bounds because atm you can't move the camera to most of the level.

Well,it fixes it,but I can't move the camera.I know nothing at all about cameras and POIs,so,can you fix the camera problem for me?Please?:3

The problem isn't your camera or poi's...
The problem is your scene bounds. (see ii in my previous)

Click the Scene tab and click the top item (scene)
You'll see minx,maxx,miny,maxy in the properties
These set the edges of the level, and the camera won't ever go outside them.
They show as the black - - - rectangle in the middle of the WoG Editor view.

You need to set
minx about -1000
maxx about 1000
maxy about 1200

And because almost everything is asleep, your should also...
Go to the Level Tab, click the top item (level) and change autobounds to false

This should let you see the level and move the camera around.

Thanks !

Worked!Uploaded,waiting for publishing*yawn*

Check the page.. and read my comments...

Now read mine!