How do you prefer a multimode flashlight ? - Poll 1

One default mode or a memory feature


  • Total voters
    96

Tally-ho

Banned
Joined
Apr 6, 2010
Messages
335
Location
France
Hello CPFers,

I would like to collect opinions/preferences of users for further discussion with a manufacturer of P60 hosts and modules. The basis is a basic UI that cycles through different mode without hidden features.
(Sorry for my bad english that not help to enter into details to make a better methodology which is far to be perfect but it is just to collect a sort of "1st round of basic opinions". Try to be as concise as possible to specify your choices, you can then digress about you favorite emitter, tint, etc but this is not really the purpose of those polls.
The purpose is to see if clear preferences emerge to fulfil needs of a wide range of users about "memory feature or default mode" and "decreasing, increasing levels or specific order" or to see if there is to many combinations without clear differences/emergences).

It is obvious that a part of us are using more than 1 flashlight to match different needs but imagine that you would have only one multimode flashlight (with cree XP-G.R5) for different situations, how would you prefer it ?

1st poll (above)

That it always lights up with a default mode sets by manufacturer. Always high, always mid, always low ?
1- Always high (higher mode)
2- Always mid
3- Always low (lower mode)

That it lights up with the last mode you select before switching it off ? Memory feature to allow users choose which one.
4- Memory

EDIT: Consider that you do not need to remember in which mode you left the flashlight the last time. As an experienced user, you always check your flashlight before starting a new activity to be sure that the flashlight is set to the appropriate mode (the mode that you are going to need). So before starting your activity, you light up the flashlight to check the level, and you cycle through the different mode to select the one that is needed, then you turn it off. Your flashlight is ready to use. (i.e. you are planning a night hiking, set your light to low at home when preparing your backpack. The next day, check it and set it to high before going to work)


2nd poll (link)

1- Increasing levels
2- Decreasing levels
3- Specific order levels (specify it in this thread)

Please specify in top of your message the different levels you (would) prefer and in which order. The 1st poll was made on a basis of a 3 mode flashlight but it could be a 2 or 4 or 5 mode flashlight (you can prefer to keep the basis of a 3 mode flashlight for a better homogeneity of responses).
Before the cycling order levels, specify "default" or "memory". The first level of the cycling order will be the mode by default if you pick "default" in the first poll (we don't know your vote, so write/specify it in your message)

i.e.:
If you pick "increasing order", please specify:
Default: low - mid - high
Memory: 0.5 lm - 5 lm - 100 lm - max
If you pick "specific order", please specify:
Default: max - 40%
Default: max - 10 lm - 120 lm

Specify if you prefer a 1000mA or 1200mA driven XP-G.
Of course you can respond/answer on a general basis, based on your general preference without taking into account the emitter, just to let know how you prefer cycling order levels and outputs level/brightness on a multimode flashlight for general uses (indoor, outdoor (hikings, ...), etc).
The main point is not knowing which type of UI (sophisticate UI, multimode UI, single mode, etc) a user prefers in absolute terms but rather what does he prefer in the case of a basic multi-mode UI.


To resume it, respond to the 2 polls then specify in top of your message something like:
--
Memory: 0.5 lm - 5 lm - 100 lm - max
1000mA
--

Then explain why if you wish
--


Thank you in advance.
 
Last edited:
My favorite multimode has to cycle through:
Memory: 0.5 lm - 120 lm - max
1200mA

Or

Memory: 0.5 lm - 10 lm - 120 lm - max
1200mA
 
Last edited:
Since we are talking about a multimode P60 module specifically, and I currently only use single mode with momentary/twist tailcaps this is a bit hypothetical.

I picked memory simply because my uses dictate which is preferred. Memory is the most multifunctional between the various layouts possible.
 
I voted Memory, and thats my general fave. But its not really a deal breaker for me. I have several lights with different switching mechanisms for different uses. Depending on the type of switch and how I use the light, there are advantages to all 4 UIs.

My biggest complaint is Disco/SOS modes and visible PWM. Visible PWM is inexcusable, and can easily be alleviated... its just the frequency of the pulse programmed into the EPROM.
 
Since we are talking about a multimode P60 module specifically, and I currently only use single mode with momentary/twist tailcaps this is a bit hypothetical.

Hypothetical, yes this is the main thing. It is not to know what setup you are currently using because there is to many combinations. I hope that the main frame I tried to make is clear but my bad english doesn't help to be very clear with this. I'm afraid that I was not enough clear about principles of those polls, anyway...
So an hypothetical basis is perfect.

Memory is the most multifunctional between the various layouts possible.
I totaly agree with this but it seems to not be so obvious for everyone because we don't use or light the same way.
The main point is to consider that this flashlight has to cover the wider range of your indoor and outdoor needs, but will not be the best for a specific use (ie: keychain EDC, search and rescue flashlight, etc).
To cover the wider range of uses, there is probably a better one than an other. For example a flashlight that always lights up in high mode will probably not be the best when you will have to wake up late at night in a mountain refuge full of people asleep (sleeping (?)), not taking into account that it will blind yourself. Well if it already happened to you, you know what I mean.
 
Last edited:
I voted "always lowest" because I wouldn't want to use a brighter mode than needed and ruin my night adapted vision. I like memory too but the more lights one owns, the HARDER it is to remember what level each particular light was set on the last time it was used.😕
 
I voted memory, and to take it further, I prefer that the tailcap button is ONLY an on-off and momentary switch, or only have an extra feature of double-tap for temporary mode upgrade (i.e., double-tap for LOW to MID, MID to HIGH, HIGH to strobe, etc.). I prefer mode switching to be done by twisting the tailcap or bezel, which prevents accidental mode switching when you just want two quick momentary bursts. The twisting action must have tactile feedback such as a light click when you reach each mode.
 
I voted "always lowest" because I wouldn't want to use a brighter mode than needed and ruin my night adapted vision. I like memory too but the more lights one owns, the HARDER it is to remember what level each particular light was set on the last time it was used.😕

That's why I always check the 2 or 3 flashlights I will carry for a specific activity, before starting this activity.
i.e.: Before a night hiking I set all my flashlights to the lowest mode. For a night walk in my city with enlighted and dark parts, I carry one flashlight sets to mid before putting in my pocket, ready to use if needed. I always have a keychain EDC (sets to mid or high). Etc...
That's the reason why I personnally prefer a memory feature (on a flashlight that cycles through at least 3 modes) to match with ( to fit (?)) a specific use.
 
Personally, I HATE cycling through various modes every time I pick up a torch. That is why I am in love with the Quark Tactical UI. It has ~8 modes, you program your two favorite modes and you'll have one with the head tight and the other mode with the head loose. It's the perfect UI that should be on every light IMO. Well, if they could somehow add one more mode selection, that would be even better!


-
 
Personally I prefer the always low type setup as it is very natural to use. However, memory is very valuable with larger lights that I expect more output from and the low is not very useful since it is usually 15+ lumens.

For this reason, I voted memory for P60 type dropins. There are different kinds of memory. The button-last-mode memory is not as desirable for me as the quark tactical/MD2 switch type.

The bezel derived memory is better since the user can choose which mode is set before the light is activated. Something like "ok the bezel is loose, so its on low" is easier work with than a switch derived last mode memory like Dereelight has. There is also no guess work "oh this is not as bright as I remember, have I messed up the modes? or are the batteries dying?" definitely easier.

This type of memory is very intuitive and extremely easy to use.
 
Last edited:
Personally, I HATE cycling through various modes every time I pick up a torch. That is why I am in love with the Quark Tactical UI. It has ~8 modes, you program your two favorite modes and you'll have one with the head tight and the other mode with the head loose. It's the perfect UI that should be on every light IMO. Well, if they could somehow add one more mode selection, that would be even better!


-

I thought I felt the same way too. I started with a Quark regular R2 then an R5 tactical then a regular neutral and finally a tactical warm. I use my tactical ones on medium and turbo for work but I use moonlight every morning to see to kiss the kids goodbye without waking them so I need the regular UI so I'm not constantly reprogramming the tactical ones.
 
One aspect of the UI that wasnt mentioned in the original post was selecting the modes. I prefer a design that doesnt require a sequential cycle that is selected by a serieis of rapid on and off clicks.

the best UI for selecting modes is the Blackhawk Gladius. It is all contained in the tailcap selector switch and a big tailcap button.

it is very intuitive to rotate the selector with the thumb and index finger.

however for a light that only has two modes like the A2 aviator I prefer the low at half press and high on full press.
 
One aspect of the UI that wasnt mentioned in the original post was selecting the modes. I prefer a design that doesnt require a sequential cycle that is selected by a serieis of rapid on and off clicks.

I initially tried to stay on a very general basis with as less details as possible. I edited OP several times to add details for a better comprehension but I was wrong with the principles and formulation of those polls 😱

In fact I would rather have entitled those polls as "how (do you think) a basic P60 module UI have to be to fulfil (to respond to (?)) the wider range of users needs ?" (or something like that in a better english for clear comprehension)
- UI cycles through different modes with reverse clicky.
- ...

1st poll
...
2nd poll
...

Anyway, it is very informative to read all your point of views.
 
Last edited:
I'm a big fan of single mode lights. There's something very elegant and useful about having one switch turn on one mode. However, there are times I also like a light with modes. In those cases, I do like some kind of memory function, whether it's a novatac-style "press X times to enter programming mode" or quark-style "twist to change memory setting". I don't particularly like having to "bump" through different settings to get to the level of light I want.

All that said, I've actually been liking the Maratac-style med-low-high twisty lately.
 
Check out Lumapower's UI. Best I've come across. It has memory, 3 modes, and you can easily lock it into any mode you want it to stay. I keep mine locked on high, I unlock it, and cycle to a lower mode when needed. When finished, I go back to where I want it to operate and lock it there. It really is the best of both worlds. I prefer a single mode....but sometimes want less light. Especially with the power that most lights have these days.
 
Last edited:
Personally I like the Fenix L1T/L2T UI. Loosen bezel for Low, Tighten bezel for high. I can always check the light level before pushing the switch. Unfortunately Fenix has patented the simplest way of doing this.

-

Can not do the rotate bezel thing in a P60 host so...
Memory.
Light levels:
Low - 3 lumens or less. Do not disturb others. Preserve night vision with optional red filter (if you build your host correctly the Surefire ones will fit).
Mid - 30 lumens. My Nitecore EZAA at 10 lumens is too dim for indoor use. Quark Mini AA at 15 lumens just adequate. Fenix L1P at 30 lumens is nice.
High - Brightest you can get reliably for outdoor use. Some people especially law enforcement officers want minimum 2 hour runtime instead.

-

4sevens has gone through this exercise over the years, 1st for Fenix then for himself. He ended up with the following:
Preon 2
Low first.
Low - 2.2 OTF lumens.
Medium - 22 OTF lumens.
High - 160 OTF lumens. That is about the best he can get out of an AAA head. His 2*123 Quarks get 230 OTF lumens on max.
-
His regular Quarks ended up having too many levels. So people are buying the Quark Tactical and programming the 2 levels for bezel loose/bezel tight positions.
 
I would like my lights to always light up at the lower settings.

The reasoning being that if I am out at night and want to light up something small to see it, I definitely don't want it turning on initially at full brightness, dazzling me and ruining my night vision when all I need is a low amount of light to illuminate something without destroying my night vision. If it starts at low, I can always then ramp up the brightness without having any negative impact on my environment (other than taking a fraction longer to get to full output)

With a memory mode, you do admittedly say to ignore the 'forgetting which setting you left it at' problem, but I can't - I want to be able to grab my light and turn it on at a known setting, whether it was last used 30 seconds ago or 30 days, so defaulting to whatever I last used it at is useless when I cannot rely on my memory to guide me to the setting I need...

I would agree with LEDninja that ideally I would go for some form of Fenix L1T UI, which can be preset before tuning it on and double checked easily if you cannot remember what it was last set to. Unfortunately that won't work as well with a light with more than two output settings - for me something along the lines of 20/100 lumens in two steps would be perfect though.
 
Re: poll #2
I like my lights to start up at a useful indoor level ~30 lumens.
So 30-100-300 lumens.
But 30-3-300 lumens.
 
Couldn't vote in the poll, because none of the options seem to fit.

For me, the Photon ReX is currently the ultimate in multimode functionality. No need to remember the last setting, and no need to have a light that always starts at high, or always at low.

Click on and the light comes on at full brightness, press and hold the switch for the light to come on at its lowest level. Very easy and intuitive.

At the lowest level, if you continue to hold the button, the light will gradually increase until it reaches full brightness (blinks). To go from full bright to less bright, after clicking the light on, press and hold the button, and it dims until it reaches the lowest setting (blinks). Release the button anywhere in between, and the light stays on at that level. As far as I know, there is no memory function however, to start the light at any of the mid-levels.
 
Back
Top