I think it is included in the thread download section with other ACPI files as yours were the basis (the guide is still needs edits and I will give you and others the credit you all deserve). However, I received a comment from Rehabman at some point saying the SSDT for disabling optimus is 'an attempt but not working'. He said the method _OFF() have to be called in the SSDT to actually disable the card.
Well, if you take a closer look at this ssdt, it consists of
\_SB.PCI0.PEG0.PEGP._DSM (Buffer (0x10)
/* 0000 */ 0xF8, 0xD8, 0x86, 0xA4, 0xDA, 0x0B, 0x1B, 0x47,
/* 0008 */ 0xA7, 0x2B, 0x60, 0x42, 0xA6, 0xB5, 0xBE, 0xE0
}, 0x0100, 0x1A, Buffer (0x04)
0x01, 0x00, 0x00, 0x03
If you look at _SB.PCI0.PEG0.PEGP._PS3 method in ssdt5, you'll find this
If (LEqual (\_SB.PCI0.PEG0.PEGP.OMPR, 0x03))
Store (One, DGOS)
Store (0x02, \_SB.PCI0.PEG0.PEGP.OMPR)
so, it calls _OFF method if OMPR is set to 3.
And, if you look at what _DSM does with the parameters provided in the call, you'll notice that one of the side-effects will be setting OMPR to 3. Looks like _DSM with these parameters makes some preparations needed to turn GPU off safely/in a proper way.
Also, in your guide you recommend to inject string into AirPortBrcm4360 > info.plist > IONameMatch. There's a bit more update-safe way. You can do Toleda's DSDT patch from here http://www.insanelym...pcie-half-mini/ , there's only one difference: in the original patch, properties are injected into RP04. In our DSDT, RP04 is wired LAN, and wireless LAN is RP05, so you have to inject PXSX into it, or you'll break both LAN and WLAN.
The ultrabay PCI-E seems to be connected to the display and not the optimus.
This is highly unlikely. In windows, NVidia reports that display is connected to GPU#0, which is not ultrabay GPU. Maybe I'll have more time to get it working on the weekend.
I stopped getting such problem once I fixed the Clover version and most of its configurations, efi images, etc. It is not a scientific approach and I have not made any research for the reason to get these but certain configuration can lead to this. The steps I listed here in the guide will not result in this, I hope.
I think that this is related to DSDT patching, though the only patch I have is FixRegions. I'm gonna try Clover's debugLog/have a closer look at my dsdts.