It varies based on how much water is in a given area (water isn't drawn in ortho4xp so an area with many lakes and rivers will have a smaller size). So rest assured you will probably only have to generate the scenery once and just plop it into XP12 once it releases.Īs for file size, the increase is exponential with a given zoom level. PS Like, I guess, all of us, I am really looking forward to XPlane12įirst, it's almost certain that ortho scenery for XP11 will work just fine in XP12- thats how it was with XP10 -> XP11 and LR doesn't seem to be changing the scenery system. I am looking at a 4TB HDD just for the ortho scenery and am wondering if this will be sufficient.Īny information would be very much appreciated. I do appreciate that this will take up an awful lot of Disc space but I wonder if anyone could estimate just what space I would be requiring. So, what I am looking for is some opinions from diehard XPlaners who have tried MSFS and can give me some sort of comparisons regarding Ortho quality scenery for XPlane vs MSFS scenery graphics.įurther to this, if practical, I would like to have ortho general scenery set at 17 with airports and near surrounds at 18 or 19. The only really good, and I mean, good, aspect of MSFS is the scenery graphics and this includes VR of course. Secondly, mostly due to the incredibly bad VR, particularly controller issues, implementation for MSFS, I find myself increasingly drawn to XPlane. I am looking for a really good and simple guide to the whole process (preferably video tutorials) please.
If you do your own orthos using Ortho4XP, I recommend to do it in ZL 17 and maybe around airports in ZL 19.įor tiles in ZL16/17 for Europe please refer toĪ tile – which is 1 x 1 degree – needs in ZL16 2 GBytes, in ZL17 8 GB and in ZL18 32GB space on your harddisk, 7-zip-compressed to download it is 1,5GB for ZL16, and 6GB for ZL17.I really do not want this to develop into an XPlane vs MSFS war.įirstly, I am having some difficulties downloading and processing ortho content for Australia initially, followed by Indonesia and New Zealand.
Otherwise you get in trouble with memory overflow, decreasing frame rates, loading time before and during flight and maybe hard disk capacity. So if you look at the pictures below, showing different ZL at 500 ft, you’ll see ZL 16 or 17 is sufficient. The bigger the zoom level (ZL) is, the more file size, download time, decrease in frame rates in your simulator. Photo or ortho sceneries are available or can be generated in different resolutions.
0 kommentar(er)
