Jump to content

Search the Community: Showing results for tags 'opengl'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Those who use Mojave with an OpenGL (non-Metal) Video Card in "dark mode" have noticed that global transparencies are working fine, while in "light mode" encountered the "grey" Finder menu bar and sidebars issues, this patch is intended for those who want to use Mojave mainly in "light mode" saving some transparencies around, so here is my "hybrid reduce transparency" patch. It is totally safe, harmless and reversible, it has been deeply tested and will 100% work until restart or logout, even after sleep lock screen it will still work. To return with normal "transparency" you can also do that from Accessibility prefpane disabling the "reduce transparency" checkbox. To use this patch just double click on this attached shell "mojavehld.command" and it will launch through Terminal. [METHOD 1: Enable hybrid transparency] After launch the mojavehld.command just follow these steps: type 1 type 4 close Terminal (CMD+Q) and any other app previously opened. (The choice number 3 is not mandatory) [METHOD 2: Force hybrid transparency] If for some reason after that you will still get Dock and Notification Center without "transparencies" then relaunch the mojavehld.command: type 2 type 1 type 4 close Terminal (CMD+Q) and any other app previously opened. Download attached here: mojavehld.zip
  2. Hi guys, long term lurker forced to post or be kicked out! Failed the quiz a couple of times so I guess I wasn't the hot shot I thought I was Anyway, cut a long story short. I've been developing for 30 years, and make apps for everything, but mostly iOS and mac. Onto the problem as I see it: 1. Apple still has not moved to OpenGL 4.x 2. Windows can run DX11 and OpenGL 4.x This is giving our little company a real conundrum, because Apple effectively has decided to be 11 minor versions of OpenGL behind. I understand they like to talk about compatibility, but the onus is on the developer for that, and being an entire major version number behind is not helping them. With Unity 4 and Unreal 4 engines, it is easy for us to support cutting edge features even as small developers. But it seems like Apple isn't interested in cutting edge "gaming" features. So that'll be Tessellation and Geometry shader support for windows and linux but not OSX. At this point we are very frustrated with this behaviour. How do other developers feel about this?
  3. After some research (took me a year ) I think I finally found a solution to get a more smoother interface. I don't know if this also fixes "Channel Timeout" errors, more testing is needed. Some history: After reading several topics/post about power-states that are used on GeForce-cards, I found out that the Fermi series only has 3 P-states instead of 4 (or more). P-states can control clockings on a GPU down or up when needed. (Down when more 'power' is needed/Up when being more idle) You can check your clocks by running the tool nvidia Inspector in Windows My EVGA GeForce 450 GTS (1GB) has the following clock-speeds: State 3 (lowest energy use) CPU Clock: 50Mhz CPU Memory: 324Mhz State 2 (mid. energy use) CPU Clock: 405Mhz CPU Memory: 324Mhz State 1 (high. energy use) CPU Clock: 783Mhz CPU Memory: 1.80Mhz After looking in Windows 7 what state the nVidia card runs on, I found out that this is usually state 3. In OS X however I could only get smooth animations if the GPU was running in state 2. My theory is that OS X simple needs more 'power' because it is running on OpenGL and their are way more animations (enabled) than on Windows. I also checked how my card was running on Linux (KDE). When using their interface I also find out my card was more in state 2 than in state 1. Editing AppleGraphicsPowerManagement.kext: To set the correct clock-speeds based on load, editing AGPM.kext was needed since they are undefined for my GPU. After searching through some post, I found out that some users were using all the 4 'load-fields', when my Fermi-card only has 3. Also some users simple tried to disable the last two, by setting really high values. This should prevent the CPU hitting state 3. Some users claim that state 3 is causing the freezes and the slow interface. My theory is that the GPU doesn't switch to state 2 when needed. It is either taking to much time for the GPU to reach state 2 or it would simply mean that the GPU doesn't like being on state 2 all the time for some reason. To make a long story short: I wanted to have a smooth interface, but also don't wanted the GPU to be fully loaded all the time (causing me a high energy bill). At the moment I'm using iMac12,2 as model. This because my i5-2400 seems to be inside this model. By setting this model, it also loaded the AGPM.kext. These are the values I have chose for my GPU (device id 0dc4): <key>Vendor10deDevice0dc4</key> <dict> <key>BoostPState</key> <array> <integer>0</integer> <integer>1</integer> <integer>2</integer> </array> <key>BoostTime</key> <array> <integer>2</integer> <integer>2</integer> <integer>2</integer> </array> <key>Heuristic</key> <dict> <key>ID</key> <integer>0</integer> <key>IdleInterval</key> <integer>200</integer> <key>SensorOption</key> <integer>1</integer> <key>TargetCount</key> <integer>1</integer> <key>Threshold_High</key> <array> <integer>70</integer> <integer>87</integer> <integer>100</integer> </array> <key>Threshold_Low</key> <array> <integer>0</integer> <integer>60</integer> <integer>92</integer> </array> </dict> <key>LogControl</key> <integer>0</integer> <key>control-id</key> <integer>17</integer> </dict> As you can see (or don't) I have simply removed the last row (aka row 3). My GPU is clocking as it should be and I can enjoy movies again. Also the sound from the GPU fan seems to be lower as it normally would, since this is also controlled by the GPU-clock. Setting details: I have set the IdleInterval from 250 to 100. It seems that setting this as 250 it takes to long for the GPU to switch to a higher or lower state. My theory is that the 250 value is set for the GFX0 (aka the nVidia/ATI-GPU) because it 'only' needs to render a game/high-use application. When the 100 IdleInterval of the Intel GPU, is needed because more/faster switching is needed for 'normal' use. The BoostPState and the BoostTime simple defined what state to be used when an application needs more 'power'. The SensorOption should need to be set to read-out the GPU-status. The TargetCount should be the state were the GPU should focus on. At least I think so, please let me know if you have more/better information. Testing: I would like to see some (test) results from Fermi-card users. That's why I posted this as new topic. But please know that doing this is at your own risk! As 'proof' please check the following pictures: Idle (4% idle or less): Browsing/doing stuff: (more than 4% load) Benchmarking: (more than 45% load) AppleGraphicsPowerManagement.kext.zip
  4. Mobo : Gigabyte UD3LR CPU : Intel Q8200 RAM : 4 Gb 1066 Mhz GEIL GPU : NVidia Geforce 9600 GT HDD : Samsung Sata II 750GB (non SSD) I have been using Snow Leopard for 2 years almost without major problems. Then on one day i downloaded a DSDT file for my mobo to try it out. At boot it started "PCI configuratin begin" and was hanging there for a few seconds. I lost my patience and pushed the reset button. I never could boot the system anymore(HFS got corrupted at System folders, no chance to repair it). So installed Lion and Mountain Lion right after. It was working for one year. About 3 weeks ago i checked if sleep mode was working fine. I did some patches to make it work before, but looks like never bothered with it. Waking up from sleep mode reseted my CMOS. Then it took me 10 days to stabilize my RAM, because something happened with that, and i could not use the old settings for my memory. I had about 120 BSODs in Windows on one day. It was all because the RAM was dropping errors. 120 BSODs, and WINDOWS DID NOT GET CORRUPTED! I am using that Windows right now, and its stable again. BUT if i have to reset Mac OS X, i am pretty sure, that files and folders will be lost suddenly, and in an unrepairable way! This is below any standards. I had to reinstall Mavericks 4 times in one week! All because of HFS getting corrupted and Disk Utility and fsck could not repair it. (Of course they make it more worse while trying to repair it.) I was having OpenGL Channel Exception errors while watching html5 videos and going fullscreen in Safari (try here some if you would like test as well : http://ink361.com/app/tag/video ) , which means the whole ui got freezed / crashed and screen got being stuck garbled at one point. But the system was still running in the background. I could not do anything cause no mouse or keyboard input worked anymore. So at this point, what can i do ? I was watching if there was any flashing of the HD leds on my PC. When it stopped doing anything for a while i pushed reset. Later i had a feeling its better to turn off the PC completely, maybe the disk won't be damaged that way. But it will be damaged EVERY F*CKING TIME. AND IRREPAIRABLY. Next time i boot up, it says "fsck started blabla, and then possibly something like this: "removed 15 directories and 16 orphaned files" or so. Oh great. They ARE GONE. FOREVER. Its like RUSSIAN ROULETTE. If i am lucky those were not System folders and i can still boot up. Well, most of time i am not so lucky. I had lost 500 megs of stuff from my HFS partition once with a freeze. Checked those folders in R-Studio on Windows. Folders i never touched, and among those System/Library/Extensions, and everything needed for the system to boot up. I was trying to fix this issue with the OpenGL Channel Exceptions on the last days. Meanwhile i had to reinstall the whole b*tch system 3 times because of the freezes. And then after one install it got stuck at first boot on some Bluetooth kexts. I waited for 5 minutes, then i turned off the machine. Boom. Next boot not working anymore, HFS DAMAGED BADLY. The Disk was not even doing anything when i turned it off! Later i found out i have to boot with -x after install not to get stuck at the Bluetooth kexts. (And right after i need to rebuild kextcache with Kext Utility so i can drop the -x from that point) So i installed the system once again. It looks like i have no more freezes and Channel Exceptions. Although there are still some artifacts when going fullscreen playing html5 videos. Luckily it fades away and does not crash anymore.Things might have helped is that I removed AGPM.kext and wiped out PCIRoot=anything from boot arguments. Its pretty badly documented what the f*ck that switch is for anyway. Looks like its better for me to leave that off completely. I remember i had to use value 1 for Snow Leopard. Don't have to anymore as it looks with Mavericks. But. The problem remains. Which is. Anytime my Mavericks system crashes, or i have to reboot / turn it off, there is a 90% chance the HFS will get corrupted, and possibly i need a reinstall, because Disk Utility from Install USB Drive and fsck ain't repair anything. I was searching for things like how could i prevent this damaging thing each time the system crashes or being stuck in a freeze state. How could i make HFS more stable not to loose folders and files so easily, but did not find really useful things sadly.
  5. Hi everyone! I just installed SL 10.6.8 using nawcom bootcd & kernel and retail 10.6.3. Updated it to 10.6.8. Everything works just fine, except video. I added GraphicsEnabler=yes flag and now I can change resolutions, dual monitor mode works and I definitely have hardware acceleration — menu bar is semi-transparent and so on. But I have problems running games (tried Half-Life 2 and Quake 3) and, for example, applying some filters in Photo Booth. Applications just crash. One more observation — OpenGL acceleration in Photoshop CS5 works really slow — I had to turn it off. My configuration is as follows: Athlon X4 3.0 GHz, Asus M4A785T-M, 4 Gb DDR3, Asus GeForce 210 512 Mb, two 19" 1280x1024 panels, SL 10.6.8 Settings applied: GraphicsEnabler=yes, legacy_kernel, -force64 (tried disabling it), arch=i386 and busratio=15 (fixes sound problems). Also tried installing nVidia official drivers. Any thoughts?
  6. Hello folks, I already posted this on Ask Different but didn't get any good answer yet. It may be too specialized for Ask Different, but I was told I may found kext experts here 1 - Original issue I own a Macbook Pro 15" from Early 2011, which suffers from the well-known-but-denied-by-Apple GPU problem. TL;DR: the AMD Radeon HD 6XX0M is dead and the Macbook can't boot, or can boot but with huge graphic glitches on screen. 2 - Workaround There is a workaround to this problem, which consists to disable the AMD GPU and only use the Intel HD 3000 chipset. The main way to do this is to use a software like gfxCardStatus. However, since my Macbook wasn't booting (stuck on blue screen after Apple logo), I managed to disable my AMD Radeon HD 6490M by entering single-user mode and deleting the following files from /System/Library/Extensions/ : AMDRadeonAccelerator.kext AMDRadeonVADriver.bundle AMDRadeonX3000GLDriver.bundle AMDRadeonX4000GLDriver.bundle ATI2400Controller.kext ATI2600Controller.kext ATI3800Controller.kext ATI4600Controller.kext ATI4800Controller.kext ATI5000Controller.kext ATI6000Controller.kext ATI7000Controller.kext ATIFramebuffer.kext ATIRadeonX2000.kext ATIRadeonX2000GA.plugin ATIRadeonX2000GLDriver.bundle ATIRadeonX2000VADriver.bundle ATISupport.kext 3 - Remaining problems But, as I said, this is just a workaround to get OS X to boot. I now have 2 main issues: - I can't plug an external screen on the Thunderbolt port - I can't play any avi or mkv video I know there isn't any solution for the first issue, since the Intel HD 3000 is not even physically linked to the Thunderbolt port. However, I am looking for a solution to the second issue. The Intel HD 3000 chipset may not be a killer GPU, but I am sure it can handle a simple video, and even 1080p videos. When I open a video file in VLC, I get the following error: And in the logs: I think Mac OS X is trying to get OpenGL acceleration thanks to the AMD GPU. And since the GPU is supposed to work properly, it never tries to get the adequate features from the Intel HD 3000 chipset. So, is there any way to get more from this chipset?
×