It's a no from me - although I'm trying on a 2014 MacAir, so it was always a gamble. I get a crash at the title screen (although it ran Shadow of Mordor just fine, so I suspect it can run it on minimum settings, there's just some sort of software call that panics it).
Anyone had any luck?
Well, that's mildly terrifying to hear. I'm on a Late 2013 Macbook Pro, mid-range. Hopefully I'll be able to run it-- won't know for another seven hours.
Damn.
It's a no from me - although I'm trying on a 2014 MacAir, so it was always a gamble.
Can you change any config files to lower graphics settings before it starts?
I'll be playing on PS4, but i have a 2014 11" Macbook Air which played Diablo 3 fine, and would be great to get DA:I working for a semi-portable fix; please update us if you get it working.
Can you change any config files to lower graphics settings before it starts?
I'll be playing on PS4, but i have a 2014 11" Macbook Air which played Diablo 3 fine, and would be great to get DA:I working for a semi-portable fix; please update us if you get it working.
I've been fiddling with that - no luck so far. I've had aid from a Bioware rep on here: the problem is the config file is only generated after the first save. Another forum member kindly posted his, and I constructed the folders and file and have been poking about..... but no luck so far.
I can get it running if I launch than go to another window, so it loads in a window - you can see the marching chaps in the main menu as a window in the background. But as soon as you click on that window, boom crash.
I'm pretty sure that menu is an in-engine generated scene, so I don't think it's a hardware issue, I think it's a software issue.... which I think is something only Bioware can fix.
I got mine to work just fine on a 2013 Macbook Air in Bootcamp (Windows 7). It doesn't look very pretty (everything is on low settings), but it loaded without any glitches and is playable so far (FPS dips noticeably in heavy combat, though).
I'm sorry you're having trouble! I don't know how to help exactly, but if you have specific questions for me about what the files look like on my end or something, please feel free to ask.
That menu scene is not engine rendered iirc, but I'm not sure if the vfx and such that plays on pressing start is.I'm pretty sure that menu is an in-engine generated scene, so I don't think it's a hardware issue, I think it's a software issue.... which I think is something only Bioware can fix.
I got mine to work just fine on a 2013 Macbook Air in Bootcamp (Windows 7). It doesn't look very pretty (everything is on low settings), but it loaded without any glitches and is playable so far (FPS dips noticeably in heavy combat, though).
I'm sorry you're having trouble! I don't know how to help exactly, but if you have specific questions for me about what the files look like on my end or something, please feel free to ask.
Interesting! That's essentially an identical system, bar minor bumps. That means there's clearly a solution!
I'm using Windows 8 though, and also updated this morning to Intel's new graphics drivers (which Windows doesn't auto-recommend, I used the Intel updater).
I might try rolling back the graphics driver and maybe trying Windows 7 compatibility?
That menu scene is not engine rendered iirc, but I'm not sure if the vfx and such that plays on pressing start is.
(Edit) actually the vfx I'm thinking are only from actually starting a new game, so when you click start I think that's when profileconfig and such might get generated?
Hmm..... the mystery deepens! But if the previous generation of Macbook Air works on Windows 7, this must be either an OS issue (unlikely, given it's built for W8, and I don't think a Bootcamp W8 is any different, practically, for a program running on it than without an OS partition ) or possibly the latest Intel 5000 graphics driver (which came out about 6 weeks ago).
Rolledback to last drivers from Intel, and tried on Compatibility for Windows 7.
No luck, still crashing.
I'm tempted to wipe and install Windows 7 if others have had luck.... but it seems a bit extreme.
Rolledback to last drivers from Intel, and tried on Compatibility for Windows 7.
No luck, still crashing.
I'm tempted to wipe and install Windows 7 if others have had luck.... but it seems a bit extreme.
I didn't do the latest Intel graphics update, but I guess it's not that, then. I hope you're able to figure it out soon. There MUST be a way 
Also, maybe if there's a Day One patch, that will fix things? I'm assuming there will be a patch with the NA release at midnight.
Also, maybe if there's a Day One patch, that will fix things? I'm assuming there will be a patch with the NA release at midnight.
To be fair, I suspect people running on Bootcamp on under-specced machines are such a tiny market segment to not really hit that FIRST DAY PATCH! sweet spot.... 
I tried playing the game and it invariably locks up on the main menu screen about 10-20 seconds into launching. Complete freeze, necessitating a crtl+alt+del wipe.
Late 2013 mid-range MacBook Pro running Windows 7 through Bootcamp, 8 GB ram, quad core i5, 5100 Iris Graphics. Strange that it can't handle DAI at all; it seemed to do fine with several other recent games.
Edit: Going to try seeing if I need to update my graphics card drivers, I'll report back once that's done.
Upgraded my Iris 5100 drivers to the newest available version (according to Intel's in-house utility), and now the game won't even start. Instead of locking up at the main menu screen, it just flickers to the black beginnings of launch and then flickers back out to my desktop without initializing the game.
How very unfortunate. I thought updating drivers was supposed to help.
I have it running on Windows 7, ultra settings (with the exception of shadows). My fan's running full force but I'm getting ~30-50 fps.
I have a more powerful machine though. iMac 3.2 GHz, 16GB of RAM and an Nvidia GTX 680MX 2GB graphics card.
Looks like my laptop's processor is actually a dual-core, and I was just a moron thinking that it was a quad-core because four separate units showed up in the Device Manager window. Whoops.
Although, emma-v said they got the game working on a 2013 Macbook Air, and as far as I know all of the Airs from that year are dual-core as well... quite curious indeed.
Not sure whether to just give up now, or hold out in case something is dug up to fix whatever the underlying issues are.
There are now three or four reports on this forums with the identical problem, but running on pure-blood PCs.
Maybe this is simply a quad-core or nothing issue, rather than anything particular to the quirks of Bootcamp?
At least there are now a handful of us, so it might be patched (or at least be told "Yeah, sorry, it's quad or nothing").
Oh dear... from this tech support thread:
http://answers.ea.co...en/td-p/3983595
it seems that this issue is indeed zero to do with Bootcamp, and entirely about dual core vs quad core...... and it looks like it's not going to be fixed, but rather a "Sorry...you're below minimum spec.... get a refund".
Hi guys,
Thank you all for the quick replies with your DxDiag reports.
I hate to be the bearer of bad news, but it looks like all of you are on dual core CPUs. Dragon Age: Inquisition requires a quad-core CPU.
If you ordered a digital copy of the game on Origin and you absolutely won't have a chance to play the game on a computer that meets the minimum requirements, you can request a refund (granted that you are eligible) here: http://help.ea.com/en/refund/
Cheers,
Nils
Retour en haut