Do you believe they should be law?  

189 members have voted

  1. 1. Do you believe they should be law?

    • Yes
      93
    • No
      96


Recommended Posts

i dont think anyone here has said that having DRLS is less safe then not having them. The argument is there are times when you need to have no lights at all.

No, there are no times at all, actually. Being on the road is not about sneaking your GF home after curfew or stuff like that.

No, there are no times at all, actually. Being on the road is not about sneaking your GF home after curfew or stuff like that.

perhaps you misunderstood me. i was not asking your opinion, i was stating fact. there are times when i dont want my lights on. maybe you have not been in a situation when you dont want yours on, and thats fine. cars are not always on the road, though. a driveway is not a public road. if im parked and want to keep the car running, im not driving, i dont want my lights on.

perhaps you misunderstood me. i was not asking your opinion, i was stating fact. there are times when i dont want my lights on. maybe you have not been in a situation when you dont want yours on, and thats fine. cars are not always on the road, though. a driveway is not a public road. if im parked and want to keep the car running, im not driving, i dont want my lights on.

So pull up your emergency brake (it should be up anyway if parked). The lights go out. Problem solved.

Of course, you shouldn't leave your car running for no reason when not moving, but that's another thread.

I've been pondering this for a while, since I first saw the thread come up a while back. I've dodged it a bit and made my little funny comment and have now decided to offer my conjecture.

If, according to research done around the world, that DRL's reduce accident rates somewhere between one to ten percent....

How many accidents occur around the world and what would one to ten percent of that number be?

Let's assume every country has 20,000 accidents per year (I know, not accurate but bear with me)...

How many countries are there?

Let's assume there are 120 countries with cars and roads (I think there are more, but I'm being cautious)...

That means there are (at least) 2,400,000 accidents per year around the world.

Let's humor the anti-DRL crowd and say that ONLY 1% of those accidents would have been prevented by DRL's....

That means that 24,000 people (and up to 240,000 people) could have had their accident avoided or maybe even life saved by DRLs...

That is, if you didn't whine and b!tch about them.

You want your social equality and government hand-outs and tax the rich and I could go on... but...

Are you that selfish that you want 24,000 people dead just because you don't want your headlights on during the day...

... or because you want to sneak into your girl/boyfriends neighborhood?

Best post in teh thread. If a vehicle is moving it needs to be seen. Period.

Hell no, DRL's are just too metro to gain popularity here.

-DRL's were created to deal with lighting deficiencies that we don't have in the US

-Higher natural light requires brighter DRL's = more glare

-They are annoying to other drivers

-No positive effect on bright, sunny days

-Dubiously addresses only one or two types of crashes

-Inefficient

-Detracts from motorcycle use that is proven to be effective

Installing sensors that react to ambient light is a much more elegant solution that this feel good baldurdash but neither should be regulated. GM's latest study only shows that 423 people were 'saved' by them in the last ten years. (Thats about oh, 0.1% and not statistically significant)

Your 'even if it saves just one person!' type arguments scare the hell outta me.

Edited by Dashel
Hell no, DRL's are just too metro to gain popularity here.

-DRL's were created to deal with lighting deficiencies that we don't have in the US

What the hell does that mean?

-Higher natural light requires brighter DRL's = more glare

-They are annoying to other drivers

-No positive effect on bright, sunny days

-Dubiously addresses only one or two types of crashes

I don't believe that any of those are true. For one, they are useful even on bright, sunny days - they make it easier to tell whether a car is running or parked (less likely to be surprised by a car your eyes or peripheral vision thought was parked).

-Inefficient

Then why have car manufacturers like Saab, when asked, insisted that the effect on gas mileage is indiscernable?

-Detracts from motorcycle use that is proven to be effective

Huh?

Installing sensors that react to ambient light is a much more elegant solution that this feel good baldurdash but neither should be regulated. GM's latest study only shows that 423 people were 'saved' by them in the last ten years. (Thats about oh, 0.1% and not statistically significant)

I bet those 423 people would disagree...

My car has both light sensors (which are optional, they're only used if you have the lights set to "auto"), and DRLs which have an on/off switch. Though on my car the DRLs appear to be the high-beams, which I haven't yet read about (likely has something to do with the bi-xenon setup), and so far I've left them disabled.

I'm not saying they should be regulated, just that your arguments against them seem shallow and illogical.

DRL (and the majority of 'positive studies') originated in northern countries with lower levels of outdoor ambient light than we experience in the US. If we can't see another car on a bright, sunny day I think there are more pressing issues at stake. I really don't see how your example is of that much importance. If the car is behind me what do I care for if he is parked or not? That it would enable you to see if a car in front of you was going to pull out just doesn't hold weight.

They were created to assist with head-on and front-corner collisions only (i.e. taking a curve or passing and not 'clipping' each other due to misleading light).

Having something run all the time will consume unnecessary engergy. What you are really asking is that if a 'nominal' fee is worth it for the percieved safety. I don't think 1.2B of mandated technology is the answer.

I could see the state of Alaska reasonable push for this during certain seasons, but even there 24/7 lights aren't the answer. Really though, its simply a matter of taking power away from the driver, which is where it belongs. Proponents want to install something you can't turn off. Do you really need anymore reason than that?

-DRL's were created to deal with lighting deficiencies that we don't have in the US
Nope, for better visibility in ALL conditions.
-Higher natural light requires brighter DRL's = more glare
Nope, the candela level is regulated.
-They are annoying to other drivers
Nope, I can't imagine anyone saying, "damn you, your DRL made me notice you more on the road. How dare you?"
-No positive effect on bright, sunny days
Let's say you're correct; what's the negative effect? BTW, you're actually not correct. Bright days don't suddenly render DRLs useless.
-Dubiously addresses only one or two types of crashes
What's your point? Better yet, which studies are you referring to? Nothing posted was so limited, except for the single study done in the US
-Inefficient
Compared to what?
-Detracts from motorcycle use that is proven to be effective
So DRLs are useless but they also make motorcycles more visible? :blink: Which one is it?
Really though, its simply a matter of taking power away from the driver, which is where it belongs. Proponents want to install something you can't turn off. Do you really need anymore reason than that?
So your whole point is that there's something out of your control? Seatbelts are mandated; do you NOT wear them just to be contrary?
Cars are more visible. You don't notice it probably because you don't see it much. It's just one of those things that you get used to.

Indeed AND there are plenty of cars down here which don't turn on any lights when it rains so we see them really late. Therefore such law would be handy there you always have to turn on your lights.

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

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!