[F1 US GP]- 6 Runners!


Recommended Posts

I suppose the danger now is that the rumoured 'breakaway' F1 tour might actually happen, and if that does come into being the divide will bring about the total collapse of F1 as we know it. Should that be the case, chances are that the only (roughly) comparable series of racing we will be seeing is a World Indy/Champ car series and with it the end of F1 and standing start races.

stupid? think about it first. who made the tires that teams can't drive? if someone does bad job, then punishing is easy to come. nothing to do. michelin sucked and 0 points to all michelin drivers!

586091274[/snapback]

I was being sarcastic you know :happy:

Everyone seems to take it out on Ferrari, no matter what happens. It is clearly not their fault, but everyone seems intent on bashing them instead.

so screw u michelin ... aam going home :rofl:

586089031[/snapback]

You forgot the Cartaman Voice Tags :p

Lets all blame ferrari. Anything bad that happens with F1 is ferrari's fault.

586089848[/snapback]

Yeah... It's like IT...If something goes wrong in the Mighty World of Computers...Blame Microsoft :sleep: (I think you were being ironic, right?)

I'm happy for Tiago Monteiro, first time in F1 and a 3rd place....nice

586091218[/snapback]

And it's the first time a Portuguese racer wins a place in the podium...

So who is to blame?

Michilen -> FIA -> Ferrari

In that order.

Michilen should have made a safe tyre and had back-up ones available, but I don't blame them totally because they didn't make the tyres faulty on purpose, they found out during the run-up to the weekend. Whether it was the new surface, lack of testing, whatever. They did all they could, offered to fly in new tyres and to modify the track. The FIA wouldn't let them use new tyres and Ferrari were against the new chicane. Even though the Michilen teams offered to get 0 points from racing with the chicane for the sake of the sport and US fans. So yes, Ferrari are in part to blame. My dislike for them grows as their unsportsmen-like attitude shows. Pretty much every new rule change you hear about is "9/10 teams agree, Ferrari doesn't". I wouldn't mind a breakaway sport with the 9 teams that haven't signed up to F1 past 2007.

That's just my view ;)

So who is to blame?

Michilen -> FIA -> Ferrari

In that order.

Michilen should have made a safe tyre and had back-up ones available, but I don't blame them totally because they didn't make the tyres faulty on purpose, they found out during the run-up to the weekend. Whether it was the new surface, lack of testing, whatever. They did all they could, offered to fly in new tyres and to modify the track. The FIA wouldn't let them use new tyres and Ferrari were against the new chicane. Even though the Michilen teams offered to get 0 points from racing with the chicane for the sake of the sport and US fans. So yes, Ferrari are in part to blame. My dislike for them grows as their unsportsmen-like attitude shows. Pretty much every new rule change you hear about is "9/10 teams agree, Ferrari doesn't". I wouldn't mind a breakaway sport with the 9 teams that haven't signed up to F1 past 2007.

That's just my view?;))

586091760[/snapback]

well the 2007 agreement is signed only by ferrari:pp

look at it this way : in the last 5 years ferrari won everyting either because the rules helped them or because they adapted better to them. so who in their place whould want to change those rules?

the tyre rules for this year clearly helped michelin (because bridgestone has 0 experience in endurance races) and this is clear if you look at results. so it's a bit ironically that they suffered this drawback. i think they trusted themself too much:)). the statement that the michelin will run for no points it's only made by briatore (and you know briatore) and doesn't appear in the michelin requests. so, to modify the circuit to avoid a flaw of some teams will of course affect those teams that had no problem and i guess this is unfair as well. as barichello putted: in bahrain he had tyre issues too and nobody modified the track.

however the basic rule of the two dry tyre sets is that one is for speed and one should resist no matter what. michelin failed to do so and they've admited they've made some calculation mistakes.

edit: this is from dailyf1:

Michelin's failure to supply its teams with safe and durable tyres came less than two weeks after it was warned by the FIA not to sacrifice safety for performance. Mosley wrote to Michelin in the wake of Kimi Raikkonen's suspension failure in the European Grand Prix - caused by vibrations which built up after the Finn flat-spotted his right front tyre - warning it should take no risks in the specifications of its tyres
Edited by [xan]

I personally am ANGRY with the US fans for throwing objects onto the circuit, thats endangering lives of the 6 drivers racing, and just shows how dumb americans can be. A F1 car doing 170mph, hitting a 800ml drinks bottle, could cause MAYHEM, think about it.

586088518[/snapback]

i live in us, but i'm not american

and i totally agree

i love this country, but some people in it are idiots

Well, what can I say? I was there for the race, the entire race and I have to tell you that I'm ok with it. I knew at 7AM that there was a problem but I figured that the race would be cancelled. Still I went to it and saw the race. As they went into the pits, people threw stuff and they were rightfully ****ed off. They are demanding refunds but I am not going to ask for mine. I went to the race, saw Indianapolis. Had a nice time and got back.

http://spook.squarespace.com/weblog/i-was-...nd-i-think.html

"Michelin would have been to blame if it had raced. Can you imagine what would have happened if, having seen the failure on Friday, we had decided to race the tyre and we had a problem," This is what a person from Michelin said and I agree with him, why risk the drivers lives for the fans? And to the person that said the risk was worth taking, are you insane?

This one set of tyres rule is awful. I remember the days when teams could use non-grooved (slick?) tyres and change them as often as they liked. Yesterday's 'race' was a sham though. I can understand Ferrari and Jordan not agreeing to have a chicane built - but why not come up with some other solution so at least we got a race?

They should have had a mandatory speed limit around turn 13 for all drivers on Michelin tyres. Or allowed tyre changes for both Michelin and Bridgestone runners. For me, the entertainment should be bigger than the sport and even if the race had been a 73 lap parade behind a safety car then at least people could say it was common sense.

I don't 'blame' Ferrari for anything that happened yesterday but I thought it was extremely arrogant of them not to refuse to race. It was they, yesterday, that had that power to stop all the silliness in one fell swoop, but they put themselves ahead of the fans and the entertainment. By refusing to race, the FIA would have HAD to come to a decision. If the Ferraris had pulled out then I think the Jordans and Minardis would have had to have pull out too. In fact the comments made by Paul Stoddard after the race indicated that the only reason they raced is because there was going to be a race anyway and they needed the sponsorship money.

Refund half the ticket price of all the US attendees, I say.

586091311[/snapback]

Totally agree with the above statement 100%.

I think it would be a shame to lose the F1 GP at the Indy in the future, it's a great circuit and I for one don't think that this years fiasco should be the end of F1 there. Of course the FIA and F1 management in general should learn from what happened this year - maybe the Indy circuit should become one of the nominated test tracks - then nobody could have any excuse for tyre failures or anything else.

I personally agree with the Michelin teams decision to withdraw, no one wants to see some one die, AFTER they had be warned that could happen, especailly as the Indy walls are steel re-enforced. They could of sorted this out last night but they failed to do so, so the blame so far looks to be equal between the FIA and Michelin.

I personally am ANGRY with the US fans for throwing objects onto the circuit, thats endangering lives of the 6 drivers racing, and just shows how dumb americans can be. A F1 car doing 170mph, hitting a 800ml drinks bottle, could cause MAYHEM, think about it.

586088518[/snapback]

Good for the fans...F1 really messed this one up by not refunding their money and not running the race...who the HELL runs a race with 6 cars!!! F1 really messed up here in the US...I'm a fan of Team West and F1, but they screwed this one up baaaaaad. If they played their cards right they could be as successful as NASCAR, but this looks awful on the series. Being run by Bernie Ecclestone doesn't help either...what a dumb****.

while the F1 likely won't come back to the US next year or ever again it's because of the stupid stupid fans that were endangering drivers throwing stuff onto the track .. but then again the situation would have been even worse then that if Michellin had kept their collective mouth shut ... it sucks all the way around

Don't bash the fans in the US just beause they are in the US....especially when Europeans are throwing flairs and darts around soccer stadiums.

I understand the frustration the F1 fans had in Indy. However throwing objects at Race car drivers going 200mph isn't the smartest thing to do in any situation. Watching the race from start to finish on sunday, felt like watching a basketball game except with 2 vs 4. Which was what it seemed because ferrari owned the jordans and minardi cars. Ferrari was at least 1-2 laps ahead of "other" cars. And as for Tiego Monterio getting third place, that was a good job and good effort, however I feel it may be the last time this season he is ever on a podium (considering his previous races this year reflects on close to last place finishes.)

Ticket Holders File Suit

INDIANAPOLIS (AP) - The fallout from the depleted U-S Grand Prix race Sunday at the Indianapolis Motor Speedway has gone to the courts.

Lawyers for a Colorado fan have filed a suit in federal court seeking reimbursement for client Larry Bowers and other ticketholders. They claim they were defrauded after only six cars took part in the Formula One race yesterday. The other 14 drivers withdrew due to Michelin tire concerns.

An Indiana ticketholder has also filed suit. This is in Marion Superior Court seeking a refund.

A Speedway spokesman didn't comment on the lawsuits but says many fans were renewing their tickets.

Speedway President, Joie Chitwood, says no decision has been made whether to refund ticket prices or whether the race would even return to Indy.

The fallout also has extended to the online gambling Web site, Sportsbook-dot-com, which says it would refund all bets placed on the drivers who withdrew.

FIA's Letter to the Michelin Seven

FIA's letter to the Michelin seven

Tuesday June 21 2005

Email Us Chat Forum

Mail article Print article

The following is a copy of the letter the FIA have sent to the seven team principals of the Michelin teams...

'Dear Sir,

Article 151c of the International Sporting Code

You are hereby requested to appear at the forthcoming meeting of the FIA World Motor Sport Council which is to be held in Paris on 29 June 2005 (FIA ? 8 place de la Concorde, 75008 Paris, meeting room ?Salle du Comite? at 09:30 hrs to answer charges that, in breach of the above, you committed one or more acts prejudicial to the interests of a competition, namely the 2005 United States Grand Prix and/or to the interests of motor sport generally in that you?

- failed to ensure that you had a supply of suitable tyres for the race and/or

- wrongfully refused to all allow your cars to start the race and/or

- wrongfully refused to allow your cars to race, subject to a speed restriction in one corner which was safe for such tyres as you had available and/or

- combined with other teams to make a demonstration damaging to the image of Formula One by pulling into the pits immediately before the start of the race.

And that you failed to notify the stewards of your intention not to race in breach of article 131 of the FIA Formula One Sporting Regulations.

A full dossier will be sent to you within 48 hours

At this hearing you may assisted by the council of your choice

Should you wish to send us any comments in writing before this meeting we will make sure that they are circulated to the members of the World Motor Sport Council.

Yours faithfully

FIA'

Nine of Ten Teams Wanted a Chicane In Order To Race

As was well documented over the course of the weekend, the installation of a chicane at Indianapolis could have solved the Michelin tyre problem and allowed 20 cars to take to the grid for the start of the United States Grand Prix - and the decision not to install one well and truly split the grid.

Following Michelin's warning to its seven teams that it could not guarantee there would be no repeat of the blowout which put Ralf Schumacher into the wall at turn 13 - again - the suggestion was put to the FIA that a chicane would slow the cars down and solve the problem of the 14 Michelin-shod cars being on rubber which wasn't suitable for the increased load generated while taking the high speed banked turn.

"Given the combination of oval exit speed of the F1 cars and the subsequent downforces experienced by the tyres Michelin is not able to guarantee that such incidents would not reoccur during race conditions," Michelin said ahead of race day. "Therefore Michelin is not able to guarantee the total safety of the drivers.

"As a result, Michelin, in total agreement with our partner teams has asked the FIA that a chicane, allowing the reduction of car speed be installed at the entrance to the oval. In this condition the Indianapolis F1 GP would be able to take place with the tyres that we used during the qualification."

Although nine out of ten teams agreed that a chicane could have been installed, the FIA and Jean Todt of Ferrari refused to give permission for one to be put in place, meaning that no-one was totally sure what would happen when the 20 cars left the grid to complete the warm-up lap. However within minutes it became clear what the situation was as the 14 Michelin cars peeled off into the pit-lane to retire from the event.

"I have a horrible feeling in my stomach," David Coulthard, who was heard on the team radio as late as the halfway around the lap saying that he wanted to race, sighed when interviewed by ITV as the race got underway. "I have never experienced anything like this in my career. It will leave a long-lasting bad taste, and I'm embarrassed to be involved with it.

"It's not Bridgestone's fault [that the race got underway with just six runners], because it was a technical problem with the Michelins, but, when it came down to it, no-one could find a resolution. Mature adults simply were not able to reach a decision that would enable us to put on a show."

"A chicane could have been built in that short timeframe, definitely," Sauber driver Jacques Villeneuve added. "That would have been very easy, but Ferrari didn't want to, I think. With the chicane, the tyre would have been safe. We were just hoping a chicane would have been put in, because then we could have raced."

Even Minardi boss Paul Stoddart, who saw his team score double points as a result of the Michelin pull-out would have been happy to see the chicane installed.

"Nine of the ten competing teams had agreed that, in the interests of safety, a temporary chicane needed to be placed before the final turn," he said, "and that unless that took place, the nine teams would not compete. This idea was rejected by FIA President Max Mosley, and in no uncertain terms, the teams were told that, should this occur, there would be no race. This, in my opinion, is clearly not in the interests of the sport, the American public, or Formula One fans around the world."

But with the FIA issuing a statement to attack the teams that withdrew, it is even clearer than a chicane had never been an option.

"Formula One is a sporting contest," the governing body said. "It must operate to clear rules. These cannot be negotiated each time a competitor brings the wrong equipment to a race.

"The Michelin teams seemed unable to understand that [a chicane] would have been grossly unfair as well as contrary to the rules. The Bridgestone teams had suitable tyres. They did not need to slow down. The Michelin teams' lack of speed through turn 13 would have been a direct result of inferior equipment, as often happens in Formula One.

"A chicane would have forced all cars, including those with tyres optimised for high-speed, to run on a circuit whose characteristics had changed fundamentally - from ultra-high speed (because of turn 13) to very slow and twisting. It would also have involved changing the circuit without following any of the modern safety procedures, possibly with implications for the cars and their brakes. It is not difficult to imagine the reaction of an American court had there been an accident (whatever its cause) with the FIA having to admit it had failed to follow its own rules and safety procedures."

But could that chicane have been installed without causing any major problems for the Bridgestone runners? Well certainly so in the eyes of Crash.net cartoonist Sprocket with his latest take on F1 action....

Good Ol' Ferrari and the FIA

I understand the FIA's stance on not changing the rules everytime a competitor brings the wrong equipment, BUT when the majority of the field does it then you have a different ball game. This is where NASCAR rules are by far superior...The rules in NASCAR are in place so that the best DRIVER wins..not the best MANUFACTURER (which is obviously the case in F1). My opinion is the F1 drivers are extremely overrated...I think you could put any driver in a Ferrari and they would be extremely competitive. You can't put just any driver in a Hendrick Stock Car and have them be competitive. If F1 really wants to even the playing field then they need to regulate the design and style of the cars along with tires, and set specifications of engines...then let the manufacturers work within those boundries.

Edited by DreAming in DigITal
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!