3dRaddict Posted January 12, 2022 Share Posted January 12, 2022 The last year has seen me building a number of 2.14.1.1 C++ API trial projects in attempting to get familiar with Unigine. It has been hard work, but I've managed to get most of them compiling (VS2019) and running successfully. However, I recently upgraded the SDK Browser to enable upgrading Unigine to 2.15. I enabled the automatic upgrade/migration of all my 2.14.1.1 projects. I then found that I was unable to successfuly compile them because of all the changes that had been made to the C++ API. Being a 75 year old hobbyist 3D graphic programmer, I do not have the time nor inclination to wade through the supplied API Migration Docs to make all the neccessary manual changes to the code of my 2.14.1.1 projects. It is for this reason that I have reverted back to using 2.14.1.1 of this wonderful 3D graphics engine. Link to comment
werner.poetzelberger Posted January 13, 2022 Share Posted January 13, 2022 Sounds totally reasonable. We usually dont migrate but produce in one version and take the next projects to actual SDK version at least there is a killer feature we want to utilize. Migrating is not fun ;). best.w. Link to comment
silent Posted January 13, 2022 Share Posted January 13, 2022 3dRaddict That's understandable. Unfortunately, we can't provide any automatic code migration, because it's sometimes not as simple as just find and replace thing. Have a good day! :) How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Recommended Posts