On the attached file, left resistor appears to be missing and right resistor appears to be in a vertical Orientation. Is it possible for you to confirm what resistors are in place. So that is encouraging and leaves hope that we'll be seeing improved 7000 kexts in the following OS X increments. Word is, ati has actually been contacting some companies like blizzard already about any issues their games have with 7950.
1440p civilization v wallpaper mac#
Apparently ati is backing the official saphire mac editions after all. I'm hoping by poking blizzard, they will put some weight on ati to address this. any other games don't have issues with fuzzyness though. It's only SC2 and D3 that really dislike the rom though with the way they do resolution code, well that and OS X THINKING best resolution is a non native one for my cinema display. Not something that is the result of the modding. Oh mine is a factory mac edition sapphire unmodded, which is why i commented the resolution behavior is obviously something in the original rom that likely carried over to the modded roms. Did you add EFI to your original ROM or flash the ROM that ROMINATOR posted? I also get corruption on the boot screen towards the end. I just flashed my reference AMD 7950 and noticed the same thing. Still, it is a bit annoying that the firmware on card is giving odd best for display data. It seems unique to sc2 though so i'm sure blizzard will have to address this particular issue. translation, with 7950 i have to play at 2560x1600 or a scale resolution with fussy text and not as sharp of an image, even though i played at a crisp 1680x1050 before. it actually causes issues with starcraft 2, as blizz tries to force what OS X tells is your native resolution, then offers it's own scale options that fuzzy up the game if you play at anything other than native. so now i'm running "scaled" down to 1680x1050.
Post by: Concorde Rules on March 29, 2013, 12:19:03 PMīut the "best for display" resolution is set to 2560x1600i noticed on official card that for some reason as well, it set my screen to that even though native resolution is 1680x1050. I tried on a Sapphire 7870 and it ran 3 screens with ease, but HDMI was gone.
1440p civilization v wallpaper full#
I have seen the behavior of drawing a 1920x1200 at 2560x1600, at first I thought my eyes were going bad.Īre you certain that you have full acceleration? Only 1 display working is standard for when it is in "safe" mode. Easiest to start with a reference design and go from there. When choosing a card to flash, the #1 consideration is that the ports be the same. But it's always fun to tinker! :)Įdit: I should add that I'm using a MacPro early 2008. I'm reverting back to the old rom since I don't actually need the boot screen. Oh, and when adding the EFI part to the rom, parts of the shell script wasn't working well when there is a space somewhere in the file path. Maybe this is the reason the miniDP ports showed a black screen? Card is showing up as a HD7950 in "About this Mac". For some reason I got a picture even at 2560x1600. DVI works, but the "best for display" resolution is set to 2560x1600 (even though my screen has max resolution of 1920x1200). The miniDP ports don't seem to work, getting black screen. I must add that I'm using modified AMDRadeonAccelerator.kext and ATI7000Controller.kext (can't find the post at anymore) with the ID for 7850 added, but I dunno if that's needed.
I managed to apply the HD7950 EFI part to my Gigabyte HD7850 OC 1GB () card and it sort of works. if its much larger than 65kb) then it will be overwritten with new efi part WARNING, if you have uefi part in bios already (e.g. makerom.sh -efifile=7950mac.efi -romfile=efiromheader.rom -originalrom=cardname.rom -devid=697a Run script, replace 697a with your deviceid and cadname.rom with your actual original video bios file It is ONLY FOR MACPRO, hackint0sh doesn't need this, it will not make hackint0sh run a little bit betterĭump bios from your 77xx-79xx card and save it into this folder as cardname.romįind your 4 digit deviceid (if its 697a1002, then obviously you need only 697a, since 1002 is ATI vendor id (dont be stupid here, please) No framebuffer name change yet, so far testing ability to get bootscreen
0 kommentar(er)
