It used to be that iFly remembered opacities for Terrain, Airspace, NEXRAD, etc. separately for all the permutations of day/night and Maps. Now it's just day/night, independent of Map.
I request reverting back to remembering all the user's last settings for the day and night version of all the different maps. Here's an example of the problem caused by the way things are now:
Painting terrain is very important out here in the SW, where we have a lot of mountains, especially when I fly at night.
So, at night, when using the VFR Map in Night mode, I have the Terrain opacity set to 95% so that I can see it on the (dark) map.
The initial problem is that when I switch to Vector or IFR Map during a Night VFR flight, I don't need the opacity set so high and it's especially distracting on the Vector Map at 95%. (I have Terrain set to flash.) So when in Vector, I have to set the opacity to something much lower - like 35%. But then when I go back to VFR, it's still at 35%. So I can't see the terrain and have to dial it back up.
It's a pain, but I can deal with it, since I know that I'm switching Maps on that flight. But the more insidious problem is if I my last flight is night IFR. Then I'll have the Terrain opacity set low again, but then a week or two later, find myself flying VFR at night and forgetting that the Terrain opacity is set too low.
All the same is true for NEXRAD and Airspace opacity, where I have it set higher for VFR Map both Day and Night (to punch thru the coloring of the Sectional), but set a lot less for Vector and IFR, where it doesn't need to be so high against a white background.
It's probably a coding nightmare for Brian - although we had it before, so it seems it would be a reversion.
But if it's too hard to implement, then could I request that just the Terrain opacity remember its different settings for the different day/night Maps? Even tho it wouldn't be consistent behavior with the other Layers (although other Layers don't flash), Terrain is the most critical (and problematic) in my scenario above.
Alternatively, a "user reset" might be a work around for this, where, on power up, iFly resets everything to a User configured configuration (perhaps locked to Pilot Profile?), a baseline where I'll know where everything is set and can go from there.
One advantage of this is that I might have turned Terrain off while on final approach to an airport at night (to kill the flashing Terrain) only to forget that Terrain is still off when I depart that same airport later at night. Would be nice for iFly to reset Terrain to my preferred "enabled" for departure.
Or maybe y'all could offer an EEG option, where iFly reads my mind and knows what I want it to do?