Recommended Posts

Finally!

HWA disabled by default, so you have to enable it in Opera:config

Here at Opera HQ, we're buckling down for the final push before the beta launch of Opera 12. Right now, Wahoo is getting more complete, with even more fun things to come as we get closer to launch. We have one of those fun things today, in fact. This new snapshot includes the first look at the DirectX backend. Most users on Vista and Windows 7 will by default use this backend instead of the OpenGL backend for performance and stability reasons, but be aware that currently WebGL support using the OpenGL backend is more complete than when using DirectX.

There's also another change in this snapshot. After careful consideration and extensive testing, we've decided to let users of Opera 12 opt-in to WebGL and hardware acceleration.

We're doing this for an important reason. We want to bring the first true hardware accelerated browser to market. This means using the graphics processor to boost rendering speeds not only for the pages themselves, but also the UI of the browser. It means making it an awesome experience for as many Opera desktop users as possible, whether they're on Windows XP, Linux or Lion.

But in some cases, our hardware accelerated speeds do not yet beat our incredibly optimized software backend, Vega. Shipping a feature that could actually be less effective at boosting speed is a big no-no, especially if its a final release that many people will use for day-to-day browsing.

Now, if you're reading this blog post, you're probably in the group of people who will want to turn on WebGL and hardware acceleration. You enable these features by setting both opera:config#UserPrefs|EnableHardwareAcceleration and opera:config#UserPrefs|EnableWebGL to 1, then saving and restarting Opera.

Try it in this release and see how you like it. We think it ensures that Opera 12 will be a great release for everyone, whether you are a browser expert or just discovering Opera for the first time.

As Wahoo is approaching a beta release, we're focusing on stability and fixing regressions. This build includes an important performance and stability fix for plugins on Windows, and should speed up scrolling with plugins significantly.

Known Issues

HTML5 Drag and Drop is work in progress. Things like dragging to and from external applications may not work. Some existing demo sites may not work fully

HTML5test.com could freeze or show other problems on Mac

OTW-8246 Opera 64-bit on Windows not supported on Google+

DSK-361109 Address dropdown not populated when searching page content with multiple words

CORE-45774 [Windows] [HWA] Border-color messes up background colour for element with border-radius with DirectX

DSK-357831 [Windows] [HWA] Negative letter spacing with DirectX on 64-bit builds

http://my.opera.com/...ion-in-opera-12

It's about time. And not surprisingly, turning on the DirectX renderer will also turn on DirectWrite for the entire browser UI, minus menus.

edit: and it performs pretty well on integrated Intel graphics!

edit 2: but DirectWrite is still a bit slow. Oh well.

So how much is actually accelerated? Text and layers? Or full blown D2D?

Also it is still slower than software, better than OGL though.

On my machine it's faster than software with DirectX, in everything apart from scrolling with the mouse wheel. Dragging the scroll bar up & down with insane speed works perfectly fine though, so I'm not sure what's up with that :p

Opera say they want to be the "first true hardware accelerated browser", so I'm not sure how much is accelerated now, but they're planning on basically everything, including the UI and menus to be hardware accelerated (though a lot of the UI is already).

Except IE10 is still beta, so either could be first, depending on which releases a final version first.

In real life, we know that IE10 came into existence before this version of Opera despite whatever developmental progress tag you wish to attribute to it, but alright.

Opera say they want to be the "first true hardware accelerated browser", so I'm not sure how much is accelerated now, but they're planning on basically everything, including the UI and menus to be hardware accelerated (though a lot of the UI is already).

Mozilla recently had to disable hardware acceleration in menus due to random driver issues (Like the drop shadows sticking around after the menu was closed.). I don't see much point in using HW accel for rendering a menu though, unless you want to throw something like WebGL rendering in there.

Mozilla recently had to disable hardware acceleration in menus due to random driver issues (Like the drop shadows sticking around after the menu was closed.). I don't see much point in using HW accel for rendering a menu though, unless you want to throw something like WebGL rendering in there.

*shrugs* I suppose if they have the code they might as well do it and get everything running on the same code. But on Windows at least, DirectWrite text rendering is faster than normal GDI+ text rendering, so there's at least some tiny benefits to be had somewhere.

If you really want to be technical, the first fully HW accelerated browser (UI included) is Chrome for Android :p

Also I though IE9 just did HW acceleration for page content, instead of page content and UI.

Opera's OGL HWA in previous builds was atrocious and slowed things down immensely (instead of speeding it up) - I have no faith that they can deliver DX HWA which is any better.

OGL drivers on windows are often poor/buggy, give it a chance. its also still in early testing... Firefox's hardware accel used to suck in development, so did chrome's.

OGL drivers on windows are often poor/buggy, give it a chance. its also still in early testing... Firefox's hardware accel used to suck in development, so did chrome's.

Well the D3D10 HWA they added is slightly better. I still feel like they have the same issue as with OGL - it slows things down, not speeds them up for some reason.

Now it is less noticeable, but they should still keep HWA opt-in.

*shrugs* I suppose if they have the code they might as well do it and get everything running on the same code. But on Windows at least, DirectWrite text rendering is faster than normal GDI+ text rendering, so there's at least some tiny benefits to be had somewhere.

It still uses DirectWrite/Direct2D, it just doesn't use Direct3D for showing it on the screen.

I'm still not sure what Opera means by saying they want to be the first to be fully hardware accelerated, does that mean they'll do Theora/WebM decoding on the GPU? (Compared to Firefox that decodes on the CPU, and does colour space conversion/scaling/painting on the GPU)

, does that mean they'll do Theora/WebM decoding on the GPU? (Compared to Firefox that decodes on the CPU, and does colour space conversion/scaling/painting on the GPU)

Yes. The blog post says the following:

You enable these features by setting both opera:config#UserPrefs|EnableHardwareAcceleration and opera:config#UserPrefs|EnableWebGL to 1,

Well the D3D10 HWA they added is slightly better. I still feel like they have the same issue as with OGL - it slows things down, not speeds them up for some reason.

Now it is less noticeable, but they should still keep HWA opt-in.

Did you use the FF4 alpha builds when they first started adding HWA? It was crap and slowed things down, because it was in early development ;)

But yeah, its a good thing its opt-in until its optimized further.

It still uses DirectWrite/Direct2D, it just doesn't use Direct3D for showing it on the screen.

I'm still not sure what Opera means by saying they want to be the first to be fully hardware accelerated, does that mean they'll do Theora/WebM decoding on the GPU? (Compared to Firefox that decodes on the CPU, and does colour space conversion/scaling/painting on the GPU)

Yes. The blog post says the following:

That is impossible outside of CUDA / OpenCL. Then it is just very very unlikely / impractical and a massive amount of work.

Opera is just trolling, albeit, it would be nice if they added support for DXVA2.

That is impossible outside of CUDA / OpenCL. Then it is just very very unlikely / impractical and a massive amount of work.

Opera is just trolling, albeit, it would be nice if they added support for DXVA2.

How are they trolling? The blog post does not specifically mention theora acceleration (or anything about video acceleration really) When they say "fully hardware accelerated", they are referring to that the UI of the browser should be accelerated as well, not just the web pages like other browsers do.

This topic is now closed to further replies.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!