Open FPS Tutorial Project - 'VisibilityCullingArea' error

Unity Engine
1

Hi,

I appear to be having a bad Unity day today. I’ve been working with Unity Iphone for about a month no problem, thought I’d finally install the standard Unity Indie and open the project FPS Tutorial, however immediately I get the following message :

‘VisibilityCullingArea’ does not denote a valid type.

I’m running on a MacBook Pro (latest gen), Snow Leopard, and latest version of Unity Indie, I read that Snow Leopard has caused problems with Unity however I work around those with Unity Iphone, and I don’t think this error is anything to do with that. I’ve also seen similar errors in scripts when changing standard unity projects to unity iphone versions.

Has anyone fired up the fpstutorial on mac unity with no problems?

Appreciate any help

Cheers,

2

Yap, im running the FPS tutorial on the Mac OS X no problem, im running it on a MAC-mini and works actually better then on my Windows.
Good luck with that…

3

Which file and line of code are producing the error?

4

Sorry for the delay, I’ve just tested it again now, and it doesn’t error anymore. Which… makes not a blind bit of sense, since I don’t use Unity very often, only Unity Iphone, nothing could have changed. I’ll try and recreate it, when it happened it was a complete show stopper and restarting Unity and opening the project again didn’t help, now it won’t reoccur so I’m even more befuddled and just look stupid :slight_smile:

The error was in script VisibilityCullingArea or VisibilityCuller from what I remember.

Cheers

5

you didn’t by error open a unity iphone project with unity indie.
because occlusion culling and visibility areas are a unity iphone only thing and don’t exist on the unity desktop (indie / pro )

6

yeh I thought that, I checked though and opened the project more times than I can remember correctly and it failed everytime hence I signed up just to post this thread whereas normally I’m a silent observer :). Curiously the ‘completed’ project worked fine, it was just the ‘tutorial’ project that was failing. I’d happily admit I was in error, but I just don’t see how so may have to lay this one to rest until I can recreate it, which so far I can’t do :confused: