mika
did you delete old build folder after setting variable? then build again. also i had to downgrade cmake to 3.22.5 to get rid of some similar errors.. (although still havent...
i added these into top of CMakeLists.txt (note custom folder for toolkit, use our own or remove that line) ``` set(TCNN_CUDA_ARCHITECTURES "86") set(CUDA_ARCHITECTURES "86") set(CMAKE_CUDA_ARCHITECTURES "86") set(CudaToolkitDir "D:/sdk/CUDA/") ``` but...
so finally got it to run, here's my notes.. https://gist.github.com/unitycoder/7e59247ad0f36f77bc8402cd9a22d4fb but i think my solution was to install everything on default locations.. (had to get bigger c: drive, reinstalled windows,...
changed again, new urls, https://unity3d.com/unity/whats-new/2017.4.24 https://unity3d.com/unity/whats-new/2018.3.12 https://unity3d.com/unity/whats-new/2019.1.0 but then some versions are: https://unity3d.com/unity/whats-new/unity-2017.1.0 https://unity3d.com/unity/whatsnew/unity-2017.1.5 https://unity3d.com/unity/whats-new/unity-5.0 https://unity3d.com/unity/whats-new/5.6.7
changed again? doesnt work: https://unity3d.com/unity/whats-new/unity-2018.4.5 should be: https://unity3d.com/unity/whats-new/2018.4.5
complicated, have differences even within same version.. https://unity3d.com/unity/whatsnew/unity-2017.4.3 https://unity3d.com/unity/whats-new/2017.4.24
yup, several times a year it comes to mind that, what if could bypass package manager.. feel free to expand those ideas into quick sketches or lists (how it could/should...
adding link for reference, local package importer: https://assetstore.unity.com/packages/tools/utilities/local-package-importer-105554
can open links into packagemanager: asset store item, com.unity3d.kharma:content/1 UPM package links, com.unity3d.kharma:upmpackage/com.needle.engine-exporter
info about that, [How to avoid the "Windows Defender SmartScreen prevented an unrecognized app from starting warning"] https://stackoverflow.com/a/66582477/5452781 *Submitted zip to MS analysis, lets see what happens. ok, got results...