The title is pretty straight forward; The textures on the ingame map could give a unecessary load on slow machines and\or heavy missions and it makes the map reading more difficult.
- Legacy ID
- Ingame UI
Even after the many game engine optimizations (or the few optimizations depending on perspective ;-)... I still have to disable the excessive 3D or real color map textures after each re-login as the 3D/"real color" map textures significantly hinder performance when switching to map display!
As to why that base map image does not stay loaded within memory and has to be updated on each view is beyond me. (Maybe to save video ram while within the engine? But if that were true, the basic non-3D map should be displayed by default!)
By the time the 3D map renders, the aircraft drops altitude significantly from even safe altitudes! Same goes for when driving. (Are they poking pun at distracted driving?)
Personally if we were under Linux, I'd rather just export that real time map (or GPS) view to an external monitor! Should be no real need to be blanking the entire screen while in flight or piloting! Simply briefly look to the lower right or left and back to the window.
I think once they implement an environmental or configuration variable, I think they'll find most people will be switching off 3D map view off, and resorting to the basic topographical map. Or at least those that know how to. Even when performance is increased with the engine or the performance is fixed with this map slow loading, the 3D map view has difficult to discern topographical features making the non-3D map view highly preferred.
Shrugs. Some look at maps to view the pretty mountain photos. Some look at maps for such essential details such as topography features! (ie. Some like to run into mountains, while some like to avoid them. ;-)
The first thing I do when I load into a mission is turn the map textures off. It would be wonderfully convenient to not worry about it anymore - not to mention relieving loading issues and whatnot for having textures enabled by default.
Still toggling this option using a Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (ie. 4xCPU SMP, 4xHT), GeForce GTX 670, 32199 MB RAM.
The map takes more than five seconds to render, and this is not a good thing while piloting or driving, or performing some other time important task.
I'm sure anybody using less then these hardware specifications are certainly doing the same of toggling advanced textures off for the map view or fall into one of the following categories; 1) They don't know about this Map option (as it is the button cannot be immediately seen) or, 2) They don't know about this bug or, 3) fear filing another bug which might be marked a duplicate of the more popular performance related bug.
Although there are several other bugs, I'd have to say this bug should be one of the upper priority ones. Likely only lower because users are assuming this bug is related to the more popular CPU performance related bug. (Because the game is adapted more for NVidia video cards, may God help AMD video card users!)
Again, the solution for this bug would likely be either, 1) Have the map textures remain in memory instead of reloading during each press of the 'm' key, or 2) provide an option within users' configuration options to remember or state the level of map textures to provide. Likely providing an option would be more preferable for short and long term use, while fixing having textures remain within memory could be grouped with the performance related bug and easily delayed a little longer.
Well said RogerX: "Although there are several other bugs, I'd have to say this bug should be one of the upper priority ones" . . . "the solution for this bug would likely be either, 1) Have the map textures remain in memory instead of reloading during each press of the 'm' key, or 2) provide an option within users' configuration options to remember or state the level of map textures to provide."
Agree 100% Although for now, I prefer option 2).
I would consider this more of a bug than a feature request.
Should be up there with issues on page #1 of the vote comparison page, as most everything else after page #2 is just feature requests, or "I want this" feature.