Patersonski Posted June 9, 2017 Posted June 9, 2017 I have Nevada/2.0 and am waiting for a couple more weeks of bug fixes before I download Normandy, but I'm reading on these forums that 1.5 skins need to be updated for 2.1. Should I also assume skins made for 2.1 going forward will not work properly in 1.5? At the moment I essentially have a single liveries folder (a symbolic link in 2.0 references the 1.5 folder), which works very well, but going forward will I now need separate 1.5 and 2.1 folders because the skins will be incompatible? Thx Rig: i7-6850K, Sapphire 6900XT, 32GB RAM, Asus X99-Pro board. Gear: VPC WarBRD/MongoosT-50 Stick, VPC MongoosMT-50 Throttle, VKB T-Rudders Mk.IV Pedals, HP Reverb G2.
nrgized Posted June 9, 2017 Posted June 9, 2017 Deferred is not backwards compatible with not deferred rendering. Thus if someone is making skins to support deferred they are not backwards compatible.
Art-J Posted June 10, 2017 Posted June 10, 2017 Incompatibility of 1.5 is related mostly to specmaps, the normal ones might work more or less OK - for example YoYo's custom Spitfire skins look actually much better "out of the box" in new engine, with slightly over-polished finish of 1.5.6 now rendering properly semi-flat in 2.1 without any tweaks. Try out any flat-painted aircraft skins and see how they look, most of them should be reusable. The reflective, natural metal ones, however, will most often need serious rework. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Recommended Posts