Quote:
Originally Posted by ETR3(SS)
I've come across an odd error while using JSGME in conjunction with S3D. This error has occurred since the V2.3 update of JSGME. What's happening is when I open a file using S3D to work on a mod, and then attempt to enable/disable the mod via S3D, JSGME attempts to make a new MODS folder in the S3D root folder. If I open JSGME before opening S3D, it works fine. I'm also posting this in the S3D thread as well.
|
Yes, I suspect this will be the experience for anyone using S3D with JSGME v2.3.0.
I can hazard a guess as to the cause, but only Skwas will know for sure. I'll wait to hear back from him.