I'm actually right there with you. I even have this issue to some extent with the FW3A. During the day I've mostly been carrying my D25C this past month. I can quick-tap the tail switch without looking and always know exactly how much light I'm getting. My second-most carried is my SC62, which has never turned on in my pocket either, and I can also shortcut to any mode quickly and blind.
This... also kind of looks like a pain in the butt to mod. If I wanted to swap the LEDs, I'd have to disconnect that crazy aux board to get to it. But at the same time, the aux board and stainless bezel are like 90% of the reason I'd want one at this point. I wonder if the driver + aux board + stainless bezel can swap into an older D4 host, because I'm not thrilled with the color options offered either.
I too will await future revisions. I'm pretty close to modding the metal ring around the switch on my old D4 to prevent pocket-burn, and then it would be nearly perfect.
Ramping IOS V2 was very simple and could be “mastered” by everyone. Anduril is complicated, too complicated for non-flashoholic people and those who uh… how to put it… lack the mental capabilities. It’s certainly not an inclusive UI. Although of course it’s heaven for flashlight enthusiasts.
No. Although I will certainly use manual MM. What I meant is that Anduril doen’t remember the mode accessed by using a shortcut, either hold for moonlight or double click for turbo. In theory it has sense but practical it looks like this:
I use the flashlight to lighten a big turbine hall in an abandoned power plant. It happens i do this by ramping up to turbo. Next a want to go to another building but to do that I have to go trough a corridor which has windows on the opposite of a shed of the security guards so i have to be discreet. I turn the light off from turno, open the door leading to that corridor and hold to switch to activate moonlight in order to not to be seen but also not to fall in hole or something. I walk through the corridor and see through the window that a guard has left the shed to smoke. I turn the light of to make sure I’m not seen. The guard goes back to the shed, an I can continue my journey.
Then I make one click on the flashlight because I know the light has MM. But it activates not the firefly mode as my brain assumed but the turbo mode because it doesn’t memorize levels reached by using a shortcut. 4000 lumens blast through the corridor, the guards obviously see it and start chasing me through the building. End of story.
My brain doesn’t remember whether the last mode I used was accessed by using a shortcut (remembered by the flashlight) or by ramping (not remembered), a certainly not in situations I use the light instead of just toying with it. This leads to unpleasant situations I think I get firefly (I use that mode a lot) but instead I get a high mode.
The point I’m trying to make: it would be better the driver would use mode memory for levels acceded both by ramping and by using shortcuts for the sake of reliability and predictability.
In an urbex situation like that, I’d be inclined to set my D4’s manual memory to the lowest level, so it always comes on in moonlight with no surprises. That way, it makes it very hard to accidentally screw up and blast out more light than intended.
The problem for you could also be the opposite though,
I used the shortcut for high/turbo, then off, then on again expecting the low mode I was using before turbo.
My point is that if you have a flashlight that can produce both moonlight and turbo there is ALWAYS a chance you will not get what you want. (or be disappointed by the sequence)
My D18 and D4S, with two different software versions (RampOsV2 vs Anduril), DO remember the last level used, even if it was from a “shortcut.” You may need to set your ramp floor to moonlight and your ramp ceiling to turbo to get this functionality though, I believe. But, this is how I configure all my newer Emisars anyway, so it works great.
TK, have you ever tried the firmware flashing pads yourself? I remembered that similar lights like Fireflies E07 cannot be flashed via the pads, unless you de-solder the aux light board. So can we flash the D4V2 successfully without de-soldering anything?
Below is one of the reasons I finally ordered my first Emisar. Don't like my lights to get hot at all (I don't mind sacrificing output). The Muggle mode is great too.
Things that caught my attention:
[quote]
Much smoother thermal regulation
[/quote]
Temperature limit. This sets the maximum temperature the light
can reach before it will start doing thermal regulation to keep
itself from overheating. Click once per degree C above 30. For
example, to set the limit to 50 C, click 20 times. The default
is 45 C.
it's very ugly clip and am straggling to remove it from the flashlight! It's very hard to remove and really pocket shredder!! I hate everything about it
The 5-click sets it to the level you’re currently at I’m assuming? That sounds both simple and fast, I dig it.
I think the only change I would suggest to Anduril is setting the click, click+hold lockout mode to be the same output as this memory mode if it is on.
Edit: And I missed the answer to my question on this page before I asked it, oops :person_facepalming:
