[Series 11] Top Gear


Recommended Posts

Lol yes. Although about the cheese, he asked for it. Lol their cars were falling apart and May said "my heater is stuck in the on position" :laugh:

But i heard something about a Japan special? Is that this season?

It's the next episode ;) A Nissan GT-R vs a bullet train. Should be a good one.

Well, I've just got back from the bank with the presenters' wages, and it took a while because it's a bugger parking a container ship outside Natwest.

Anyway that'll keep them happy for a day or so, which means we can put another programme on air.

Show four of the run to be precise, and we're all excited because we've got one of our big races to show you.

Now the last time we did one was a couple of years ago with the Veyron against the plane, and to be honest it wasn't the film it could have been because it all got a bit silly side up - too big and overblown - and it didn't have the purity of the run to Verbier or Monaco.

Anyway, we shelved the whole idea of big races until we could think of another one that made sense, and then this year Nissan very kindly decide to launch the GT-R, and the clouds parted.

GT-R versus Bullet Train across Japan: one of the world's most hi tech cars against the world's most formidable public transport.

What's not to like?

You'll see it on Sunday, and you'll notice how everything else is squeezed to death, because the Japan film came out at over half an hour, but it's good at that length.

Lots of people ask lots of questions about the races - how do you shoot them so nicely if you're in a race? Are the results fixed? - that's two popular ones.

Well, what we do is shoot the race in real time - car on the road, camera car alongside, no stopping for extra shots - get the result, and then the director and camera crew spend another two days after the race going back over the route to get the pretty shots.

You have to do this because a race shown on telly with just the shots you get on the move during the actual race will look ****, and you and us deserve better than that.

And in answer to the second question, no, the result is the result. If the car wins the car wins and vice versa.

People get suspicious because the results always go to the wire, but what we do is plan the route beforehand, and we always make sure that mathematically both journey times will be close.

It's not rocket science, you just need average motorway speeds and train times etc. After that the presenters are on their own.

If something goes wrong for them - say they get lost, the camera crew can't dive in and help them, because they're only recording the race, not taking part in it.

With the three minutes we've got left in the show, there's a power test of the sexually arousing Alfa Romeo 8C, some news where the three of them talk bollocks, and some rather attractive women in the Reasonably Priced Car.

So, given that there's no tennis or football or crown bowls on the other side, just watch the bloody show.

PS - since I wrote the above I've watched the finished programme in full and don't think I boasted nearly enough.

You know my thoughts on this series so far - the first two shows were solid but not classics, that Alfa film in the third programme was very good but this Japan one is on another level.

If I don't mind myself saying it. So, enjoy...

Source - http://www.topgear.com/blogs/planettopgear...show-4-preview/

Can't bloody wait :woot:

Radish?

Yeah, cant wait till sunday, tv wise :laugh: New blog entry from Clarkson himself:

On Sunday night, there is a race between a Nissan GT-R and a bullet train right the way across Japan.

It is extremely exciting. I think the best film we've ever made.

Unfortunately, it will be spoiled because I shall have to spend the next few weeks explaining how these races are filmed to a bunch of people who imagine they're staged, scripted and pre-ordained.

Of course, the routes are carefully planned so the result will be close but it is impossible to guess what will actually happen after the flag drops.

You may notice if you watch carefully, the on board cameras in the GTR were flickering red and green. But did we stop to fix them? Did we hell as like.

During our race to Oslo, the poor cameraman in the back of the tracking car had to pee in a bottle. We do not stop.

In the Ferrari versus plane race to Verbier, I actually overtook the tracking car, leaving me with nothing but the on board mini cams. I was that desperate to get there first.

And we get back to be accused of fakery by some internet dweeb. It makes my effing teeth itch with rage.

Of course, once the race is run and the result in the bag, the camera crews stay behind to pick up the shots needed to make the whole thing work on television. The details. The icing. But that doesn't affect the outcome.

I hope you enjoy the race across Japan. And now you know it's all for real, every ball breaking moment of it, I hope you enjoy it even more.

Source: http://www.topgear.com/blogs/planettopgear...son-japan-race/

I enjoyed it all this week - even Star in a Reasonably Priced Car - only because Fiona Bruce and Kate Middleton are rather good looking (and not up their own backsides like many celebs on that sofa) - and the 'lesbian' comment just got my mind whirring ;) That and I laughed out REALLY loud when Jezza said to save the swear words for whenever Gordon Brown was on TV - hahah..

The GT-R race was brilliant. Really enjoyable in every sense.

Oh and the newsreaders were sexy with their accents

Quite. Mmmm...

what was with the "dont use your cell phone " on public transport about?

I think Japanese people find it disrespectful or just generally annoying/antisocial. I can't say I disagree with them either, although to be fair Hammond and May were trying to be as quiet as they could. I'm sure having a whole camera crew crammed into the train/bus would've been a tad more irritating.

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

    • No registered users viewing this page.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!