Macbook Pro Retina (Yosemite) and Process errors on 1.08.03.1123

[photosinferno]

Hi,
I'm having issues with Pixinsight Version 1.08.03.1123 on my Macbook Pro 15" Retina running OS X 10.10.5.

Program starts and loads projects/Files as normal - These at the moment are files and projects that originated from a PC- however when I try and perform a STF process on a loaded image I get the error message ' Unknown Exception'.
If I then try and continue to work in Pixinsight (e.g. click on an image click or click on the screen background) It will then come up with the error 'Critical signal caught (11): Segmentation Violation' - then gets stuck in a loop of saying that till you ‘Force Quit’ with the OS.

I have tried downloading the 'Obsolete version' for Mac OS X that didn't work either.
I've tried running it with or without updates (the ones that pixinsight tells you is available ) to no avail.

i'm currently a bit stuck with this  , so any help/ideas would be welcome.

Regards
John

[Russ]

I also use a MacBook Pro with Retina screen and have the same version of PixInsight as you. My OS is version 10.10.5. I don't have any problems with PixInsight.

I'm eagerly waiting for the Mac version 1.8.4 of PixInsight. What a pleasure it will be when PixInsight will support a Retina screen! Maybe the sensible thing for you is to wait for 1.8.4 to arrive and see if that resolves your issues.

[photosinferno]

Russ,
Thank you for that information.
 I feel however that the only potential for me going forward is to try an erase and install of the OS - as no other options are currently on offer.

John

[pfile]

can you upload a small project that exhibits the problem somewhere? i wonder if this is some kind of platform interoperability problem rather than a specific problem with your machine.

rob

[photosinferno]

Rob,
Thankyou for the ideas - Have also spoken to another user who suggests that one of the issues could be that the projects I created on the PC were on a later version of PI (1.8.4) so the issues could be the backward compatibility.
Also tried holding down the 'Control' key and resetting the 'pref' file for PI - and that seemed to resolve the issue so far.
So currently in testing mode with projects etc.

Many thanks
John

[pfile]

ah hah, yeah it could just be a PI version compatibility problem.

rob