News: Unity 4.5 Breaks iVidCapPro Post-Build Processing

It has been pointed out to me that changes in the AppController.mm file of the Xcode project in Unity 4.5 have broken the iVidCapPro post-build processing, making it unable to add some necessary code automatically.

I haven’t installed Unity 4.5 yet, but it doesn’t surprise me that it broke iVidCapPro’s post-build processing. It’s rather sensitive to changes in AppController.mm.

The necessary changes can be made manually, however, and all will be well.  Many thanks to Eyal Erez for notifying me of the problem and for developing this workaround:

After you have built the iOS Xcode project, and before attempting to run it, add the following to AppController.mm:

// Added for use by iVidCapPro.
extern “C” EAGLContext* ivcp_UnityGetContext()
{
DisplayConnection* display = GetAppController().mainDisplay;
return display->surface.context;
}

after

void UnityInitJoysticks();

I have a looming deadline at the day job right now (just returned home after a 16 hour day :P) and it may be some time before I can release a fixed version.

6 thoughts on “News: Unity 4.5 Breaks iVidCapPro Post-Build Processing

  1. Hi Ive Followed the instruction on unity 4.5.0 but it gets me an error, I’ve copy
    // Added for use by iVidCapPro.
    extern “C” EAGLContext* ivcp_UnityGetContext()
    {
    DisplayConnection* display = GetAppController().mainDisplay;
    return display->surface.context;
    }

    inside UnityAppController.mm after the void UnityInitJoysticks(); but its gets me this error:
    http://f.cl.ly/items/3u1A420z2M420q3U3J0T/Screen%20Shot%202014-06-27%20at%205.38.24%20PM.png

    Can You please help me what should i do
    Thanks
    AMIR

  2. Hey Fille,

    Thanks for problem report and the follow-up! I’ve reproduced the problem you’re seeing and I have a fix in the works to the iVidCapPro post build script that should correct it.

    Cheers,
    James

Leave a Reply

Your email address will not be published. Required fields are marked *