Currently, MSFS can only support a total of 4 Maps in a Cockpit, more than 4 will cause a CTD.
If you have multiple GPS displays, that a total of 4 maps for the whole cockpit.
This is already severely limiting development of more realistic & complex GPS Gauges.
(1) Selecting GPS maps should NOT cause a CTD.
(2) MSFS needs to support more maps. Ideally a minimum of 16.
Video, showing the CTD when a 5th map is selected.
.
.
.
MOD file, that has 5 Maps in the GNS530, to demonstrate the 4 map limitation.
.
.
Please try this for yourselves, and if you want to see developers able to reproduce more complex GPS gauges, submit a Zen Desk BUG report, (especially if you try it yourself and see the CTD limitation)
Can be reproduced in any plane that has a Garmin GNS530 GPS.
All credit for this BUG discovery and the test MOD to demonstrate it, goes to @ScorpionFilm422 , the GNS530 Mod developer.
Voted and agreed. Third party development of sophisticated and realistic avionics (GNS 530/430 in this case) should be facilitated. The number of maps we should be able to see and use should match the number we would see and use in a GNS 530/430 in real world.
You are missing that fact that a single Display can display a selection of maps.
Each map is a different map, generated with different things on it, and add to the number of map types that that display may have…
Assume at a Max, 3 displays, and 5 different Map type are not unreasonable = 15
Due to things being binary, 1 2 4 8 16 etc, then 16 is a reasonable choice.
Currently the MSFS MOD GNS530 has 4 maps. That means that a GNS430 in the same cockpit cannot have any maps !!!
Must be even more of an Issue with more Complex G1000 & G3000 systems.
Ok for a very dumbed down Asobo base model, but highly limiting for anyone trying to develop a more RW Garmin.
Exactly… you do not want to have just one “MAP” area, and have to delete, and re-draw/generate the new map, each time you switch between maps. That would take some time, and you would see the map “Build” over seconds, when you switched to it.
It would be like having a One page book, and each time you want to turn the page to read the next page, the Book printer had to come in and erase that sheet of paper, and then print the next page for you, as you watched them do it …doing so, each color at a time … etc etc etc
Very graphic.
Have done a fair bit of programming over the years, so understand the concept.
Wasn’t counting all the individual ‘versions’ of the same map.
I would think drawing them ALL in the background would result in an excessive frame hit. Maybe that’s why Asobo gave us a glass cockpit refresh slider. I would think that just drawing the new map behind the displayed map right before dropping the ‘front to back and destroy’ would be more efficient? would reduce the number required as well as the number of background redraws.
Watch the Video, of the selection of the 4 screens for the 1st time. You would not want that every time you switched screens.
I don’t thing the slowness is the drawing of the screens, but rather getting the data from the MSFS kernel code.
UPDATE: 1/29/2021
It appears there are Coding techniques that allow one to use the same MAP, with different parameters, to achieve a larger selection of Maps , than the assumed 4 Map limits.
The 4 map limits still exists, but any of those 4 maps can be dynamically changed to display different things.
The CTD when 4 Maps are exceeded is still an Issue that should not occur, and could still be an issue in the future, if there are multiple Gauges in a Cockpit, and they , as a group, exceed the 4 Map limitation.
