|
Post by rosebud1773 on Dec 7, 2022 12:14:25 GMT -5
I've been using Studio almost since the beginning alongside Blender 2.70 with no problems. I updated my game and grabbed the newest version of Studio available expecting full functionality. First it wouldn't launch without .net for 64bit. Ok, installed that since I'm on a laptop from 2014. Launched Studio without a hitch, thought it was all good. Exported some meshes for a project and opened in Blender. Nothing there but lamps and camera. I've tried a variety of work-arounds and have grown absolutely sick of fighting with it over the last several hours. Some help would be greatly appreciated.
|
|
|
Post by mauvemorn on Dec 7, 2022 13:38:50 GMT -5
|
|
|
Post by rosebud1773 on Dec 8, 2022 8:50:29 GMT -5
Studio and Blender are both 'floating' installations. All permissions are already granted. I made sure of that. Both are already running as admin since the only account on this system is the admin account. Again, I made sure of that. None of the suggests and/or work-arounds have worked. I'm still not able to export meshes with the newest version.
(Star) v3.2.0.3 does not work properly on my system. No meshes are exporting no matter what files, extensions or permissions I alter. I can't be the only one having this issue.
Fortunately, I had yet to delete the compressed folder of the previous version. I have gone back to (Wishes) v3.1.6.3 as it actually works. The unfortunate point here is the game will eventually outdate the app entirely.
|
|
|
Post by mauvemorn on Dec 8, 2022 11:06:25 GMT -5
This is the permission issue but, for whatever reason, your system is extra hostile toward the idea of the new s4s putting a plugin in the blender directory. There is nothing that the developers can do about it, so you’ll have to put it in the appdata yourself. Before I’ll give you the folder, I need to know if you are still using 2.7 or updated to the latest version of blender as well?
|
|
|
Post by rosebud1773 on Jan 13, 2023 18:20:44 GMT -5
I prefer 2.70 & 2.79 as the newest version of blender is more of a learning curve than I've pushed through as of yet. I did attempt to manually put the plugin for the older version of blender into appdata file as one of the work-arounds I mentioned and it didn't work. Maybe I didn't have the correct plugin, I don't know.
|
|
|
Post by mauvemorn on Jan 14, 2023 12:33:12 GMT -5
- download this zip and open it; - go to C:\Users\----\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons. If you do not see Appdata file, enable something like Show hidden; - drag the content of addons.zip into addons; - restart s4s.
|
|
|
Post by rosebud1773 on Jan 21, 2023 22:50:01 GMT -5
Sorry, no dice. It didn't work the first three times I tried this method either. It isn't my antivirus causing the problem. I've already been through it all. Nothing in quarantine, it's all whitelisted, nothing being flagged as virus, spyware or maleware. This version of studio is simply not compatible with my version of Windows 10 apparently or some other component of my laptop. I cannot upgrade to Windows 11. My system doesn't meet the requirements. This sucks because I like studio better than tsr workshop.
Note: For future reference, the _MACOSX file is a native Mac file. On a Windows pc, that file is bad mojo. It'll crash any app that has it in its archives before it even manages to launch. Please be sure that anyone on Windows getting this kind of file from you understands that they cannot put that one in their file archives.
|
|
|
Post by rosebud1773 on Jan 22, 2023 6:55:23 GMT -5
And now I can't use any version of Studio with any version of blender. Returning to a previous version of Studio has produced the exact same results now; no meshes are exporting. This has happened after tossing your files into my archives. Removing them doesn't fix the issue. I will not be recommending Studio to anyone else if this issue isn't resolved soon.
|
|
|
Post by mauvemorn on Jan 22, 2023 12:48:02 GMT -5
S4S is used by thousands of people and none of them are having your exact problem. When s4s exports nothing despite being configured correctly, putting the plugin in appdata always fixes it. I have never had any problems with s4s on windows 10 because I know how to install and configure it correctly. So is this a problem with how s4s is written? And the folder I shared would not prevent s4s from exporting in the previously compatible versions of blender if the path leads to them, that is not how things work. Also, I took it from my Appdata and I have windows 10, so do not worry about that Mac folder, s4s puts it there itself and it causes no problems ( deleting it will also cause no problems, so you can do that). What i forgot, though, was that i had other addons that you do not need in it, so i updated the file How to install Sims 4 Studio correctly and avoid problems ( the answer for everybody who might find this post): - delete any previously installed version of s4s from your computer if you had any; - download the latest beta version for your system, does not matter .zip or installer. If you have the D drive, install it there instead of the C drive. Do not install it in \Documents\Sims 4 Studio (serves a different purpose) or in The sims 4 game files; - if you prefer to use Blender 3+, check what is the latest supported version on s4s download page. If you prefer to use 2.7x, download the version that s4s developers deem the most reliable and recommend on s4s download page, which is 2.76. Contrary to what CAS tutorials tell you, one does not need 2.7 to rig and vertex paint meshes and 2.79’s principled BSDF is not better than the previously used nodes ( it just has all the settings in one node and most of them are useless for cc making), so 2.76 is enough. Again, install on the D drive if possible; - open s4s and change the path to blender.exe in the installation folder of it; - if you will still encounter problems, there are two alternatives to s4s for you to use instead
|
|
|
Post by rosebud1773 on Jan 22, 2023 19:24:22 GMT -5
First off, I'm not trying to be a shrew. I've had an exceptionally bad day today and that very likely colored my complaint earlier. I've been installing/updating these programs and using them for a number of years now. As a matter of fact, I'm part of a blender help desk on discord because I have better than fifteen years experience with blender. I've got more than twenty years experience with computers in general. If I'm telling you this solution isn't working, then trust me, it isn't working. So... if you don't mind, let's try to be civil, rational adults here and sort this out reasonably. I'm not the only one having this problem. There are enough people on my help desk having the same problem that the main modderator set up a channel specifically for Sims4Studio support. Some of them have been using studio only to create recolors and that works well enough for them. There are others who are just starting out in their meshing journey and have found they cannot export the meshes they want to tinker with. They're currently waiting for some kind of solution as well. Most of them won't ask here because they either haven't gotten a response at all or they've gotten solutions that just don't work. With that being said, please, let's try to sort this problem out. This is clearly not a problem completely isolated to me and my computer only. Obviously, I've gone through the instructions to the letter repeatedly. That's not the solution because that's not the problem. I've also made sure my antivirus isn't blocking it. I've added the files you sent and that did, in fact, result in the older version of studio producing files with no meshes. Dialing my version of blender back to 2.76 produced the exact same results. There's no mesh, no rig, not a single pixel or vertex. The only things in the scene are the camera and four lamps. This is a problem and it isn't going to resolve itself. Dialing the program itself back to a previous version produces the exact same results now as well. Just because it works on your Windows 10 system, doesn't mean it's going to be universal. Older computers, such as mine, may have older components and possibly different config file setups. I'm on a 2014 Acer laptop. This is the result I'm having with every single version of blender and studio now. You can imagine how frustrating this is. photos.google.com/search/_tra_/photo/AF1QipN7GIWA4wJdjjMfuStB2NASbnUrtE2zxEYjpQ-s
|
|
|
Post by mauvemorn on Jan 23, 2023 3:25:47 GMT -5
One last thing to try: -delete sims 4 studio folder from \documents\, then restart s4s, specify new paths, and let it re-index
If s4s and blender are installed on the d drive, s4s has no problem putting a plugin in all needed directories. If s4s and blender are installed on the c drive, the system doesn’t allow s4s to put a plugin in the blender installation folder and it does not appear in AppData\Roaming\Blender Foundation\Blender\(the version of blender)\scripts\addons Giving s4s explicit permission to do everything and repeating the process generally fixes this issue. If it doesn’t, manually putting the plugin in the appdata does. Is there anything you, as s4s developers, can do to prevent the system from viewing s4s actions as a threat and stopping it from doing what it needs to? In the op’s case, after putting the plugin in one version of blender in appdata, s4s stopped supporting previously supported versions. This makes no sense since those folders are not tied together in any way and can be modified individually or straight up deleted. Do you know what else could have possibly caused this?
|
|
|
Post by rosebud1773 on Jan 23, 2023 7:54:15 GMT -5
photos.google.com/search/_tra_/photo/AF1QipOQPbF906Hc1zbr6I-075IQvnZOMcfcCaK0Wzo1This is a clean installation on a completely different system (still an older system and an HP). It's never had any version of blender or studio installed. I was hoping to snitch the AppData file from it if the mesh had been exported properly. As you can see, the same issue persists. It's not isolated to one computer. I'm currently at a loss and so is my husband. We've both tried to sort this out. He says he's tempted to tear the program itself apart and find the coding error causing this. He simply doesn't have the time to do so currently. I will attempt giving permissions on this system again later. Repeating the same processes over and over continues to produce the same results, but we'll see if something changes. At this point in time, however, Studio is a complete bust for me and I'm not happy with that. No other program out there does what Studio does.
|
|
|
Post by mauvemorn on Jan 23, 2023 11:44:35 GMT -5
Both links give errors, could you upload them on Imgur?
|
|
|
Post by rosebud1773 on Jan 23, 2023 12:15:01 GMT -5
|
|
|
Post by rosebud1773 on Jan 25, 2023 7:35:29 GMT -5
And here's what happens when I try to import. I do not have a D-drive. I'm on a laptop. C-drive is all I have. So installing in D-drive is not an option. I'm not a programmer, but this looks like a script error to me. So this has become an Export and an Import issue.
(I've been scrolling through the other complaints of similar issues. This is not an isolated event.)
The Sims 4 Studio - Version 3.2.0.3 System.AggregateException: One or more errors occurred. (Could not find file 'C:\ProgramData\S4Studio\Scripts\1828f7da-2a69-4428-848d-a5d315d64964\s4s.out.mlod'.) ---> System.IO.FileNotFoundException: Could not find file 'C:\ProgramData\S4Studio\Scripts\1828f7da-2a69-4428-848d-a5d315d64964\s4s.out.mlod'. File name: 'C:\ProgramData\S4Studio\Scripts\1828f7da-2a69-4428-848d-a5d315d64964\s4s.out.mlod' at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.File.OpenRead(String path) at S4Studio.ViewModels.ObjectLodItem.ImportMesh(BlenderUtilities blender_util, String blender_path) at S4Studio.ViewModels.ObjectLodItem.<>c__DisplayClass46_0.<ImportMesh>b__0() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.<>c.<.cctor>b__272_0(Object obj) at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of inner exception stack trace ---
|
|