[Release] Hackintool v3.x.x

[headkaze]

Edit: Just done a bit more testing, it works if I check VRAM on the General options page, but then it also generates code for framebuffer-fbmem and framebuffer-stolenmem which is different behaviour from previous versions which would only generate code for framebuffer-unifiedmem if the 2048MB VRAM option was ticked and the VRAM option unchecked.

You probably have DVMT pre-alloc 32 MB set or Patch->Apply Current Patches and it's applying current VRAM patches.

 

[headkaze]

Hackintool v2.3.7 Released
- Improved Clover EFI Mounting
- Clover PCI export now uses SubClass for device_type

 

[jaymonkey]

You probably have DVMT pre-alloc 32 MB set or Patch->Apply Current Patches and it's applying current VRAM patches.

@headkaze,

Nope i don't have either of those options enabled ...



Its not an issue for myself as I can work around it but the behaviour is different to earlier versions (detailed in my guides) where you could just check the VRAM 2048 MB (in Patch -> Advanced) and with the VRAM option unchecked (in Patch -> General) the patch generator would add the following :-

                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-unifiedmem</key>
                <data>
                AAAAgA==
                </data>

So basically it used to just add the 2048MB VRAM Patch, however if you try this with current version it only adds :-

                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>

Checking the VRAM option (in Patch -> General) the patch generator adds all of the following :-

                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-fbmem</key>
                <data>
                AAAAAA==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-stolenmem</key>
                <data>
                AAAgAg==
                </data>
                <key>framebuffer-unifiedmem</key>
                <data>
                AAAAgA==
                </data>

So it's not possible to just apply the 2048 MB VRAM Patch with the current version ...

Hope this makes sense

Cheers
Jay

 

[headkaze]

Hope this makes sense

I'm not ruling out a bug just yet; I'm just not seeing the behavior you describe. I'm guessing you don't have "Auto Detect Changes" set?

 

[headkaze]

I took the attached screenshot of its menubar popdown of resolution choices and I see that 2560x1440, which I just selected, does not have a HiDPI icon to the right of it... if that answers your question.

Can you send me your DisplayProductID-xxxx file. I don't see why the resolution you've added is not being shown.

 

[buddyjack2]

Can you send me your DisplayProductID-xxxx file. I don't see why the resolution you've added is not being shown.

No problem. Exported from Hackintool version 2.3.7. Had to zip the folder it was in to be able to attach it here.

 

[headkaze]

No problem. Exported from Hackintool version 2.3.7. Had to zip the folder it was in to be able to attach it here.

I'm at a loss really. If you visit https://comsysto.github.io/Display-...or-with-HiDPI-Support-For-Scaled-Resolutions/ and enter 2560 x 1440 with hidpi unchecked it generates "<data>AAAKAAAABaA=</data>" which you have in the file you attached.

 

[headkaze]

Hackintool v2.3.8 Released
- Bug fixes (thanks ReddestDream)

 

[hackmefrancis]

@headkaze

What does the PCI Devices do under the Patch tab? Is this use to populate the PCI section of System Report? And is it necessary to have this patch?
Thanks.

 

[jaymonkey]

I'm not ruling out a bug just yet; I'm just not seeing the behavior you describe. I'm guessing you don't have "Auto Detect Changes" set?

@headkaze,

You where quite correct .... I did not have "Auto Detect Changes" checked.
With it set the 2048MB VRAM patch code can now be generated on its own.

Sorry for the false alarm buddy ... my bad.

Cheers
Jay