After some issues with my computer (needed to clean up some disk space as well). My axoloti suddenly won't play along as it used to. I have tried re-installing but it doesn't seem to help. I'm unfortunately not so good with computers so most gibberish looks like... well... gibberish.
Hmm, seems I'm having bad luck here at this forum at the moment. No one able to take a guess?
Anyway, digging around a bit more on my own. I recall that in cleaning up that precious disk space mentioned in my former post. Which I needed to be able to create an boot USB drive with WIN10 via microsoft (for another micro computer). I removed: Visual C++ Redistributable for Visual Studio 2015.
According to this thread:
It seems to be needed to be able to run Axoloti patcher. Is that correct? That redistributable was/is around 4GB hard disk space IIRC.
I tried Axoloti 2.0 and my board installs the firmware but I couldn't run any demo patches but didn't really expect them to either since it being a pre-release (experimental) version.
So I downgraded back to 1.0.12 or whatever version it is. Connection fine with board but when, again, trying demo patches it complains alot regarding java-gibberish (many lines of different errors/issues but many if not all contains java somewhere in them).
Does anyone know if abovementioned visual c++ redistributable would solve this? Or am I at an entirely different problem now? Sorry I don't have any screenshot this time...
Version 2.0 is still experimental. I tried it for a day and most of my patches didn't work, so I went back to last release. So if you are having issues, I would not recommend using 2.0 for now, wait until it is stable. It will most likely cause more errors.
But in general if you followed the install guide for the platform that you are using, it should work.
I probably have uninstalled and reinstalled both runtime and the other part 2-3 times. Unless there is something specific regarding installing runtime that isn't clearly written out in the windows install post by technobear?
What I recall that I do: Unzip the axoloti_runtime zip. And put it in the same folder as the axoloti editor ends up in (program files). Or should it even be IN the axoloti folder too (program files/axoloti)?
I'm currently not close to my computer at the moment so all I mention are from memory...
It says in the install guide: "now check that you have C:\Program Files\axoloti_runtime\platform_win or C:\Program Files (x86)\axoloti_runtime\platform_win as appropriate."
Which I read as when all is done I have (in program files):
C:\Program Files\Axoloti
&
C:\Program Files\axoloti_runtime\platform_win
If that seems correct. Then I suspect the errors might be from when I removed the visual redistributable the day earlier. But I don't understand the connection/reason why...
I'm planning to try that. But I will need to download it again.
I needed to uninstall it in the first place to free up hard disk capacity to be able to create that USB win10 boot stick. I don't remember that I had installed it, and even less the reason of why I would need it installed either.
Installed once again and this time demo patches works. Only difference is that my OS (win 7) detected an newer java update than the one installed being aviable, so I downloaded that and installed it. Haven't even got to the visual redistributable yet...
Is it possible for normal java updates to make the axoloti patcher losing its stability?