launcher flashes for a milisecond, then quits

I have the exact same issues. Late 2013 Macbook Pro. I did find something interesting though:
After trying in bootcamp and getting the same issue, I tried it in a new virtual machine in Parallels. I had been running SWTOR in parallels quite often on my other MBP when I didn't need high frame rates, so I gave it a try.
The problem is exactly the same! I know for a fact that Parallels does not show the game an NVIDIA card, so I'm doubtful it's the video driver. I am using the same version of parallels I was using on my other Macbook, so the drivers should be identical.

But... the processor has changed, even in the virtual machine. So if video, audio, usb and all those drivers haven't changed and the only thing (I can think of) that has changed is the CPU, could it be possible the new Haswell processor is the culprit? If so, that should be a good direction to look for an answer I suppose.

Any thoughts (and hopefully solutions) about this?

EDIT: I'm seeing so many other threads with very similar issues I can't assume it's just the CPU anymore. Still, I'm keeping the post here just in case it helps find the source. If I need to do any testing, let me know.

Same here, new 15" retina launcher quits. I should mention I tried all the troubleshooting methods in the sticky in this forum and all the others mentioned above.

Ditto on my brand new 15" retina NVIDIA trying through bootcamp to 8.1. So frustrating. Could it be having to install by BIOS rather than EFI?

Is it possible to try Bootcamp 4 instead of 5 ? (sorry don't own a mac myself) if the older ones had 4 and newer ones have 5, that is another possiblitly, if that fails then it is likely not driver based.

So far, I tried it with a new installation on Bootcamp and as a virtual machine in Parallels and VMWare Fusion. I used a new virtual machine, not BootCamp. They all give the exact same result (short flash right after start, then nothing). Now, I also tested a Parallels virtual machine that worked on my previous laptop. Exact same image, same version of Parallels. Again, the same result. I also tried all suggestions I found online so far.

This means that many of the drivers (especially audio and graphics) don't matter to this problem because all methods I tested use completely different drivers for most components. That also rules out most of the BootCamp drivers. SWTOR does work on other machines and also DID work on the exact same version of Parallels and Fusion on Fusion (just started, no game) on my previous Retina Macbook Pro (early 2013, don't ask). Because I tested a previous image that worked a week ago, this also rules out anything in the Windows or SWTOR installation.

That means it HAS to be something that is unique to the new Macbook Pro 2013 that is apparent in BootCamp, Parallels AND Fusion. I think that's important information.

As far as I know, the only unique component in my tests is the CPU. So unless I'm making some assumption I shouldn't have, please fix the SWTOR CPU issue for the latest Haswell processors used in Apple Macbook Pros ?

Thanks in advance
Qira

Ugh, so happy/sad I found this thread. Having the same problems. I've tried Bootcamp, Parallels, Wine and even Crossover. Nothing works. It's awesome that I'm paid through next February for a game I haven't been able to touch for weeks now with no possibility of that happening again any time soon.

My main concern is that people with similar problems all post here and no developers read the thread :-/
I'm hoping they do, but I fear they might not be. Also, as far as I've seen, the only way to open a case is IN game or by calling them. I'd like to be able to send a support email detailing the problems in this thread. Did I miss where I can do that or is that really not possible?

Do this if you can, I forgot to ask if the Setup installed ?

If it did, open the main install folder and run the launcherDiag. Then mail the 2 created files to support@swtor.com.

They will look like this: diag12220332245_br and diag12220332245

You may have to send them separately if the file size is too large.

Just to follow if the setup did get that far and there is a launcher.setting file , can someone try the below settings just in case, even if the other folders don't all exist yet. trying to look at all possibilities for you guys.

Heya everyone,

Thank you very much for your reports. We had been investigating this internally and have made significant progress. We have learned that the recently released MacBook Pro utilized a new CPU which has a different architecture than previously implemented. Unfortunately, a third party library used by the launcher is incompatible.

We intend to deploy a fix with our next launcher update, which is currently unscheduled. As soon as we have more information or a timeframe for resolution, we will post an update in this thread.

We apologize for any inconvenience caused while we work to implement a solution. Thank you for your understanding and patience.