Jump to content

meaganmargaret

Members
  • Content count

    137
  • Joined

  • Last visited

About meaganmargaret

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
    Female

Recent Profile Visitors

1,473 profile views
  1. meaganmargaret

    Vega Frontier Edition on High Sierra

    Just to be clear! That VegaTab I posted is for XFX Vega 64 cards only, and I made that clear in the post. I also recommended in the post that if you use another card (and you are @hackaro), you should generate a VegaTab that fits your card. Or, use another method to generate a driver that fits your particular card better. And, @CMMchris, on the XFX Vega 64 card that VegaTab was generated for, on full load the fans typically went up to 2800 rpm, sometimes higher.
  2. meaganmargaret

    Vega Frontier Edition on High Sierra

    Well, thanks. That answered my question. Appreciate it!
  3. meaganmargaret

    Vega Frontier Edition on High Sierra

    Thanks, Chris! But how did you get the second parameter, the clover properties?
  4. meaganmargaret

    Vega Frontier Edition on High Sierra

    So, the PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) is a static value that you just entered? You didn't look it up in IOReg? Or anything else? Oops, my bad: Your value was determined by the result of your gfxutil: PciRoot(0x0)/Pci(0x1,0x0) and your addition of: Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0), which is an arbitrary value you pulled from one of Chris's posts?
  5. meaganmargaret

    Vega Frontier Edition on High Sierra

    Hey, how did you get the Clover properties value? I got the DevicePath value, but not the Clover properties value. How did you get that value?
  6. meaganmargaret

    Vega Frontier Edition on High Sierra

    One thing folks should keep in mind with Vega 64 cards: Power! Vega's draw lots more power than nVidia cards, and a highly driven card could easily exceed 300 Watts. Think about that when you are configuring your systems, and make sure you have enough power in your system to support these cards.
  7. meaganmargaret

    Vega Frontier Edition on High Sierra

    Okay, this is my final shot on this topic....... First of all, I haven't loaded FCPX in a long long time, but just in case, I decided I would see if I could reproduce your issues. The short answer is: I couldn't. Running with the VegaTab_Best kext, I first loaded Bruce X 5K test. If anything could crash FCPX (10.4.3), this should be able to. Then I exported it at 5K (5120x2700). In less than 10 seconds it outputted a complete final movie and it was perfect. It ran flawlessly. Then I opened an older project, about 2 minutes long. It was loaded with special effects, color corrections, transforms, 3d text, customized audio, stabilization, etc. I exported it and again, FCPX flew through it with no problems, and quickly, very quickly produced a final project, and it was, again, flawless. I really don't know what kind of computer you are running, but it appears to me there's more going on with your system than just the graphics card drivers. At any rate, if my kexts don't work for you, work with Max or CMMChris and use their configurations, and, at this point, just work with them. On the previous page, CMMChris posted a config that might work for you using the insertion method.....try it! I can't help you any further than I have. Sorry it didn't work out for you.
  8. meaganmargaret

    Vega Frontier Edition on High Sierra

    I don't use that method, so I can't help you as to why it didn't work. I am on Mojave, and using the method I use, (which is to copy the kext into EFI\Clover\Kexts\Other) these kexts work fine. I have tested them with Heaven, Luxmark, and Geekbench (compute). I work on this computer every day, and I've had no issues. The 30Best is the one I use, but if you're feeling like you want to be safer, you could use the 29300kext, or even use one of Chris's kexts (like the one he says give you 28000 on a Luxmark). Be careful with Plist Editor Pro if that is what you used. For that editor, you must have the hex version of the configuration data, and I don't have that. If you copied the TGII.... into Plist Editor Pro, it will fail. If you used TextWrangler, that would be okay, but then I really don't know what happened and why it wouldn't work. As I said in another post, I only copy the 30best kext into EFI/Clover/Kexts/Other, because for me, that is so very very very much easier. Much easier to change as well. If I were you, I would copy the current config.plist to another place (say on your desktop). Then I would take the remaining config.plist that should still be in your EFI folder and delete that insertion method entirely, (and I do mean ALL of it - every bit of it, all the tables you entered and devices for the Vega card) and copy the 30Best kext into EFI/Clover/Kexts/Other and reboot and test. (Remember, you have your original config.plist with all of your previous configuration data for the insertion method sitting on your desktop). If that works, then there is something wrong with your insertion method, and that you would have troubleshoot on your own. But to revert back to your insertion method, all you would have to do is remove the config.plist (the one that doesn't have the insertion method anymore) and replace it with the one (the config.plist that should still have your initial attempt using the insertion method) on your desktop. Okay, I've got things I need to work on, so I have to move on. Hope that's helpful.....
  9. meaganmargaret

    Vega Frontier Edition on High Sierra

    Either one will work: 1. Move the 30Best kext to EFI\Clover\Kexts\Other (or 10.14). Put it in the folder where all of your other kexts are.. OR Insert the values you have already in inside Device Properties.....what you have looks okay, but make sure you are using a text editor to do this. IF you intend to use Plist Editor Pro or Xcode, you can't use the TGII as this is text and won't work there (there you would have to use the hex version (B602....."). I don't think I still have the hex output for those two kexts that I posted. Either method will work, but just do one of the two. If you choose one and it doesn't seem to work, delete that method and use the other. For me, it's easier to just if I want to change or alter the performance of my card to just delete the kext from EFI\Clover\Kexts\Other (that's where I keep all of my Clover kexts), and replace it. But there are probably good reasons/arguments for doing it the other way too. And, I want to be very clear to everyone: The kexts I posted should work with an XFX Vega 64 card. I am not advocating the use of these kexts for any other card. Will they work with other Vegas? Probably, but they are configured and tested on my XFX Vega 64 card and so are specific to my XFX card....
  10. meaganmargaret

    Vega Frontier Edition on High Sierra

    Well, which one did you use? The 29K one or the 30 one? And 20fps less than what? What were you using that was 20fps more? And no you shouldn't change AMD10000Controller.kext. In fact, you should have a plain vanilla unmodified original AMD10000Controller.kext to use with these kexts...... This all depends on the method you use. Max prefers to modify AMD10000Controller.kext, and that's perfectly valid. But my method, and also Chris's method, best I can tell, is to leave AMD10000Controller.kext alone and just use VegaTab to create a kext to influence the performance of the Vega card in macOS, applying it by adding a kext in Clover - Kexts - Other, or inserting the configuration generated by VegaTab via the Clover - Devices configuration page of Clover Configurator. I would suggest you choose one of the two methods, and not mix the two of them, as that will produce erratic results. The main reason I posted my kexts is because I have an XFX card, which has been denigrated in this forum, and other places, and little development has been done on it. I wanted an XFX Vega 64 working kext posted from a real user of an XFX Vega 64 card to be available for XFX Vega 64 owners. And both of the kexts I posted run well on my system and produce great results. Are they perfect? No, they are not. They produce respectable results. BUT, they are ONLY for XFX Vega 64 cards!! If you're not satisfied, then you should spend some time with VegaTab and see if you can produce a Kext that gives you the results you need. Good luck.....!
  11. meaganmargaret

    Vega Frontier Edition on High Sierra

    I should note that the 30200 kext (the one labelled "best") matches the Windows built-in Vega configuration performance for a Vega 64 XFX card ONLY (do not use for any other card!!) almost exactly. Fan speeds, Luxmark results, temps, pretty much the same. It might pull more power, but I can't tell. The 29500 kext has more moderate settings, with lower initial power (I think I set it to 100). Finally, I ran Heaven on both and some other tests, but I got a very good score with the 30200 kext (again the one labelled "best") at 1080p. On Heaven, it appears to run hot (according to Heaven), but the temps that I got from running the ioreg script in terminal were much lower......don't know why, but it completed Heaven just fine. Got a good Metal score on "compute" from Geekbench (around ~220000) Of course.....YMMV......we all understand that, right?
  12. meaganmargaret

    Vega Frontier Edition on High Sierra

    So, here's a screen shot.....it shows the settings for MSIAfterburner which puts PP_PhmSoftPowerPlayTable into the registry, (for me, after a reboot)
  13. meaganmargaret

    Vega Frontier Edition on High Sierra

    Well, yes it can. The PP_PhmSoftPowerPlayTable doesn't show up normally, but if you download MSIAfterburner and load it up (your AMD Vega card does not have to be MSI, btw - my Vega 64 is an XFX), and go into settings and tick "show extended power adjusts" (Thanks Max!!), the PP_PhmSoftPowerPlayTable will show up in the registry. You will have to massage it some to get the tables to hex version (so that they will show up like the "B6020801 0050....., etc" like CMMChris shows a lot in his VegaTab kexts). Then you can convert them using a couple of different methods. Iodine131 outlined one method in this thread - check page 11 of this thread, his post dated June 21 for that method. If you add in the hex version using Xcode, and then save the file (info.plist), and then open that in Clover Configurator, it will show you the version (text) that usually starts with TGII....
  14. meaganmargaret

    Vega Frontier Edition on High Sierra

    No, didn't find it yet......the existing macOS driver works ok, but I want it better, and so I will see if I can find it, and then post it here.......
  15. meaganmargaret

    Vega Frontier Edition on High Sierra

    Thank you, Max!!! I mean, it works now, and it's not bad, but I'd just like to tune it a bit, and the Windows version of the driver is just a little better, so I thought I'd take a shot at seeing if I could convert it. Again, thank you very much!
×