Okay, i tried taking this to LearnMMD and NVIDIA, and now I'm taking it here:
For the second half of December, I've been dealing with a particular problem with MMD acting extremely fickle about saving anything with AutoLuminous attached to it. It all started with this Xmas picture I made to commemorate the holidays:
Usually whenever I export an image file from MMD, I always save it as a .png to save space and because uploading bitmaps anywhere online seems to be a hassle... Unknown to everyone here, whenever I was trying to save this image. I'd keep getting this strange message:
Whenever this happens, I can no longer get back into MMD and when I try to re-enter the program, I get this message:
I also notice that when this happens, NVIDIA's GeForce Experience stops working too... To make matters worse, this same sort of glitch also effects my Adobe CC products from time-to-time, since I notices NVIDIA (and MMD as a result) stops working again whenever I get into one of their apps. I've been able to bypass this issue by disabling and then re-enabling my NVIDIA display adapters in my system's properties... Normally this wouldn't be a problem because while I cannot save to .png or .jpg for reasons I'm not getting, I can still save it to bitmap with no problems at all. HOWEVER, now this issue is effecting my video rendering capabilities, and this is NOT good seeing as I intend on using MMD for development on "Gathering of the Kings"...
First off, I will say that everything SHOULD be installed properly on my end for MMD to work (Microsoft Visual C++ Redistributional Packages 2005, 2008, 2010, and DirectX9) and MMEffect has been installed normally. Many I've spoken to suggest it's because of the amount of models I have attached to the project, others suggest it's a RAM-related, and others more think it's because of something deeper within the laptop I've been making the past few images with (which I will address momentarily). I want to put to rest that I've used AutoLuminous and several others on several occasions with others pictures once I did get my laptop. The likes of which include the following (and others I've made but didn't include because this should be good enough proof):
- MMD Version = 9.31x64 version
- Laptop = Lenovo Legion Y520
- CPU = Intel(R) Core(TM) i7-7700 HQ @ 2.80GHz
- GPU1 = Intel(R) HD Graphics 630
- GPU2 = GeForce GTX 1050 Ti
- RAM = 16GB
- HDD = 128 GB SSD + 2TB HDD
- OP = Windows 10 64-bit
Right now, the advice I have been presented with that I haven't taken yet due to my work schedule (and concerns about what it could do to my laptop since my warranty may have expired at this point) is the following explanations:
Before I try any of the following advice, I figured I'd post this entry on here in case there is/was another MMD user who has dealt with this type of problem before and can relay any sort of experience to me on what I should do.
- Uninstall my current Intel and NVIDIA drivers and in their place, install older "certified drivers" tailored specifically for the laptop (suggested by NVIDIA and LearnMMD)
- My laptop's battery is overheating and I need to downloading some software to monitor it (suggested by LearnMMD)
- Check any other software that I've installed between now and when this issue started and see if it's interfering with MMD (suggested by LearnMMD)
- Prepare System Restore in the event I try one of the previous following options (suggested by LearnMMD)
Any sort of help is appreciated, and preferably, the sooner the better...
UPDATE (1/8/19): AutoLuminous still doesn't work, and now I'm getting these additional messages:
(This is present in both Version 9.31 and 9.31x64)