Suddenly, InstaLOD stopped working after putting an additional RAM memory.
Answered
Hello,
Recently, after using InstaLOD Seat Free license, we had to add more RAM into our PC for the InstaLOD usage purposes.
After doing that, we are no more able to use the license, it gives a splash screen like that:
https://i.gyazo.com/160c8aebad9b8ed189f99c0f86b94fd4.png
After launching it, it gives those screens:
https://i.gyazo.com/5ee092a7845e685f687a64da644746dd.png
http://ae0969d8d756928aa6bfce57510a8270.png
After contacting support mail - they told us, that for an exception, they could do one-time free reactivation, after which we will need to pay. Which, to be honest, is pretty misleading for us because I don't see any reason why adding more RAM into PC should result in such issues.
Anyway, I have been asked to include Previous Computer Machine Key and Current Computer Machine Key with details that "The machine key can be displayed in InstaLOD Studio XL, by clicking the “Help” menu item and choosing “Manage License”.
But, we cannot do that, because it shows only this window, and there's no "help" menu inside.
https://i.gyazo.com/9051fd2d326597ecf0604a2f030cddf4.png
I have been advised to join this forum and create a topic by the support team.
Could we get some help on what to do, and why this happened? Also, can we get a clearance if doing such things as adding RAM into PC could lead to paying for the license over and over again?
-
Official comment
Hello Jan,
The machine key is a unique identifier that is generated by InstaLOD when authorizing a computer. Reinstalling the OS on a computer typically affects the machine key that is used to identify it. Putting in more RAM, however, shouldn't affect the machine key.
Changing the machine key in your account requires manual interaction on our side, and thus, the Free-Seat-License (FSL) includes only one free reactivation.
The current machine key is displayed in the License Dialog that you see when starting InstaLOD Studio XL. You can find it in the Offline Authorization panel. To find your previous machine key, please log in to InstaLOD Cloud and go to Machine Activations.
By the way, I noticed that you're still using InstaLOD Studio XL 2019 Preview 2. In December, we've released InstaLOD Studio XL 2020 which contains many new features and improvements. The new version is also available to FSL users and can be downloaded from InstaLOD Cloud.
Thanks,
Andreas
Comment actions -
Sadly it didn't helped - https://i.gyazo.com/9649e4054a084a2aefb4fc10740be28a.png
-
Hello Jan,
It seems that the problem is unrelated to the exchange of memory in your computer.
After the release of the InstaLOD 2020 product wave in December 2019, some license entitlements have been changed. This can cause issues for InstaLOD Studio XL 2019 Preview 2 users. Can you update to the latest version of InstaLOD Studio XL to resolve the problem?
Thanks,
Andreas
-
We are not sure yet, it simply creates bugged imposters at this moment, we had a hope that we won't need to spend time to debug and update our implementation which is using Jason files and InstaLODCmd because of forced version change - once more, is there a way to let us keep using 2019?
-
Hello Jan,
Unfortunately, InstaLOD Studio XL 2019 Preview 2 is no longer supported. As you're working with Unity, I'd recommend trying InstaLOD for Unity - SDK2020 directly.
If you can share some data that reproduces the unexpected behavior, we will be glad to look into it. It would be great if you could also share the JSON profile that you're using. To share files with us, please upload them to InstaLOD Cloud (simply log in and click Share Files).
It seems that you've been using InstaLOD Pipeline, which was never part of your licensing agreement.
Previously, our licensing server was not able to determine if your particular seat-licensing agreement covers the use of InstaLOD Pipeline or not.
With the release of InstaLOD 2020, this black-spot in our licensing system has finally been covered.
To clarify, the use of InstaLOD Pipeline as a standalone app outside of DCC applications was not covered under the SLA for seat licenses.
For the usage of InstaLOD Pipeline, we have specific licensing options such as game licenses, grid licenses or other automation licenses.
Thanks,
Andreas
-
Wait, so you have offered us a Free license, which part of the application was InstaLOD CMD, as which we have done our implementation for our needs - as your SDK was not enough for our needed automatization.
We took about months to do that implementation, used the system a few times after that and it stopped working. First - we received information it was about RAM exchange on the PC and as "one time offer you will unlock it for free". Luckily - I have started digging further, and it was not RAM, it was a change of version of the software.
And after that, we received that information the software which was fully usable using login details we have received from you, using the download link you have provided to us. And now, suddenly you write here that we no longer can use Pipeline (which I understand is a part of another license now).
I don't know what we can do about that now, we were speaking some time ago with other developers giving them tips how InstaLOD could be a good solution, but for now, I will simply feel bad for anyone who would get trapped like we are now.
All we need is a possibility of usage of running commands from InstaLOD CMD, but I guess it won't be enough it application will update, and changing integration without the InstaLOD application would be even more complicated afterward.
Can I get information on what license we should have, and how much does it cost? I never saw a situation like that in my entire career and I am really confused.
Post is closed for comments.
Comments
13 comments