Jump to content

sl0wtarget

Members
  • Content Count

    43
  • Joined

  • Last visited


Reputation Activity

  1. Like
    sl0wtarget reacted to izo1 in AMD Radeon Vii in macOS Mojave   
    Why? I sold my Vega FE and bought a Radeon VII
     
    Only ~$250 difference (+Waterblock of course). Worth the upgrade for me (I can play 4k games easily at high framerates) and it does better in certain applications.
     
    Also if you want you can sell the games it comes with on eBay and save some more. I'm not sure about EU prices though, this is for USA only.
     
    To me Radeon VII is what Vega 64/FE should have been. I wasn't super happy with Vega FE performance, but I am extremely happy with Radeon VII. It should last for a couple of years.
     
  2. Like
    sl0wtarget reacted to CMMChris in AMD Radeon Vii in macOS Mojave   
    Radeon VII arrived and working well. No AGDP patch or Whatevergreen needed. PowerPlayTable modding is working as well. Did a 970mV UV and with that Dirt 4 runs at 1440p with max settings at stable 60fps (Vsync) with barely audible fans.

     
    Edit:
    Gaming Performance
    (recorded with Quick Time)
     
    Benchmarks

  3. Thanks
    sl0wtarget reacted to MACJO in AMD Radeon Vii in macOS Mojave   
    Hi everyone.
    What about the performance of the Radeon VII vs Vega 64 ?
  4. Like
    sl0wtarget reacted to gnarfy in AMD Radeon Vii in macOS Mojave   
    thanks guys, I moved from Mojave to Beta and my radeon 7 is now fully accellerated ! awesome!
  5. Haha
    sl0wtarget reacted to Wozniak in AMD Radeon Vii in macOS Mojave   
    I just found the problem ! Clover was configured with ATI inject. I turn it off. If it can helps someone!
    Thanks a lot anyway, I finally finished my Mackintosh !!
     
     

  6. Thanks
    sl0wtarget reacted to Hameer Abbasi in AMD Radeon Vii in macOS Mojave   
    Success. I just hope there aren't any more freezes. Note that you do not need the kext in the public beta at all, everything is native.
     
    https://browser.geekbench.com/v4/compute/3844879
     
     
     

     
    Even GeekBench Metal works:
    https://browser.geekbench.com/v4/compute/3844952
  7. Thanks
    sl0wtarget reacted to Pavo in [pre-release] macOS Mojave 10.14.5   
    Looks like they added they added Radeon VII support.

  8. Thanks
    sl0wtarget reacted to blazinsmokey in Corsair iCUE (MacOS) Now Available as Open Beta!   
    TLDR, a lot of Corsair HID peripherals are now supported. I know there were other solutions like CKB-Next that got some things working but now we have a more streamlined experience. I hope this was the proper place to post this.
     
    Link below and the post it refers to.
    http://forum.corsair.com/v3/showthread.php?p=982647#post982647
     
     
    Hi everyone,
    It has been a long time coming but I am happy to finally announce the beginning of our OPEN BETA for iCUE on MacOS! 
    Link: http://downloads.corsair.com/Files/CUE/iCUE-3.10.125-release.dmg
     
    Some of you may remember that I was beta testing a macOS version of CUE2 about a year ago. Since we were planning to launch iCUE in early 2018, I made the hard decision to stop development on macOS for CUE2 because I did not want two different experiences on both platforms. We used this time to accomplish a few tasks:
    1.) Ensure that almost all of our CUE2 products will be supported on the macOS platform.
    2.) Complete iCUE for Windows and then port it over to macOS.
    3.) Validate it for MacOS on desktop and laptop models to ensure a clean transition.
     
    The difficulty of implementing iCUE on macOS wasn’t so much the software but the firmware. Due to architectural changes, existing firmware on our devices would not properly be detected in macOS iCUE. Those who tested CUE2 would be familiar with this issue. To resolve this problem, we had to implement a new protocol for firmware. This means that most users will have to update the devices on their Windows machine first, if you have a legacy product, while users with our newest keyboard (K68 RGB and newer) can actually use their devices out of the box without any update. For reference, here are all of the devices that will support iCUE without requiring a firmware update:
    K68 RGB
    K70 RGB MK.2 SE
    K70 RGB MK.2/RAPIDFIRE
    K70 RGB MK.2 LP
    Strafe RGB MK.2 
    M65 RGB Elite
    M65 PRO RGB
    K70 RGB LUX
    K70 RGB RAPIDFIRE
    SCIMITAR PRO
    STRAFE RGB
    HARPOON RGB
    All VOID headsets (except Stereo)
    All HS headsets (except Stereo)
    ST100
    MM800 (All versions)
     
    To prevent any potential issues with deploying firmware updates, we decided to stagger out firmware releases this time in batches for macOS compatibility. Therefore, the first batch of legacy products that will support macOS will be the following and are live already:
    K95 RGB PLATINUM
    K55 RGB
    K63 WIRELESS/SE
    DARK CORE RGB/SE
     
    Users should use iCUE (Windows) to update their hardware. You will know you’re on the proper firmware if you are on version 3.XX for the legacy devices (STRAFE MK.2 and K68 RGB will show 1.XX but already use the new protocol). For users who don’t have an access to a Windows machine, we are in the process of documenting how to do a manual firmware update with a Mac so you can do the update without iCUE. However, I advise using iCUE is the best method when possible. 
    I hope you all enjoy iCUE on a new platform as we’ve been working on this for more than a year and a half. We will start to deploy more and more firmware updates so if your product isn’t support yet, it will be by sometime in December. If any of you have any questions, feel free to PM me anytime. And as always, thank you for your support with our CORSAIR products!
     
    Regards,
    James
     
    FAQ:
    1.) What products are supported in iCUE for macOS?
    iCUE for macOS will only support HID products (keyboards, mice, headset, headset stand, and mousepads).
    2.) Why does iCUE for macOS not support DIY products?
    We use Windows Service to control DIY products and we also use CPUID SDK to do so. Unfortunately, neither of these are compatible with macOS at this time. We are looking at alternative methods but as most people are using macbooks and mac desktops, we don’t think there is a strong enough demand yet to support DIY with users who have Hackintosh’s. However, we are carefully monitoring feedback as well as investigating how to improve the overall experience when it comes to device support.
    3.) Is it possible to update firmware on iCUE macOS in the future?
    Yes but we have not uploaded any firmware for this platform yet. We will do so soon so we can continually monitor people’s experiences during the open beta.
    4.) Is there anything missing from iCUE macOS from Windows besides device support?
    We currently support all the features (Actions, Lighting Effects, Surface Calibration, Performance, Hardware Playback, Surround Sound, etc.) but one known issue is OSD. We are still working on that for macOS but do not have an ETA for now. However, all the main features of iCUE supported with your peripheral are available now.
    5.) Will we be able to update iCUE versions on macOS?
    Yes, when we deploy a new version on the mac, you’ll be prompted to update it through the software just like we do on Windows.
    6.) Is there anything special I need to do in macOS?
    If you want key repeat enabled in macOS, you will need to enable this through the terminal.
    This is the command to enable press and hold:
    Enable: defaults write -g ApplePressAndHoldEnabled -bool true <return>
    Disable: defaults write -g ApplePressAndHoldEnabled -bool false <return>
    (Thanks Manofclay)
    After you enable this, you will need to restart your system.
    7.) Is this an official release for macOS?
    No, this is just an Open Beta so we can gather bugs and feedback. However, this can be shared with anyone you desire.
    8.) What version of macOS does this support?
    We are supporting High Sierra and newer but we recommend using the latest if possible.
     
  9. Haha
    sl0wtarget reacted to Fergarth in [pre-release] macOS Mojave 10.14.4   
    Yep! Honestly, there is even more than one option! In fact, at least three options! Either Nvidia and Apple come to an agreement and decide to publish the Web Driver dedicated to Mojave, or you trade your graphics for an AMD RX or Vega, or just use Windows or Linux...
  10. Thanks
    sl0wtarget reacted to Slice in HWSensors3   
    Hi all,
     
    I created an installer for my version of FakeSMC with plugins and applications latest revision.
     
    Compatibility from 10.6 up to 10.11.
    Test, please.

    Download here: HWSensors.pkg.zip
    See my signature
     
    FakeSMC 3.4.0 revision 751
    HWSensors.pkg-751.zip
     
    New project home is
    https://sourceforge.net/projects/hwsensors3.hwsensors.p/
    where you can download most recent versions.
    Now it is FakeSMC 3.4.1
     
    Explanations about the difference between versions 3 and 6
      #137 
     
    20.05.2016
    Revision 32 with explanation at    #220 
     
    10.10.2017
    FakeSMC is 3.5.0 compatible with High Sierra.
    New plugin VoodooBatterySMC created on the base of VoodooBattery by Superhai but with SMC keys generating to show Battery voltage and amperage. As well it created key BATP needed for right speedstep and FileVault2.
    Other kexts revised.
  11. Like
    sl0wtarget reacted to unixb0y in Brief and simple way to explain DSDT and SSDT ?   
    This might be a bit late, but I found this FAQ that explains it pretty well: 
     
  12. Like
    sl0wtarget reacted to uisik34 in Brief and simple way to explain DSDT and SSDT ?   
    Hello everybody,
     
    In which case I may need these things to compile for my system? How do i understand it and how i can learn how to make it in right way? Or should I expect someone else has already managed and shared DSDT or SSDT on same configuration system like mine etc?
     
    Thanks
  13. Thanks
    sl0wtarget got a reaction from fantomas1 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    Update posted for 17G65, 10.13.6; WebDriver-387.10.10.10.40.105.pkg
  14. Like
    sl0wtarget got a reaction from Matgen84 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    FWIW, Firefox updated to version 60 and PDFs are displaying all black, again. smh
  15. Like
    sl0wtarget got a reaction from Matgen84 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    FWIW, Firefox updated to version 60 and PDFs are displaying all black, again. smh
  16. Like
    sl0wtarget reacted to Fergarth in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    Hi bocajoe, 
    Have you already figured it out?
    If not, search for this NVDA WEB PATCHER script or here on this site... it is the most practical and easy way to do it.
    https://github.com/chris1111/Easy-Web-Drivers-Patcher
  17. Like
    sl0wtarget got a reaction from bocajoe in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    106 work with latest Security update?
     
    UPDATE: According to xlr8yourmac the build changes to 17E202 and breaks the driver.
  18. Like
    sl0wtarget reacted to BreBo in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    NVIDIA Alternate Graphics Drivers for macOS 10.13.4 (17E199)
    https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.30.106.pkg
  19. Thanks
    sl0wtarget reacted to ricoc90 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    Your version prediction was wrong, @fantomas1 

    387.10.10.10.30.103
    https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.30.103.pkg
  20. Haha
    sl0wtarget got a reaction from fantomas1 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    Both are "404 Not Found."
     
    EDIT; Oh you KNOW I didn't double-check the grammar of your post!
  21. Thanks
    sl0wtarget reacted to ricoc90 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    If anyone is interested in testing, 
    I've made a new tool to patch the webdrivers.
    It does the exact same thing as the one I posted before, except now it uses dialog boxes.

    I decided to redo everything because I lost the code from the previous ones and because I'm bored.
    Downside: the script uses dialog and it will download and make the source if it is not present on your system.
    For more info about dialog, see https://invisible-island.net/dialog/
    Expect bugs.
    Download: NVDAWebPatcher.zip
    Screenshots:
     
  22. Like
    sl0wtarget reacted to Cyberdevs in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    new web drivers:
    macOS 10.13.3 High Sierra (17D2102) - iMacPro
    https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.25.160.pkg
    macOS 10.13.3 High Sierra (17D102)
    https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.25.161.pkg
     
  23. Like
    sl0wtarget reacted to Awesome Donkey in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    Well, I saw the lag with a Z370 board and Maxwell card and .158 so it can't just be Pascal cards.
     
     
    If it wasn't for this, I would've jumped to an AMD Vega card by now.
  24. Like
    sl0wtarget reacted to fantomas1 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    Guys, I just removed 2 pages of 'off topic' (or potentially) posts. I know it is hard to stay focused on the main thread, as dealing with webdrivers pushes us necessarily to talk about of the rest.
     
    But I'm asking you to do your best. I'm counting on you. 
     
    BR
     
    fantomas1
  25. Like
    sl0wtarget reacted to fantomas1 in Nvidia Web Driver updates for macOS High Sierra (UPDATE May 15, 2019)   
    Hi InsanelyMacaliens    
     
    Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS High Sierra.
     
    10.13.6
    Nvidia Web Driver - 387.10.10.10.40.128 --> build 17G7024 (thanks to flowrider) New!
    Nvidia Web Driver - 387.10.10.10.40.127 --> build 17G6030 (thanks to Extreme™) 
    Nvidia Web Driver - 387.10.10.10.40.124 --> build 17G6030 (thanks to flowrider) 
    Nvidia Web Driver - 387.10.10.10.40.123 --> build 17G6029 (thanks to Badruzeus) 
    Nvidia Web Driver - 387.10.10.10.40.122 --> build 17G5019 (thanks to TimeLord04) 
    Nvidia Web Driver - 387.10.10.10.40.118 --> build 17G5019 (thanks to ReddestDream)
    Nvidia Web Driver - 387.10.10.10.40.113 --> build 17G4015 (thanks to flowrider)
    Nvidia Web Driver - 387.10.10.10.40.108 --> build 17G3025 (check here)
    Nvidia Web Driver - 387.10.10.15.15.108 --> build 17G2307 (thanks to marcozardi)
    Nvidia Web Driver - 387.10.10.10.40.105 --> build 17G65 (thanks to sl0wtarget)
     
    10.13.5
    Nvidia Web Driver - 387.10.10.10.35.106 --> build 17F77 (check here)
     
    10.13.4
    Nvidia Web Driver - 387.10.10.10.30.107 --> build 17E202 (check here)
    Nvidia Web Driver - 387.10.10.10.30.106 --> build 17E199 (thanks to BreBo)
    Nvidia Web Driver - 387.10.10.10.30.103 --> build 17E199 (thanks to ricoc90)
     
     
    10.13.3
    Nvidia Web Driver - 387.10.10.10.25.161 --> build 17D102 (thanks to Cyberdevs)
    Nvidia Web Driver - 387.10.10.10.25.160 --> build 17D2102 (thanks to Cyberdevs)
    Nvidia Web Driver - 387.10.10.10.25.159 --> build 17D2012 (thanks to cyberdevs)
    Nvidia Web Driver - 387.10.10.10.25.158 --> build 17D102 (thanks to cyberdevs)
    Nvidia Web Driver - 387.10.10.10.25.157 --> build 17D2047 (thanks to cyberdevs)
    Nvidia Web Driver - 387.10.10.10.25.156 --> build 17D47 (thanks to darthsian) 
     
     
    10.13.2
    Nvidia Web Driver - 378.10.10.10.25.106 --> build 17C2205 (thanks to KGP-X99)
    Nvidia Web Driver - 378.10.10.10.25.105 --> build 17C2120 (see this post)
    Nvidia Web Driver - 378.10.10.10.25.104 --> build 17C205 (thanks to ReddestDream)
    Nvidia Web Driver - 378.10.10.10.25.103 --> build 17C89 (thanks to Il Francy MacPc) 
    Nvidia Web Driver - 378.10.10.10.25.102 --> build 17C88 (thanks to piiggggg)
     
     
    10.13.1
    Nvidia Web Driver - 378.10.10.10.20.109 --> build 17B1003 (see this post)
    Nvidia Web Driver - 378.10.10.10.20.108 --> build 17B1002 (thanks to BreBo)
    Nvidia Web Driver -378.10.10.10.20.107 --> build 17B48 (thanks to piiggggg) 
     
     
    10.13.0
    Nvidia Web Driver - 378.10.10.10.15.121 --> build 17A405 (thanks to Asgorath)
    Nvidia Web Driver - 378.10.10.10.15.120 --> build 17A405 (thanks to phi777)
    Nvidia Web Driver - 378.10.10.10.15.117 --> build 17A405 (thanks to phi777)
    Nvidia Web Driver - 378.10.10.10.15.114 --> build 17A365 (thanks to Asgorath).
×