|
|
Post by c2oh25n3o on Jul 24, 2024 6:48:29 GMT -5
It's me again 😭 I'm trying to make a custom baby changing table model. I took the end table from Horse Ranch as base, adjusted it a little bit, appended the mesh to the changing table from Growing together, moved the slots slightly and edited shadows. Removed old main (s4studio_mesh_0) mesh vertices and merged in the new ones. But when I tried importing that in S4S, it said 'No meshes found'. I've checked the cut numbers, they are all fine. Today I tried again - this time I didn't delete all old vertices and merged them into my appended mesh (s4studio_mesh_0.001) and renamed it to proper name, and now I just get an error. Whenever I import I also get new rig.001 and bone_bone_shape.001 layers - when I make things for CAS I usually delete them but I don't know if I should do the same here, it's kinda confusing to me. I don't understand how to make a new model for an object that has some rigs/animations/etc bound to it and not get errors when I import it and make it work properly. Could anyone please help me figure out what I'm doing wrong? The folder with all files and error txt is here simfileshare.net/folder/223505/Ty in advance! |
|
|
|
Post by mauvemorn on Jul 24, 2024 9:23:53 GMT -5
Hi. I dont really see anything wrong with the file ( did you switch versions of blender in the process?) but remaking it works, so try this: - open the package, export the blend, open; - delete all 3 meshgroups, append all 3 from your blend, save, re-import
yes, you delete rig.001 and bone_bone_shape thing
also, unrelated, but this object is not meant to have vertex paint, so delete the attribute
|
|
|
|
Post by c2oh25n3o on Jul 24, 2024 12:26:49 GMT -5
I personally didn't switch anything, but found out that in s4s I had Blender 3.6 set instead of 4.0 that I use so I switched to 4.0 now But now I get this when inporting  Can it have something to do with geometry states of the object (there are 2) or it's only because or Blender/s4s problems? Should I switch back to 3.6? I also tried importing the original Horse Ranch end table mesh and it does work. But my mesh doesn't for some reason! And yes, ty, will remove the attribute! |
|
|
|
Post by c2oh25n3o on Jul 24, 2024 16:44:14 GMT -5
Oh gosh, this was an issue with a couple vertices.  This area was causing the problem for some reason, I've been sitting there for an hour applying mesh pieces little by little, and once I removed this cut it finally imported without any errors. Not sure what exactly is wrong with it though, but at least the issue is fixed (for now) 😅 |
|
|
|
Post by mauvemorn on Jul 24, 2024 17:10:25 GMT -5
Each version of blender has a separate installation folder. When you switch to a new one, you must change Blender path in s4s settings so that s4s can put a plugin there. Then you need to open your file there, check the cut(s) and save.
This was not the problem, i was able to import the blend without changing the mesh in any way. You most likely just re-saved in a version that has a plugin.
|
|
|
|
Post by c2oh25n3o on Jul 24, 2024 18:14:08 GMT -5
I don't understand how to fix it properly then :( So I was able to import the first geometry state mesh only after I removed those vertices (I didn't even remake anything, was just having Blender and s4s open side to side and kept saving and trying to import), at least what I thought, and now as I'm doing the second geometry state ('Default') I have an error showing up once again. This time I'm trying to add a new mesh piece to the main object and when I merge them and try to import, I get an error as on my last screenshot. I don't understand what's going on, I've switched to Blender 4.0 in s4s settings and using Blender 4.0, and exported new meshes from packages already using Blender 4.0 I've uploaded new files to the same folder simfileshare.net/folder/223505/ |
|
|
|
Post by mauvemorn on Jul 25, 2024 5:11:20 GMT -5
I can import this file, meaning the problem is not related to the blend itself:
- make sure you have the latest version of s4s;
- may as well get blender 4.1;
- open s4s settings, click on ... next to blender path and navigate to blender.exe in blender 4.1 installation folder;
- open the package with the table, select the second geostate, export the blend, open;
- delete all meshgroups, append all 4 from your blend;
- select bow for s4studio_mesh_0, rename the uv map to uv_0, assign to transformBone;
- join bow for s4studio_mesh_0 and s4studio_mesh_0, make sure the cut is at 0, delete uv_1;
- save, import back
|
|
|
|
Post by c2oh25n3o on Jul 25, 2024 7:39:31 GMT -5
Updated to the last s4s version and switched to Blender 4.1 and it worked!! Thank you so so much for your help as always ✨ Just one more little question: Are these lines I get on some of my cc (in s4s and in game) normal or it's a sign I've done something wrong?  |
|
|
|
Post by mauvemorn on Jul 25, 2024 11:13:32 GMT -5
|
|
|
|
Post by c2oh25n3o on Jul 25, 2024 13:57:26 GMT -5
I think I checked the versions compatibility but yep I should have definitely updated everything earlier  Also I'm SO sorry to annoy you again, I don't know to adjust the size of this green thing. I thought it was a footprint and used 'Adjust footprint size to fit mesh' for all geometry states but that doesn't fix the issue for some reason, is it related to something else? (If I should make a separate thread for this please let me know)  |
|
|
|
Post by mauvemorn on Jul 25, 2024 14:48:55 GMT -5
Adjust footprint size to fit mesh should have fixed it.
Maybe you have some geometry (loose vertices, edges, faces) over there? Try checking in blender
select everything in edit mode and then view -frame selected (or something like this), if it does not focus on the table, then something is over there
|
|
|
|
Post by c2oh25n3o on Jul 26, 2024 20:45:27 GMT -5
Checked the way you mentioned and nothing was there 😄 There were some objects next to the table before, that I imported in a package when tested stuff - I removed them later, but for some reason the footprint got stuck. But I've just created a new package and the footprint was normal over there, so it's fine now. Thank you so much for the help and all advice!  |
|
