|
|
Post by Pyroclastic on Nov 15, 2022 17:57:10 GMT -5
Using blender 3.3.0. the linked net framework couldn't be installed as my current version is desktoip runtime 6.0.11, linked version is 6.0.9 but I have no idea if it matters.
exporting a mesh from a CC I made with an earlier 32 bit version created a .blend file that did not contain the actual mesh or its rig.
I am not sure if it's the same export error in the other thread, so I'd like to know if I'm doing something wrong or if I have to wait for a fix
|
|
|
|
Post by mauvemorn on Nov 15, 2022 18:07:52 GMT -5
Hi. Show us your s4s settings please
|
|
|
|
Post by Pyroclastic on Nov 15, 2022 18:21:01 GMT -5
|
|
|
|
Post by Pyroclastic on Nov 15, 2022 18:22:28 GMT -5
I also seem to be missing the sims tools in the scene tab
|
|
|
|
Post by mauvemorn on Nov 16, 2022 3:06:50 GMT -5
|
|
|
|
Post by Pyroclastic on Nov 16, 2022 9:06:02 GMT -5
I've tried all of this but no dice, not even on blender 3.3.1 since I saw it was the most used version in successfull posts. Lemme know if you have any more tips, if not I'll just use the latest 32 bit versions until this is fixed thanks for your help anyway though <3 |
|
|
|
Post by mauvemorn on Nov 16, 2022 11:44:58 GMT -5
Double-check that you have the latest version of beta.
This is not a problem on s4s end, otherwise everybody would be having it. There is nothing the developers can do about how your system perceives s4s’s actions, so if you will not be able to fix this manually, you will have to use the 32bit version forever.
Try these things:
1). Try adding s4s to exceptions in your antivirus, including windows defender. Repeat the process of changing the path, exporting new blend, opening it;
2). If you have the d drive, try installing both blender and s4s studio there, then changing paths, and restarting s4s. Clone something again, export, open;
3). Try getting the exact version of network mentioned on s4s download page. Logically this should not change anything but who knows
|
|
|
|
Post by Pyroclastic on Nov 18, 2022 17:16:16 GMT -5
Double-check that you have the latest version of beta. This is not a problem on s4s end, otherwise everybody would be having it. There is nothing the developers can do about how your system perceives s4s’s actions, so if you will not be able to fix this manually, you will have to use the 32bit version forever. Try these things: 1). Try adding s4s to exceptions in your antivirus, including windows defender. Repeat the process of changing the path, exporting new blend, opening it; 2). If you have the d drive, try installing both blender and s4s studio there, then changing paths, and restarting s4s. Clone something again, export, open; 3). Try getting the exact version of network mentioned on s4s download page. Logically this should not change anything but who knows tried all except the d drive since I don't have one and the network version since my other apps require it, including installing 3.3.1 instead of using it as portable, to no avail. I really don't know what else to do |
|
