Thisdale Posted August 26, 2016 Posted August 26, 2016 Hey guys, With 2.5 coming (eventually); which merges Caucassus and Nevada; will current missions made in Nevada remain compatible? Or is there a good chance that due to the major update, all missions be rendered incompatible? (map getting bigger, reoriented, scaled... whatever). Anyone has any idea regarding this? http://www.youtube.com/konotani Computer Specs: Z97X-gaming Mobo 4670k i5 24G DDR3 GTX 1080 Asus PG278Q Rog Swift 27-INCH G-SYNC Valve Index Thrustmaster Warthog Fanatec Clubsport Pedals (used as Rudders) Thrustmaster T300 Arcantera Wheel Obutto R3volution rig
NeilWillis Posted August 26, 2016 Posted August 26, 2016 The Nevada map will most probably not be changed as part of the 2.5 merger, so given that assumption, then the 2.0 missions shouldn't have any issues at all. The update is about being able to migrate the earlier map to the new graphics engine, and that situation has been used by ED to overhaul the Caucasus, whereas the Nevada map is already compliant. Not sure whether we will see Caucasus missions transitioning as smoothly given the terrain mesh update. It is possible that some units will be underground and others in mid air, and with the greatly increased tree count, stuff that was in the open may well be hidden in woodland. The truth is though, that unexpected bugs appear with a lot of the updates, so it is possible some may be broken.
Grimes Posted August 29, 2016 Posted August 29, 2016 Testing compatibility for stuff like that when the map physically changes is part of the normal testing procedure. I think the hoped worst case scenario is that you have to re-save the mission file and maybe make some tweaks if needed. Not sure whether we will see Caucasus missions transitioning as smoothly given the terrain mesh update. It is possible that some units will be underground and others in mid air, and with the greatly increased tree count, stuff that was in the open may well be hidden in woodland. Ground units and static objects always spawn "on the ground" there is no altitude option that is enforced. The only way for the altitude position of a unit to change is if two or more objects share the same coordinate. The issue of changes to tree, buildings, etc positions may have an impact, its just really dependent on where things are at, its kinda impossible to know before you actually go into the mission and see. The other big area of potential changes are the road network. If you are using roads and a new road connection was created that has a shorter route, its possible the pathing might change. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
tintifaxl Posted August 29, 2016 Posted August 29, 2016 @Grimes: Do you know if the campaigns provided by ED (A-10C, P-51D, etc...) will be tested for 2.5 compatibity and tweaked, if problems are found? Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.
Recommended Posts