Recommended Posts

Heartripper, I've started a topic on your Script page...

http://forum.userstyles.org/discussion/25510/there-is-a-bug

Please check it whenever you have available time.

It should be fixed now!

Thanks but this code didn't fix the problem in my case. This is how FF looks adding this code:

senzatitolo1lg.jpg

and changing the height value seems irrilevant.

My code style:

/* Tab Fixes */

#navigator-toolbox[tabsontop="true"] #TabsToolbar
{ padding: 0px 110px 0 50px !important; }

#main-window[tabsontop="true"]
{ margin-top: -17px !important; }

.tabbrowser-tab[fadein]:not([pinned])
{ max-width: 200px !important; }

.tabbrowser-tab[fadein][pinned] 
{  margin-top: -0.2px !important; }

#tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
        height: 22px !important;
}

/* Menu Bar Fixes */

#main-window[tabsontop="true"] menubar 
{    margin-left: 48px !important; 
     padding-top: 0px !important; }

Please put the full code of your style so we can analyze it. Or all styles, if you use more than one.

It should be fixed now!

Please, check it again... Additional bugs/informations! :/

Any way to make it look like ie9?

I'm pretty sure, in a while there will be available as a Theme by someone... You just have to wait...

Like-Chrome already there is... Not 100% perfect yet, but not bad at all... It's the first version.

Please put the full code of your style so we can analyze it. Or all styles, if you use more than one.

/* Tab Fixes */

#navigator-toolbox[tabsontop="true"] #TabsToolbar
{ padding: 0px 110px 0 50px !important; }

#main-window[tabsontop="true"]
{ margin-top: -17px !important; }

.tabbrowser-tab[fadein]:not([pinned])
{ max-width: 200px !important; }

.tabbrowser-tab[fadein][pinned] 
{  margin-top: -0.2px !important; }

#tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
        height: 22px !important;
}

.tabbrowser-tab{
  max-height: 18px !important;
}

.tabbrowser-tabs {
  max-height: 23px !important;
}

/* Menu Bar Fixes */

#main-window[tabsontop="true"] menubar 
{    margin-left: 48px !important; 
     padding-top: 0px !important; }

/* Menu Button Fixes */ 

#appmenu-button
{   border: 0.5px solid rgba(90,30,0,0.8)!important;
    border-top:none!important;
    padding: 2px 5px 1px 5px !important;
    height: 22px !important;
    min-width: 43px !important;
    width: 43px !important;
    -moz-box-shadow: 0 0 3px rgba(255,255,255,.5) inset, 0 0 1px rgba(255,250,200,0.8) inset, 0 0 1px rgba(255,250,200,0.8) inset, 0 0 1px rgba(255,250,200,0.8) inset, 0 0 1px rgba(255,250,240,0.5) !important;  }

#appmenu-button:hover:active, #appmenu-button[open]
{    background-image: -moz-linear-gradient(rgba(0,0,0,.2), rgba(0,0,0,.1) 10%, transparent 60%), -moz-radial-gradient(14px, circle cover, rgba(248, 233, 164, 0.5) 29%, rgba(248, 233, 164, 0.2) 35%, rgba(248, 233, 164, 0) 50%) !important;  }

#appmenu-button .button-text
{ 
    color: transparent !important;
    text-shadow: none !important;
    margin-left: -27px !important;
    margin-right: -33px !important;
    background: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAADK0lEQVQ4jV2TTWxUZRSGn++7d+bey3SYMgMzdNLMTCu2VcE0CjG1qYqRSEhYKElTA66MooaNLozDwh8WjAs3JsSFSxeKRg0axSj+EApFYotAS0ctWmeEOpTS6fx0fu+9n4v+pPqsTk7yvuck57wCIGXIT4BUsu6OBbr2bO+p5J71OfWHxvzxMEuMA6eBLwu/nxxlDWLZQAGcDG09Ou/xDR3IXegE2F9zEMDg/rd59eky1z467575pfLdrrmLRw7dqJxjWXwgZUh1682gShlSra2Ha0qdK9nq63xDbXniLTUx8pz68Y1+9U5XuPrhwMZBACkEjwRDGgD7hoLE457V9c4GNF5u9XK1WGfw4B4efT1B594eHnvlHrNUku99/mRks9SkuL/jTk+jkrVxF6ps7/Ovmu0bChKXUEQnH9uCMrx8MNJK4sEIoZgVKN9sJqXHENFou+ZtVl18iaXp1UKEjbuf4dPj86hTC1y+eJuJM3/hojF5rUGhYNO9K8TiXG2nrhTrfa0SXQoqJUnLwB0A6J5JAGamcuQn05RmctiuzlhaYkmHSNxkMe/06PWaa2CD2SYZ/rZE8/tRZnIKgKOPv0vz/Y8RysGSLtWaIJKo0Lp+nnylQq1o69LwiHKpoEBAMKKxye/S1iYBOPzNi3zW9wOv7chQnJ2jUczzcHsW8vOUf72J1SIqugZX/sk2+/0bNLruNvl73GZbXOfeHSY+0+ZC5hacOI3d/jwxK8vB3jT1XIPrZ/Nowh3XbUcdnxpv3BcI6VY4ZtK+LYjdcBj7aZHMHw3gKknfU/Sv+40Xdt8mpNVZmFpg8mcNb2vwlEgZssXSGNaF6N055Mc0dBxHR5oa03kvc8Ua68QisXCTRMKgik56pMyfGau4ObapWwAcMeQDluQLS4rw1j6LSFRD1ySapjCkjeMIbMAMQSarmLhUr81NOwPJujsqVr4uZcheQ+MrBdFQi6Sz20sgKNAtwCOYvd4kc0OgqnYlN+v2J+vupdUwrXDMp3W4gpdcpfY6UiQce+k6piHYEJA1p6lOlBfU4UOLzvR/0vh/jvm0DuAuILrcmgHSa4Ur/AsXclHwqDchzQAAAABJRU5ErkJggg==") no-repeat 16px !important; }

#appmenu-button dropmarker
{  margin: 0 1px 0 0 !important; }

#appmenu-button-container
{    position: fixed !important;
    top: 0 !important;   }

#main-window[sizemode="maximized"][tabsontop="true"] #appmenu-button-container 
{    position: fixed !important; 
     margin: 6px 0px 4px 4px !important;
     top: 2px !important; }

/* Stop Reload on the left */

toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #urlbar {
  -moz-border-radius: 0 2px 2px 0 !important;
  border-left: 0 !important;
}

toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button,
toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button + #stop-button{
  border-color: rgba(0,0,0,.25) rgba(0,0,0,.25) rgba(0,0,0,.25) !important;
  -moz-border-radius: 2px 0 0 2px!important;  
  -moz-box-shadow: 0 0px 0 rgba(0,0,0,.1) inset,
                   0 0px 0 rgba(255,255,255,.4) !important;
  background: rgba(255,255,255,.725) !important;
  margin-right: -3px !important;
  list-style-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAMCAYAAABm+U3GAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAA2RpVFh0WE1MOmNvbS5hZG9iZS54bXAAAAAAADw/eHBhY2tldCBiZWdpbj0i77u/IiBpZD0iVzVNME1wQ2VoaUh6cmVTek5UY3prYzlkIj8+IDx4OnhtcG1ldGEgeG1sbnM6eD0iYWRvYmU6bnM6bWV0YS8iIHg6eG1wdGs9IkFkb2JlIFhNUCBDb3JlIDUuMC1jMDYwIDYxLjEzNDc3NywgMjAxMC8wMi8xMi0xNzozMjowMCAgICAgICAgIj4gPHJkZjpSREYgeG1sbnM6cmRmPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAyLzIyLXJkZi1zeW50YXgtbnMjIj4gPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9IiIgeG1sbnM6eG1wTU09Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC9tbS8iIHhtbG5zOnN0UmVmPSJodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvc1R5cGUvUmVzb3VyY2VSZWYjIiB4bWxuczp4bXA9Imh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8iIHhtcE1NOk9yaWdpbmFsRG9jdW1lbnRJRD0ieG1wLmRpZDozQkQ3OTNFRTYwOTZERjExODRFOUQ2RDI3Qzg1RENGMCIgeG1wTU06RG9jdW1lbnRJRD0ieG1wLmRpZDo0ODAwNTk3Rjk2NjExMURGOTRBMUI2RTAyRUYxRjAxNiIgeG1wTU06SW5zdGFuY2VJRD0ieG1wLmlpZDo0ODAwNTk3RTk2NjExMURGOTRBMUI2RTAyRUYxRjAxNiIgeG1wOkNyZWF0b3JUb29sPSJBZG9iZSBQaG90b3Nob3AgQ1M1IFdpbmRvd3MiPiA8eG1wTU06RGVyaXZlZEZyb20gc3RSZWY6aW5zdGFuY2VJRD0ieG1wLmlpZDozQ0Q3OTNFRTYwOTZERjExODRFOUQ2RDI3Qzg1RENGMCIgc3RSZWY6ZG9jdW1lbnRJRD0ieG1wLmRpZDozQkQ3OTNFRTYwOTZERjExODRFOUQ2RDI3Qzg1RENGMCIvPiA8L3JkZjpEZXNjcmlwdGlvbj4gPC9yZGY6UkRGPiA8L3g6eG1wbWV0YT4gPD94cGFja2V0IGVuZD0iciI/PoZDigQAAAN3SURBVHjajJJ/aBNnGMefy11ySS65kOtilyZNurX+rAYzEJ2DaVn9R+vAsblUN2m1UK2KKM5J/bEaVnGsqfujigqWOqZVmJPqtO3arbINEcfEiVpbtYKm1NCY1OSa5HJ573yutFDY/tgLH7jn5b3v+7zP90s9HonrAMCE8IgV/r1yCLOybGnFQP+DZvi/C4VtyMyvvz26xOUubDCY7ReBy+sz2J0XnQVFQW1/1py5u4Ay9amqChVFBVWIQ/ueDu4JyKapmtJEd9bVzLva0bXFIOQZXM4ZYY/b/TIhivnxV8k3QadTiKLSRM7CO5lIO0vTJ0FH3ZVzpPzSk+ejWnNrigsFPUP3gqL6JUK2dwyFW5jzP7TlXbvcVWtzFYiHDtR3ra8MvFBUNaMoqvR5dc1HY4nxhQaTEZJjMag/ePhJW8O+iBSP+XI03RuY5S1HXWJhDb16AL9BsEU3HAg+1i6j3B7vVxFRXhY60nh2XSAwnM7KYUkm2ZVl71eIYFhd6CkEjuMgGX8Jt/o6Vz0beFj3XW317uyrsXx8zV1QgQDJ+Rmej+440Rp6q3RBC+qKFKM3XSqe7xu98fv1y5Kcu5+ScjIatXZwaHi1p6QEBEEAhmZATMSh//bNMvzJHB4cqDu9c+tuRUzmg6Lgjim68ejxkHfe/AlRrWOGUIzF5XI9xaenUDSubV7ru/Gzxai/iXMT/sPvVOfpU+0sy26nFYK62LCezfScaT1f802zOHUIm9GL6VTajnOVsaaRJBIWM3IUQMbRgRZHosVOsBihesFMwW7lr9g5zmN8wxGlVELGRl647/3W01E19+3ytv6hCUN1+YL1n9FYzHuuvd2Ldd5klrULVO1ihJ1sYhzNEvRompFS/TqzOfpJQ2NobWNTk95mjbAU+LRk4BnHhPCmzXW/SBlJvvDjTx+fOnli9qS4E3EE9+8vXfHeu5/+cf1XF9YW1sx9hg36wcRFNxxpDrlmz2lxFpccrwoda6J5PoIB9hk5rmoiFVqO9+7Z4xt4NFhrsfIMIeQpZnQ4mUw60+lM8Xgill1fWXnuiy/39ngdfEHrwfpDHwTW/TndKM3Q55iWnrPfL98YPBzE+pYmbMOPGZ1Xr3i6u7s/TIipEimbNaMrot3GP9q2dcvfS5csjuFc7uCMR/DsIqR/mujUMiOlyF9a8VqAAQCMEogyPkkkHQAAAABJRU5ErkJggg==") !important;
  opacity: 1 !important;
  padding: 0 6px 0 6px !important;
  -moz-transition: -moz-box-shadow .1s !important;
}


toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button {
  -moz-image-region: rect(0 11px 12px 0) !important;
}


toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button + #stop-button {
  -moz-image-region: rect(0 22px 12px 11px) !important;
}


toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button:not([disabled]):hover{
  background-image: -moz-linear-gradient(rgb(158,204,241), rgb(111,177,225) 49%,
                                   rgb(91,159,217) 50%, rgb(81,152,210) 60%,
                                   rgb(62,138,204)) !important;
  -moz-box-shadow: 0 0 1px 0 rgba(255,255,255,.40) inset, 
                   0 1px 0 rgba(255,255,255,.4) !important;
}

toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button + #stop-button{
  background-image: -moz-linear-gradient(rgb(230,161,138), rgb(209,119,100) 49%,
                                   rgb(192,93,78) 50%, rgb(185,85,70) 60%,
                                   rgb(193,90,74)) !important;
  -moz-box-shadow: 0 0 1px 0 rgba(255,255,255,.40) inset, 
                   0 1px 0 rgba(255,255,255,.4) !important;
}

toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button + #stop-button:not([disabled]):hover{
  background-image: -moz-linear-gradient(rgb(240,161,138), rgb(219,119,100) 49%,
                                   rgb(203,93,78) 50%, rgb(195,85,70) 60%,
                                   rgb(203,90,74)) !important;
}


toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button:not([disabled]):hover:active,
toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button + #stop-button:not([disabled]):hover:active {
  -moz-box-shadow: inset 0 0 3px rgba(0,0,0,.8), 
                   0 1px 0 rgba(255,255,255,.4) !important;
}

#stop-button .toolbarbutton-icon,
#reload-button .toolbarbutton-icon{
  height: auto !important;
  width: auto !important;
}


#navigator-toolbox:not([tabsontop="true"]) toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button,
#navigator-toolbox:not([tabsontop="true"]) toolbar[mode="icons"][currentset*="reload-button,stop-button,urlbar-container"] #reload-button + #stop-button {
  background-clip: padding-box !important;
}

Thanks!

Thanks!

Give this a try (replace your "Tab Fixes" section with this one):

/* Tab Fixes */

#main-window[sizemode="normal"] #navigator-toolbox[tabsontop="true"] #TabsToolbar { 
        padding: 0px 110px 0 50px !important; 
}

#main-window[sizemode="normal"][tabsontop="true"] { 
        margin-top: -17px !important; 
}

.tabbrowser-tab[fadein]:not([pinned]) { 
        max-width: 200px !important; 
}

.tabbrowser-tabs {
         max-height: 23px !important;
}

#tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
        height: 23px !important;
}

.tab-content {
	margin-top: -1px !important;
	min-height: 16px !important;
}

how can I get my add-ons in location bar like this

screenhunter02feb231656.png

I use useChromejs 1.3 with the following code:

var urlbar = document.getElementById("urlbar-icons")
var go = urlbar.lastChild

var nsI = document.getElementById("noscript-tbb")
var adpS = document.getElementById("abp-status")
var gmS = document.getElementById("gm-status")
var gmM = document.getElementById("gm-status-popup")
var stY = document.getElementById("stylish-toolbar-button")

urlbar.insertBefore(stY, go)
urlbar.insertBefore(gmS, go)
urlbar.insertBefore(gmM, go)
urlbar.insertBefore(adpS, go)
urlbar.insertBefore(nsI, go)

I use useChromejs 1.3 with the following code:

var urlbar = document.getElementById("urlbar-icons")
var go = urlbar.lastChild

var nsI = document.getElementById("noscript-tbb")
var adpS = document.getElementById("abp-status")
var gmS = document.getElementById("gm-status")
var gmM = document.getElementById("gm-status-popup")
var stY = document.getElementById("stylish-toolbar-button")

urlbar.insertBefore(stY, go)
urlbar.insertBefore(gmS, go)
urlbar.insertBefore(gmM, go)
urlbar.insertBefore(adpS, go)
urlbar.insertBefore(nsI, go)

This worked for me but just for one time. It vanished when i restart firefox. It works again when i remove gm-status-popup.

Where can i find extension ids? I want to put other ones like webmail or foxyproxy.

I use useChromejs 1.3 with the following code:

var urlbar = document.getElementById("urlbar-icons")
var go = urlbar.lastChild

var nsI = document.getElementById("noscript-tbb")
var adpS = document.getElementById("abp-status")
var gmS = document.getElementById("gm-status")
var gmM = document.getElementById("gm-status-popup")
var stY = document.getElementById("stylish-toolbar-button")

urlbar.insertBefore(stY, go)
urlbar.insertBefore(gmS, go)
urlbar.insertBefore(gmM, go)
urlbar.insertBefore(adpS, go)
urlbar.insertBefore(nsI, go)

thx but I have same problem as tyler78 here http://forums.mozillazine.org/viewtopic.php?f=48&t=1006795&start=90

I dont understand where to put js code after installed the add-on.

Is there a way to remove the favcons from the tabs? And is there a way to take some of the height off of the tabs/url bar area? I'm going for an extremely minimalist look, and most things I try from userstyles.org look awful in the release candidate.

I use useChromejs 1.3 with the following code:

....

Foxxyn8, what is the advantage of having the add-on icons within the url bar?

(I know that Chrome has some of them inside and some to the right of the omnibar and there's nothing the user can do to move them around because there's something about "page action" and "browser action" that determines whether extension icons show inside or outside Chrome's omnibox.)

thx but I have same problem as tyler78 here http://forums.mozillazine.org/viewtopic.php?f=48&t=1006795&start=90

I dont understand where to put js code after installed the add-on.

The code goes in userchrome.js which is located in the chrome folder of your firefox profile. If the file doesn't exist create it.

Make sure any toolbarbutton you want to relocate add is present on a toolbar. It gives me problems on occasion, usually when Fx "forgets" the location of the toolbarbutton and moves it back to the customization pallette. Also, if you're not using the same addons, it may not work. Remove the references to the ones you don't need.

You get the ids the same way as with css -- Dom Inspector.

thx but I have same problem as tyler78 here http://forums.mozillazine.org/viewtopic.php?f=48&t=1006795&start=90

I dont understand where to put js code after installed the add-on.

Create a folder under your profile folder called "chrome" and create a text file under that folder called "userChrome.js". Add the code in that text file.

The code goes in userchrome.js which is located in the chrome folder of your firefox profile. If the file doesn't exist create it.

Make sure any toolbarbutton you want to relocate add is present on a toolbar. It gives me problems on occasion, usually when Fx "forgets" the location of the toolbarbutton and moves it back to the customization pallette. Also, if you're not using the same addons, it may not work. Remove the references to the ones you don't need.

You get the ids the same way as with css -- Dom Inspector.

got it working... but only for 5min(restart) .. I give up.. Thanks

got it working... but only for 5min(restart) .. I give up.. Thanks

Hi man. I found a better way for it. It puts all the status bar instead of one or two extensions.

Try this code:

var urlbar = document.getElementById("urlbar-icons");
var go = urlbar.lastChild;

var stat = document.getElementById("status-bar");

urlbar.insertBefore(stat, go);

Hi man. I found a better way for it. It puts all the status bar instead of one or two extensions.

Try this code:

var urlbar = document.getElementById("urlbar-icons");
var go = urlbar.lastChild;

var stat = document.getElementById("status-bar");

urlbar.insertBefore(stat, go);

That will work so long as the addon provides a status bar icon as opposed to a toolbar button, but the status bar is being phased out and only exists in its current form for legacy purposes.

Give this a try (replace your "Tab Fixes" section with this one):

/* Tab Fixes */

#main-window[sizemode="normal"] #navigator-toolbox[tabsontop="true"] #TabsToolbar { 
        padding: 0px 110px 0 50px !important; 
}

#main-window[sizemode="normal"][tabsontop="true"] { 
        margin-top: -17px !important; 
}

.tabbrowser-tab[fadein]:not([pinned]) { 
        max-width: 200px !important; 
}

.tabbrowser-tabs {
         max-height: 23px !important;
}

#tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
        height: 23px !important;
}

.tab-content {
	margin-top: -1px !important;
	min-height: 16px !important;
}

That's work! Thanks!

Hi man. I found a better way for it. It puts all the status bar instead of one or two extensions.

Try this code:

var urlbar = document.getElementById("urlbar-icons");
var go = urlbar.lastChild;

var stat = document.getElementById("status-bar");

urlbar.insertBefore(stat, go);

that worked for all but my stylish icon.

Foxxyn8, what is the advantage of having the add-on icons within the url bar?

(I know that Chrome has some of them inside and some to the right of the omnibar and there's nothing the user can do to move them around because there's something about "page action" and "browser action" that determines whether extension icons show inside or outside Chrome's omnibox.)

I don't know that there's any advantage at all, it's just a personal preference. :).

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      FloatingFatMan
      66
    5. 5
      +Edouard
      66
  • Tell a friend

    Love Neowin? Tell a friend!